public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Kallol Biswas <kallol@nucleodyne.com>
To: "Ju, Seokmann" <sju@lsil.com>
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: RE: LSI Logic's Ultra320 320-4X RAID adapter
Date: 02 May 2005 09:17:37 -0700	[thread overview]
Message-ID: <1115050656.31377.4.camel@driver> (raw)
In-Reply-To: <0E3FA95632D6D047BA649F95DAB60E5703662836@exa-atlanta>

The system's PCI bridge is broken,  MEM Mapped IO does not work.

Only we can use IO mapped IO to access PCI devices(inb, outb) those are
behind the bridge.

I am looking for a LSI mega raid adapter (SCSI, SATA or SAS) that
supports IO mapped IO and has a  linux driver for it.



On Mon, 2005-05-02 at 05:56, Ju, Seokmann wrote:
> On Saturday, April 30, 2005 9:02 PM, Kallol wrote:
> > The memory space PCI register access can not be used.
> I'm not sure what this means. Can you please add more details on it?
> 
> > Question #1: Does 320-4X support IO Space device register access?
> No, the controller does not support IO mapped I/O.
> 
> > Question #2: Do we have a linux driver for it that supports 
> > IO ports also?
> Yes, to support LSI MegaRAID controllers (typically old controllers), driver
> on the 2.4 kernel supports I/O mapped I/O.
> 
> Thank you.
> 
> Seokmann
> LSI Logic Corporation.
> 
> > -----Original Message-----
> > From: kallol@nucleodyne.com [mailto:kallol@nucleodyne.com] 
> > Sent: Saturday, April 30, 2005 9:02 PM
> > To: linux-scsi@vger.kernel.org; linux-kernel@vger.kernel.org
> > Subject: LSI Logic's Ultra320 320-4X RAID adapter
> > 
> > 
> > 
> > Hello,
> >       We have been evaluting different IO adapters for a 
> > storage system vendor.
> > 
> > LSI logic's 320-4X RAID controller seems to be a good choice.
> > 
> > There is an issue with the system on which we are measuring 
> > performance.
> > The memory space PCI register access can not be used.
> > 
> > Question #1: Does 320-4X support IO Space device register access?
> > Question #2: Do we have a linux driver for it that supports 
> > IO ports also?
> > 
> > The megaraid linux driver seems to check the BAR0, if it is 
> > memory bar then mem
> > space is used otherwise IO space.
> > 
> > May be the adapter supporting memory space also support IO 
> > space access.
> > 
> > 
> > Thanks,
> > Kallol
> > -
> > To unsubscribe from this list: send the line "unsubscribe 
> > linux-scsi" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> > 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/


  reply	other threads:[~2005-05-02 16:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-02 12:56 LSI Logic's Ultra320 320-4X RAID adapter Ju, Seokmann
2005-05-02 16:17 ` Kallol Biswas [this message]
2005-05-03  3:32   ` Matt Domsch
  -- strict thread matches above, loose matches on Subject: below --
2005-05-01  1:02 kallol

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=1115050656.31377.4.camel@driver \
    --to=kallol@nucleodyne.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=sju@lsil.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox