mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Richard Purdie <rpurdie@linux.intel.com>
To: Valdis.Kletnieks@vt.edu
Cc: Andrew Morton <akpm@linux-foundation.org>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.29-mmotm0109 Odd prompt for Sharp Corgi backlight.
Date: Sun, 11 Jan 2009 23:59:59 +0000	[thread overview]
Message-ID: <1231718399.5304.62.camel@dax.rpnet.com> (raw)
In-Reply-To: <67095.1231699127@turing-police.cc.vt.edu>

On Sun, 2009-01-11 at 13:38 -0500, Valdis.Kletnieks@vt.edu wrote:
> So I'm building mmotm-0109, doing a 'make oldconfig', and out pops:
> 
>     Generic (aka Sharp Corgi) Backlight Driver (BACKLIGHT_GENERIC) [Y/n/m/?] (NEW) ?
> 
> Say y to enable the generic platform backlight driver previously
> known as the Corgi backlight driver. If you have a Sharp Zaurus
> SL-C7xx, SL-Cxx00 or SL-6000x say y.
> 
> 
> Two questions:
> 
> 1) Is it a Corgi driver, or truly a generic one?  It can't be *too* generic
> if it only applies to 3 Sharp Zaurus models?  Or do I want to specify it for
> my Dell laptop that has a backlight too (in which case that help text needs
> fixing)...

It is truly generic code now. Your Dell laptop won't use it but it won't
hurt it either.

> 2) Why does this default to 'Y'? (Probably depends on the answer to (1) - if
> it's for one vendor, it probably should be N, but Y may make sense if it's
> proper for the vast majority of all laptops and similar that have a backlight.

It defaults to Y since its harmless if not used and will become the
common case for a large number of devices.

Cheers,

Richard




  reply	other threads:[~2009-01-11 23:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-11 18:38 Valdis.Kletnieks
2009-01-11 23:59 ` Richard Purdie [this message]
2009-01-13  6:25   ` 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=1231718399.5304.62.camel@dax.rpnet.com \
    --to=rpurdie@linux.intel.com \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=akpm@linux-foundation.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

all inboxes | Powered by JetHome®