Re: beagleboard expansion boards, was Trying to understand how to use new OMAP mux code

[Tony Lindgren <tony@atomide.com>]

* Koen Kooi <koen@dominion.thruhere.net> [100602 17:01]:
> 
> "Support all beagle expansion boards mentioned in http://elinux.org/BeagleBoardPinMux#Vendor_and_Device_IDs out of the box"
> 
> That means that a user can plug in an expansion board, apply power and it will "just work". That's the case now for the zippy, zippy2, trainer and beaglefpga boards with the current u-boot and kernel setup. I agree it doesn't scale, but I haven't seen any actual effort by the beagleboard/omap3 community to make the muxing and initializing the board (i2c, spi, gpio, rtc) work completely in the kernel :(

Well how about patch u-boot to allow saveenv the revision
and then pass it to kernel as ATAG_REVISION? That's available
as system_rev in the kernel. Then you can initialize the platform
devices in the board-*.c files.

The other option would be to somehow to detect the hardware
during the boot, but that may not work for all the devices.

Regards,

Tony