public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Janusz Krzysztofik <jkrzyszt@tis.icnet.pl>
To: "Ju, Seokmann" <Seokmann.Ju@lsil.com>
Cc: akpm@osdl.org, James.Bottomley@steeleye.com, linux-scsi@vger.kernel.org
Subject: Re: [patch 18/24] megaraid: Dell CERC ATA100/4ch support
Date: Wed, 27 Sep 2006 12:39:15 +0200	[thread overview]
Message-ID: <451A54D3.5090302@tis.icnet.pl> (raw)
In-Reply-To: <890BF3111FB9484E9526987D912B261932E347@NAMAIL3.ad.lsil.com>

Ju, Seokmann wrote:
> Hi,
> On Tuesday, August 15, 2006 2:10 AM, Janusz Krzysztofik wrote:
>> Add CERC subsystem ids to the old megaraid driver.  Tested, works.
> NACK - This addition will create PCI ID overlapping with megaraid_{mbox,mm} module under driver/scsi/megaraid.
> Since 2.6.16, we have removed some IDs in the megaraid module under driver/scsi to address ID overlappijng issue.
> Please switch to megaraid_{mbox,mm} module for the controller support. megaraid module under driver/scsi is dedicated to very old products.
> 
> Seokmann

Hi,

Dell CECR ATA100/4ch does not work with the new megaraid_mbox driver for 
me. The adapter is recognized, but it does not show any virtual nor 
physical drives. I have no skills to correct the problem. Furthermore, I 
have found some comments on this hardware no longer supported by Dell, 
RedHat, etc.

Will you accept a patch that limits PCI IDs with VID=101E, DID=1960 and 
SSVID=1028 in the new driver to exactly three models specified in its 
source file comments and, on the other hand, adds PCI ID of Dell CERC 
ATA100/4ch to the old driver?

Janusz


  reply	other threads:[~2006-09-27 10:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-15 14:19 [patch 18/24] megaraid: Dell CERC ATA100/4ch support Ju, Seokmann
2006-09-27 10:39 ` Janusz Krzysztofik [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-09-27 13:48 Ju, Seokmann
2006-09-27 16:25 ` Janusz Krzysztofik
2006-10-25 13:58   ` Janusz Krzysztofik
2006-08-15  6:09 akpm

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=451A54D3.5090302@tis.icnet.pl \
    --to=jkrzyszt@tis.icnet.pl \
    --cc=James.Bottomley@steeleye.com \
    --cc=Seokmann.Ju@lsil.com \
    --cc=akpm@osdl.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