> Hi Tobias, > > good to see progress in the device tree area. I didn't spend much time > on nubus-pmacs over the last days. Though my plan is to continue on > that > project soon. > > Instead of passing the dtb via a bootloader you may include the device > tree directly into the kernel. There is a special option in the kernel > configuration at least for later kernel versions (e.g. I was using it > starting from 2.6.23.x for a different powerpc-based embedded > project). > It might mean that each kernel is tightly configured for a specific > machine then. > That might be a solution - at least in the miBoot case, which we'd prefer to use as boot loader.
> IMHO the best solution regarding arch=powerpc drivers is to get > started > with so called platform drivers, which fetch all resources (IRQs, > memory > regions, etc.) from the device tree. The actual hardware-drivers > attach > to those drivers later on. > Currently this would mean even more work for me to get the most basic > functionality running. Therefore I will continue to work on arch=ppc > until there is at least a partly working kernel available. > Of course the ultimate goal is to have a recent arch=powerpc based > kernel, which probably has got some of the nasty toolchain-related > issues already resolved. > Well as our hardware is that ancient I don't see any need for the flexibility the platform drivers would bring us (of course it is a much cleaner approach - and therefore desirable). It would be more easy and not less accurate to port the existing drivers that interface directly with the device tree (which are all the built-in devices)- or with the nubus drivers (in that case it would be horrible having to write an OF platform bus driver for the nubus - although very nice, indeed). I'd prefer to use your already ported drivers, then continue with the rest of the drivers. Will we be forced to provide platform drivers in the future? > Can you provide the .dts files please? > All my latest changes are in the linuxppc-2.6-nubus CVS module. The dts file (only PB 1400 until now, more to come) is in "arch/powerpc/ boot/dts", the derived assembler source file is in "arch/powerpc/ appleboot". This appleboot directory and its integration into the kernel build system is a halfway working mess - I'd appreciate if someone could help in that area. > Cheers, > > Florian > > Tobias Netzel schrieb: >> Hi all, >> >> I've been trying to get the kernel with powerpc architecture (until >> now we have been using the now deprecated ppc architecture) to launch >> on my PB 1400. >> Using MkLinux Booter the kernel now launches and the architecture >> setup is done but there still have to be ported the drivers. >> I used dtc (device tree compiler) to compile a flat device tree for >> the PB 1400. which is copied into kernel memory and passed to the >> kernel by the second stage bootloader code that is launched by the >> MkLinux Booter and which decompresses kernel and ramdisk and sets up >> the fake BootX bootinfos. My plan is to compile different device >> trees for all the Performas, PDMs and PowerBooks and have the correct >> one copied and passed to the kernel depending on the Gestalt ID. >> I think I should be able to enhance BootX 1.1.3 to support this, too. >> In order to do the same for the miBoot part I might need CodeWarrior >> 4 because I don't think I'd be able to integrate a PPC compiled code >> fragment into it, what shouldn't be a problem on BootX. >> >> Florian might port his 2.6 work done for the ppc architecture to the >> powerpc architecture. >> Anyone else here who'd like to contribute? >> >> Cheers, >> Tobias >> >> --------------------------------------------------------------------- >> --------- >> _______________________________________________ >> Nubus-pmac-users mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/nubus-pmac-users >> > > > ---------------------------------------------------------------------- > -------- > _______________________________________________ > Nubus-pmac-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/nubus-pmac-users ------------------------------------------------------------------------------ _______________________________________________ Nubus-pmac-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/nubus-pmac-users
