public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert <robert.woerle-y2s3ugBAdl9BDgjK7y7TUQ@public.gmane.org>
To: Ducrot Bruno <ducrot-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
Cc: Pavel Machek <pavel-+ZI9xUNit7I@public.gmane.org>,
	kernel list
	<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	ACPI mailing list
	<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
	Robert Woerle <robert-fPtsKRK0pHxl57MIdRCFDg@public.gmane.org>
Subject: Re: [ACPI] PaceBlade broken acpi/memory map
Date: Tue, 25 Feb 2003 15:53:18 +0100	[thread overview]
Message-ID: <3E5B835E.7050601@symplon.com> (raw)
In-Reply-To: <20030225143505.GH13404-j6u/t2rXLliUoIHC/UFpr9i2O/JbrIOy@public.gmane.org>



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

>  
>

  parent reply	other threads:[~2003-02-25 14:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-20 17:21 PaceBlade broken acpi/memory map Pavel Machek
     [not found] ` <20030220172144.GA15016-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2003-02-24 16:42   ` [ACPI] " Ducrot Bruno
     [not found]     ` <20030224164209.GD13404-j6u/t2rXLliUoIHC/UFpr9i2O/JbrIOy@public.gmane.org>
2003-02-24 18:39       ` Pavel Machek
     [not found]         ` <20030224183955.GC517-jyMamyUUXNJG4ohzP4jBZS1Fcj925eT/@public.gmane.org>
2003-02-25 14:35           ` [ACPI] " Ducrot Bruno
     [not found]             ` <20030225143505.GH13404-j6u/t2rXLliUoIHC/UFpr9i2O/JbrIOy@public.gmane.org>
2003-02-25 14:53               ` Robert [this message]
     [not found]                 ` <3E5B835E.7050601-y2s3ugBAdl9BDgjK7y7TUQ@public.gmane.org>
2003-02-25 15:13                   ` Ducrot Bruno
     [not found]                     ` <20030225151341.GI13404-j6u/t2rXLliUoIHC/UFpr9i2O/JbrIOy@public.gmane.org>
2003-02-25 17:44                       ` Pavel Machek
     [not found]                         ` <20030225174449.GD12028-jyMamyUUXNJG4ohzP4jBZS1Fcj925eT/@public.gmane.org>
2003-02-25 20:09                           ` Ducrot Bruno
     [not found]                             ` <20030225200907.GJ13404-j6u/t2rXLliUoIHC/UFpr9i2O/JbrIOy@public.gmane.org>
2003-02-25 20:49                               ` Ducrot Bruno
     [not found]                                 ` <20030225204911.GK13404-j6u/t2rXLliUoIHC/UFpr9i2O/JbrIOy@public.gmane.org>
2003-02-26  9:39                                   ` [ACPI] " 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=3E5B835E.7050601@symplon.com \
    --to=robert.woerle-y2s3ugbadl9bdgjk7y7tuq@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=ducrot-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=pavel-+ZI9xUNit7I@public.gmane.org \
    --cc=robert-fPtsKRK0pHxl57MIdRCFDg@public.gmane.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