Devel Digest, Vol 32, Issue 13

Mitch Bradley wmb at
Sun Oct 5 00:29:47 EDT 2008

rihoward1 at wrote:
> Mitch,
> Are there any other tests you would like me to run with q2e19?

This might be a lot to ask, because it can be pretty tedious to test, 
but since you offered ... :-)

The "Handle ramdisk location changes required by new Linux kernels" 
change is potentially disruptive, so it could use more testing.  
Specifically, it would be good to test booting from several different 
kernels, both in the 2.6.22 series and the 2.6.25 series , in both 
secure and non-secure modes.

I tried 2.6.25-whatever from os 759 in non secure mod, 2.6.25-whatever 
from OS 703 in secure and non-secure, and a custom 2.6.22 kernel in 
non-secure.  Other data points would be most welcome.

You could also try out the multicast nand update thing if you are really 
eager. tells how.

> I have successfully connected to a linksys wrt54gL and used chat
> for a chat session of an hour or 2 duration so the network interface 
> seems to be working.
> /Robert H.
> On Oct 4, 2008, at 7:23 PM, Mitch Bradley wrote:
>>> Is q2e19 going to be included in the 8.2 release?
>>> The reason I ask is that trac 8451, test-all crash after the touchpad
>>> test,  found in q2e18 is very disconcerting.
>> q2e19 is a quick-turn release (half-day turnaround from head's up to
>> release) for a pre-build of a limited run of machines with a new
>> keyboard controller.  It has new and barely-tested EC code plus a
>> barely-tested change to the keyboard driver.  It might not survive the
>> weekend before e20 is issued.  The mouse test problem that you found is
>> likely to be e19's demise.  It's possible that the problem could affect
>> the keyboard in some cases.
>> I have determined that the mouse test problem is caused by some device -
>> either the EC or the touchpad - returning a "RESEND" code instead of an
>> "ACK" in response to the first "IDENTIFY" request.  I have never seen
>> that happen before.  It doesn't happen all the time; a lot of the time
>> it works.  I'm working on a fix.
>> _______________________________________________
>> Devel mailing list
>> Devel at

More information about the Devel mailing list