From: Stefan Roese <sr@denx.de>
To: Roger Quadros <rogerq@ti.com>
Cc: tony@atomide.com, linux-omap@vger.kernel.org, balbi@ti.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: OMAP3: Beagle: Fix USB Host on beagle xM Ax/Bx
Date: Fri, 12 Jul 2013 12:52:04 +0200 [thread overview]
Message-ID: <51DFDFD4.3040900@denx.de> (raw)
In-Reply-To: <51DFC92F.1050701@ti.com>
Roger,
On 07/12/2013 11:15 AM, Roger Quadros wrote:
>>> Good idea. I'm currently using a "dirty" local version. I'll try to
>>> switch to an officially available version tomorrow. And send you the
>>> version/git id.
>>
>> I updated my U-Boot to the following version: Based on mainline git
>> commit ID 225fd8c. Only this patch added:
>>
>> http://patchwork.ozlabs.org/patch/256702/
>>
>> This is needed for USB to work in U-Boot. Otherwise my external USB
>> SMSC95xx will not be detected in U-Boot.
>
> I can only test on beagle-xm (which is also rev. C2) with integrated SMSC ethernet chip
> as I don't have an external USB-ethernet adapter.
Too bad. This difference in boards makes the tests a bit less
meaningful. Is there really no USB-ethernet adapter somewhere in your
department (perhaps a non-SMSC95xx might serve as well?)? I might
send/order you one if necessary. ;)
> The above commit doesn't work well for beagle-xm,
Why is this? What does happen? Does U-Boot not boot up to the prompt?
Please send me a log.
> so my u-boot is on tag v2013.04
> and you don't need that additional patch.
>
> Can you please retest on it? Thanks.
Done, please see below.
> You will need to set "usbethaddr" before starting USB else SMSC will not work.
> e.g.
> setenv usbethaddr A6:66:4D:B0:69:04
I don't have a beagle-xm, only my beable. And my U-Boot network setup is
already working, thanks.
> Also could you please increase the Linux console message verbosity to debug (8), so that
> all kernel messages are visible in the log? If it spits out something more than what you
> sent last time then do send it to me.
I added "ignore_loglevel" to the cmdline. But I cannot see anything
interesting that has not been there before with "debug" as well.
> Let's first sort out the beagle-xm problem, then we can see about old beagle.
Okay, I tested again with U-Boot v2013.01 plus my SMSC patch. Same
problem. NFS booting/mounting hangs at some time.
Thanks,
Stefan
WARNING: multiple messages have this Message-ID (diff)
From: sr@denx.de (Stefan Roese)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: OMAP3: Beagle: Fix USB Host on beagle xM Ax/Bx
Date: Fri, 12 Jul 2013 12:52:04 +0200 [thread overview]
Message-ID: <51DFDFD4.3040900@denx.de> (raw)
In-Reply-To: <51DFC92F.1050701@ti.com>
Roger,
On 07/12/2013 11:15 AM, Roger Quadros wrote:
>>> Good idea. I'm currently using a "dirty" local version. I'll try to
>>> switch to an officially available version tomorrow. And send you the
>>> version/git id.
>>
>> I updated my U-Boot to the following version: Based on mainline git
>> commit ID 225fd8c. Only this patch added:
>>
>> http://patchwork.ozlabs.org/patch/256702/
>>
>> This is needed for USB to work in U-Boot. Otherwise my external USB
>> SMSC95xx will not be detected in U-Boot.
>
> I can only test on beagle-xm (which is also rev. C2) with integrated SMSC ethernet chip
> as I don't have an external USB-ethernet adapter.
Too bad. This difference in boards makes the tests a bit less
meaningful. Is there really no USB-ethernet adapter somewhere in your
department (perhaps a non-SMSC95xx might serve as well?)? I might
send/order you one if necessary. ;)
> The above commit doesn't work well for beagle-xm,
Why is this? What does happen? Does U-Boot not boot up to the prompt?
Please send me a log.
> so my u-boot is on tag v2013.04
> and you don't need that additional patch.
>
> Can you please retest on it? Thanks.
Done, please see below.
> You will need to set "usbethaddr" before starting USB else SMSC will not work.
> e.g.
> setenv usbethaddr A6:66:4D:B0:69:04
I don't have a beagle-xm, only my beable. And my U-Boot network setup is
already working, thanks.
> Also could you please increase the Linux console message verbosity to debug (8), so that
> all kernel messages are visible in the log? If it spits out something more than what you
> sent last time then do send it to me.
I added "ignore_loglevel" to the cmdline. But I cannot see anything
interesting that has not been there before with "debug" as well.
> Let's first sort out the beagle-xm problem, then we can see about old beagle.
Okay, I tested again with U-Boot v2013.01 plus my SMSC patch. Same
problem. NFS booting/mounting hangs at some time.
Thanks,
Stefan
next prev parent reply other threads:[~2013-07-12 10:52 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-15 11:20 [PATCH] ARM: OMAP3: Beagle: Fix USB Host on beagle xM Ax/Bx Roger Quadros
2013-04-15 11:20 ` Roger Quadros
2013-04-15 11:20 ` Roger Quadros
2013-05-08 22:12 ` Tony Lindgren
2013-05-08 22:12 ` Tony Lindgren
2013-07-09 13:02 ` Stefan Roese
2013-07-09 13:02 ` Stefan Roese
2013-07-09 13:55 ` Roger Quadros
2013-07-09 13:55 ` Roger Quadros
[not found] ` <51DC1B47.7070504@denx.de>
2013-07-09 17:20 ` Roger Quadros
2013-07-09 17:20 ` Roger Quadros
2013-07-11 10:24 ` Roger Quadros
2013-07-11 10:24 ` Roger Quadros
2013-07-11 10:45 ` Stefan Roese
2013-07-11 10:45 ` Stefan Roese
2013-07-11 12:00 ` Roger Quadros
2013-07-11 12:00 ` Roger Quadros
2013-07-11 12:33 ` Stefan Roese
2013-07-11 12:33 ` Stefan Roese
2013-07-11 12:41 ` Stefan Roese
2013-07-11 12:41 ` Stefan Roese
2013-07-11 14:35 ` Roger Quadros
2013-07-11 14:35 ` Roger Quadros
2013-07-11 15:34 ` Stefan Roese
2013-07-11 15:34 ` Stefan Roese
[not found] ` <51DEF0DE.4050607@denx.de>
2013-07-12 9:15 ` Roger Quadros
2013-07-12 9:15 ` Roger Quadros
2013-07-12 10:52 ` Stefan Roese [this message]
2013-07-12 10:52 ` Stefan Roese
2013-07-15 8:16 ` Roger Quadros
2013-07-15 8:16 ` Roger Quadros
2013-07-15 8:24 ` Stefan Roese
2013-07-15 8:24 ` Stefan Roese
2013-07-16 14:37 ` Roger Quadros
2013-07-16 14:37 ` Roger Quadros
2013-07-16 16:19 ` Stefan Roese
2013-07-16 16:19 ` Stefan Roese
2013-07-19 13:04 ` Roger Quadros
2013-07-19 13:04 ` Roger Quadros
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=51DFDFD4.3040900@denx.de \
--to=sr@denx.de \
--cc=balbi@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=rogerq@ti.com \
--cc=tony@atomide.com \
/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.