mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: Jay.Estabrook@compaq.com
Cc: ink@jurassic.park.msu.ru, garloff@suse.de, jochen@scram.de,
	linux-kernel@vger.kernel.org, rth@twiddle.net
Subject: Re: Busmaster DMA broken in 2.4.18 on Alpha
Date: Mon, 11 Mar 2002 07:16:56 -0800 (PST)	[thread overview]
Message-ID: <20020311.071656.15433588.davem@redhat.com> (raw)
In-Reply-To: <20020311100200.A1181@linux04.mro.cpqcorp.net>
In-Reply-To: <20020311124511.J2346@nbkurt.etpnet.phys.tue.nl> <20020311171058.A9038@jurassic.park.msu.ru> <20020311100200.A1181@linux04.mro.cpqcorp.net>

   From: Jay Estabrook <Jay.Estabrook@compaq.com>
   Date: Mon, 11 Mar 2002 10:02:00 -0500
   
   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()) ???

What you could do currently is whip up a dummy pci_dev structure with
the mask you want and pass that into the PCI dma routines.  So you
could, for example, default to 24-bit DMA mask when you get "NULL"
as pci_dev, but cook up a special one using a 32-bit DMA mask for the
floppy ISA device in question.

The idea in 2.5.x is to move to a generic struct device, at which time
something like this can be done much more cleanly.

  parent reply	other threads:[~2002-03-11 15:23 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
2002-03-11 15:16     ` David S. Miller [this message]
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=20020311.071656.15433588.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=Jay.Estabrook@compaq.com \
    --cc=garloff@suse.de \
    --cc=ink@jurassic.park.msu.ru \
    --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®