All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tyler Hall <tyler_hall@sympatico.ca>
To: linux-kernel@vger.kernel.org
Subject: device classes in sysfs
Date: Thu, 01 Jan 2004 01:12:12 +0000	[thread overview]
Message-ID: <3FF373EC.3000207@sympatico.ca> (raw)

Has there ever been any discussion about classifying devices according 
to their function, and providing an interface (say with libsysfs) for 
user apps to enumerate a particular class? The new udev project _does_ 
provide the nice feature of persistent naming of a given device that can 
change positions on a bus (like 2 USB printers that change USB ports), 
but what about hunting for devices that provide the same function that 
can exist on any bus (like 1 parallel port printer and 1 USB printer)?

_After_ devices are configured and assigned names, users can depend on 
udev and friends to provide the same name to their devices. But _before_ 
the devices are initially configured, users (rather, writers of user 
apps) have to pull some special hacks to scan buses or dig deep into 
/proc to find what devices provide some target function (like printing).

I see /sys/class, but that seems more defined as "hardware architecture" 
class rather than "function" class.

Any opinions?

Tyler


                 reply	other threads:[~2004-01-01  1:11 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3FF373EC.3000207@sympatico.ca \
    --to=tyler_hall@sympatico.ca \
    --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.