X86 platform drivers
 help / color / mirror / Atom feed
From: Matthew Garrett <mjg59@srcf.ucam.org>
To: AceLan Kao <acelan.kao@canonical.com>
Cc: "platform-driver-x86@vger.kernel.org"
	<platform-driver-x86@vger.kernel.org>
Subject: Re: [PATCH] dell-wmi: Add quirk for Dell Inspiron 3138
Date: Wed, 4 Dec 2013 11:15:00 +0000	[thread overview]
Message-ID: <20131204111500.GA1613@srcf.ucam.org> (raw)
In-Reply-To: <CAMz9Wg_CF1un4i_FKhGkJ4=adB0VxennFDy+zrrMD_8bOYGoXg@mail.gmail.com>

On Wed, Dec 04, 2013 at 04:14:15PM +0800, AceLan Kao wrote:

> It does what you say above.
> But, the variable use_native_backlight is false by default, and user
> has to enable this by adding one kernel parameter
> video.use_native_backlight=1
> I don't see this do any difference with acpi_backlight=vendor as user
> has to add the kernel command line explicitly to get rid of the broken
> acpi_video0.

Right. The default needs to be changed.

> We always encourage OEM BIOS to follow the ACPI spec., if not, we'll
> ask them to remove _BCL, _BCM, _BQC functions.
> And Dell Inspiron 3138 is the first one that they refuse our request,
> so I would like to fix it in the kernel.

The best thing to do is to send a patch that flips the default on 
Windows 8 systems and get it pushed through the drm-next tree in order 
to work out the remaining bugs in the intel backlight driver.

> So, I think we probably need some quirks to disable acpi_video0 by the
> mean while before use_native_backlight is default true.

Sorry, I'm not adding any machine-specific quirks to fix generic 
problems.

-- 
Matthew Garrett | mjg59@srcf.ucam.org

      reply	other threads:[~2013-12-04 11:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-03  6:50 [PATCH] dell-wmi: Add quirk for Dell Inspiron 3138 AceLan Kao
2013-12-03  7:07 ` Matthew Garrett
2013-12-03  7:31   ` AceLan Kao
2013-12-03  7:40     ` Matthew Garrett
2013-12-04  8:14       ` AceLan Kao
2013-12-04 11:15         ` Matthew Garrett [this message]

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=20131204111500.GA1613@srcf.ucam.org \
    --to=mjg59@srcf.ucam.org \
    --cc=acelan.kao@canonical.com \
    --cc=platform-driver-x86@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