From: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
To: Jay Estabrook <Jay.Estabrook@compaq.com>
Cc: Kurt Garloff <garloff@suse.de>,
Jochen Friedrich <jochen@scram.de>,
linux-kernel@vger.kernel.org, Richard Henderson <rth@twiddle.net>
Subject: Re: Busmaster DMA broken in 2.4.18 on Alpha
Date: Mon, 11 Mar 2002 19:04:33 +0300 [thread overview]
Message-ID: <20020311190433.A16552@jurassic.park.msu.ru> (raw)
In-Reply-To: <Pine.NEB.4.33.0203111049580.1675-100000@www2.scram.de> <20020311124511.J2346@nbkurt.etpnet.phys.tue.nl> <20020311171058.A9038@jurassic.park.msu.ru> <20020311100200.A1181@linux04.mro.cpqcorp.net>
In-Reply-To: <20020311100200.A1181@linux04.mro.cpqcorp.net>; from Jay.Estabrook@compaq.com on Mon, Mar 11, 2002 at 10:02:00AM -0500
On Mon, Mar 11, 2002 at 10:02:00AM -0500, Jay Estabrook wrote:
> There are ISA cards, regardless of what ISA bus machine they are
> plugged into, that are able to generate only something less than
> 32-bits worth of address.
Indeed, I missed that.
> Since ISA devices don't have pci_dev structures, there's (currently)
> no way to pass an ISA device-dependent DMA mask to the IOMMU routines.
> Perhaps there needs to be an addition to the API that would allow
> for this (pci_set_isa_device_dma_mask()) ???
Yes, it would be nice to have something like this.
Another workaround also seems to be possible - for ISA devices
use mask other than 0x00ffffff _only_ if we don't have working
IOMMU. This doesn't help to get older Miatas work with such
type of ISA cards though...
Ivan.
next prev parent reply other threads:[~2002-03-11 18:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-11 9:57 Jochen Friedrich
2002-03-11 11:45 ` Kurt Garloff
2002-03-11 13:53 ` Jochen Friedrich
2002-03-11 14:10 ` Ivan Kokshaysky
2002-03-11 14:32 ` Jochen Friedrich
2002-03-11 15:02 ` Jay Estabrook
2002-03-11 15:45 ` Alan Cox
2002-03-11 16:04 ` Ivan Kokshaysky [this message]
2002-03-11 15:16 ` David S. Miller
2002-03-11 15:44 ` Jay Estabrook
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=20020311190433.A16552@jurassic.park.msu.ru \
--to=ink@jurassic.park.msu.ru \
--cc=Jay.Estabrook@compaq.com \
--cc=garloff@suse.de \
--cc=jochen@scram.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rth@twiddle.net \
/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
all inboxes | Powered by JetHome®