linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michal Simek <monstr@seznam.cz>
To: Peter Korsgaard <jacmet@sunsite.dk>
Cc: dhlii@dlasys.net, linuxppc-embedded <linuxppc-embedded@ozlabs.org>
Subject: Re: Is anyone using the C67x00 USB Host ?
Date: Wed, 10 Dec 2008 15:36:28 +0100	[thread overview]
Message-ID: <493FD3EC.3060305@seznam.cz> (raw)
In-Reply-To: <87iqpsme9j.fsf@macbook.be.48ers.dk>

Hi Peter,

>>>>>> "Michal" == Michal Simek <monstr@seznam.cz> writes:
> 
> Hi,
> 
>  Michal> You should try to swap mailbox and addr address.
> 
>  Michal> /* HPI registers */
>  Michal> #define HPI_DATA	0
>  Michal> #define HPI_MAILBOX	2
>  Michal> #define HPI_ADDR	1
>  Michal> #define HPI_STATUS	3
> 
> Why? Have you swapped your A0 / A1?

I found that ml40x designs have different connection that ml505 usb design. This
is no problem for me. But I think that in David case is that problem.

We used 2.6.20 kernel because we have this kernel well tested.
I found where the problem was.

Thanks for your driver and help,
Michal


> 
>  Michal> Peter:
> 
>  Michal> What does it mean when I am getting TIMEOUT when kernel is
>  Michal> trying to assign address to device?
> 
>  Michal> Here is the correspond log part. usb_control_msg 5 means
>  Michal> address assigning. And there is timeout description. Star
>  Michal> means interrupt occur.
> 
>  Michal> *usb_control_msg 5, -115
>  Michal> hub_set_address 4 ffffff8d
>  Michal> hub_set_address 8 ffffff8d
>  Michal> +-------------retval ffffff8d ---------------+
>  Michal> OK*... 0x14 ......*---c67x00_td_to_error---
>  Michal> *timeout
>  Michal> --------------------------------------1-----------
>  Michal> *<6>c67x00 c67x00.0: ### TIMEOUT at 0x0500
> 
> I'm not quite following here - Is that the
> wait_for_completion_timeout() in c67x00-sched.c?



> 
> USB questions are probably better asked on the
> linux-usb@vger.kernel.org list.
> 
>  Michal> Don't you have your testing version for any kernel before
>  Michal> 2.6.23? There were some change in usb subsystem.
> 
> There's some older patches at
> http://peter.korsgaard.com/patches/linux, but why are you using such
> an ancient kernel?
> 

  reply	other threads:[~2008-12-10 14:36 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-05 15:32 Is anyone using the C67x00 USB Host ? David H. Lynch Jr.
2008-12-08  9:13 ` Peter Korsgaard
2008-12-09 20:22   ` David H. Lynch Jr.
2008-12-09 21:11     ` Peter Korsgaard
2008-12-08 14:11 ` Michal Simek
2008-12-09 20:27   ` David H. Lynch Jr.
2008-12-10  9:20     ` Michal Simek
2008-12-10 12:00       ` Peter Korsgaard
2008-12-10 14:36         ` Michal Simek [this message]
2008-12-10 14:43           ` Peter Korsgaard
2008-12-10 16:34             ` Michal Simek
2008-12-11 23:52               ` David H. Lynch Jr.
2008-12-12  7:14               ` David H. Lynch Jr.
2008-12-13 18:41               ` David H. Lynch Jr.
2008-12-13 18:58                 ` Peter Korsgaard
2008-12-13 20:27                   ` David H. Lynch Jr.

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=493FD3EC.3060305@seznam.cz \
    --to=monstr@seznam.cz \
    --cc=dhlii@dlasys.net \
    --cc=jacmet@sunsite.dk \
    --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).