public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adam Belay <ambx1@neo.rr.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PnP Fixes for 2.6.0-test5
Date: Wed, 24 Sep 2003 16:25:47 +0000	[thread overview]
Message-ID: <20030924162547.GA25424@neo.rr.com> (raw)
In-Reply-To: <1064230334.8592.7.camel@dhcp23.swansea.linux.org.uk>

On Mon, Sep 22, 2003 at 12:32:15PM +0100, Alan Cox wrote:
> On Sul, 2003-09-21 at 21:11, Adam Belay wrote:
> > # --------------------------------------------
> > # 03/09/21	ambx1@neo.rr.com	1.1357
> > # [PNP] remove DMA 0 restrictions
> > #
> > # The original argument for blocking DMA 0 was to avoid conflicts with
> > # "memory refresh"  but such configurations are only found on very old
> > # 8-bit systems that are likely not supported by the linux kernel.
>
> DMA0 is used by lots of 386/486 era systems for memory refresh. It is
> also "borrowed" by some other systems that know it isnt available to the
> OS. There are a couple of heuristics I've seen suggested by vendors of
> things like sound cards
>
> 1.	Check the PnPBIOS information (never looked into this myself)

Assuming the PnPBIOS provides this information through device nodes, the
current pnp code will ensure that dma 0 is not used.

> 2.	Assume DMA 0 is free if the machine has a PCI bus detected
> 3.	Read the DMA 0 counter a few times. If it is continually 	changing
> don't use DMA 0
>
> #2 is certainly a good idea IMHO, I don't know how well the others work.

Thanks, I'll look into these further.

Regards,
Adam

  reply	other threads:[~2003-09-24 20:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-21 20:09 [PATCH] PnP Fixes for 2.6.0-test5 Adam Belay
2003-09-21 20:10 ` Adam Belay
2003-09-21 20:10 ` Adam Belay
2003-09-21 20:11 ` Adam Belay
2003-09-22 11:32   ` Alan Cox
2003-09-24 16:25     ` Adam Belay [this message]
2003-09-21 20:11 ` Adam Belay
2003-09-21 20:12 ` Adam Belay
2003-09-21 20:12 ` Adam Belay
2003-09-21 20:13 ` Adam Belay

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=20030924162547.GA25424@neo.rr.com \
    --to=ambx1@neo.rr.com \
    --cc=alan@lxorguk.ukuu.org.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