From: Greg KH <greg@kroah.com>
To: Jonas Diemer <diemer@gmx.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Which interface: sysfs, proc, devfs?
Date: Sun, 1 Feb 2004 13:28:03 -0800 [thread overview]
Message-ID: <20040201212802.GA16301@kroah.com> (raw)
In-Reply-To: <20040201215721.737ef5a3.diemer@gmx.de>
On Sun, Feb 01, 2004 at 09:57:21PM +0100, Jonas Diemer wrote:
> On Thu, 29 Jan 2004 15:02:50 -0800
> Greg KH <greg@kroah.com> wrote:
>
> > What about not writing a kernel driver at all and just using
> > libusb/usbfs? Any reason you have to have a kernel driver for your
> > device?
>
>
> Well, I have just looked into libusb 0.1.x... I would like to have
> asynchronous (non-blocking) access to my device, which libusb doesn't
> currently support.
You mean "submit a urb and be notified when it was completed?" I
thought libusb supported that with signals.
> Also I don't like the way libusb finds devices - manually scanning all
> busses doesn't seem very handy.
What other way can a userspace library do this? It doesn't take very
long at all, what is the problem with this?
> Thus I will probably go for a kernel module, using sysfs to interface
> with the user. Thanks for all the help anyways-
Remember that sysfs is "1 value per file". If that works for your
device, then I suggest you look at the usbled driver, as that is a tiny
usb driver that only uses sysfs. Nothing like a 4kb kernel driver :)
Good luck,
greg k-h
next prev parent reply other threads:[~2004-02-01 21:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-29 21:28 Which interface: sysfs, proc, devfs? Jonas Diemer
2004-01-29 23:02 ` Greg KH
2004-01-30 9:54 ` Jonas Diemer
2004-02-01 20:57 ` Jonas Diemer
2004-02-01 21:28 ` Greg KH [this message]
2004-02-01 22:00 ` Jonas Diemer
2004-02-02 3:25 ` Greg KH
2004-02-02 6:59 ` Jonas Diemer
2004-02-02 7:50 ` Duncan Sands
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=20040201212802.GA16301@kroah.com \
--to=greg@kroah.com \
--cc=diemer@gmx.de \
--cc=linux-kernel@vger.kernel.org \
/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