From: Russell King <rmk+lkml@arm.linux.org.uk>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Linus Torvalds <torvalds@osdl.org>, Andi Kleen <ak@colin2.muc.de>,
Mika Penttil? <mika.penttila@kolumbus.fi>, Andi Kleen <ak@muc.de>,
David Hinds <dhinds@sonic.net>,
linux-kernel@vger.kernel.org
Subject: Re: PCI memory allocation bug with CONFIG_HIGHMEM
Date: Wed, 7 Jan 2004 09:31:43 +0000 [thread overview]
Message-ID: <20040107093143.A29200@flint.arm.linux.org.uk> (raw)
In-Reply-To: <m13casmk28.fsf@ebiederm.dsl.xmission.com>; from ebiederm@xmission.com on Tue, Jan 06, 2004 at 09:58:23PM -0700
On Tue, Jan 06, 2004 at 09:58:23PM -0700, Eric W. Biederman wrote:
> ffff0000-ffffffff : reserved
>
> That last reserved region is 64K. Which looking at the pci registers
> is technically correct at the moment. Only 64K happen to be decoded.
We already have this distinction between in use (or busy) resources and
allocated resources. Surely the BIOS ROM region should be an allocation
resource not a busy resource, so that the MTD driver can obtain a busy
resource against it?
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 PCMCIA - http://pcmcia.arm.linux.org.uk/
2.6 Serial core
next prev parent reply other threads:[~2004-01-07 9:31 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1aJdi-7TH-25@gated-at.bofh.it>
2004-01-06 3:32 ` PCI memory allocation bug with CONFIG_HIGHMEM Andi Kleen
2004-01-06 3:40 ` Linus Torvalds
2004-01-06 4:05 ` Andi Kleen
2004-01-06 5:04 ` Linus Torvalds
2004-01-06 8:12 ` Andi Kleen
2004-01-06 9:11 ` Mika Penttilä
2004-01-06 9:44 ` Andi Kleen
2004-01-06 10:16 ` Mika Penttilä
2004-01-06 10:49 ` Andi Kleen
2004-01-06 15:27 ` Linus Torvalds
2004-01-06 15:37 ` Andi Kleen
2004-01-06 15:48 ` Linus Torvalds
2004-01-06 22:29 ` Adam Belay
2004-01-07 4:06 ` Linus Torvalds
2004-01-07 5:02 ` Andi Kleen
2004-01-07 5:55 ` Dave Jones
2004-01-07 6:06 ` Linus Torvalds
2004-01-07 6:08 ` Dave Jones
2004-01-07 6:45 ` Linus Torvalds
2004-01-07 6:51 ` Andi Kleen
2004-01-07 2:43 ` Adam Belay
2004-01-07 8:32 ` Helge Hafting
2004-01-06 22:45 ` Eric W. Biederman
2004-01-07 0:06 ` Linus Torvalds
2004-01-07 4:58 ` Eric W. Biederman
2004-01-07 5:32 ` Linus Torvalds
2004-01-07 15:53 ` Eric W. Biederman
2004-01-07 16:32 ` Linus Torvalds
2004-01-07 17:32 ` Eric W. Biederman
2004-01-08 19:34 ` Eric W. Biederman
2004-01-07 9:31 ` Russell King [this message]
2004-01-07 15:06 ` Eric W. Biederman
2004-01-07 20:29 ` Russell King
2004-01-06 22:56 ` Eric W. Biederman
2004-01-05 20:07 David Hinds
2004-01-05 23:00 ` Russell King
2004-01-05 23:45 ` David Hinds
2004-01-06 0:36 ` Linus Torvalds
2004-01-06 0:44 ` David Hinds
2004-01-06 1:11 ` Linus Torvalds
2004-01-06 1:41 ` Linus Torvalds
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=20040107093143.A29200@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=ak@colin2.muc.de \
--cc=ak@muc.de \
--cc=dhinds@sonic.net \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.penttila@kolumbus.fi \
--cc=torvalds@osdl.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