public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Ozan Çağlayan" <ozan@pardus.org.tr>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: [PATCH] ACPI: video: DMI workaround broken Acer 5710 BIOS	enabling display brightness
Date: Mon, 14 Jun 2010 19:19:16 +0300	[thread overview]
Message-ID: <4C165684.1060609@pardus.org.tr> (raw)
In-Reply-To: <20100614142554.GA22158@srcf.ucam.org>

Matthew Garrett wrote:
> On Mon, Jun 14, 2010 at 10:17:44AM +0300, Ozan Çağlayan wrote:
>> Acer Aspire 5710 suffers from a similar ACPI problem reported at:
>>  http://bugzilla.kernel.org/show_bug.cgi?id=13121
> 
> Bleah. Is this really necessary? If we set maximum brightness and then 
> read back something other than maximum brightness, then that gives us 
> the offset.

By *this* do you mean the specific quirk that I sent or the whole offset workaround
suggested and upstreamed in the bug report?

Actually I sync'ed the video driver from linux-2.6 on top of 2.6.31.13 and applied this patch.
The user reported that it fixed the issue but it is possible that this quirk
is NOOP and the bug is already fixed with what I've backported.

I'll let him try without the patch, and report back.

Thanks,
Regards.
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2010-06-14 16:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-14  7:17 [PATCH] ACPI: video: DMI workaround broken Acer 5710 BIOS enabling display brightness Ozan Çağlayan
2010-06-14 14:25 ` Matthew Garrett
2010-06-14 16:19   ` Ozan Çağlayan [this message]
2010-06-14 16:36     ` Matthew Garrett

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=4C165684.1060609@pardus.org.tr \
    --to=ozan@pardus.org.tr \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjg59@srcf.ucam.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