Re: kernel 2.6.32.46 upgrade

----- Original Message ----- 
From: "Olaf Westrik" <weizen_42-Yz37vSk3/[email protected]>
To: "Gilles Espinasse" <[email protected]>
Cc: "IPCOP devel" <[email protected]>
Sent: Thursday, September 15, 2011 9:02 AM
Subject: Re: [IPCop-devel] kernel 2.6.32.46 upgrade


> On 2011-09-15 07:44, Gilles Espinasse wrote:
> > I have 2.6.32.46 kernel compiled but I am waiting kernel.org emerge from
the
> > maintenance to commit that upgrade.
>
> Please postpone until afer v2.0.0 release, or is there something
> absolutely critical for our use-case?
> As is the number of modifications since 1.9.20 are small and mostly
> already verified and tested. If we again make larger modifications we
> would need another 'release candidate'.
>
I was alerted by recent distrib kernel upgrade (debian and ubuntu), but in
fact they include much more than the changes from 2.6.32.45 to 46.

I look at 2.6.32.46 list of changes at http://lwn.net/Articles/456780/ ,
this is a small list of fix, probably only 5 or 6 may matter for us.
If I recompile with 2.6.32.46 changes applied except futex: Fix regression
with read only mappings,
diff -ur build*/ipcop/boot/System.map-2.6* doc/System.map-2.6.32.45
show no difference.
(doc/System.map-2.6.32.45 is a manual copy of system.map-2.6.32-4 on a
vanilia 1.9.20 build)

With full 2.6.32.46 changes (including futex), System.map is different and
to my understanding, that mean there is an ABI change and we would need to
supply vmlinuz and all modules and 2.6.32-5
I think we could include 2.6.32.46 and revert futex change (will need a
reboot) or stay to 2.6.32.45 and wait for 47 to provide a full kernel
update.

> I only see 1 open point at the moment, the use of size/minsize in
> logrotate config for FLASH installations. For that I'll make a decision
> pretty soon, so 2.0 could go public next week.
>
There is one issue with binutils-2.21. This package is no more vailable for
download like gdb-7.3 (there was some missing sources, package has been
removed and a new 'a' version has been released for 2.21.1 only). So mostly
our only choice is to upgrade to 2.21.1a (the a is only on the tar name,
package open to binutils-2.21.1 directory).

Gilles


------------------------------------------------------------------------------
BlackBerry&reg; DevCon Americas, Oct. 18-20, San Francisco, CA
http://p.sf.net/sfu/rim-devcon-copy2