From: Valentine Barshak <vbarshak@ru•mvista.com>
To: jyoung5@us•ibm.com
Cc: linuxppc-dev@ozlabs•org, linux-usb-devel@lists•sourceforge.net,
Hollis Blanchard <hollisb@us•ibm.com>
Subject: Re: [PATCH 0/3] usb: ehci ppc device-tree-aware driver
Date: Mon, 08 Oct 2007 22:18:22 +0400 [thread overview]
Message-ID: <470A746E.4050804@ru.mvista.com> (raw)
In-Reply-To: <1191867353.5618.17.camel@laptop>
Jerone Young wrote:
> So the issue here with the Sequoia board is that if you load a kernel or
> initrd from usb stick while under u-boot environment, when Linux boots
> it will see the network adapter & even set an ip for it. But no matter
> what it is unable to access any outside ip.
>
> The way we recreated this scenario was:
>
> - Have a USB stick with
> - partition 1 is fat partition with our kernel & initrd
> - partition 2 is ext3 with our root filesystem
>
> 1) Boot Sequoia board with USB stick plugged in. Go to u-boot prompt.
> 2) start usb using "usb start"
> 3) Load kernel off usb stick using "fatload" command in uboot
> * Optionally load initrd off of usb stick
> * Example:
> fatload usb 0:1 4000000 cuImage.sequoia
>
> 4) stop usb using "usb stop"
> 5) Then boot kernel using bootm
>
> Now from this point linux loads and will mount the filesystem on the usb
> stick. But if you want to use networking in anyway you have a problem.
> You can start the telnet daemon and access from the board using
> 127.0.0.1 address (loopback). Trying to access the telnet from an
> outside ip is unsuccessful.
>
> Also, if you have it setup so that the root filesystem is on a nfs root,
> the kernel is never able to get to the nfs root. Basically something is
> really borked.
>
> I'm a little late getting back to this email :-0
>
> On Sat, 2007-09-22 at 23:00 +0000, Hollis Blanchard wrote:
>> On Mon, 17 Sep 2007 16:50:39 +0400, Valentine Barshak wrote:
>>
>>> Some PowerPC systems have a built-in EHCI controller.
>>> This is a device tree aware version of the EHCI controller driver.
>>> Currently it's been tested on the PowerPC 440EPx Sequoia board.
>>> Other platforms can be added later.
>>> The code is based on the ehci-ppc-soc driver by Stefan Roese <sr@denx•de>.
>> We're having a strange issue on our Sequoia where the network stops
>> functioning when USB is active. Jerone can supply more detail...
>>
>> Have you seen anything like that?
>>
>
Please try this patch:
http://ozlabs.org/pipermail/linuxppc-dev/2007-October/043435.html
Thanks,
Valentine.
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@ozlabs•org
> https://ozlabs.org/mailman/listinfo/linuxppc-dev
next prev parent reply other threads:[~2007-10-08 18:19 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-17 12:50 [PATCH 0/3] usb: ehci ppc device-tree-aware driver Valentine Barshak
2007-09-17 12:55 ` [PATCH 1/3] usb: add device-tree-aware ehci driver Valentine Barshak
2007-09-17 13:00 ` [PATCH 2/3] usb: ehci-ppc-of dts bindings Valentine Barshak
2007-09-19 0:25 ` Segher Boessenkool
2007-09-19 13:52 ` Valentine Barshak
2007-09-19 16:50 ` Segher Boessenkool
2007-09-19 16:55 ` Valentine Barshak
2007-09-24 19:32 ` [linux-usb-devel] " Valentine Barshak
2007-09-20 0:52 ` David Gibson
2007-09-24 21:40 ` Segher Boessenkool
2007-09-17 13:28 ` [PATCH 1/3] usb: add device-tree-aware ehci driver Stephen Rothwell
2007-09-17 14:00 ` Josh Boyer
2007-09-17 18:17 ` Valentine Barshak
2007-09-18 4:26 ` Stephen Rothwell
2007-09-18 5:39 ` David Gibson
2007-09-17 18:18 ` Valentine Barshak
2007-09-17 13:02 ` [PATCH 3/3] Add PowerPC 440EPx Sequoia ehci dts entry Valentine Barshak
2007-09-22 23:00 ` [PATCH 0/3] usb: ehci ppc device-tree-aware driver Hollis Blanchard
2007-09-24 10:33 ` Valentine Barshak
2007-10-08 18:15 ` Jerone Young
2007-10-08 18:18 ` Valentine Barshak [this message]
2007-10-08 18:22 ` Valentine Barshak
-- strict thread matches above, loose matches on Subject: below --
2007-09-24 19:25 Valentine Barshak
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=470A746E.4050804@ru.mvista.com \
--to=vbarshak@ru$(echo .)mvista.com \
--cc=hollisb@us$(echo .)ibm.com \
--cc=jyoung5@us$(echo .)ibm.com \
--cc=linux-usb-devel@lists$(echo .)sourceforge.net \
--cc=linuxppc-dev@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox