From: Bastos Fernandez Alexandre <ALEBAS@televes.com>
To: 'Pantelis Antoniou' <panto@intracom.gr>,
Bryan O'Donoghue <typedef@eircom.net>
Cc: linuxppc-embedded@ozlabs.org
Subject: RE: MPC885 - USB HCI drivers.
Date: Wed, 27 Jul 2005 20:08:00 +0200 [thread overview]
Message-ID: <51DB8827D393D411BB69003048003F4601B1C220@tvesntr> (raw)
Guys,
Finally, was the patch submitted to the list?
I have searched deeply both ozlabs and gmane, but I couldn't
find it ...
I have been disconnected from the list for several weeks (wedding holidays
:-) )
so I am a bit unplugged with all this stuff.
By now, I would apprece a lot this usb host driver for 82xx.
Thanks,
Alex BASTOS
> -----Original Message-----
> From: Pantelis Antoniou [SMTP:panto@intracom.gr]
> Sent: Tuesday, May 17, 2005 11:45 AM
> To: Bryan O'Donoghue
> Cc: linuxppc-embedded@ozlabs.org
> Subject: Re: MPC885 - USB HCI drivers.
>
> Bryan O'Donoghue wrote:
> > Pantelis Antoniou wrote:
> >
> >
> >>Well I have USB host drivers for both 8xx & 82xx working.
> >
> >
> > Speaking of which... would it not be a good idea, to get these comitted
> > to the 2.6 tree... at some stage ... at least to stop people
> > periodically posting to this list... saying "Dear all have spent 2
> > months, writing code for m8xx_hci drivers", when it's a needless
> > replication of effort ?
> >
>
> Well, they are too hideous for human eyes :)
>
> >
> >>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.
> >
> >
> > Also, one easy way to find out, how well or badly said code performs, in
> > hetrogenous environments, is to... suck it and see.
> >
> > As I was attempting to intimate above, I'm sure there'd be a legion of
> > eager people to debug, modify and recode such drivers, if there lived in
> > an obvious place... in the 2.6 tree.
> >
> > Just my EUR0.02.
> >
>
> Also they're 2.4 only :)
>
> I'll try to clean them up and post them sometime this week.
>
> But I don't have time left to hack them for 2.6. I'll need
> vict^H^H^Holunteers to do it...
>
> Regards
>
> Pantelis
>
>
> > --
> >
> > Best,
> > Bryan
> >
> >
>
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
next reply other threads:[~2005-07-27 18:08 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-27 18:08 Bastos Fernandez Alexandre [this message]
2005-08-16 1:21 ` MPC885 - USB HCI drivers Adam Kent
-- strict thread matches above, loose matches on Subject: below --
2007-12-20 6:53 Jonathan Journo
2007-12-20 18:41 ` Vitaly Bordug
2005-05-13 13:14 insmod problem 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-05-17 12:10 ` Guillaume Autran
2005-05-17 18:05 ` Kylo Ginsberg
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=51DB8827D393D411BB69003048003F4601B1C220@tvesntr \
--to=alebas@televes.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=panto@intracom.gr \
--cc=typedef@eircom.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.