linux-kernel - Re: [RFC] USB driver for talking to the Microchip PIC18 boot loader

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <a276da400712292052h5808c33apd5269e773edfb592@mail.gmail.com>
Date:	Sun, 30 Dec 2007 12:52:55 +0800
From:	"Xiaofan Chen" <xiaofanc@...il.com>
To:	mgross <640e9920@...il.com>
Cc:	"Alan Stern" <stern@...land.harvard.edu>,
	linux-kernel@...r.kernel.org, linux-usb@...r.kernel.org
Subject: Re: [RFC] USB driver for talking to the Microchip PIC18 boot loader

On Dec 30, 2007 11:53 AM, mgross <640e9920@...il.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/