From: Thomas Hood <jdthoodREMOVETHIS@yahoo.co.uk>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] parport_pc.c PnP BIOS sanity check
Date: Fri, 21 Sep 2001 14:45:06 -0400 [thread overview]
Message-ID: <3BAB8AB2.C6DB27B0@yahoo.co.uk> (raw)
In-Reply-To: <Pine.LNX.4.33.0109210209520.21008-100000@terbidium.openservices.net>
Thanks for the replies.
I'd like to underline Alan Cox's reply that DMA0 _is_ usable.
In fact, my sound chip is configured to use DMA0.
If (and only if) parport _cannot_ use DMA0 for some reason
then the sanity check is justified. In that case I'd just ask
that a short comment be added to the code that gives the reason.
Cheers
Thomas
Ignacio Vazquez-Abrams wrote:
> DMA0 is reserved for memory refresh. It _can't_ be used for anything else,
> therefore a value of 0 is representative of no value whatsoever.
Alan Cox wrote:
> This has been unsafe since about 1995, when DMA 0 became available as PC's
> stopped using the ISA DMA engine for memory refresh (a very neat original PC
> hack)
Gunther Mayer wrote:
> 1)
> I think I saw some BIOS report DMA0 for "none" (could even have
> been ACPI which is returning PNP formatted legacy resource data).
> 2)
> I have never seen DMA0 for parport configured by a BIOS.
> 3)
> Try "lssuperio" if you want the real hardware thing.
>
> This qualifies the code as it is as a sanity check.
next prev parent reply other threads:[~2001-09-21 18:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-21 6:00 [PATCH] parport_pc.c PnP BIOS sanity check Thomas Hood
2001-09-21 6:11 ` Ignacio Vazquez-Abrams
2001-09-21 12:07 ` Alan Cox
2001-09-21 18:45 ` Thomas Hood [this message]
2001-09-22 0:08 ` Philip Blundell
2001-09-21 18:09 ` Gunther Mayer
-- strict thread matches above, loose matches on Subject: below --
2001-08-13 21:46 Thomas Hood
[not found] <no.id>
2001-08-08 15:20 ` Alan Cox
2001-08-08 16:13 ` Richard B. Johnson
2001-08-08 21:58 ` H. Peter Anvin
2001-08-08 22:12 ` Russell King
2001-08-10 9:18 ` Eric W. Biederman
2001-08-08 15:15 Thomas Hood
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=3BAB8AB2.C6DB27B0@yahoo.co.uk \
--to=jdthoodremovethis@yahoo.co.uk \
--cc=linux-kernel@vger.kernel.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