From: Guillaume Autran <gautran@mrv.com>
To: Pantelis Antoniou <panto@intracom.gr>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: MPC885 - USB HCI drivers.
Date: Tue, 17 May 2005 08:10:55 -0400 [thread overview]
Message-ID: <4289DF4F.4060301@mrv.com> (raw)
In-Reply-To: <4289A635.5000509@intracom.gr>
Hi Pantelis,
Are your drivers compatible with linux kernel 2.6.x ?
I'll be interested to have a look at them if you don't mind.
Also, do you think an USB bus analyzer is a *must have* in order to work
on the drivers ?
Regards,
Guillaume.
Pantelis Antoniou wrote:
> Wolfgang Denk wrote:
>
>> Dear Mike,
>>
>> in message <428995CB.4050301@compulab.co.il> you wrote:
>>
>>> Do you know if the same is applicable to CPM2 USB controllers
>>> present for example on mpc8247?
>>
>>
>>
>> Sorry, I don't know from personal experience. But from what I heard
>> there might be some "surprises", too.
>>
>>
>>> The Freescale sales representative we work with actually says that
>>> CPM2 USB host controller is working well.
>>
>>
>>
>> Of course they do. They say the same for the 850 and 823 :-(
>>
>> Best regards,
>>
>> Wolfgang Denk
>>
>
> Well I have USB host drivers for both 8xx & 82xx working.
>
> It was not a piece of cake exactly to get them to work
> but they seem to work fine even under heavy traffic.
>
> However I use them connected to a specific peripheral
> so I don't know how well they fare when used as a PC
> style USB host controller.
>
> YMMV
>
> Regards
>
> Pantelis
>
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>
--
=======================================
Guillaume Autran
Senior Software Engineer
MRV Communications, Inc.
Tel: (978) 952-4932 office
E-mail: gautran@mrv.com
=======================================
next prev parent reply other threads:[~2005-05-17 12:10 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-13 12:33 insmod problem Marco Schramel
2005-05-13 12:46 ` Pantelis Antoniou
2005-05-13 13:14 ` Mark Chambers
2005-05-13 13:46 ` Kumar Gala
2005-05-13 17:27 ` MPC885 - USB HCI drivers Guillaume Autran
2005-05-16 21:50 ` Kylo Ginsberg
2005-05-16 22:03 ` Wolfgang Denk
2005-05-16 22:39 ` Kylo Ginsberg
2005-05-16 22:52 ` Dan Malek
2005-05-17 8:28 ` Jonathan Masel
2005-05-16 23:27 ` Wolfgang Denk
2005-05-17 6:57 ` Mike Rapoport
2005-05-17 8:15 ` Wolfgang Denk
2005-05-17 8:07 ` Pantelis Antoniou
2005-05-17 9:58 ` Bryan O'Donoghue
2005-05-17 9:44 ` Pantelis Antoniou
2005-05-17 11:33 ` Mike Rapoport
2005-05-17 12:13 ` Guillaume Autran
2005-06-09 21:19 ` linux/drivers/net/fec_8xx/* vs. linux/arch/ppc/8xx_io/fec.c Guillaume Autran
2005-06-10 6:43 ` Pantelis Antoniou
2005-05-17 12:10 ` Guillaume Autran [this message]
2005-05-17 18:05 ` MPC885 - USB HCI drivers Kylo Ginsberg
2005-05-14 2:55 ` floating point in kernel (Re: insmod problem) Roger Larsson
-- strict thread matches above, loose matches on Subject: below --
2005-07-27 18:08 MPC885 - USB HCI drivers Bastos Fernandez Alexandre
2005-08-16 1:21 ` Adam Kent
2007-12-20 6:53 Jonathan Journo
2007-12-20 18:41 ` Vitaly Bordug
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=4289DF4F.4060301@mrv.com \
--to=gautran@mrv.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=panto@intracom.gr \
/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).