OpenSUSE kernel news – 21.08.2010

Posted: August 21, 2010 in kernel, OpenSUSE

Hi y’all and welcome to this week’s kernel news! In this week’s edition…

-…John W. Linville posted a pull request for Dave Miller, with the following summary :

“This group of fixes is intended for 2.6.36. This includes a fix for a
warning backtrace related to pm_qos in ipw2100, a packet injection oops
for ath9k_htc, a connectivity regression for ath9k_htc related to HT
capabilities handling, a scanning regression in wl1251,
a firmware loading error in ath9k_htc, and a patch to disable L0s for
all ath5k cards (causes misc wierdness).”
Also, Jason Wessel had a pull request for kgdb targetted at -rc1, with some fixes, apparently nothing big.

-Luis Rodriguez announced compat-wireless for 2.6.36-rc1 :
“Linus released 2.6.36-rc1 over the weekend. We’ve been following the
next kernel’s development cycle through the master branch of both
compat-wireless.git and compat.git. I just created the branch for each
of those git trees for the 2.6.36.y release and put up the first
tarball for testing purposes:

Note that the extra -1 here accounts for the fact that we can have bug
fixes within compat-wireless.git and/or comat.git during one extra
version of the kernel or even during one rc release.You can find the
ChangeLog of what went in to this kernel by reading this:

Please report any issues, remember this is a stable kernel so if there
is a bug it should be reported ASAP.”

-Ryusuke Konishi has a pull request for the nilfs2 tree (2.6.36-rc1) with some bugfixes, one regression fix and a fix for a
kerneloops; Philippe De Muyter proposed a few patches for m68k, including a fix for strace for 68328 and 68360 processors
and a removal of old asm-only flags bitdefs : “Long ago, PT_TRACESYS_OFF and friends were introduced as hard defines
to avoid straight constants in assembler parts of linux m68k.
They are not used anymore, and were not updated to follow changes
in linux kernel. Remove them. When similar constants are needed,
they are now generated using asm-offsets.c.”

-Bobby Crabtree, in a message named “Regulator voltage aggregation” proposed a rather interesting feature , as quoted below :
“I’m looking to upstream a new feature in which the regulator core
aggregates voltage requests from multiple consumers and applies the best
fitting voltage (e.g. max voltage) to a shared supply. The core would
recompute the best fitting voltage when a consumer requests a voltage
change or requests to enable/disable the regulator (similar logic to

The reason we need this feature is for power savings. It would allow two
or more consumers to “vote” on a voltage that’s lower than the normal
operating voltage.

I’ve got a couple implementations in mind.

1. Introduce a new API:

int regulator_set_optimum_voltage(struct regulator *regulator,
int min_uV, int max_uV);

2. Add a flag to the regulation_constraints structure and reuse the
existing regulator_set_voltage API.

struct regulation_constraints {

unsigned aggregate_uV:1;


Does this sound like a reasonable feature? And if so, are there any
preferences as to how the feature is implemented and exposed?”
Following this message is a talk with Mark Brown and Alan Cox, which had some corrections/ideas/improvements
as a result; we’ll see what will come out of this and no doubt, you’ll hear about it here!

-David Miller came up with a pull request with a number of bugfixes regarding the networking tree, Ingo Molnar, in a pull req,
updated the perf tree, containing mostly fixes, Takashi Iwai came up with sound fixes (-rc2), which he described as “small
and local fixes”, Al Viro requested git pulls for the vfs tree (-rc1) and Steven Rostedt added some cleanup code for the tracing tree.

-Jiri Kosina added a number of fixes in a pull request for the HID tree : “The most
important is the memory corruption fix in hiddev, which was caused by Arnd’s
patch that tried to get rid of BKL, but messed up intf private data. It’s verified to fix various bug
reports (warnings from kobject core code, suspend-resume failures, etc).

Apart from that, a few minor fixes in picolcd driver and a device ID
addition.”; Trond Myklebust had some minor changes to the NFS tree (client part) and Stephen Boyd proposed
a patch for fixing the udelay() issue on ARM. As written by Stephen, the problem was “some SMP
machines can scale their CPU frequencies independent of one
another. loops_per_jiffy is calibrated globally and used in
__const_udelay(). If one CPU is running faster than what the
loops_per_jiffy is calculated (or scaled) for, udelay() will
be incorrect and not wait long enough (or too long). A similar
problem occurs if the cpu frequency is scaled during a udelay()
call.”; he also proposed re-writing udelay and gang in C instead of asm, thus making it easier to work on. For
the complete list of propositions and fixes , read the corresponding post on lkml.

-Other minor fixes by means of pull requests : Ingo Molnar – perf,
Frederic Weisbecker – perf also (in Ingo’s attention :), Joel Becker – ocfs2 (2.6.36),
John W. Linville – wireless, David Miller – sparc (fixes for, among others, some
rwsem issue and addition of entries for the new 2.6.36 syscalls) and
Paul Mundt with sh updates (-rc2) .

-Mathieu Desnoyers announced the release of LTTng 0.222 for :
“It includes a fixup to follow changes introduces to splice.c in, where
the checks for seekable files changed subtly. Eventually I’ll have to implement
a proper seek rather than dealing with this at the lttng splice actor level, but
for now just setting the extra fmode flags works upon open works well.”
and Junio C. Hamano announced git, containing minor bugfixes and
documentation updates.

-Mathieu Desnoyers announced LTTng 0.223 and 0.224 (!) with really nothing interest-worthy to put here :).
and Greg Kroah-Hartman announced kernels,,, and

And that’s it, fellows and gals! Enjoy your weekend and keep reading the OpenSUSE Weekly!


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s