public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Henschel <acpi-1rjuZeEg9oEb1SvskN2V4Q@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: dsdt patch
Date: Thu, 5 Feb 2004 10:39:14 +0100	[thread overview]
Message-ID: <20040205093914.GB2047@fuchi> (raw)
In-Reply-To: <401FB726.1080105-rdE3vRTOlSC6c6uEtOJ/EA@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 1683 bytes --]

re alimin..

* Alimin Bijosono Oei <alimin-rdE3vRTOlSC6c6uEtOJ/EA@public.gmane.org> [2004-02-03 16:46 +0100]:
> Sebastian Henschel wrote:
> >
> >* Alimin Bijosono Oei <alimin-rdE3vRTOlSC6c6uEtOJ/EA@public.gmane.org> [2004-02-02 09:12 +0100]:
> >
> >>Just want to ask where can I find a patch that will allow me to use my 
> >>own dsdt for kernel 2.4.24? Is there such a patch flying around or is 
> >>the kernel itself patched to allow implementation of custom dsdt table?
> >>I am sorry if this is the wrong place to ask such a question but I could 
> >>not find a mailing list for dsdt itself. I would very much appreciate if 
> >>someone can point me to the right direction.
> >
> >
> >you might try this:
> >
> >http://gaugusch.at/kernel.shtml
> >
> >also dino klein has announced a more generic patch last week or so,
> >check the archives for that version.
> 
> Thanks Sebastian. I feel a bit lost after consulting the more generic 
> patch you suggested before. Yes, at the moment I have two choices, one 
> is to use the initrd patch as you pointed out and the other one is to 
> patch osl.c and compile the custom dsdt into the kernel. I just want to 
> know if there is a patch to osl.c for kernel 2.4.24 made available? If 
> there isn't one, then I can always use the initrd patch which I am using 
> at the moment. I am not sure which method is the best though.

well, the initrd patch is quite flexible. there is no need to recompile
your kernel if you change the DSDT.
dunno about osl.c patch for 2.4.24 (or 2.6).

bye,
 sebastian
-- 
::: .O.
::: ..O
::: OOO
::: lynx -source http://www.kodeaffe.de/shensche.pub | gpg --import

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2004-02-05  9:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-01  9:48 dsdt patch Alimin Bijosono Oei
     [not found] ` <401CCB50.6010003-rdE3vRTOlSC6c6uEtOJ/EA@public.gmane.org>
2004-02-02  8:44   ` Sebastian Henschel
     [not found]     ` <20040202084457.GC8164-5sK/Rx+du8M@public.gmane.org>
2004-02-03 14:58       ` Alimin Bijosono Oei
     [not found]         ` <401FB726.1080105-rdE3vRTOlSC6c6uEtOJ/EA@public.gmane.org>
2004-02-05  9:39           ` Sebastian Henschel [this message]
2004-02-02  9:05   ` Luca Capello
     [not found]     ` <401E12BC.60905-wlebWZzHoyE@public.gmane.org>
2004-02-03 14:46       ` Alimin Bijosono Oei
  -- strict thread matches above, loose matches on Subject: below --
2004-02-03  8:39 Yu, Luming
     [not found] ` <3ACA40606221794F80A5670F0AF15F8401CBB674-SRlDPOYGfgogGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-02-03 14:40   ` Alimin Bijosono Oei

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=20040205093914.GB2047@fuchi \
    --to=acpi-1rjuzeeg9oeb1svskn2v4q@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@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