public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Bas Mevissen <ml-Y9IUUvl1dgU0Iwp8Nzs06g@public.gmane.org>
To: Robert Woerle <robert-fPtsKRK0pHxl57MIdRCFDg@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
	Andrew de Quincey
	<adq_dvb-fmPXVN3awWJAJAzL26g0SA@public.gmane.org>
Subject: Re: Using INITRDDSDT:  was Re: Changing IRQ`s at DSDT
Date: Wed, 01 Oct 2003 13:50:41 +0200	[thread overview]
Message-ID: <3F7ABF91.208@basmevissen.nl> (raw)
In-Reply-To: <3F7A57B0.6040906-fPtsKRK0pHxl57MIdRCFDg@public.gmane.org>

Robert Woerle wrote:

> 
> Suggestion :  Why dont you guys put the "Read DSDT from initrd " into 
> the core ACPI source .. so that it gets
> merged to the vanilla kernel at one point .

The patch that floats around works quite well, but it is a hack. It 
would be better to make a module that can be loaded from initrd at boot 
time. With some modprobe.conf smartness, you can select the proper table 
module to be loaded.

But I'm not sure if the ability to load modules doesn't come availabe 
too late in the boot process for ACPI as ACPI has influence on the 
interrupt routing.

> I really like idea to be able to load fixed DSDT`s . This can also be 
> extended by the big distributions then to implement a routine
> in their hardware scan so if a known Mainboard with  a buggy BIOS 
> version ( is there a tool to check the version string of a BIOS ?? ) is
> found they can load a fixed DSDT ....
> This would be a great thing which ACPI enable`s us and so make Linux run 
> even better on more units ...
> 

I agree only in part. Main problem is that you need the fix for exactly 
the same revision as in the BIOS to be sure you don't introduce 
problems. So that means that distribution makers need to maintain a huge 
collection of fixed DSDT's and need a fully reliable way to detect the 
BIOS version to be safe.

I think the best solution for the present time is to relax the ACPI 
interpreter syntax checking even more. But it should warn at boot time 
when it does work around syntax errors to attend the user that it's DSDT 
is actually wrong, but readable to the interpreter.


Bas.





-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

      parent reply	other threads:[~2003-10-01 11:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-29 10:44 Changing IRQ`s at DSDT Robert Woerle
     [not found] ` <3F780D1A.20908-fPtsKRK0pHxl57MIdRCFDg@public.gmane.org>
2003-09-29 18:37   ` Andrew de Quincey
     [not found]     ` <200309291937.53825.adq_dvb-fmPXVN3awWJAJAzL26g0SA@public.gmane.org>
2003-09-30  8:15       ` Robert Woerle
     [not found]         ` <3F793B88.60104-fPtsKRK0pHxl57MIdRCFDg@public.gmane.org>
2003-09-30 11:15           ` Andrew de Quincey
     [not found]             ` <200309301215.13202.adq_dvb-fmPXVN3awWJAJAzL26g0SA@public.gmane.org>
2003-09-30  8:30               ` Robert Woerle
2003-10-01  4:27               ` Using INITRDDSDT: was " Robert Woerle
     [not found]                 ` <3F7A57B0.6040906-fPtsKRK0pHxl57MIdRCFDg@public.gmane.org>
2003-10-01 11:50                   ` Bas Mevissen [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=3F7ABF91.208@basmevissen.nl \
    --to=ml-y9iuuvl1dgu0iwp8nzs06g@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=adq_dvb-fmPXVN3awWJAJAzL26g0SA@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