Greetings.
The following is a submission to reduce the number of files that will
be installed when one wants to compile kernel modules, offering
saving both in time and space. Disks are touted as cheap, but let's
face it, spending ~340 MB for kernel sources means you have 340 less
for your personal files. The time savings should be obvious too: less
files to install, and also less files to index — locatedb, quota,
beagle/etc., you name it. This is especially beneficial for
developers and OBS or OBS-like instances where packages are not only
built in random order(*), but where the chroots are usually torn down
everytime.
(*) Calling build locally and manually, without --clean, and with the
same buildroot everytime would allow for a time optimization when
all KMPs are built after another, as big packages like kernel-* would
not have to be reinstalled/deleted everytime.
With this patch(set) — there is a bit of cleanup upfront —, the
"kernel-devel" package is introduced which contains all (and only)
the necessary files to support external module building. The entire
source for personal recompilation orgies is moved out to
"kernel-source", which now behaves like "kernel-source-vanilla"
already did.
The standalone sources' (kernel-source) path has been changed so as
to not overlap with those used for module building, because people
always trash their KMP build environment for the shipped kernel when
they ran cloneconfig.
Another desired side-effect of the so-codified separation into
the kernel-devel package is that dangerous calls that would cause
above-mentioned trashing are now completely inhibited.
This modification has been tested with various kinds of free and
non-free packages and kernel versions already. The latter is
especially important because they are the most likely ones to
break because of their awkward-to-horrid Makefiles. These have been
made available for a long time already at jftp.medozas.de; the list
includes at least:
fglrx-kmp-default-8.681~2.6.31.11~jen93-jen0.x86_64.rpm
ndiswrapper-kmp-default-1.55~2.6.31.11~jen93-3.4.jen2.x86_64.rpm
nvidiagfx-kmp-default-190.53~2.6.31.11~jen93-jen8.x86_64.rpm
nvidiagfx-legacy173-kmp-default-173.14.22~2.6.31.11~jen93-jen8.x86_64.rpm
nvidiagfx-legacy71-kmp-default-71.86.11~2.6.31.11~jen93-jen8.x86_64.rpm
nvidiagfx-legacy96-kmp-default-96.43.14~2.6.31.11~jen93-jen8.x86_64.rpm
ttyrpld-kmp-default-2.60~2.6.31.11~jen93-jen4.x86_64.rpm
virtualbox-modules-kmp-default-3.1.2_56127~2.6.31.12~jen93-jen0.x86_64.rpm
vmware-modules-kmp-default-6.5.3~185404~2.6.31.12~jen93-jen3.x86_64.rpm
xtables-addons-kmp-default-1.22~2.6.31.12~jen93-jen0.x86_64.rpm
It was also tested with 2.6.32 and — since somebody decided out of
the blue to rebase last week :-) — just now with .33-rc6 too.
The resulting kernel-devel package is 10x smaller in installed size
and has roughly 3x fewer files.
The following changes since commit 69aad1a30e31d4f33ab56a1f195c7c4229c9dd66:
Nikanth Karthikesan (1):
- patches.fixes/dm-stripe-zero-stripes: dm-stripe: return -EINVAL if stripe count is zero (bnc#576312).
are available in the git repository at:
git://dev.medozas.de/suse-kernel less-source
Jan Engelhardt (3):
misc: use proper tar options
kernel-source: use more macros
kernel-source: split devel files and full-source
doc/README.SUSE | 4 +-
kernel-source.changes | 7 +++++
rpm/compute-PATCHVERSION.sh | 2 +-
rpm/group-source-files | 33 +++++++++++++++++++++++++
rpm/kernel-binary.spec.in | 12 ++++----
rpm/kernel-source.spec.in | 56 +++++++++++++++++++++++++++++++++++++++----
rpm/kernel-syms.spec.in | 4 +-
scripts/tar-up.sh | 2 +-
8 files changed, 103 insertions(+), 17 deletions(-)
create mode 100755 rpm/group-source-files
--
To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org
This patch is in mainline under the listed commit, and has been applied
to the 2.6.32 stable tree. If possible, it should be included in the
2.6.31 kernel of openSUSE 11.2.
Thanks,
Larry Finger
---
commit b6c3f5be7c6ac3375f44de4545c1ffe216b34022
Author: Larry Finger <Larry.Finger(a)lwfinger.net>
Date: Tue Feb 2 10:08:19 2010 -0600
b43: Fix throughput regression
Commit c7ab5ef9bcd281135c21b4732c9be779585181be entitled "b43: implement
short slot and basic rate handling" reduced the transmit throughput for
my BCM4311 device from 18 Mb/s to 0.7 Mb/s. The basic rate handling
portion is OK, the problem is in the short slot handling.
Prior to this change, the short slot enable/disable routines were never
called. Experimentation showed that the critical part was changing the
value at offset 0x0010 in the shared memory. This is supposed to contain
the 802.11 Slot Time in usec, but if it is changed from its initial value
of zero, performance is destroyed. On the other hand, changing the value
in the MMIO register corresponding to the Interframe Slot Time increased
performance from 18 to 22 Mb/s. A BCM4306/3 also shows dramatic
improvement of the transmit rate from 5.3 to 19.0 Mb/s.
Other changes in the patch include removal of the magic number for the
MMIO register, and allowing the slot time to be set for any PHY operating
in the 2.4 GHz band. Previously, the routine was executed only for G PHYs.
Signed-off-by: Larry Finger <Larry.Finger(a)lwfinger.net>
Cc: Stable <stable(a)kernel.org> [Any stable version back through 2.6.28]
Signed-off-by: John W. Linville <linville(a)tuxdriver.com>
diff --git a/drivers/net/wireless/b43/b43.h b/drivers/net/wireless/b43/b43.h
index fe3bf94..c484cc2 100644
--- a/drivers/net/wireless/b43/b43.h
+++ b/drivers/net/wireless/b43/b43.h
@@ -115,6 +115,7 @@
#define B43_MMIO_TSF_2 0x636 /* core rev < 3 only */
#define B43_MMIO_TSF_3 0x638 /* core rev < 3 only */
#define B43_MMIO_RNG 0x65A
+#define B43_MMIO_IFSSLOT 0x684 /* Interframe slot time */
#define B43_MMIO_IFSCTL 0x688 /* Interframe space control */
#define B43_MMIO_IFSCTL_USE_EDCF 0x0004
#define B43_MMIO_POWERUP_DELAY 0x6A8
diff --git a/drivers/net/wireless/b43/main.c b/drivers/net/wireless/b43/main.c
index 19b4eae..fcbf0e2 100644
--- a/drivers/net/wireless/b43/main.c
+++ b/drivers/net/wireless/b43/main.c
@@ -628,10 +628,17 @@ static void b43_upload_card_macaddress(struct b43_wldev *dev)
static void b43_set_slot_time(struct b43_wldev *dev, u16 slot_time)
{
/* slot_time is in usec. */
- if (dev->phy.type != B43_PHYTYPE_G)
+ /* This test used to exit for all but a G PHY. */
+ if (b43_current_band(dev->wl) == IEEE80211_BAND_5GHZ)
return;
- b43_write16(dev, 0x684, 510 + slot_time);
- b43_shm_write16(dev, B43_SHM_SHARED, 0x0010, slot_time);
+ b43_write16(dev, B43_MMIO_IFSSLOT, 510 + slot_time);
+ /* Shared memory location 0x0010 is the slot time and should be
+ * set to slot_time; however, this register is initially 0 and changing
+ * the value adversely affects the transmit rate for BCM4311
+ * devices. Until this behavior is unterstood, delete this step
+ *
+ * b43_shm_write16(dev, B43_SHM_SHARED, 0x0010, slot_time);
+ */
}
static void b43_short_slot_timing_enable(struct b43_wldev *dev)
--
To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org
The current kernel in openSUSE Factory (rc7 based) does not boot on my laptop,
it fails very early in the boot sequence.
Updating to kernel head instead works for me. I propose to submit a new
kernel to openSUSE:Factory asap.
FYI: I see Kernel panic: Fatal exception in interrupt - and the rest is
scrolled out of the screen and therefore not readable.
This is on my Thinkpad x86-64 laptop with kernel-desktop,
Andreas
--
Andreas Jaeger, Program Manager openSUSE, aj(a){novell.com,opensuse.org}
Twitter: jaegerandi | Identica: jaegerandi
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
Maxfeldstr. 5, 90409 Nürnberg, Germany
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
All,
I just joined this list and I'm not sure it is the right place to post
the question, so please point me in the right direction if this is
wrong.
I am working with a kernel project that does not yet any code in mainline.
The kernel portion of the project has two major components, a ext4
patch (series) and a new module. I already have the new module in the
OBS as a KPM.
If feasible I'd like to use the OBS to publish a ext4 KMP package that
replaces the default one for users that want to try out our new kernel
module.
Is that a simple possibility, or complex.
Thanks
Greg
--
Greg Freemyer
Head of EDD Tape Extraction and Processing team
Litigation Triage Solutions Specialist
http://www.linkedin.com/in/gregfreemyer
Preservation and Forensic processing of Exchange Repositories White Paper -
<http://www.norcrossgroup.com/forms/whitepapers/tng_whitepaper_fpe.html>
The Norcross Group
The Intersection of Evidence & Technology
http://www.norcrossgroup.com
--
To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org
This should be fixed now in kernel-git.
Jan
>>> Michal Marek <mmarek(a)suse.cz> 23.02.10 10:16 >>>
On 23.2.2010 10:00, Andreas Jaeger wrote:
> The current kernel in openSUSE Factory (rc7 based) does not boot on my laptop,
> it fails very early in the boot sequence.
>
> Updating to kernel head instead works for me. I propose to submit a new
> kernel to openSUSE:Factory asap.
Current kernel-xen fails to build on Factory :(
/usr/src/packages/BUILD/kernel-xen-2.6.33/linux-2.6.32/drivers/xen/netfront/netfront.h:179:26:
error: variably modified 'tx_skbs' at file scope
/usr/src/packages/BUILD/kernel-xen-2.6.33/linux-2.6.32/drivers/xen/netfront/netfront.h:180:26:
error: variably modified 'rx_skbs' at file scope
/usr/src/packages/BUILD/kernel-xen-2.6.33/linux-2.6.32/drivers/xen/netfront/netfront.h:184:27:
error: variably modified 'grant_tx_ref' at file scope
/usr/src/packages/BUILD/kernel-xen-2.6.33/linux-2.6.32/drivers/xen/netfront/netfront.h:186:27:
error: variably modified 'grant_rx_ref' at file scope
/usr/src/packages/BUILD/kernel-xen-2.6.33/linux-2.6.32/drivers/xen/netfront/netfront.h:193:29:
error: variably modified 'rx_pfn_array' at file scope
/usr/src/packages/BUILD/kernel-xen-2.6.33/linux-2.6.32/drivers/xen/netfront/netfront.h:194:32:
error: variably modified 'rx_mcl' at file scope
/usr/src/packages/BUILD/kernel-xen-2.6.33/linux-2.6.32/drivers/xen/netfront/netfront.h:195:27:
error: variably modified 'rx_mmu' at file scope
(https://build.opensuse.org/package/live_build_log?arch=x86_64&package=kerne…).
Michal
--
To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org
--
To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello,
I was wondering why have there been no updates to the gitorious
clone of the opensuse kernel-source repository [1] in the last two
weeks. The last change was on Jan 12. As the KOTD kernel [2] has been
changing since then almost every day I don't suppose there have been no
commits.
Thanks.
[1] http://gitorious.org/opensuse/kernel-source
[2] http://ftp.suse.com/pub/projects/kernel/kotd/master/
- --
Kshitij Kulshreshtha
Institut für Mathematik,
Fakultät Math. Nat. II,
Humboldt-Universität zu Berlin,
Raum 2.022,
Rudower Chaussee 25,
12489 Berlin.
Sterndamm 62,
12487 Berlin.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.12 (GNU/Linux)
iQEcBAEBAgAGBQJLXZ6SAAoJEDWYtU3xIcMouY4H/jczoUADKzPEPLpa2cdRpExp
7riBH93h9xBEHEmUkFAPIXlNX5Yw/To0OLXu7r5OGQcL8EspSK6Rfb7BcfhNBn/4
LqicHX7b1Pjul9RPOWj2ElXIWBJ6NGvd/hFTlx30pfZNOHqnUBBuFwXUcX6q+/uI
oztzcMl/RyH4LFjea9Lx57UWvcop5LRY2kKXgJd8yF+JvDee6EaPedKRIPN4s6tX
U4LXQ/gdcawXBxCnWDJOlKe2ipHtrR7qc6RYfv1IHJVYlaUtiYJfZwBH+LYTRNaO
q7V+1pB9yovC7SV1UBGzjZWJZ3z0W7wYFAHcykzg5zhVJXuZhKjte+pxL5Vqb5I=
=84J2
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org
Hello Mates,
excuse me please for disturbing you.
ATM in Kernel 2.6.31.12-0.1-desktop i can't mount an external webdav
Folder. My boot.msg says:
<3>[ 0.280957] tmpfs: No value for mount option 'mode'
<6>[ 0.280957] devtmpfs: initialized
I think it is maybe like:
https://bugzilla.novell.com/show_bug.cgi?id=578064
Do you know, when this is fixed?
Have a nice day...
--
Sincerely yours
Sascha Manns
openSUSE Community & Support Agent
openSUSE Marketing Team
Blog: http://saigkill.wordpress.com
Web: http://www.open-slx.de (openSUSE Box Support German)
Web: http://www.open-slx.com (openSUSE Box Support English)
--
To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org
Hi,
On Tue, 23 Feb 2010, Richard Guenther wrote:
> On Tue, 23 Feb 2010, Jan Beulich wrote:
>
> > >>> Richard Guenther <rguenther(a)suse.de> 23.02.10 15:35 >>>
> > >So that's a more convincing example to at least get consistency
> > >here. I'll open a bug, but please fix the kernel to use offsetof.
> >
> > Yeah, I meanwhile got confirmation that this is going to be accepted
> > upstream.
>
> Hm, but it is all fine according to 6.6 and 6.7.5.2 - the fine
> reading differencing between integer constant expression and
> constant initializer.
Array sizes must be integer constant expression for the type to not be
variably modified. All evaluated casts in integer constant expressions
must convert arithmetic types to integer types. Pointer types are no
arithmetic types. That's the catch which renders the whole thing invalid.
Additionally (to Jan) 6.6/10 gives leeway only to accept other forms of
constant expressions. Integer constant expressions are completely
specified and are the ones that must be used in array lengths to make it
not variably modified.
Regarding the wish to not have to use stddef.h: that's premature. Even a
freestanding conforming implementation (which means one that doesn't
provide a full C library, exactly something that the kernel wants) is
required to provide the <stddef.h> header. The kernel can make use of it,
and probably is better off actually doing this, as ptrdiff_t, size_t and
offsetof _are_ compiler specific. Unless the kernel wants to provide
its own definitions for each compiler it wants to support, it better use
the header that's designed for that.
Ciao,
Michael.
--
To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org
>>> Richard Guenther <rguenther(a)suse.de> 23.02.10 15:51 >>>
>Hm, but it is all fine according to 6.6 and 6.7.5.2 - the fine
>reading differencing between integer constant expression and
>constant initializer.
But the part talking about the size expression of an array declaration
specifically says "integer constant expression". So I think I can still
only refer to "An implementation may accept other forms of constant
expressions" being taken to support the construct in question by
the majority of (or all?) compilers.
Jan
--
To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org
>>> Richard Guenther <rguenther(a)suse.de> 23.02.10 15:35 >>>
>So that's a more convincing example to at least get consistency
>here. I'll open a bug, but please fix the kernel to use offsetof.
Yeah, I meanwhile got confirmation that this is going to be accepted
upstream.
Jan
--
To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org