Guillaume Gardet wrote:
Le 23/09/2014 09:54, Dirk Müller a écrit :
But if I don't load the fdt file (bcm2835-rpi-b.dtb - what is that anyway?), I get all the way to the network: the fdt file is the device tree, its a binary blob that should exactly describe the hardware. This is used to avoid the kernel having to guess about the hardware (as sometimes probing is not possible on ARM hardware due to lack of standardization). The obvious question for me is whether you actually use a Raspberry Pi - Type B board. It looks like the device tree is not actually matching your hardware.
if it boots without it - we might consider building an image without the device tree, since I find it actually surprising that it works without device tree.
I think you can use 2 kernel images for RPi:
- upstream kernel which need a device tree
- downstream kernel which still uses a *.c source file to describe the board and not a device tree.
I thought I fixed that in my last JeOS commit (with the partition problem fix).
Thanks for filling me in on the fdt files. I do have a RPi Model B revision 2 board (not the B+). This board works with the 13.1 JeOS images (build 38.14). I didn't see a fdt file there, which lead me to the experiment earlier. But then it hangs when loading the network module, so it doesn't quite work with auto detection. I'm not sure what the problem is, but I'm happy to keep testing. -Alex -- To unsubscribe, e-mail: firstname.lastname@example.org To contact the owner, e-mail: email@example.com