Florian, currently there is no usb support on the beagleboard xm.
Because of this you will also not have networking because the xm uses
a usb/ethernet device.

On Fri, Aug 23, 2013 at 10:58 AM, Florian Stinglmayr
<fstinglm...@gmail.com> wrote:
> Hi list,
>
> I have a BeagleBoard xM and through a very helpful mailing list post I
> set up a cross compiling toolset on i386 and got it to boot OpenBSD just
> fine.
>
> However the USB and the Ethernet port do not seem to work, and I did not
> have a lot of luck getting them to work.
>
> Are they supported and if so, what do I need to do to get them working?
>
> Down below is the dmesg of the BeagleBoard xM.
>
> Regards,
> Florian
>
> OpenBSD 5.4-current (GENERIC) #2: Thu Aug 22 12:33:26 MDT 2013
>     r...@noname.my.domain:/usr/src/sys/arch/beagle/compile/GENERIC
> real mem  = 536870912 (512MB)
> avail mem = 519208960 (495MB)
> mainbus0 at root
> cpu0 at mainbus0: ARM Cortex A8 R3 rev 2 (ARMv7 core)
> cpu0: DC enabled IC enabled WB disabled EABT branch prediction enabled
> cpu0: 32KB(64b/l,4way) I-cache, 32KB(64b/l,4way) wr-back D-cache
> omap0 at mainbus0: BeagleBoard
> prcm0 at omap0 rev 1.0
>
> intc0 at omap0 rev 4.0
> gptimer0 at omap0 rev 1.3
> gptimer1 at omap0 rev 1.3
> omdog0 at omap0 rev 3.1
> omgpio0 at omap0 omap3 rev 2.5
> omgpio1 at omap0 omap3 rev 2.5
> omgpio2 at omap0 omap3 rev 2.5
> omgpio3 at omap0 omap3 rev 2.5
> omgpio4 at omap0 omap3 rev 2.5
> omgpio5 at omap0 omap3 rev 2.5
> ommmc0 at omap0
> sdmmc0 at ommmc0
> com0 at omap0: ti16750, 64 byte fifo
> com0: console
> /dev/ksyms: Symbol table not valid.
> scsibus0 at sdmmc0: 2 targets, initiator 0
> sd0 at scsibus0 targ 1 lun 0: <SD/MMC, Drive #01, > SCSI2 0/direct fixed
> sd0: 15320MB, 512 bytes/sector, 31375360 sectors
> vscsi0 at root
> scsibus1 at vscsi0: 256 targets
> softraid0 at root
> scsibus2 at softraid0: 256 targets
> boot device: lookup 'root=/dev/rsd0a' failed.
> root device: sd0a
> swap device (default sd0b):
> root on sd0a swap on sd0b dump on sd0b
> WARNING: CHECK AND RESET THE DATE!

Reply via email to