From: Robert <robert.woerle-y2s3ugBAdl9BDgjK7y7TUQ@public.gmane.org>
To: Ducrot Bruno <ducrot-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: could not map ACPI
Date: Wed, 22 Jan 2003 16:03:29 +0100 [thread overview]
Message-ID: <3E2EB2C1.1010206@symplon.com> (raw)
In-Reply-To: <20030122142525.GA18109-j6u/t2rXLliUoIHC/UFpr9i2O/JbrIOy@public.gmane.org>
>
>Well, normally bios inform the OS that the ACPI data region is for
>the usage of ACPI, and is located in the 'normal' RAM, no?
>Well, it's right also to thing that OSPM can tell then that
>regions marked as 'ACPI data' can be used for normal RAM usage.
>Perhaps Redmonds OS do that?
>
>Well, well. I will look if we can (in general, not your perticuliar
>problem) use the ACPI data memory when we know that we can
>use them.
>
>Back to your trouble:
>Fortunately, we can add a e820 entry in arch/i386/kernel/setup.c
>Those, this prevent to make an cruel hack to arch/i386/boot/setup.S
>wich should be a little bit more harder..
>
>Basically, I add a memory region marked for acpi data use,
>in sanitize_e820_map().
>
>It's way more easy.. Could you please try without mem=xxx at all?
>
>I see also that you use 2.4.19. Perhaps this patch will be
>OK for 2.4.19 but I am not sure at 100%.
>
>Cheers,
>
>
>
Ok it boots up fine without mem=XX option i get ACPI to load ..... so
gimme some time and i ll double check
if the system is still crashing or not ...
but so far it looks nice ...
Rob
-------------------------------------------------------
This SF.net email is sponsored by: Scholarships for Techies!
Can't afford IT training? All 2003 ictp students receive scholarships.
Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more.
www.ictp.com/training/sourceforge.asp
prev parent reply other threads:[~2003-01-22 15:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-21 11:52 could not map ACPI Robert Woerle Paceblade/Support
[not found] ` <3E2D3471.1070307-fPtsKRK0pHxl57MIdRCFDg@public.gmane.org>
2003-01-21 13:19 ` Ducrot Bruno
[not found] ` <20030121131925.GB14593-j6u/t2rXLliUoIHC/UFpr9i2O/JbrIOy@public.gmane.org>
2003-01-21 14:26 ` Robert
[not found] ` <3E2D5879.6020908-y2s3ugBAdl9BDgjK7y7TUQ@public.gmane.org>
2003-01-21 16:10 ` Ducrot Bruno
2003-01-21 20:42 ` Ducrot Bruno
[not found] ` <20030121204235.GJ15023-j6u/t2rXLliUoIHC/UFpr9i2O/JbrIOy@public.gmane.org>
2003-01-22 8:10 ` Robert
[not found] ` <3E2E51FD.3070902-y2s3ugBAdl9BDgjK7y7TUQ@public.gmane.org>
2003-01-22 10:53 ` Ducrot Bruno
[not found] ` <3E2E7DBD.5040109@symplon.com>
[not found] ` <20030122142525.GA18109@poup.poupinou.org>
[not found] ` <20030122142525.GA18109-j6u/t2rXLliUoIHC/UFpr9i2O/JbrIOy@public.gmane.org>
2003-01-22 15:03 ` Robert [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=3E2EB2C1.1010206@symplon.com \
--to=robert.woerle-y2s3ugbadl9bdgjk7y7tuq@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=ducrot-kk6yZipjEM5g9hUCZPvPmw@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