From: Ismail Donmez <ismail@pardus.org.tr>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: Arjan van de Ven <arjan@infradead.org>,
Yu Luming <luming.yu@gmail.com>,
Matt Domsch <Matt_Domsch@dell.com>, Pavel Machek <pavel@ucw.cz>,
Andrew Morton <akpm@osdl.org>,
Alessandro Guido <alessandro.guido@gmail.com>,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
len.brown@intel.com, jengelh@linux01.gwdg.de, gelma@gelma.net
Subject: Re: [PATCH 2.6.18-mm2] acpi: add backlight support to the sony_acpi driver
Date: Wed, 11 Oct 2006 11:04:48 +0300 [thread overview]
Message-ID: <200610111104.50563.ismail@pardus.org.tr> (raw)
In-Reply-To: <20061011070412.GA6128@srcf.ucam.org>
11 Eki 2006 Çar 10:04 tarihinde, Matthew Garrett şunları yazmıştı:
> On Wed, Oct 11, 2006 at 08:59:04AM +0200, Arjan van de Ven wrote:
> > it'd also be nice if the linux-ready firmware developer kit had a test
> > for this, so that we can offer 1) a way to test this to the bios guys
> > and 2) encourage adding/note the lack easily
>
> Sure. Reading /proc/acpi/video/*/*/info should tell you whether a device
> is an LCD or not.
On my Sony Vaio with latest linux-2.6 git kernel it says its a CRT :
[~]> cat /proc/acpi/video/*/*/info
device_id: 0x0100
type: CRT
known by bios: no
device_id: 0x0320
type: UNKNOWN
known by bios: no
device_id: 0x0410
type: UNKNOWN
known by bios: no
device_id: 0x0240
type: UNKNOWN
known by bios: no
device_id: 0x0100
type: CRT
known by bios: no
device_id: 0x0111
type: UNKNOWN
known by bios: no
device_id: 0x0118
type: UNKNOWN
known by bios: no
device_id: 0x0200
type: TVOUT
known by bios: no
So I don't think its reliable.
Regards,
ismail
next prev parent reply other threads:[~2006-10-11 8:04 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-30 17:08 [PATCH 2.6.18-mm2] acpi: add backlight support to the sony_acpi driver Alessandro Guido
2006-09-30 17:14 ` Alessandro Guido
2006-09-30 17:31 ` Jan Engelhardt
2006-10-02 0:19 ` Andrew Morton
2006-10-02 0:39 ` Matt Domsch
2006-10-02 0:48 ` Matt Domsch
2006-10-05 10:36 ` Pavel Machek
2006-10-06 21:17 ` Matt Domsch
2006-10-06 22:44 ` Pavel Machek
2006-10-10 14:32 ` Yu Luming
2006-10-10 14:47 ` Richard Hughes
2006-10-10 16:10 ` Matt Domsch
2006-10-11 16:28 ` Yu Luming
2006-10-16 17:45 ` Yu Luming
2006-10-25 7:07 ` Pavel Machek
2006-10-27 17:24 ` Luming Yu
2006-10-29 17:50 ` Pavel Machek
2006-10-30 15:49 ` Luming Yu
2006-10-10 21:26 ` Matthew Garrett
2006-10-11 3:02 ` Matt Domsch
2006-10-11 3:16 ` Matthew Garrett
2006-10-11 16:37 ` Yu Luming
2006-10-11 6:59 ` Arjan van de Ven
2006-10-11 7:04 ` Matthew Garrett
2006-10-11 8:04 ` Ismail Donmez [this message]
2006-10-11 8:12 ` Matthew Garrett
2006-10-11 16:31 ` Yu Luming
2006-10-11 16:45 ` Ismail Donmez
2006-10-02 10:29 ` Holger Macht
2006-10-02 11:25 ` Alessandro Guido
2006-10-10 15:17 ` Yu Luming
2006-10-10 15:22 ` Richard Hughes
2006-10-10 21:23 ` Matthew Garrett
2006-10-11 3:20 ` Dmitry Torokhov
2006-10-11 16:48 ` Yu Luming
2006-10-11 19:08 ` Dmitry Torokhov
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=200610111104.50563.ismail@pardus.org.tr \
--to=ismail@pardus.org.tr \
--cc=Matt_Domsch@dell.com \
--cc=akpm@osdl.org \
--cc=alessandro.guido@gmail.com \
--cc=arjan@infradead.org \
--cc=gelma@gelma.net \
--cc=jengelh@linux01.gwdg.de \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luming.yu@gmail.com \
--cc=mjg59@srcf.ucam.org \
--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