View Single Post
Old 10-07-2012, 07:10 AM   #30
knc1
Going Viral
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
Quote:
Originally Posted by geekmaster View Post
This happens on other ARM devices too, and there is a kernel patch to fix it:
http://docs.openmoko.org/trac/attach...2.6.22.5.patch
Did I not read somewhere in one of these information post dumps that the K5/Kpw was running 2.6.31?

That patch from back in the 2.6.22 days should have made it into the code, although it may not have been optioned in the build configuration.

Hint:
If you have read access to the u-boot environment area, dump the script strings and see how it is setup for network booting.

Those defaults may be the same as the K4/K5 - but might not.
knc1 is offline   Reply With Quote