Tony Lindgren had written, on 05/19/2010 08:24 PM, the following:
* Nishanth Menon <nm@xxxxxx> [100519 18:03]:
Tony Lindgren had written, on 05/19/2010 08:06 PM, the following:
* Nishanth Menon <nm@xxxxxx> [100519 17:58]:
Tony Lindgren had written, on 05/19/2010 08:00 PM, the following:
* Nishanth Menon <nm@xxxxxx> [100519 12:56]:
looks like network is still not functional on SDP4430. different issue
Oh so Ethernet does not work either? What's wrong with that?
I was told offline that the driver is somewhere in the net ML on the
way I believe in parallel.. I dont have collaborative links though
:(
Santosh,
Can you point out the status?
I thought I have those in omap-testing and merged into the master
branch in linux-omap:
ks8851: Add caching of CCR register
ks8851: Low level functions for read/write to companion eeprom
ks8851: companion eeprom access through ethtool
Okay then it makes this an operator error - I have been playing with
vanilla linus 2.6.34 tree and adding just the basic patches I need..
I can give the omap-testing a whirl..
OK, cool.
tried with omap_testing i pulled a few mins back, omap3_defconfig with
CONFIG_EARLY_PRINTK enabled
Good news:
need as pointed out by Santosh -
a) http://www.mail-archive.com/linux-omap@xxxxxxxxxxxxxxx/msg27363.html
b) this patch for NFS even to try.
Bad news: Same results I got as in linus tree - NAK for NFS booting :(
full log: http://pastebin.mozilla.org/725960
from the log, I dont see the driver probe even starting up or any
reports as you posted above (which I guess is from Blaze)..
--
Regards,
Nishanth Menon
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
