From: Ducrot Bruno <ducrot@poupinou.org>
To: Robert <robert.woerle@symplon.com>
Cc: Ducrot Bruno <ducrot@poupinou.org>, Pavel Machek <pavel@ucw.cz>,
kernel list <linux-kernel@vger.kernel.org>,
ACPI mailing list <acpi-devel@lists.sourceforge.net>,
Robert Woerle <robert@paceblade.com>
Subject: Re: [ACPI] PaceBlade broken acpi/memory map
Date: Tue, 25 Feb 2003 16:13:41 +0100 [thread overview]
Message-ID: <20030225151341.GI13404@poup.poupinou.org> (raw)
In-Reply-To: <3E5B835E.7050601@symplon.com>
On Tue, Feb 25, 2003 at 03:53:18PM +0100, Robert wrote:
>
>
> Ducrot Bruno schrieb:
>
> >On Mon, Feb 24, 2003 at 07:39:55PM +0100, Pavel Machek wrote:
> >
> >
> >>Hi!
> >>
> >>
> >>
> >>>>I have PaceBlade here, and its memory map is wrong, which leads to
> >>>>ACPI refusing to load. [It does not mention "ACPI data" in the memory
> >>>>map at all!]
> >>>>
> >>>>
> >>>I have made those patches to workaround that. I have no time
> >>>
> >>>
> >>Yes, I have seen those... I also made a patch that enables you to do
> >>that workaround from mem= options at kernel command line.
> >>
> >>
> >>
> >
> >I doubt you received the latest one, since I have not make it public
> >unless this day.
> >
> >
> i did sent it to him since he recieved our machine from Suse Nuernberg
>
Ah, OK. Wasn't aware of that. But why then making a mem= opitons in
that case. I have take care to *not* use any mem= at all because that
can make things worse.
--
Ducrot Bruno
-- Which is worse: ignorance or apathy?
-- Don't know. Don't care.
next prev parent reply other threads:[~2003-02-25 15:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-20 17:21 Pavel Machek
2003-02-24 16:42 ` [ACPI] " Ducrot Bruno
2003-02-24 18:39 ` Pavel Machek
2003-02-25 14:35 ` Ducrot Bruno
2003-02-25 14:53 ` Robert
2003-02-25 15:13 ` Ducrot Bruno [this message]
2003-02-25 17:44 ` Pavel Machek
2003-02-25 20:09 ` Ducrot Bruno
2003-02-25 20:49 ` Ducrot Bruno
2003-02-26 9:39 ` Pavel Machek
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=20030225151341.GI13404@poup.poupinou.org \
--to=ducrot@poupinou.org \
--cc=acpi-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=robert.woerle@symplon.com \
--cc=robert@paceblade.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
all inboxes | Powered by JetHome®