From: DervishD <lkml@dervishd.net>
To: Johannes Erdfelt <johannes@erdfelt.com>
Cc: Oliver Neukum <oliver@neukum.org>,
Linux-kernel <linux-kernel@vger.kernel.org>,
linux-usb-users@lists.sourceforge.net
Subject: Re: USB API, ioctl's and libusb
Date: Thu, 27 Jan 2005 12:02:04 +0100 [thread overview]
Message-ID: <20050127110204.GA76@DervishD> (raw)
In-Reply-To: <20050126212411.GB21204@sventech.com>
Hi Johannes :)
* Johannes Erdfelt <johannes@erdfelt.com> dixit:
> On Wed, Jan 26, 2005, DervishD <lkml@dervishd.net> wrote:
> > * Oliver Neukum <oliver@neukum.org> dixit:
> > > You are supposed to use libusb.
> > That's irrelevant, the program I was trying to fix uses libusb.
> > My question is about the preferred kernel interface, 'cause I don't
> > know if it's the ioctl one or the URB one (well, I'm calling 'URB'
> > interface the API that is implemented using URB's inside the kernel).
> ioctl() calls are for userspace only.
I was pretty sure of that. My doubt was the other way round. I
was assuming that the functions in <linux/usb.h> were syscalls, that
they're not.
> It just so happens there is an ioctl() call that provides an URB like
> interface and an ioctl() call that provides a synchronous call to do
> a control message.
Didn't knew about that... Thanks a lot for the info!. Is there
any documentation available for the ioctl USB interface to the
kernel? Any API guide or something like that?
Thanks :)
Raúl Núñez de Arenas Coronado
--
Linux Registered User 88736
http://www.dervishd.net & http://www.pleyades.net/
It's my PC and I'll cry if I want to...
next prev parent reply other threads:[~2005-01-27 11:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-26 12:20 USB API, ioctl's and libusb DervishD
2005-01-26 13:40 ` Oliver Neukum
2005-01-26 16:38 ` DervishD
2005-01-26 21:24 ` Johannes Erdfelt
2005-01-27 11:02 ` DervishD [this message]
2005-01-27 22:08 ` Johannes Erdfelt
2005-01-28 10:22 ` DervishD
2005-01-26 22:15 ` [Linux-usb-users] " Alan Stern
2005-01-26 23:57 ` DervishD
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=20050127110204.GA76@DervishD \
--to=lkml@dervishd.net \
--cc=johannes@erdfelt.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-users@lists.sourceforge.net \
--cc=oliver@neukum.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.