mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stelian Pop <stelian@popies.net>
To: Len Brown <len.brown@intel.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>,
	ACPI Developers <acpi-devel@lists.sourceforge.net>
Subject: Re: [ACPI] [PATCH, new ACPI driver] new sony_acpi driver
Date: Tue, 15 Feb 2005 16:39:12 +0100	[thread overview]
Message-ID: <20050215153912.GA3523@crusoe.alcove-fr> (raw)
In-Reply-To: <1108481448.2097.71.camel@d845pe>

On Tue, Feb 15, 2005 at 10:30:49AM -0500, Len Brown wrote:

> On Thu, 2005-02-10 at 11:18, Stelian Pop wrote:,
> 
> > 
> > PS: I am also going to submit a bugzilla RFE for the acpi people,
> > I have been told they are more receptive to that.
> 
> I guess that refers to me:-)

Hey, you *are* more receptive to bugzilla then !

> E-mail is fine, but the unfortunate reality is that due to simple
> volume, it is lossy.  The reason we like bugzilla is that it never
> forgets:-)
> 
> So thanks for taking the extra time to file a bug report
> http://bugzilla.kernel.org/show_bug.cgi?id=4193
> 
> If it turns out that there is no way a generic solution
> can handle the SNC Sony laptops, then I agree that a

Note: this is not a subset of the Sony laptops, we are talking
about all the Sony laptops here.

> platform specific wart is the only way to go.  But
> it would be best if we can make the exotic Sony/SNC
> look more generic to the user so that the user
> (and the distro supporting them) don't need to learn
> special things to handle this system.

I agree, but unfortunately I don't think it's possible to handle
them in a generic way. However, my understanding of the ACPI layer
is limited, so I very well be wrong.

I attached two DSDT in bugzilla, I have a few more if you want them.

Stelian.
-- 
Stelian Pop <stelian@popies.net>

  reply	other threads:[~2005-02-15 15:38 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-10 16:18 Stelian Pop
2005-02-10 19:39 ` [ACPI] " Bruno Ducrot
2005-02-11  9:16   ` Stelian Pop
2005-02-11 10:30 ` Jean Delvare
2005-02-11 11:17   ` Stelian Pop
2005-02-11 11:05 ` Pekka Enberg
2005-02-11 11:36 ` Stelian Pop
2005-02-11 12:02   ` Pekka Enberg
2005-02-12 13:21   ` Jean Delvare
2005-02-14 10:07     ` Stelian Pop
2005-02-14 12:13       ` Jean Delvare
2005-02-14 12:38         ` Stelian Pop
2005-02-14 18:42           ` Jean Delvare
2005-02-16 15:39             ` Stelian Pop
2005-02-18 18:38               ` Jean Delvare
2005-02-16 19:12   ` Emmanuel Fleury
2005-02-14 10:53 ` Matthew Garrett
2005-02-14 10:58   ` Stelian Pop
2005-02-14 20:32     ` Vojtech Pavlik
2005-02-15 16:14       ` Romano Giannetti
2005-02-16 14:41         ` Stelian Pop
2005-02-16 15:40           ` Romano Giannetti
2005-02-16 23:18       ` [ACPI] " Pavel Machek
2005-02-15 15:30 ` [ACPI] " Len Brown
2005-02-15 15:39   ` Stelian Pop [this message]
2005-02-16 19:40     ` Bruno Ducrot
2005-03-15  6:07 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=20050215153912.GA3523@crusoe.alcove-fr \
    --to=stelian@popies.net \
    --cc=acpi-devel@lists.sourceforge.net \
    --cc=akpm@osdl.org \
    --cc=len.brown@intel.com \
    --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®