All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Berger <gmane@reliableembeddedsystems.com>
To: poky@pokylinux.org
Subject: Re: bernard 5.0.1 and beagle-xm rev c
Date: Wed, 15 Jun 2011 14:01:04 +0300	[thread overview]
Message-ID: <4DF890F0.1020307@reliableembeddedsystems.com> (raw)
In-Reply-To: <4DF80B84.9000304@linux.intel.com>

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?

    * The revision ID on the board and the control signal for powering
the USB hub on the board changed between xM rev B and xM rev C. Older
versions of x-loader/MLO, u-boot and the Linux kernel did not properly
utilize the revision ID settings on the board, so xM rev B boards didn't
actually include settings different than xM rev A to work-around the
issue. On xM rev C, with the USB hub changes on the board, it became
necessary to no longer use this work-around and to actually change the
board revision ID. This causes older software to break. There is a bit
more discussion on this on the mailing list.

    * If you utilize the latest mainline x-loader (
http://gitorious.org/x-loader ) and u-boot (
http://git.denx.de/?p=u-boot.git ), including the variations shipped on
the microSD card on the board (available at circuitco.com/support ), the
revision will be properly detected.

    * The mainline kernel does not yet include the patch required to
utilize the proper polarity for the USB hub power enable. You can take a
look at this candidate patch for an idea of what to fix and potentially
apply this patch (
http://gitorious.org/beagleboard-validation/linux/commit/bfca58987039791522d1821e0506f8a113a0c239
) to your kernel. If you assemble an image of Angstrom using Narcissus,
you'll get a working kernel using the sources in Open Embedded.

I did not dig too much into the issue if and where changes need to be
made (x-loader, u-boot, kernel)

Judging from the u-boot output I think it needs to be patched:
Beagle unknown 0x02

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;)

Regards,

Robert
..."As soon as we started programming, we found to our surprise that it
wasn't as easy to get programs right as we had thought.  Debugging had
to be discovered.  I can remember the exact instant when I realized that
a large part of my life from then on was going to be spent in finding
mistakes in my own programs." - Maurice Wilkes discovers debugging, 1949

My public pgp key is available at:
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x90320BF1




  reply	other threads:[~2011-06-15 11:01 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 [this message]
2011-06-15 11:46     ` Robert Berger
2011-06-15 16:38     ` Darren Hart
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=4DF890F0.1020307@reliableembeddedsystems.com \
    --to=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.