From: <benh@kernel.crashing.org>
To: "David S. Miller" <davem@redhat.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: <weber@nyc.rr.com>, <tom_gall@vnet.ibm.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: 2.5.4, cs46xx snd, and virt_to_bus
Date: Tue, 12 Feb 2002 15:49:16 +0100 [thread overview]
Message-ID: <20020212144916.1889@mailhost.mipsys.com> (raw)
In-Reply-To: <E16aeHN-00020H-00@the-village.bc.nu>
In-Reply-To: <E16aeHN-00020H-00@the-village.bc.nu>
>Would putting a range check and BUG() in the ISA macros for now help there.
>
>Reminds me - we have a request_mem_region problem to address that is sort
>of related to all this. Right now we reserve mem regions without knowing
>properly about ISA mappings. That means drivers are reserving stuff like
>0xD0000. Unfortunately on some non X86 boxes the ISA hole isnt at 640K-1M
>so it appears we want an isa_request_mem_region and friends to handle those
>platforms ?
>-
I'd rather provide a function to obtain the base address of the ISA hole,
while would also allow us to
- Return an error when it doesn't exist (a given kernel may or may not
have it depending on which box it's booted, it can't be a compile time
option)
- Eventually obtain a per-PCI bus ISA hole (the "legacy one" beeing
defined as bus or with a special constant) so multi domain machines
can use multiple VGA cards (eek eek ;)
With that, at least PPC don't require isa_xxx specific functions/macros
(but I can't tell about other archs).
Ben.
next prev parent reply other threads:[~2002-02-12 14:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.fefkfjv.rmid9f@ifi.uio.no>
2002-02-11 17:38 ` 2.5.4, cs46xx snd, and virt_to_bus John Weber
2002-02-11 18:10 ` Alan Cox
2002-02-12 2:43 ` David S. Miller
2002-02-12 14:51 ` Alan Cox
2002-02-12 14:49 ` benh [this message]
2002-02-12 14:50 ` benh
2002-02-14 6:36 ` Paul Gortmaker
2002-02-14 13:26 ` Alan Cox
2002-02-11 18:09 Tom Gall
2002-02-11 17:53 ` Alan Cox
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=20020212144916.1889@mailhost.mipsys.com \
--to=benh@kernel.crashing.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tom_gall@vnet.ibm.com \
--cc=weber@nyc.rr.com \
/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