public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Matt Domsch <Matt_Domsch@dell.com>
Cc: jack@antonello.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Dell laptop backlight driver
Date: Tue, 30 Oct 2007 14:52:48 +0000	[thread overview]
Message-ID: <20071030145247.GE7742@ucw.cz> (raw)
In-Reply-To: <20071028161955.GF23359@auslistsprd01.us.dell.com>

Hi!

> > this driver implements backlight control on Dell laptops
> > which use SMI  for changing brightness levels.
> > 
> > The driver is INCOMPLETE since it is unable to probe some required 
> > parameters
> > in order to perform backlight control. Such parameters are found in a Dell
> > proprietary DMI table which should be parsed. For now external tools may be
> > used to find these parameters by hand. So if you intend to try this out,
> > FIRST write your laptop model parameters correctly inside the source code
> > as explained in Documentation/dell-laptop.txt.
> > 
> > Parts of this driver may also be used to provide additional functionalities
> > similarly to the drivers/misc/*-laptop.c drivers.
> 
> Why is this better done in the kernel rather than in userspace with
> libsmbios as you've noted?

Well, keeping the same interface as other notebooks has some
advantages... and means that kernel does its job - hw abstraction.
							Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  parent reply	other threads:[~2007-11-01 14:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-28 16:12 [PATCH] Dell laptop backlight driver jack
2007-10-28 16:19 ` Matt Domsch
2007-10-28 18:06   ` lists
2007-10-28 19:20     ` Matt Domsch
2007-10-28 23:12       ` lists
2007-10-29 15:40       ` Matthew Garrett
2007-10-30 14:52   ` Pavel Machek [this message]
2007-10-28 22:30 ` jack

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=20071030145247.GE7742@ucw.cz \
    --to=pavel@ucw.cz \
    --cc=Matt_Domsch@dell.com \
    --cc=jack@antonello.org \
    --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