public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjanv@redhat.com>
To: "Justin T. Gibbs" <gibbs@scsiguy.com>
Cc: Eric Kerin <eric@bootseg.com>, linux-scsi@vger.kernel.org
Subject: Re: [PATCH] 2.6.0 aic7xxx and aic79xx stale pci_device list entry
Date: Fri, 30 Jan 2004 09:41:50 -0500	[thread overview]
Message-ID: <1075473710.4272.2.camel@laptop.fenrus.com> (raw)
In-Reply-To: <2228980000.1075440305@aslan.btc.adaptec.com>

[-- Attachment #1: Type: text/plain, Size: 1001 bytes --]

On Fri, 2004-01-30 at 00:25, Justin T. Gibbs wrote:
> > <snip the rest>
> > -----------------
> > 
> > There are 2 reasons to work this way, and I would very much prefer the
> > adaptec drivers to behave like this:
> > 1) PCI Hotplugging
> > 2) Adding PCI ID's at runtime
> > 
> > While you may not care about 1), a lot of IHV/distros care about 2); eg if
> > Adaptec puts out a card that can be driven by aic79xx but with just a new
> > PCI ID, hardware vendors can just add the ID at runtime and have it work in
> > the (factory) installer etc but only *if the driver is loaded* ....
> 
> Well, if you look at the Adaptec drivers, they already attach to all
> possible IDs for the chips that are supported.  They do this by registering
> a very generic PCI ID table and filtering all requests through their
> own tables.  

May I ask why this is done? It sounds not the right thing that needs all
kinds of special cases in the OS userland...

Greetings,
    Arjan van de Ven

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-01-30 14:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-02 20:50 [PATCH] 2.6.0 aic7xxx and aic79xx stale pci_device list entry Eric Kerin
2004-01-03  9:01 ` Arjan van de Ven
2004-01-03 11:12   ` Eric Kerin
2004-01-03 13:59     ` Jan-Benedict Glaw
2004-01-24 16:09     ` Eric Kerin
2004-01-03 22:24   ` Justin T. Gibbs
2004-01-04 10:04     ` Arjan van de Ven
2004-01-30  5:25       ` Justin T. Gibbs
2004-01-30 14:41         ` Arjan van de Ven [this message]
2004-01-30 15:03           ` Justin T. Gibbs
2004-01-03 22:24 ` Justin T. Gibbs

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=1075473710.4272.2.camel@laptop.fenrus.com \
    --to=arjanv@redhat.com \
    --cc=eric@bootseg.com \
    --cc=gibbs@scsiguy.com \
    --cc=linux-scsi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox