From: "Grant Likely" <grant.likely@secretlab.ca>
To: gianfranco.casanova@alice.it
Cc: linuxppc-dev <linuxppc-dev@ozlabs.org>
Subject: Re: R: R: USB on lite5200 does not work.
Date: Fri, 21 Nov 2008 07:59:14 -0700 [thread overview]
Message-ID: <fa686aa40811210659l3b9a4eefwf6eb59f66386d379@mail.gmail.com> (raw)
In-Reply-To: <47602D18F269934AB73B7E550804A1E002137973@FBCMST09V03.fbc.local>
On Fri, Nov 21, 2008 at 1:36 AM, <gianfranco.casanova@alice.it> wrote:
> Hi Grant&Wolfgang
>
> thanks for yours posts. You are right about WR. For lite5200 only few patchs
> have been used. Most of the job is for support other boards or to introduce
> some patchs for its debug system.
>
> The main HW difference between our board and lite5200 is:
> console on PSC3 and
[...]
> on our HW defined as:
> /* Radionav configuration */
> port_config = 0x0C712E66;
>
You've got quite a bit of difference than just console on PSC3. USB
is on the Ethernet pin group instead of on the USB pin group. Does
the kernel change the value of port_config when it boots, or does it
leave the value setup by U-Boot intact?
> I still do not understand our bug with USB.
> Have you got some suggestions or some test to be performed in order to find
> out a solutions?
Not over a quick exchange via email. Your kernel is too old and USB
debugging can be complex. I'd need to be working with your hardware
to figure out what is going on.
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
next prev parent reply other threads:[~2008-11-21 14:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-20 14:09 USB on lite5200 does not work gianfranco.casanova
2008-11-20 14:56 ` Grant Likely
[not found] ` <47602D18F269934AB73B7E550804A1E00213796F@FBCMST09V03.fbc.local>
2008-11-20 15:49 ` R: " Grant Likely
2008-11-21 8:36 ` R: " gianfranco.casanova
2008-11-21 14:59 ` Grant Likely [this message]
2008-11-22 12:15 ` Gianfranco Casanova
2008-11-22 15:35 ` Jon Smirl
2009-01-29 9:38 ` velumani
2008-11-20 18:48 ` Wolfgang Denk
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=fa686aa40811210659l3b9a4eefwf6eb59f66386d379@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=gianfranco.casanova@alice.it \
--cc=linuxppc-dev@ozlabs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).