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: Thu, 29 Jan 2004 15:02:50 -0800 [thread overview]
Message-ID: <20040129230250.GA9988@kroah.com> (raw)
In-Reply-To: <20040129222813.3b22b2c8.diemer@gmx.de>
On Thu, Jan 29, 2004 at 10:28:13PM +0100, Jonas Diemer wrote:
> Hi!
>
> I am writing a driver for an usb microcontroller (ezusb), which will be
> used for measuring and controlling. I am confused on which interface to
> use though. The driver is for kernel 2.6.x.
> I want to send small (human readable) commends as well as data (e.g.
> firmware) to the device. Which filesystem is appropriate?
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?
thanks,
greg k-h
next prev parent reply other threads:[~2004-01-29 23:02 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 [this message]
2004-01-30 9:54 ` Jonas Diemer
2004-02-01 20:57 ` Jonas Diemer
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=20040129230250.GA9988@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.