[beagleboard] [PATCH] OMAP3: beagle: add more expansionboards, based on http://www.elinux.org/BeagleBoardPinMux#Vendor_and_Device_IDs

I'm not sure if the FPGA MUX is right, please check and provide feedback.

Complete tree is available at http://gitorious.org/beagleboard-validation/u-boot/commits/xm

From: Koen Kooi <koen@dominion.thruhere.net>

I'm not sure if the FPGA MUX is right, please check and provide feedback.

Who has these boards? Perhaps someone should at least send one to
Gerald so that Steve or Nishanth or ??? could borrow it if they wanted
to test/play. Just seems like a good idea to send a board to Gerald
when you register it on the wiki.

For what purpose?


That looks right to me. Thanks for including it.


These boards are prototypes that are still at the PCB fab, so at the
moment no one has any. I should have several in a few weeks. More info
on them is here:


FWIW, at the moment this is just a personal project. It's debatable
whether or not there would be any benefit in sending out demos for
test until there are plans for wider distribution. I just grabbed a
slot in the ID list so I'd have one...


My goal is to have u-boot at least identify the expansionboard attached and ideally setup pinmux and environment vars (e.g. display resolution for lcd addons). People who add their boards to the wiki get added and if you share extra info like pinmux requirements or env vars I'll try to add them as well.

Having u-boot do the right thing is of course only the first step, and the fpga board would need changes in the kernel as well to work properly, but it's relatively little work for me to keep at least the u-boot part up to date.

Remind me to 'port' Sakomans eeprom tools to the beagle so you can update the eeprom from within linux.



Thanks for taking the effort to hunt down my pinmux requirements - I
didn't add them to the wiki so you obviously had to take some time to
dig them out of the patch on my web page.

Kernel changes for minimal functionality of the FPGA (detection &
configuration) are fairly simple and static but since the I/O
requirements can vary depending on what the FPGA design does it's
difficult to know in advance what pinmux settings will be required by
the final design. In the best scenario the kernel would have the
ability to alter the pinmux long after boot time in response to
changing FPGA requirements. That doesn't seem feasible with the
present pinmux control resources.

Getting Sakoman's ID EEPROM script into the Angstrom environment would
be great, and having the supporting I2Ctools easily accessible would
help in many other ways.