All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Mansfield <patmans@us.ibm.com>
To: Andries.Brouwer@cwi.nl
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
	linux-usb-devel@lists.sourceforge.net,
	mdharm-kernel@one-eyed-alien.net, zwane@holomorphy.com
Subject: Re: IDs
Date: Tue, 7 Jan 2003 12:02:59 -0800	[thread overview]
Message-ID: <20030107120259.A16280@beaverton.ibm.com> (raw)
In-Reply-To: <UTC200301071854.h07IsBH22403.aeb@smtp.cwi.nl>; from Andries.Brouwer@cwi.nl on Tue, Jan 07, 2003 at 07:54:11PM +0100

On Tue, Jan 07, 2003 at 07:54:11PM +0100, Andries.Brouwer@cwi.nl wrote:

> > If we had a complete white/black list of devices with/without a unique id,
> > there would be no ambiguity.
> 
> You mean for the devices on the white list.
> But most devices will not be on the white list.

I mean if it is not on the white list, treat it as black listed or ask
for user/admin input, so we safely handle the id.

> Our perceptions differ, I think. My impression is that chaos
> is the norm, and well-behaved devices are the exception.

For usb storage, cd's, and cheap storage yes, chaos.

> As you say - we can make a best effort and get a string that
> with some luck identifies the device uniquely. But no guarantees
> given.

Yep.

> Maybe that again means that the S/Z distinction can be dropped.

We still want to tell page 0x83 (starts with a number) from page 0x80
(currently starts with S) from default values (currently starts with Z).
Dropping the Z in favour of an empty string would be good.

-- Patrick Mansfield

  reply	other threads:[~2003-01-07 20:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-07 18:54 IDs Andries.Brouwer
2003-01-07 18:54 ` IDs Andries.Brouwer
2003-01-07 20:02 ` Patrick Mansfield [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-01-07 10:55 IDs Andries.Brouwer
2003-01-07 18:02 ` IDs Patrick Mansfield
2003-01-07 18:02   ` IDs Patrick Mansfield
2003-01-07  2:19 IDs Andries.Brouwer
2003-01-07  3:15 ` IDs Patrick Mansfield
2003-01-07  0:00 IDs Andries.Brouwer
2003-01-07  0:00 ` IDs Andries.Brouwer
2003-01-07  2:13 ` IDs Patrick Mansfield
2001-09-29 19:00 IDs Tim Jansen
2001-09-29 19:56 ` IDs Vojtech Pavlik

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=20030107120259.A16280@beaverton.ibm.com \
    --to=patmans@us.ibm.com \
    --cc=Andries.Brouwer@cwi.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=mdharm-kernel@one-eyed-alien.net \
    --cc=zwane@holomorphy.com \
    /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.