linux-kernel - Re: 2.6.29-mmotm0109 Odd prompt for Sharp Corgi backlight.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 11 Jan 2009 23:59:59 +0000
From:	Richard Purdie <rpurdie@...ux.intel.com>
To:	Valdis.Kletnieks@...edu
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org
Subject: Re: 2.6.29-mmotm0109 Odd prompt for Sharp Corgi backlight.

On Sun, 2009-01-11 at 13:38 -0500, Valdis.Kletnieks@...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



--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/