From: ebiederm@xmission.com (Eric W. Biederman)
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: torvalds@transmeta.com (Linus Torvalds),
beamz_owl@yahoo.com (Edward Spidre),
linux-kernel@vger.kernel.org (Kernel Mailing List)
Subject: Re: Possible PCI subsystem bug in 2.4
Date: 04 May 2001 09:41:51 -0600 [thread overview]
Message-ID: <m1hez1nmtc.fsf@frodo.biederman.org> (raw)
In-Reply-To: <E14vNsb-0005yf-00@the-village.bc.nu>
In-Reply-To: Alan Cox's message of "Thu, 3 May 2001 19:31:04 +0100 (BST)"
Alan Cox <alan@lxorguk.ukuu.org.uk> writes:
> > I suspect it would be safe to round up to the next megabyte, possibly up
> > to 64MB or so. But much more would make me nervous.
> > Any suggestions?
>
> I'd go for 1MByte simply because I've not seen an EBDA/NVRAM area that large
> stuck at the top of RAM. 1Mb would fix the Dell. (It was only when I saw
> your email it suddenely clicked and I grabbed the bootup log)
There are a couple of options here.
1) read the MTRRs unless the BIOS is braindead it will set up that area as
write-back. At any rate we shouldn't ever try to allocate a pci region
that is write-back cached.
2) read the memory locations from the northbridge. It's not possible
on every chipset (lack of documentation) but with the linuxBIOS
project we code for a couple of them, and we are working on more
all of the time.
Eric
next prev parent reply other threads:[~2001-05-04 15:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20010503140318.7583.qmail@web10704.mail.yahoo.com>
2001-05-03 17:08 ` Possible PCI subsystem bug in 2.4 Linus Torvalds
2001-05-03 17:51 ` Alan Cox
2001-05-03 18:12 ` Linus Torvalds
2001-05-03 18:22 ` Jeff Garzik
2001-05-03 18:31 ` Alan Cox
2001-05-04 15:41 ` Eric W. Biederman [this message]
2001-05-04 15:52 ` Alan Cox
2001-05-04 16:13 ` Eric W. Biederman
2001-05-04 17:04 ` Alan Cox
2001-05-05 5:41 ` Eric W. Biederman
2001-05-08 16:01 ` Maciej W. Rozycki
2001-05-09 15:45 ` Eric W. Biederman
2001-05-04 17:44 ` Linus Torvalds
2001-05-05 5:30 ` Eric W. Biederman
2001-05-05 7:17 ` Alan Cox
2001-05-04 11:34 ` Rogier Wolff
[not found] <20010503191655.67673.qmail@web10701.mail.yahoo.com>
2001-05-03 19:28 ` 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=m1hez1nmtc.fsf@frodo.biederman.org \
--to=ebiederm@xmission.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=beamz_owl@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.