Hi,
I'm trying to get the bbtoys-wifi working on Beagle xM (rev B) with
the Angstrom 2010.x
I got it working with the 2.6.39-rc1 image used in the ELC2011 San
Francisco workshop (wl12xx renamed driver), thus the bbtoys-wifi + xM
hardware is healthy and operational.
However, I cannot get it to work under Angstrom's 2010.x with 2.6.37
kernel default build (either console or x11, though it shouldn't
matter as far as the kernel is concerned).
Examining the patch set
0013-omap3-beagleboard-add-WIP-support-for-beagleboardtoy.patch
under the recipes for linux-omap-2.6.37/base seems to be the main
patch to get the bbtoys-wifi recognized and initialized by the kernel
but when I modprobe the wl1271_sdio driver (after depmod -a and thus
all it's dependencies), the device is not detected and not turned on.
I've noticed at http://groups.google.com/group/beagleboard/browse_thread/thread/8f12c1e69d644e86
additional OMAP_MUX initialization changes that are missing from the
0013-omap3-beagleboard-add-WIP-support-for-beagleboardtoy.patch
and added them as a separate patch.
But this still does not help - i.e. I get the same result - hardware
is not getting initialized.
Would appreciate any pointers and/or a patch that will make the bbtoys-
wifi operational on beagle xM (rev B.) and Angstrom 2010.x/2.6.37
kernel release.
Thank you,
James B.
Use the u-boot from the angstrom website, or build your own with http://www.angstrom-distribution.org/building-angstrom
Although I don't quite see how u-boot affects the kernel board
initialization for bbtoys-wifi expansion board (in arch/arm/mach-omap2/
board-omap3beagle.c), I tried both the Angstrom u-boot and (obviously)
the one that I build as part of the x11-image/console-image.
Neither helps with properly initializing the bbtoys-wifi to get the Wi-
Fi to work (or Bluetooth or FM for that matter).
Does u-boot do any preparations for initialization of the bbtoys-wifi
board that remain during kernel boot?
As I mentioned, the board is an -xM (printed sticker says rev B,
kernel reports rev A).
I have noticed in that the 0013-omap3-beagleboard-add-WIP-support-for-
beagleboardtoy.patch (in linux-omap-2.6.37/base recipe) has a bug in
beagle_twl_gpio_setup:
in the beginning of the function, according to the board type (e.g.
OMAP3BEAGLE_BOARD_XM) values of gpio_wp, gpio_cd are set in mmc[0]
array, while later in the function, if the bbtoys-wifi is connected
mmcbbt array (rather than mmc) is passed to omap2_hsmmc_init, thus
leaving out pieces of initialization for Beagle xM.
Though I fixed this, I still cannot get the bbtoys-wifi to function
under Angstrom 2.6.37 kernel.
BTW, I also noticed that beagle_vmmc2_supply.dev does not get assigned
with the mmcbbt[1] device. I wonder whether this is the way it is
supposed to be?
With the angstrom uboot and kernel my bbtoys board "Just Works(TM)". I do know that some boards don't have the EEPROM programmed, so please post the output of your uboot.