Josh Boyer wrote: >> arch/boot/simple/embed_config.c jusst seems to be a random collection >> of board specific code anyway. >> A giant case statement implimented with #ifdef's. It is just >> screaming to be done some better way.
>> >> You mean like a device tree? ;) >> >> josh >> Maybe, I am waiting to see somebody move something to device tree so that I can get a better grasp of what it is and how it works. From what little I know I think it is going to be very significant for my BSP - we are trying to use a single binary for alot of different boards, or the same board with different firmware. From what I am gathering I can have the loader pass a device tree to the kernel and the device tree will basically describe the hardware to the kernel. Only at the moment I don't have the time to learn enough to attempt to lead the charge moving xilinx stuff to powerpc. Is there a way to do this in small peices ? It would be nice to end some of the debate on how to setup ppc/4xx for multiple xilinx targets and just get it over with and move to powerpc device tree, ... But I can't beat others up for what I can't find time for myself. -- Dave Lynch DLA Systems Software Development: Embedded Linux 717.627.3770 [EMAIL PROTECTED] http://www.dlasys.net fax: 1.253.369.9244 Cell: 1.717.587.7774 Over 25 years' experience in platforms, languages, and technologies too numerous to list. "Any intelligent fool can make things bigger and more complex... It takes a touch of genius - and a lot of courage to move in the opposite direction." Albert Einstein _______________________________________________ Linuxppc-embedded mailing list [email protected] https://ozlabs.org/mailman/listinfo/linuxppc-embedded
