All of lore.kernel.org
 help / color / mirror / Atom feed
From: Doug Maxey <dwm@austin.ibm.com>
To: linux-hotplug@vger.kernel.org
Subject: Question on 2.4.21 unusual_devs list.
Date: Tue, 09 Sep 2003 19:17:56 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-106314410824939@msgid-missing> (raw)

Greetings,

  I have an interesting situation with 2 different TEAC FD-05PUB-x59
  floppy drives.  The x59 designation is on the external device label,
  the two samples in my lab are -159 and -259.

  Both show the same descriptors, and both indicate they are C/B/I
  devices according to lsusb.

  However, depending on the value defined in the unusual_dev list,
  currently US_PR_CB, I can only get the older -159 drive to
  configure.

  If the unusual_devs list is edited to show the supported protocol as
  US_PR_CBI, and get the other device -259 configured, and not the
  other.

  This leads to my questions:

  1) What is the the signifigance of the unusual_devs list.  I am
     infering the list exists to provide a way to configure devices
     that do no precisely aggree with the protocol actually supported

  2) if a given device is in the unusual_devs list, how does one also
     define that it might show as the other, that is to say, correctly?

++doug


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

             reply	other threads:[~2003-09-09 19:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-09 19:17 Doug Maxey [this message]
2003-09-09 22:37 ` Question on 2.4.21 unusual_devs list Greg KH

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=marc-linux-hotplug-106314410824939@msgid-missing \
    --to=dwm@austin.ibm.com \
    --cc=linux-hotplug@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.