From: Lorenz Kolb <linuxppcemb@lkmail.de>
To: linuxppc-embedded@ozlabs.org
Subject: Re: ML403 USB driver
Date: Tue, 20 Nov 2007 23:37:13 -0800 (PST) [thread overview]
Message-ID: <13872475.post@talk.nabble.com> (raw)
In-Reply-To: <fa686aa40711200731n61d239fdw4ac1d64a95ad97ff@mail.gmail.com>
Grant Likely-2 wrote:
>
> On 11/20/07, Lorenz Kolb <linuxppcemb@lkmail.de> wrote:
>
>>
>> Anyway, only one of the two peripheral ports seems to be active.
>
> Yes, I've got that problem here too. I haven't yet solved it. Any
> help would be appreciated.
>
> Cheers,
> g.
>
>
Well that's what we have found out till now, maybe it helps, or at least
what we think to have found out:
- First of all to the non functioning peripheral port:
It is "USB Peripheral 1".
According to the schematics it should be powered using the OTGVBus-Port of
the Cypress-Controller (nevertheless it has currently no level)
- Secondly there is no configuration 1 Host + 2 Peripherals according to the
datasheet from Cypress
- Thirdly the initial configuration (at least that is what we are guessing)
seems to be done via some standalone program coming from an Eeprom.
- The three pins near the UART port are the serial console for the Cypress
chip (we have not yet done any tests with that).
- At least the peripherals are connected in a right way, as one SIE can only
have one peripheral
Some question aside the peripheral topic:
Has anyone any idea how to make the cypress chip to have a _normal_ Host not
an OTG one (as some USB-Hub might save us from our dilemma why we tried to
use gadgets in peripheral mode)?
Regards,
Lorenz Kolb
--
View this message in context: http://www.nabble.com/ML403-USB-driver-tf4844098.html#a13872475
Sent from the linuxppc-embedded mailing list archive at Nabble.com.
next prev parent reply other threads:[~2007-11-21 7:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-20 15:21 ML403 USB driver Lorenz Kolb
2007-11-20 15:31 ` Grant Likely
2007-11-21 7:37 ` Lorenz Kolb [this message]
2007-11-23 10:34 ` Peter Korsgaard
2007-11-23 17:31 ` Grant Likely
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=13872475.post@talk.nabble.com \
--to=linuxppcemb@lkmail.de \
--cc=linuxppc-embedded@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).