public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Matt Domsch <Matt_Domsch@dell.com>
To: hch@infradead.org, Alan Cox <alan@redhat.com>,
	linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
	akpm@osdl.org
Subject: Re: PATCH: Stop megaraid trashing other i960 based devices
Date: Sat, 22 May 2004 12:07:06 -0500	[thread overview]
Message-ID: <20040522170706.GA27386@lists.us.dell.com> (raw)
In-Reply-To: <20040522160718.GA8736@infradead.org>

On Sat, May 22, 2004 at 12:07:18PM -0400, hch@infradead.org wrote:
> On Sat, May 22, 2004 at 12:03:28PM -0400, Alan Cox wrote:
> > Most of the megaraids don't have subvendor ids... so that doesn't work at
> > all.
> 
> Okay.  In that case we should apply the patch and shoot some megraid
> hardware engineer.

Now, I love a good megaraid bashing as much as the next guy.  Just ask
Peter Jarrett and Atul Mukker.  But in this case I have to side with
them.  The cards w/o subsystem IDs all predate the existance of
subsystem IDs in the PCI spec, and I'm pretty sure the IDs in the i960
of that vintage are hard-coded so AMI couldn't have changed them if
they wanted to.  So their magic words were the equivalent of what we
now do with subsystem IDs.  It's only the older cards that have a
problem, AFAIK.

Thanks,
Matt

-- 
Matt Domsch
Sr. Software Engineer, Lead Engineer
Dell Linux Solutions linux.dell.com & www.dell.com/linux
Linux on Dell mailing lists @ http://lists.us.dell.com

       reply	other threads:[~2004-05-22 17:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20040522154659.GA17320@devserv.devel.redhat.com>
     [not found] ` <20040522160205.GA8643@infradead.org>
     [not found]   ` <20040522160328.GA22256@devserv.devel.redhat.com>
     [not found]     ` <20040522160718.GA8736@infradead.org>
2004-05-22 17:07       ` Matt Domsch [this message]
2004-05-22 17:11         ` PATCH: Stop megaraid trashing other i960 based devices Alan Cox
2004-05-22 17:11         ` hch

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=20040522170706.GA27386@lists.us.dell.com \
    --to=matt_domsch@dell.com \
    --cc=akpm@osdl.org \
    --cc=alan@redhat.com \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --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