public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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 23:00:10 +0100	[thread overview]
Message-ID: <20040201230010.15874b4c.diemer@gmx.de> (raw)
In-Reply-To: <20040201212802.GA16301@kroah.com>

On Sun, 1 Feb 2004 13:28:03 -0800
Greg KH <greg@kroah.com> wrote:

> You mean "submit a urb and be notified when it was completed?"  I
> thought libusb supported that with signals.

Yeah, thats what I meant. In the html doc shipped with version 0.1.7,
it says "all functions in libusb v0.1 are synchronous, meaning the
functions block and wait for the operation to finish or timeout before
returning execution to the calling application. Asynchronous operation
will be supported in v1.0, but not v0.1."...


> What other way can a userspace library do this?  It doesn't take very
> long at all, what is the problem with this?

Well, I would have liked a lib-function like 
find_device(int vend_id,int prod_id);
but thats really not a big deal.

> 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 :)

Thanks for that hint, I'll have a look at it. I only need 1 val per
file, i.e. a "firmware" file, which I learned is best done with the
firmware_class.

>Good luck
Thanks

regards
Jonas

PS: CC me in replies, please.

  reply	other threads:[~2004-02-01 21:59 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
2004-02-01 22:00       ` Jonas Diemer [this message]
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=20040201230010.15874b4c.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