linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Nigel Rudgley" <nrudgley@consultronics.co.uk>
To: "Jaap-Jan Boor" <jjboor@aimsys.nl>
Cc: <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: usb hub problem on 8270
Date: Tue, 23 Mar 2004 09:59:48 -0000	[thread overview]
Message-ID: <008901c410bd$93e0c0a0$2002a8c0@gadget> (raw)
In-Reply-To: 935CBD11-6322-11D8-89E5-000A95B15278@aimsys.nl


Hi Jaap-Jan


We're trying to bring up UBS host on the PQFADS board (8280 based) and have
recently got it running on an Adder-II board (870 based)


Maybe our experience with 870 can help - your problem looks a lot like what
we saw with the Adder board, some transmits, detecting a hub, then...
nothing.

The CPM has been altered slightly from the 823/850 and will now effect a
graceful stop when it receives a nak or stall response, you now have to
restart it manually after these are detected.

In original m8xxhci.c, this needs to be done in process_done_txbds()
around line 2183, inside "if (nak & BD_USB_NAK)"
around line 2197, inside "if ((nak & BD_USB_STAL))"
around line 2213, inside "if (nak)"

calling restart_endpoint() at these three points should work to wake up the
cpm :-)

I can send a complete patch file but other changes won't be so relevant for
you, they're for 870.


On the other hand you look further on with the 8270 than we are with the
8280, we're not seeing SOFs :-( Do we need a microcode patch on the 82xx? Do
the IDMAs need setting up to get DREQs in the right configuration or does it
just work with the external wire connected?


Cheers

Nigel
nrudgley@consultronics.co.uk


----- Original Message -----
From: "Jaap-Jan Boor" <jjboor@aimsys.nl>
To: <linuxppc-embedded@lists.linuxppc.org>
Sent: Thursday, February 19, 2004 9:28 PM
Subject: usb hub problem on 8270


>
> Hi,
>
> I found some time to adapt m8xxhci.c (for 823/850) to the 8270 with
> limited success.
> We use TOUT3 (from timer3) to DREQ0/1 to enable SOF transmitting which
> works
> more or less as one of my hubs is detected but after the host driver
> received the hub's
> device description, I get a time-out and, well that's it. Even after
> resetting the 8270 and cpm
> I'm unable to communicate to the hub:


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2004-03-23  9:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-19 21:28 usb hub problem on 8270 Jaap-Jan Boor
2004-03-23  9:59 ` Nigel Rudgley [this message]
2004-03-23 17:23   ` Jaap-Jan Boor

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='008901c410bd$93e0c0a0$2002a8c0@gadget' \
    --to=nrudgley@consultronics.co.uk \
    --cc=jjboor@aimsys.nl \
    --cc=linuxppc-embedded@lists.linuxppc.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).