From: Darren Hart <dvhart@linux.intel.com>
To: gmane@reliableembeddedsystems.com
Cc: poky@pokylinux.org
Subject: Re: bernard 5.0.1 and beagle-xm rev c
Date: Wed, 15 Jun 2011 09:38:55 -0700 [thread overview]
Message-ID: <4DF8E01F.8040209@linux.intel.com> (raw)
In-Reply-To: <4DF890F0.1020307@reliableembeddedsystems.com>
On 06/15/2011 04:01 AM, Robert Berger wrote:
> Hi,
>
> On 06/15/2011 04:31 AM, Darren Hart wrote:
>>
>> Does USB work in general on Rev C?
>>
>> --
>> Darren
>>
>
> I built a minimal-image + usbutils
>
> REV A3 with poky:
>
> root@beagleboard:~# lsusb
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp.
> Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp.
>
> REV C with Angstrom:
>
> root@beagleboard:~# lsusb
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 002 Device 002: ID 0424:9514 Standard Microsystems Corp.
> Bus 002 Device 003: ID 0424:ec00 Standard Microsystems Corp.
>
> REV C with poky:
>
> root@beagleboard:~# lsusb
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>
> This looks like the USB hub on Bus 002 is not found and hence there is
> also no Ethernet, which fits somehow into what I've found on
> http://beagleboard.org/support/faq
>
> # What do I need to do to get my software running on a BeagleBoard-xM rev C?
At the Bernard release I don't believe we had support for the xM rev C
(it supported at least up to xM rev A). I am currently working on a
refresh of the Beagleboard BSP in meta-yocto which does support rev C.
For details on that effort and it's status, please see:
https://lists.yoctoproject.org/pipermail/yocto/2011-June/001599.html
> Judging from the u-boot output I think it needs to be patched:
> Beagle unknown 0x02
Indeed.
>
> u-boot which comes with Angstrom:
> Beagle xM Rev C
>
> I'm sure Koen can tell us more about this and also what patches should
> be applied where;)
Both Koen and Jason K. have been helping to get the right bits merged
for the kernel. I had hoped to use mainline u-boot, but it appears we
may need at least a set of patches in support of Rev C.
The updated BSP will be released with 1.1. My patches and commits will
of course hit the list before then and you can build from master once
they arrive there. Within a week I suspect.
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
next prev parent reply other threads:[~2011-06-15 16:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-14 21:13 bernard 5.0.1 and beagle-xm rev c Robert Berger
2011-06-15 1:31 ` Darren Hart
2011-06-15 11:01 ` Robert Berger
2011-06-15 11:46 ` Robert Berger
2011-06-15 16:38 ` Darren Hart [this message]
2011-06-15 17:18 ` Robert Berger
2011-06-15 23:36 ` Darren Hart
2011-06-16 1:32 ` Jason Kridner
[not found] ` <4DFA2189.7020804@ahsoftware.de>
2011-06-16 17:48 ` Darren Hart
2011-06-15 18:26 ` Jason Kridner
2011-06-15 19:05 ` Robert Berger
2011-06-15 20:43 ` Jason Kridner
2011-06-18 19:05 ` [PATCH] " Robert Berger
2011-06-27 22:15 ` Darren Hart
2011-06-28 4:43 ` Robert Berger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4DF8E01F.8040209@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=gmane@reliableembeddedsystems.com \
--cc=poky@pokylinux.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.