[oe] Updating kernels to latest stable versions

[Marcin Juszkiewicz]

Dnia środa, 21 października 2009 o 14:20:33 Marcin Juszkiewicz napisał(a

> I did a check for applying all patches for those machines (they alter
> SRC_URI):
> 
> 2.6.18 - at91sam9263ek
> 2.6.19 - at91sam9263ek
> 2.6.20 - n2100, at91sam9263ek
> 2.6.21 - simpad, kb9202, at91sam9263ek, sarge-at91, gumstix-verdex (FAIL),
>  gumstix-connex (FAIL) 
> 2.6.22 - cm-x270, bd-neon
> 2.6.23 - em-x270, cm-x270, mpc8313e-rdb, mpc8323e-rdb
> 2.6.24 - simpad, gesbc-9302, mpc8313e-rdb, cm-x270, ts72xx (FAIL), oxnas
>  (FAIL), hipox (FAIL) 
> 2.6.25 - mpc8313e-rdb, cm-x270, at32stk1000 (FAIL on
>  fetching), at91-l9260, m8050 
> 2.6.26 - boc01, mpc8313e-rdb, topas910
> 2.6.27 - boc01, progear, simpad
> 2.6.28 - at91sam9263ek, ronetix-pm9263, stb225, collie, tosa, gamecube,
>  tx27 FAIL 
> 2.6.29 - boc01, canyonlands, micro2440 FAIL, tosa, ep93xx,
>  cm-x270, stamp9g20evb 
> 2.6.30 - mpc8315e-rdb, at91sam9263ek
> 2.6.31 - boc01, ep93xx
> 
> So this changeset breaks few devices at patch level:
> gumstix-verdex/connex in 2.6.21, ts72xx/oxnas/hipox in 2.6.24,
> tx27 in 2.6.28 and micro2440 in 2.6.29.
> 
> at32stk1000 patch was not available for fetching.

Did someone who maintain any of failed devices took a look at it?

Regards, 
-- 
JID:      hrw at jabber.org
Website:  http://marcin.juszkiewicz.com.pl/
LinkedIn: http://www.linkedin.com/in/marcinjuszkiewicz