From: Arnd Bergmann <arnd@arndb•de>
To: avorontsov@ru•mvista.com
Cc: dbrownell@users•sourceforge.net,
linux-usb-devel@lists•sourceforge.net, gregkh@suse•de,
linuxppc-dev@ozlabs•org, mike@compulab•co.il
Subject: Re: CPM2 USB host driver
Date: Fri, 30 Nov 2007 23:32:20 +0100 [thread overview]
Message-ID: <200711302332.21864.arnd@arndb.de> (raw)
In-Reply-To: <20071130161136.GA27760@localhost.localdomain>
(Cc:'ing linux-usb-devel)
On Friday 30 November 2007, Anton Vorontsov wrote:
> As for FHCI driver, it's not that big (6100 lines host patch + 3516
> lines usbgadget patch), but since usb subsystem changed: you have to
> know all the changes (or to look them up) and blindly follow them. Or
> start from scratch with FHCI/cpm2usb as the reference, thus evolve
> into Linux USB expert one day.
6100 lines means it's still the second-largest hcd driver in the kernel,
only drivers/usb/host/u132-hcd.c has even more.
> Today, I think I would choose the second option. Definitely more
> fun, and most probably quicker to progress. Though, I repeat,
> I didn't look into cpm2usb project.
My experience with other drivers moved into the kernel is that you
end up rewriting it completely anyway. I can also recommend starting
from scratch, and taking one of the in-kernel drivers as an example.
Maybe Greg or David can give you a suggestion which one of them
serves as the best example for a new host driver.
Arnd <><
next prev parent reply other threads:[~2007-11-30 22:32 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 [this message]
2007-11-30 23:18 ` David Brownell
2007-12-02 6:31 ` Mike Rapoport
2007-11-30 13:02 ` 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=200711302332.21864.arnd@arndb.de \
--to=arnd@arndb$(echo .)de \
--cc=avorontsov@ru$(echo .)mvista.com \
--cc=dbrownell@users$(echo .)sourceforge.net \
--cc=gregkh@suse$(echo .)de \
--cc=linux-usb-devel@lists$(echo .)sourceforge.net \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=mike@compulab$(echo .)co.il \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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