mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: marekw1977@yahoo.com.au,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: acpi4asus
Date: Tue, 16 May 2006 23:38:56 -0400	[thread overview]
Message-ID: <446A9AD0.6030509@tmr.com> (raw)
In-Reply-To: <20060508234723.GB4349@ucw.cz>

Pavel Machek wrote:

>Hi!
>
>  
>
>>>I am far from qualified to comment on this, but from a 
>>>users point of view, is it possible to not have laptop 
>>>specific code in the kernel?
>>>I have had two Linux laptops and with both I had ACPI 
>>>issues.
>>>The vendors of both laptops (Toshiba Tecra S1 and now 
>>>an Asus W3V) don't seem to be following standards. With 
>>>both I seem to need to patch ACPI to get various 
>>>functions of the laptop to work.
>>>I would love to see laptop specific functionality 
>>>definitions exist outside the kernel.
>>>
>>>      
>>>
>>I don't think that forcing laptop users to have their 
>>own code outside the kernel is really the best approach 
>>for either the developers or the users. Most users will 
>>    
>>
>
>No, we don't want that. But we do not want ibm-acpi, toshiba-acpi,
>asus-acpi, etc, when they really only differ in string constants used.
>
>We want userland to tell kernel 'mail led is controlled by AML routine
>foo', instead of having gazillion *-acpi modules.
>
>
>  
>
I see no reason why an interface to that couldn't be included in the 
kernel, with just a small table for each hardware instead of a whole 
module. Kind of a white list with detail.

-- 
bill davidsen <davidsen@tmr.com>
  CTO TMR Associates, Inc
  Doing interesting things with small computers since 1979


  reply	other threads:[~2006-05-17  3:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-11 13:07 acpi4asus Lukas Hejtmanek
2006-05-11 14:32 ` acpi4asus Andrew Morton
2006-05-12  1:16   ` acpi4asus Marek W
2006-05-12 14:22     ` acpi4asus Bill Davidsen
2006-05-08 23:47       ` acpi4asus Pavel Machek
2006-05-17  3:38         ` Bill Davidsen [this message]
2006-05-17 13:24           ` acpi4asus Pavel Machek
2006-05-11 14:09 acpi4asus Yu, Luming

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=446A9AD0.6030509@tmr.com \
    --to=davidsen@tmr.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marekw1977@yahoo.com.au \
    --cc=pavel@ucw.cz \
    /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

Powered by JetHome