From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "linux-os (Dick Johnson)" <linux-os@analogic.com>
Cc: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: linux-2.6.13 PCI bogus resource allocation
Date: Tue, 30 Aug 2005 17:52:12 +0100 [thread overview]
Message-ID: <1125420732.8276.34.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.61.0508301118590.4347@chaos.analogic.com>
On Maw, 2005-08-30 at 11:21 -0400, linux-os (Dick Johnson) wrote:
> we have been starting at 0x30001000. Now, with
> Linux-2.6.13, I see that PCI/Bus resources are
> being allocated on top of this RAM!!! This should
2.6.13 redoes the bus assignments which might have indeed made mem= do
totally the wrong thing in this case.
> not be. In my BIOS I always check for RAM before
> allocating PCI resources. It's trivial, write 0L, read
Not a very safe idea for general purpose systems. Its neither reliable
nor safe. Fortunately we also know the BIOS idea of where the device
resources are allocated so we know which bits either thinks are RAM and
which to avoid.
Alan
prev parent reply other threads:[~2005-08-30 16:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-30 15:21 linux-os (Dick Johnson)
2005-08-30 16:52 ` Alan Cox [this message]
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=1125420732.8276.34.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-os@analogic.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
Powered by JetHome