Re: [OT] 2.6.9: allow config to specify custom DSDT (Ulf Dambacher)

[Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>]

It has always been a mistake for SuSE to include that patch,
because an OSD can't possibly support modified OEM firmware.

DSDT overrides are for developers and experimentation,
not for production use.  Developers know how to build kernels,
and those that don't use initrd's can't use the initrd
method anyway.

The only argument for the initrd patch I've heard is from
somebody who deploys and supports the same kernel on
multiple systems, each with different DSDT patches.
I recommend that they choose their hardware vendor more
carefully in the future.

Also, the initrd pach isn't "clean" -- there isn't a supported
interface for appending junk onto an initrd, it is a hack to
do so with magic strings.

-Len
 
On Thu, 2004-10-21 at 23:20, Zhu, Yi wrote:
> Hi,
> 
> How about the DSDT_INITRD patch in SuSE kernel? I think it is cleaner
> than this one.
> What do you think?
> 
> Thanks,
> -yi
> 
> Len Brown wrote:
> > Note that CONFIG_ACPI_CUSTOM_DSDT depends on CONFIG_STANDALONE=n
> > 
> > The reason is that otherwise the allmodconfig and
> > allyesconfig builds break.
> > 
> > thanks,
> > -Len



-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl