mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Jenkins <aj504@student.cs.york.ac.uk>
To: "David Härdeman" <david@hardeman.nu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Loading DSDT from initrd, can it be done from grub instead?
Date: Tue, 20 May 2008 13:51:35 +0100	[thread overview]
Message-ID: <4832C957.8040004@student.cs.york.ac.uk> (raw)
In-Reply-To: <54484.145.64.134.222.1211286021.squirrel@www.hardeman.nu>

David Härdeman wrote:
> On Tue, May 20, 2008 13:58, Alan Jenkins wrote:
>   
>> David Härdeman wrote:
>>     
>>> In commit 9a9e0d685553af76cb6ae2af93cca4913e7fcd47 the
>>> ACPI_CUSTOM_DSDT_INITRD option was removed.
>>>
>>> I was wondering if it'd be feasible to hack grub to load a custom DSDT
>>> instead (since grub can read filesystems) and then pass a pointer to a
>>> memory location containing the DSDT to the kernel?
>>>       
>> Um, why?  What stops you from reverting the offending commit?
>>     
>
> Because doing it from grub (if possible) would allow custom DSDT's to be
> loaded without patching the kernel (e.g. allows distro kernels to be used)
> and without introducing code that opens files from kernel space and mucks
> with both the VFS and ACPI in ugly ways?
>
>   
>> Without further info, I'd assume the feature was removed on policy
>> grounds.  I.e. it's not nice to be effectively patching the BIOS
>> yourself, and vendors have fixed most of their BIOS's / linux is
>> slightly more tolerant to broken ones. I don't know whats wrong with
>> reading files from the initrd.
>>     
>
> If you do not understand the issue at hand, why comment?
>   
Mea cupla.  Apologies if my tone was also inappropriate.

I saw a short question on an interesting subject, without a context to 
suggest an ongoing
conversation.  I would have saved myself some embarassment if I 
remembered that linux really doesn't like in-kernel filesystem access; I 
just didn't make the connection.

I guessed wrong, didn't see where you were coming from, and didn't take 
the effort to resolve the SHA commit id.  I literally don't have the 
space for a checkout on my main PC and I feel slightly guilty when I hit 
on the gitweb host.

Ironically, I just looked it up and Google knew what the SHA ID was.  
You might be interested to know that another DH (Dave Hansen) made the 
same suggestion, but using kexec instead of grub to load the DSDT and 
boot kernel.

Alan

  reply	other threads:[~2008-05-20 13:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <avxTs-570-21@gated-at.bofh.it>
2008-05-20 11:58 ` Alan Jenkins
2008-05-20 12:09   ` Gabriel C
2008-05-20 12:20   ` David Härdeman
2008-05-20 12:51     ` Alan Jenkins [this message]
2008-05-20 10:10 David Härdeman

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=4832C957.8040004@student.cs.york.ac.uk \
    --to=aj504@student.cs.york.ac.uk \
    --cc=alan-jenkins@tuffmail.co.uk \
    --cc=david@hardeman.nu \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®