From: Arjan van de Ven <arjan@infradead.org>
To: Robert Hancock <hancockr@shaw.ca>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Marcelo Tosatti <marcelo@kvack.org>
Subject: Re: [PATCH] introduce config option to disable DMA zone on i386
Date: Thu, 28 Dec 2006 19:37:20 +0100 [thread overview]
Message-ID: <1167331040.3281.4363.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <45940E3F.1050506@shaw.ca>
On Thu, 2006-12-28 at 12:34 -0600, Robert Hancock wrote:
Hi,
> > since one gets random corruption if a user gets this wrong, at least
> > make things like floppy and all CONFIG_ISA stuff conflict with this
> > option.... without that your patch feels like a walking time bomb...
> > (and please include all PCI drivers that only can do 24 bit or 28bit
> > or .. non-32bit dma as well)
>
> That sounds like a bug if this can happen. Drivers should be failing to
> initialize if they can't set the proper DMA mask, and the DMA API calls
> should be failing if the requested DMA mask can't be provided.
...but Marcelo's patch doesn't implement anything of that kind....
In addition, many ISA bus drivers do not use the DMA API *at all*
currently. If you want to fix them all up, great! But somehow I doubt
those will get fixed in the next decade.. they've been like this for at
least half a decade or longer :-)
Greetings,
Arjan van de Ven
--
if you want to mail me at work (you don't), use arjan (at) linux.intel.com
Test the interaction between Linux and your BIOS via http://www.linuxfirmwarekit.org
next prev parent reply other threads:[~2006-12-28 18:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.Nb4Y/frBNPmoag6ZL4pL3qEyDOs@ifi.uio.no>
[not found] ` <fa.XVmR+7tQ0v2oWVb7eyfQ8pGFhp8@ifi.uio.no>
2006-12-28 18:34 ` Robert Hancock
2006-12-28 18:37 ` Arjan van de Ven [this message]
2006-12-28 20:14 ` Robert Hancock
2006-12-28 17:03 Marcelo Tosatti
2006-12-28 17:30 ` Paul Mundt
2006-12-28 17:43 ` Arjan van de Ven
2006-12-28 18:36 ` Jan Engelhardt
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=1167331040.3281.4363.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=hancockr@shaw.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@kvack.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
all inboxes | Powered by JetHome®