We plan to go ahead and build up a number of Rev. B boards and make
them available to order from http://BeagleBoard.org starting in June/
July. These Rev. B boards will not have support for the USB EHCI port
and are not yet fully supported with easy-to-download-and-use
software. USB functionality is still available using the OTG port
when utilizing the alternative power supply (non-USB). These boards
are intended for low-level software developers and a full software
stack for the boards will be a few months away.
Once the Rev. C boards are available, we expect to take orders for the
Rev. C boards under a different part number.
If you are still interested in a Rev. B board, can you please end an e-
mail to revb-request@beagleboard.org?
Simple (ignorant) question: can the OTG port be configured to be a host port?
Mark
Mark,
The OTG driver has configurations for host, peripheral and OTG. You can select this via the menuconfig.
Cheers
Jon
USB musb OTG (on-the-go):
* 480/12/1.5Mbps (HS/FS/LS) support, both host and device.
* Selection is software controlled either at boot (based on kernel
configuration) or, possibly, at run-time via software or cable
detection.
* Uses mini-AB 5-pin receptacle and requires adapter to plug in USB
peripherals.
* May be used to supply power to the board. Alternate power source is
a 5V DC wall-wart adapter.
USB EHCI Host:
* 480Mbps (HS) support host only. FS/LS support only through an
external USB hub.
* Always a host, but the DMA is very similar to what is used on PCs,
so converting drivers over from the PC is almost trivial. The musb
controller only recently got supported in the mainline versions of
Linux, so support of the EHCI controller is more mature.
* Uses standard-A receptacle and allows most HS USB peripherals and
hubs to connect directly.
* Provides 500mA power to peripherals when board is given a sufficient
supply input and never accepts power input.
With 2.6.26-rc4 cable based detection works perfectly (minus TWL4030
glitches that kill OTG, but that isn't a MUSB problem).
regards,
Koen
Something like this, http://www.vernier.com/accessories/access.html?usb-mini&template=basic.html,
seems to be the best answer for using the OTG port as a host.
Is the kernel & rootfs up and running on these boards? Does it include
the PowerVR drivers for the SGX (will it ever include these?)?
ATM there is no public driver for the SGX, rumour has that it is being
worked on and that the pandora people have a beta. Again, those are
rumours.
regards,
Koen
Latest Kernel and u-boot is up and running on this board and has filesystem and other fundamental components supported as well.
The CE/LINK and SGX drivers / binaries should also be available in coming months.
Regards,
Khasim
I need SGX drivers for what I want to do (bring Qt/Embedded up), so I
guess it's probably better for me to wait until Rev.C boards are
ready? Or are drivers likely to be made avaliable before Rev.C boards
are avaliable?
Cheers,
Tom
Drivers are same for Rev B or Rev C boards. The driver availability is independent of board revisions, the drivers should formally be reviewed for all Licensing Terms and conditions before they get out. This will take some time and can happen before or after Rev B.
Rev B should be sufficient for SGX driver validations along with the USB OTG port to connect to a Keyboard or Mouse to get the UI interface. But don’t relate the board availability with SGX driver availability 
Regards,
Khasim
In order to make a decision could you please list the differencies
between Rev B and Rev C boards.
Regards,
Andrew
Hi,
With 2.6.26-rc4 cable based detection works perfectly (minus TWL4030
glitches that kill OTG, but that isn't a MUSB problem).
This is not on linux-omap git tree is it ? afaict, linux-omap can't
switch
roles based on id pin sampling. I actually sent you a patch adding
that
to linux-omap. If you could try it out and comment on it, I'd be
really glad 
Regards,
Felipe Balbi
Well, I plug in the host cable and it works
regards,
Koen
Koen,
Does gadget work with the same kernel?
Regards,
Jason
Hi,
Will Rev C boards use the new, pin compatible TPS65950 instead of the
older TWL4030?
There was also some talk of Rev C boards being four layer. Has this
been achived?
When will Rev C boards be available?
What are your plans for Rev D boards?
And can you please publish a list of companies than can make PCB's and
mount the OMAP35x with POP memory in the UK or Europe?. We are having
difficulty in finding a suitable manufacuter for a custom board
solution.
Kind Regards,
Andrew
In the open spirit... see below...
Hi,
Will Rev C boards use the new, pin compatible TPS65950 instead of the
older TWL4030?
There was also some talk of Rev C boards being four layer. Has this
been achived?
When will Rev C boards be available?
Rev C will likely be about the end of the year. November, if we are lucky. We are going to production with Rev B. The ONLY difference is the USB EHCI port and we feel like the use cases for the USB OTG port have been very good without the EHCI port. It would still be 6 layers. We minimized the changes to minimize the risk. We will minimize our inventory of Rev B boards before building Rev C.
What are your plans for Rev D boards?
The next revision after C is more open. In general, we are looking externally for a lower-cost design using the 0.65mm ball-pitch package and TPS659x0. As we solidify the rules for engagement, we'll be sharing info. There is already at least one mailing list participant who has been very active in generating ideas for this design. This does NOT mean we'll be entertaining all ideas for stuff thrown on the board. The board should remain 100% software compatible. We are constrained by clearing our inventory of Rev B and C boards as well as not making them seem obsolete. The overriding concept will simply be cost-reduction.
And can you please publish a list of companies than can make PCB's and
mount the OMAP35x with POP memory in the UK or Europe?. We are having
difficulty in finding a suitable manufacuter for a custom board
solution.
As you are looking into companies that can support PoP memory in UK/Europe, is the issue the PoP memory, or is it the 0.4mm ball-pitch? Hopefully some others will chime in, but I will see if I can find a few recommendations.
Regards,
Jason