public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Stefan Schweizer <sschweizer-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: [Fwd: [Fwd: patch to include a custom dsdt]]
Date: Mon, 9 Aug 2004 22:02:15 +0200	[thread overview]
Message-ID: <e796392204080913023ba980bb@mail.gmail.com> (raw)
In-Reply-To: <1092080468.5021.27.camel@dhcppc4>

> Yes, the dsdt-in-initrd patch works.
> Yes, it is perfect for the unfortunate but determined soul who
> administers a variety of broken machines where they all run the same
> kernel and require a different DSDT -- I really do feel sorry for that
> person and look forward to the day they find non-broken hardware.

I only use it on one machine and if I want to change the dsdt I dont
want to recompile my kernel.
> 
> But DSDT overrides are for developers, not end-users, not customers.
> Nobody can support the OEM's firmware, or a modified version of it
> except the OEM themselves.  If a developer happens to fix an OEM's
> firmware and sends the OEM the fix, that happy situation is purely
> between the end-user and the OEM.  Distros should absolutely never
> be in the business of supporting hardware running modified firmware.
Right, distros should not support it, but people who know what they do
should have the ability to do it easy and w/o recompiling the kernel.

> I think that one major Distro pulled the dsdt-in-initrd patch, and I
> think it was a mistake for them to do so -- they can't support it.
They do not need to support it - if people use it, its on their own risk.

> That said, it is useful for developers to be able to override the DSDT.
> There are two methods -- re-build kernel or re-build kernel and also
> modify the initrd.
the difference is I can do the second one without looking into the
howto, because i know where my initrd is - in fact it is the DSDT.aml.
For the first method I would need to know the place where to copy the
dsdt - and always recompile/recopy/reinstall the kernel for minimal
changes.

> Kernel re-build is (I think) simple enought.  I think the patch at hand
> takes it from simple to trivial.


> Kernel re-build + initrd update I dislike because it depends on the
> existence of an initrd (not everybody uses has an initrd, I haven't used
> an initrd in over a year), and worse, it depends on the format of the
> initrd, which we don't control.
Initramfs would be the solution here - why not use it as additional method?
> 
> Anyway, I hope that my position, and the reason I haven't pulled the
> perfectly functional and useful dsdt-in-initrd patch before is clear.
Can you not just provide all possibilities, so that the user, sorry
the "developer", can decide himself how he wants to override his
initrd?


-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285

  reply	other threads:[~2004-08-09 20:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-09 16:59 [Fwd: [Fwd: patch to include a custom dsdt]] Len Brown
2004-08-09 17:49 ` Karol Kozimor
     [not found]   ` <20040809174935.GA20719-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
2004-08-09 19:23     ` Dominik Brodowski
2004-08-09 18:28 ` Stefan Schweizer
     [not found]   ` <e7963922040809112873fd7be4-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2004-08-09 19:41     ` Len Brown
2004-08-09 20:02       ` Stefan Schweizer [this message]
2004-08-09 20:07       ` Karol Kozimor
2004-08-09 20:30       ` Herman Sheremetyev
2004-08-11  6:20       ` Stefan Seyfried
2004-08-16  7:20 ` 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=e796392204080913023ba980bb@mail.gmail.com \
    --to=sschweizer-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@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