From: Vitaly Bordug <vitb@kernel.crashing.org>
To: Laurent Pinchart <laurentp@cse-semaphore.com>
Cc: linuxppc-dev@ozlabs.org, mike@compulab.co.il
Subject: Re: CPM2 USB host driver
Date: Fri, 30 Nov 2007 16:02:21 +0300 [thread overview]
Message-ID: <20071130160221.583f8727@kernel.crashing.org> (raw)
In-Reply-To: <200711301330.25100.laurentp@cse-semaphore.com>
On Fri, 30 Nov 2007 13:30:18 +0100
Laurent Pinchart wrote:
> On Friday 30 November 2007 12:16, Vitaly Bordug wrote:
> > On Fri, 30 Nov 2007 11:45:49 +0100
> >
> > Laurent Pinchart wrote:
> > > Hi everybody,
> > >
> > > Linux USB host support for the CPM, CPM2 and CPM2 pro is far from
> > > complete. Many people showed interest on this list (and on
> > > linuxppc-embedded) in the past, but nobody managed to complete a
> > > driver and get it merged.
> >
> > that is mainly because of its semi-software nature. However, any
> > approach would be helpful I beleive.
>
> The CPM/CPM2 USB host controller does indeed put some pressure on the
> CPU. The PowerQuick III family is much better in that respect as its
> USB host controller is EHCI compliant.
>
> We plan to use an external USB host controller when we will redesign
> the hardware. My goal in writting a CPM2 USB host driver is mainly to
> enable the hardware team to perform EMC testing on the USB interface.
> I don't expect it to be shipped to any client, but I'd still like to
> get it merged (if I complete the project) as I don't like throwing
> away useful code.
>
> > > As I need USB host support on my MPC8248 (CPM2), I decided to
> > > scratch the itch and try to get a working driver that could be
> > > merged upstream. This mail describes my plans to make sure the
> > > code I write will be useful for other people.
> > >
> > > The driver will be based on the cpm2usb project
> > > (http://cpm2usb.sf.net/). As I don't own any CPM1-based platform,
> > > I will convert the driver to use the CPM2 transaction-level
> > > interface, thus making it incompatible with the CPM1. CPM1
> > > support could be added back later. There is no planned release
> > > date, and more urgent projects could put this development on hold.
> > >
> > > Comments are welcome (and contributions too, especially in the
> > > form of a working driver :-)).
> >
> > I may have some WIP material left, will try to dig it out...
>
> Should I wait ?
>
Dunno. It was about 3 years ago so the chance is small.
--
Sincerely, Vitaly
prev parent reply other threads:[~2007-11-30 13:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-30 10:45 CPM2 USB host driver Laurent Pinchart
2007-11-30 11:16 ` Vitaly Bordug
2007-11-30 12:30 ` Laurent Pinchart
2007-11-30 12:48 ` Anton Vorontsov
2007-11-30 13:00 ` Vitaly Bordug
2007-11-30 15:28 ` Laurent Pinchart
2007-11-30 16:11 ` Anton Vorontsov
2007-11-30 22:32 ` Arnd Bergmann
2007-11-30 23:18 ` David Brownell
2007-12-02 6:31 ` Mike Rapoport
2007-11-30 13:02 ` Vitaly Bordug [this message]
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=20071130160221.583f8727@kernel.crashing.org \
--to=vitb@kernel.crashing.org \
--cc=laurentp@cse-semaphore.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=mike@compulab.co.il \
/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).