On Thursday, May 5, 2011 9:35:45 AM UTC-4, RobertCNelson wrote:
On Thu, May 5, 2011 at 3:20 AM, Pahtet <pahte...@gmail.com> wrote: > Hello > When i try to compile U-Boot using > make CROSS_COMPILE=arm-none-linux-gnueabi- omap3_beagle_config > make CROSS_COMPILE=arm-none-linux-gnueabi- > I get boot image for Beagle Board rev A but i need image for rev B. > How to configurate revision before compiling?
The image you have is fine.. .
Almost all "rev B"'s have the same gpio setting as the "rev A"'s... So there's no way for u-boot to detect a "B" unless the gpio detection routine was expanded to core id revision..
For the release of the Rev B boards, the issue of u-boot having a bug that caused newer revisions of boards to revert to pre-xM settings meant that it was easiest (had the best software experience) to not change the GPIO-based revision ID settings. If you want to detect that you have a Rev B board (that doesn't require any software changes over Rev A), then you can simply detect the CPU revision. Honestly, I don't know why it had to become Rev B, but I think that is the convention (CPU revisions causing board revision updates) and don't think it matters much either.
For xM Rev C boards, there was a change to the way the USB hub is powered, so the change to the GPIO-based revision ID settings became required. Thus, you'll find that old MLO/u-boot/uImage won't work with the xM Rev C boards due to that bug with the software treating newer revision boards as pre-xM boards. If you update the MLO/u-boot/uImage to newer versions, you'll find that software will work on both boards.
The patches in question are (placed here for my reference and soon to end up on a FAQ somewhere):