From: Jonas Diemer <diemer@gmx.de>
To: unlisted-recipients:; (no To-header on input)
Cc: linux-kernel@vger.kernel.org
Subject: Re: Which interface: sysfs, proc, devfs?
Date: Sun, 1 Feb 2004 21:57:21 +0100 [thread overview]
Message-ID: <20040201215721.737ef5a3.diemer@gmx.de> (raw)
In-Reply-To: <20040129230250.GA9988@kroah.com>
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. Also I don't like the way libusb finds devices -
manually scanning all busses doesn't seem very handy.
Thus I will probably go for a kernel module, using sysfs to interface
with the user. Thanks for all the help anyways-
regards
Jonas
next prev parent reply other threads:[~2004-02-01 20:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-29 21:28 Jonas Diemer
2004-01-29 23:02 ` Greg KH
2004-01-30 9:54 ` Jonas Diemer
2004-02-01 20:57 ` Jonas Diemer [this message]
2004-02-01 21:28 ` Greg KH
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=20040201215721.737ef5a3.diemer@gmx.de \
--to=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
Powered by JetHome