> BTW: I'm currently hacking away to see if I can get a > microblaze system > booting > using a flat device tree... I haven't decided if it's worth it to go > that > route in the end yet, but... > > Steve
I've managed to get the first step working: a microblaze system advertising of_devices in 2.6 using a flat device tree. The next task is to reimplement probe() for a driver or two (probably the xilinx_emac driver first). My plan is to have the driver advertise both through of_platform_bus, and through the regular platform bus, and have a config option that either advertises the devices through of and links in the device tree, or using the exising platform_device mechanism. Grant: Does this make sense (in terms of dealing with drivers) with your plans for moving Virtex platforms to arch/powerpc? I'd like to avoid duplicating work on the drivers, if possible. Is there a concensus on how microblaze systems should get booted? Currently, I'm linking the device tree directly into the kernel itself, loading the whole mess using SystemAce and the start address jumps directly into the kernel, which is quite a bit different than the way powerpc works. It's certainly simpler: maybe too simple. At the same time, replicating the complexity of arch/powerpc with separate boot code may or may not be worth it... Any thoughts? Steve _______________________________________________ Linuxppc-embedded mailing list [email protected] https://ozlabs.org/mailman/listinfo/linuxppc-embedded
