public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Matthew Wilcox <matthew@wil.cx>
Cc: Randy Dunlap <randy.dunlap@oracle.com>, Jun Sun <jsun@junsun.net>,
	linux-scsi@vger.kernel.org, lkml <linux-kernel@vger.kernel.org>
Subject: Re: unchecked_isa_dma and BusLogic SCSI controller
Date: Thu, 2 Nov 2006 13:35:48 +0000	[thread overview]
Message-ID: <20061102133548.GA27715@infradead.org> (raw)
In-Reply-To: <20061102124128.GC31830@parisc-linux.org>

On Thu, Nov 02, 2006 at 05:41:28AM -0700, Matthew Wilcox wrote:
> On Wed, Nov 01, 2006 at 05:33:58PM -0800, Randy Dunlap wrote:
> >     unchecked_isa_dma - 1=>only use bottom 16 MB of ram (ISA DMA addressing
> >                    restriction), 0=>can use full 32 bit (or better) DMA
> >                    address space
> > 
> > > It is hard for me to see why BusLogic controller would only do DMA
> > > in low 16MB.  Is there a fix for this?
> > 
> > Does anyone know that controller hardware and its limitations?
> 
> I don't, but:
> 
> 		if (pci_set_dma_mask(PCI_Device, DMA_32BIT_MASK ))
> 			continue;
> 
> So somebody thinks the device can do 32-bit addressing.  I would expect
> that setting unchecked_isa_dma is a historical mistake.  However, I
> don't have any cards of this type to test.

The buslogic driver also supports non-PCI devices, and at least the
ISA boards have the obvious limitiation that unchecked_isa_dma = 1
caters to.  Now someone would have to audit the driver whether it's
enough to only set this on the actual isa hosts instead of the host
template.

      parent reply	other threads:[~2006-11-02 13:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20061101235330.GA30843@srv.junsun.net>
2006-11-02  1:33 ` unchecked_isa_dma and BusLogic SCSI controller Randy Dunlap
2006-11-02 12:41   ` Matthew Wilcox
2006-11-02 13:04     ` Maciej W. Rozycki
2006-11-02 13:35     ` Christoph Hellwig [this message]

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=20061102133548.GA27715@infradead.org \
    --to=hch@infradead.org \
    --cc=jsun@junsun.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=matthew@wil.cx \
    --cc=randy.dunlap@oracle.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