9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Nigel Roles" <nigel@9fs.org>
To: <9fans@cse.psu.edu>
Subject: RE: [9fans] USB weirdness.
Date: Wed, 15 Jan 2003 21:33:45 +0000	[thread overview]
Message-ID: <HOEHIDJJJINMLFPOLFJCKEKACJAA.nigel@9fs.org> (raw)
In-Reply-To: <200301152111.h0FLBCw21088@augusta.math.psu.edu>

No, that's quite likely. If the device class of the device descriptor
is set to 0, so will be the subclass, and most likely the protocol. It
indicates that the real information is within the configuration.

As it says in Table 9-7 of USB 1,1:

	If this field is reset to zero, each interface
	within a configuration specifies its own
	class information and the various
	interfaces operate independently.

Configurations represent different operating modes of a device; this
is often used to have a device which has behaviour according to the
standard, and a proprietary mode as well. Quite a lot of proprietary
devices pass the buck to the configuration descriptor.

Unfortunately, the Plan 9 arrangements don't express alternate
configurations.

-----Original Message-----
From: 9fans-admin@cse.psu.edu [mailto:9fans-admin@cse.psu.edu]On Behalf
Of Dan Cross
Sent: 15 January 2003 21:11
To: 9fans@cse.psu.edu
Subject: [9fans] USB weirdness.


When scanning USB status files, I see a lot of ``Enabled 0x000000''.
Surely the vendor/class/device strings really *aren't* all zero's;
has anyone else seen this?

	- Dan C.



  reply	other threads:[~2003-01-15 21:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-15 21:11 Dan Cross
2003-01-15 21:33 ` Nigel Roles [this message]
2003-01-15 22:00   ` Dan Cross

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=HOEHIDJJJINMLFPOLFJCKEKACJAA.nigel@9fs.org \
    --to=nigel@9fs.org \
    --cc=9fans@cse.psu.edu \
    /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).