From: "Xiaofan Chen" <xiaofanc@gmail.com>
To: mgross <640e9920@gmail.com>
Cc: "Alan Stern" <stern@rowland.harvard.edu>,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: [RFC] USB driver for talking to the Microchip PIC18 boot loader
Date: Sun, 30 Dec 2007 12:52:55 +0800 [thread overview]
Message-ID: <a276da400712292052h5808c33apd5269e773edfb592@mail.gmail.com> (raw)
In-Reply-To: <20071230035349.GA4741@mgross-t43>
On Dec 30, 2007 11:53 AM, mgross <640e9920@gmail.com> wrote:
> 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.
http://forum.microchip.com/tm.aspx?m=275422&mpage=2
Just a guess why it does not work: this might be due to the auto-suspend.
If you update your kernel, it should be ok. The firmware is also to blame.
> 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?
>
That would be interesting to know.
Xiaofan
next prev parent reply other threads:[~2007-12-30 4:53 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
2007-12-30 4:52 ` Xiaofan Chen [this message]
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=a276da400712292052h5808c33apd5269e773edfb592@mail.gmail.com \
--to=xiaofanc@gmail.com \
--cc=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®