From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Merging device drivers to LK tree
Date: Wed, 15 Mar 2017 07:46:24 +0800 [thread overview]
Message-ID: <20170314234624.GC19475@kroah.com> (raw)
In-Reply-To: <30912.1489526052@turing-police.cc.vt.edu>
On Tue, Mar 14, 2017 at 05:14:12PM -0400, valdis.kletnieks at vt.edu wrote:
> On Tue, 14 Mar 2017 21:59:20 +0100, Bj?rn Mork said:
>
> > And another one:
> >
> > 5.) vendor independent class drivers
> >
> >
> > IMHO perfect for the independent developer since there will be
> > documentation available. The USB class specs are freely available for
> > example.
>
> Hmm... /sys/class has a bunch of stuff already.
/sys/class has nothing to do with a USB class specification :)
> How many class drivers
> are missing from there? And more importantly, class drivers for a hardware
> class that's actually available (i.e. neither extinct or not shipping yet)?
A USB "class" is a set of devices that follow a published specification.
Like a USB HID device (keyboard/mouse/etc.) These are all published on
the usb.org website. I think there still are a few class specs that are
not yet implemented on Linux, usually because no one actually made any
devices for them, or not enough that anyone really cares.
A /sys/class/ entry is a kernel subsystem that describes a set of
devices that interact with userspace in a defined way. Like an "input"
class. That is how userspace interacts with _all_ keyboards, be they
USB or PS/2 or i2c or whatever.
Hope this helps,
greg k-h
prev parent reply other threads:[~2017-03-14 23:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-13 20:21 Merging device drivers to LK tree alexhoppus
2017-03-13 21:45 ` Greg KH
2017-03-14 19:54 ` alexhoppus
2017-03-14 20:37 ` valdis.kletnieks at vt.edu
2017-03-14 20:59 ` Bjørn Mork
2017-03-14 21:14 ` valdis.kletnieks at vt.edu
2017-03-14 23:46 ` Greg KH [this message]
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=20170314234624.GC19475@kroah.com \
--to=greg@kroah.com \
--cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).