> And why does identify_xm_ddr() want to see 0 but k9f1g08r0a.c think micron is 0x2c ? That looks a bit suspicious.
The Micron POP used on the Beagleboard xM has no NAND, hence it returns 0. Yeah, this is certainly not obvious from the code :-)
This code is far from bullet-proof, but that could be said of x-load in general!
I'll put a fix patch in my repository and also ping the Beagleboard folks about it.
X-load could use lots of clean-up, but like many others, I tend to think the energy would be better spent in finding a replacement.
> And why does identify_xm_ddr() want to see 0 but k9f1g08r0a.c think micron is 0x2c ? That looks a bit suspicious.
The Micron POP used on the Beagleboard xM has no NAND, hence it returns 0. Yeah, this is certainly not obvious from the code :-)
This code is far from bullet-proof, but that could be said of x-load in general!
I'll put a fix patch in my repository and also ping the Beagleboard folks about it.
X-load could use lots of clean-up, but like many others, I tend to think the energy would be better spent in finding a replacement.