From: mgross <640e9920@gmail.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: [RFC] USB driver for talking to the Microchip PIC18 boot loader
Date: Sat, 29 Dec 2007 19:53:49 -0800 [thread overview]
Message-ID: <20071230035349.GA4741@mgross-t43> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0712291714041.26261-100000@netrider.rowland.org>
On Sat, Dec 29, 2007 at 05:15:30PM -0500, Alan Stern wrote:
> On Sat, 29 Dec 2007, mgross wrote:
>
> > I'm playing around with a PIC based project at home (not an Intel
> > activity) and found I needed a usb driver to talk to the boot loader
> > so I can program my USB Bitwhacker with new custom firmware. The
> > following adds the pic18bl driver to the kernel. Its pretty simple
> > and is somewhat based on bits of a libusb driver that does some of
> > what this driver does.
> >
> > What do you think?
>
> Not to detract from your driver, but would it be possible to do the
> whole thing in userspace using libusb? Maybe by extending the driver
> you mentioned?
>
Yeah, it has been done from user space using a libusb based
application. (that didn't work with a usb-hub in the loop) and had
code that was just too nasty for words, so I made a kernel driver that
looks nicer to me and enables a nice python FW loader program to work.
What is the linux-usb policies on new drivers that could be
implemented in user space? When does a kernel driver make sense over
a libusb one?
--mgross
next prev parent reply other threads:[~2007-12-30 3:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-29 19:34 mgross
2007-12-29 22:15 ` Alan Stern
2007-12-30 2:40 ` Xiaofan Chen
2007-12-30 4:29 ` mgross
2007-12-30 4:46 ` Xiaofan Chen
2007-12-31 1:15 ` Xiaofan Chen
2007-12-30 3:53 ` mgross [this message]
2007-12-30 4:52 ` Xiaofan Chen
2008-01-02 19:59 ` [RFC] libusb / in-kernel usb driver criteria (was: USB driver for talking to the Microchip PIC18 boot loader) Paulo Marques
2008-01-03 23:08 ` mgross
2008-01-11 17:10 ` [RFC] libusb / in-kernel usb driver criteria Greg KH
2008-01-11 21:38 ` David Brownell
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=20071230035349.GA4741@mgross-t43 \
--to=640e9920@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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
all inboxes | Powered by JetHome®