Skip to contentSkip to conversation

Buggy DSDTs policy ?

DISCUSSION Olivier Galibert 4 participants 7 messages Oct 22, 2004

lore
Share & tools
lore
#0 lore raw

What is the policy w.r.t broken DSDTs and the ACPI subsystem? Specifically, which of these two options is right:

1- Provide a non-buggy DSDT to the kernel
2- Make the ACPI subsystem tolerant of the bugs

The option 3, have all biosen over the world fixed is a nice fantasy, but nothing else.

If 1, we need to put a mechanism for that in the official kernel.

If 2, I'll start working on patches to make the laptop I play with work as-is.

So, which it is?

OG.

#1 lore raw
Quoted 10 lines · On Fri, 22 Oct 2004 14:23:27 +0200 Olivier Galibert <[email protected]> wrote:

What is the policy w.r.t broken DSDTs and the ACPI subsystem? Specifically, which of these two options is right:

1- Provide a non-buggy DSDT to the kernel
2- Make the ACPI subsystem tolerant of the bugs

The option 3, have all biosen over the world fixed is a nice fantasy, but nothing else.

If 1, we need to put a mechanism for that in the official kernel.

CONFIG_ACPI_CUSTOM_DSDT is included in 2.6.9

Quoted 4 lines

If 2, I'll start working on patches to make the laptop I play with work as-is.

So, which it is?

Signature · 2 lines
 Onur Kucuk                                        Knowledge speaks,   
 <onur.--.-.delipenguen.net>                       but wisdom listens  
#2 lore raw
Quoted 9 lines · Onur Kucuk
Quoted 6 lines · On Fri, 22 Oct 2004 14:23:27 +0200 Olivier Galibert <[email protected]> wrote:

What is the policy w.r.t broken DSDTs and the ACPI subsystem? Specifically, which of these two options is right:

1- Provide a non-buggy DSDT to the kernel
2- Make the ACPI subsystem tolerant of the bugs

Quoted 6 lines
Quoted 4 lines

The option 3, have all biosen over the world fixed is a nice fantasy, but nothing else.

If 1, we need to put a mechanism for that in the official kernel.

CONFIG_ACPI_CUSTOM_DSDT is included in 2.6.9

But fixed DSDTs are a pain to find, and fixing a buggy DSDT is impossible for a non-hacker.

Xav

#3 lore raw
Quoted 5 lines · Xavier Bestel
Quoted 1 line

CONFIG_ACPI_CUSTOM_DSDT is included in 2.6.9

But fixed DSDTs are a pain to find, and fixing a buggy DSDT is impossible for a non-hacker.

http://acpi.sourceforge.net/dsdt/index.php has quite a few.

The problem is getting the fixed dsdt in use without recompiling your kernel, since quite a few people, especially non-technical ones, use vendor kernels. There's an approach that uses initrd, but this isn't merged yet. I'd say it should be, assuming no better solution can be found.

#4 lore raw
Quoted 7 lines · Pekka Pietikainen
Quoted 5 lines · Xavier Bestel
Quoted 1 line

CONFIG_ACPI_CUSTOM_DSDT is included in 2.6.9

But fixed DSDTs are a pain to find, and fixing a buggy DSDT is impossible for a non-hacker.

http://acpi.sourceforge.net/dsdt/index.php has quite a few.

.. which aren't all proper fixes (I tried the DSDT for Armada 1700, it's a partial fix only).

Quoted 4 lines

The problem is getting the fixed dsdt in use without recompiling your kernel, since quite a few people, especially non-technical ones, use vendor kernels. There's an approach that uses initrd, but this isn't merged yet. I'd say it should be, assuming no better solution can be found.

Yes, sure. But real non-technical people won't replace their DSDT either.

Xav

#5 lore raw
Quoted 7 lines · Xavier Bestel
Quoted 4 lines

The problem is getting the fixed dsdt in use without recompiling your kernel, since quite a few people, especially non-technical ones, use vendor kernels. There's an approach that uses initrd, but this isn't merged yet. I'd say it should be, assuming no better solution can be found.

Yes, sure. But real non-technical people won't replace their DSDT either.

Their distro could do it for them :-) A simple approach would be to store md5sums of known-bad dsdt's and xdeltas to fixed ones, and the fixed one gets placed in /etc where mkinitrd automagically picks it up whenever a new kernel is installed.

But that's userspace (with possible problems in distributing dsdt's, which is why xdelta might be an acceptable solution), the kernel should just make something like like that possible, if someone wants to do it.

#6 lore raw
In reply to Xavier Bestel
Quoted 11 lines · Xavier Bestel
Quoted 7 lines · Pekka Pietikainen
Quoted 5 lines · Xavier Bestel
Quoted 1 line

CONFIG_ACPI_CUSTOM_DSDT is included in 2.6.9

But fixed DSDTs are a pain to find, and fixing a buggy DSDT is impossible for a non-hacker.

http://acpi.sourceforge.net/dsdt/index.php has quite a few.

.. which aren't all proper fixes (I tried the DSDT for Armada 1700, it's a partial fix only).

This can be an issue to work on. I am sure acpi people won't reject
proper fixes.

Quoted 5 lines
Quoted 5 lines

The problem is getting the fixed dsdt in use without recompiling your kernel, since quite a few people, especially non-technical ones, use vendor kernels. There's an approach that uses initrd, but this isn't merged yet. I'd say it should be, assuming no better solution can be found.

The initrd approach seems nicer and more customisable.

Quoted 2 lines

Yes, sure. But real non-technical people won't replace their DSDT either.

Real non-technical people follow their distros. They don't need to
recompile a kernel of their own. It is a distro's job for them.

Signature · 2 lines
 Onur Kucuk                                        Knowledge speaks,   
 <onur.--.-.delipenguen.net>                       but wisdom listens