Prev: [PATCH] remove unnecesary while loop in ext2_xattr_get
Next: [PATCH 1/3] trivial: fix typos concerning "empty"
From: Joey Lee on 12 Jul 2010 11:20
Hi Mattew,

於 一，2010-07-12 於 03:27 +0100，Matthew Garrett 提到：
> On Sun, Jul 11, 2010 at 08:12:57PM -0600, Joey Lee wrote:
>
> > He tested the drm blacklist patch can works fine on his computer, it's
> > also works on VESA mode because the acpi _BCM, _BQC direct change
> > brightness by opregion.
> >

Sorry, I write a wrong information, the MSI poulsbo netbook change
brightness by ec command in _BCM, _BQC, not opregion.

> > What can we do for this situtation? I mean if the BIOS have opregion
> > implementation but there have no opensource drm driver or native video
> > driver support opregion on Linux?
>
> The cleanest way would be to implement a stub backlight control driver
> for the chip - there should be enough information in the source of the
> poulsbo drm to do that.

M... Follow your suggestion, I am tracing the i915 drm driver and
Poulsbo drm driver from here:

http://sourceforge.net/mailarchive/message.php?msg_name=49C2ADA8.2090405%40shipmail.org

I am not sure fully understood your suggestion... Did you mean we can
extract some parts from Poulsbo drm driver and put it to a stub
backlight control driver for Poulsbo? Where can we put the stub driver?
Do we still put it in i915 drm?

On the other hand, the Poulsbo is a old and stop ship chip, do we still
want to add a special driver for it?

> The main problem with the blacklist approach is
> that there's no guarantee that all poulsbo systems will have a working
> acpi method, and I /think/ there's a couple more PCI IDs that ought to
> be covered in any case. On the other hand doing it properly does involve
> writing rather a lot more code, and the fact that Intel have shown
> absolutely no interest in making their hardware work means that the
> quick hack might be the most reasonable thing to do.
>

Thank's for your remind, I fully agreed cann't guarantee all poulsbo
systems have working acpi method. But, I am sure the MSI U110/U115 have
workable acpi backlight method.
Do you think it's good to put the special DMI detection in msi-laptop
driver to enable the the acpi backlight control by call
acpi_video_register in acpi video? But will cause msi-laptop driver
dependency to acpi video driver.

Need your kindly suggestion!


Thank's a lot!
Joey Lee

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Joey Lee on 13 Jul 2010 04:20
Hi Matthew,

First, thank's for your kindly suggestion.

於 一，2010-07-12 於 16:19 +0100，Matthew Garrett 提到：
>
> > On the other hand, the Poulsbo is a old and stop ship chip, do we still
> > want to add a special driver for it?
>
> Yeah, that's my concern. There's millions of things in the wild and
> Intel continue to refuse to take responsibility for them, so it's not
> clear to me that it's worth putting the effort into writing a "correct"
> driver.
>

Yes, fully agreed!

> > Thank's for your remind, I fully agreed cann't guarantee all poulsbo
> > systems have working acpi method. But, I am sure the MSI U110/U115 have
> > workable acpi backlight method.
> > Do you think it's good to put the special DMI detection in msi-laptop
> > driver to enable the the acpi backlight control by call
> > acpi_video_register in acpi video? But will cause msi-laptop driver
> > dependency to acpi video driver.
>
> Mm. Well, we *know* that opregion won't work on Poulsbo as is (even
> Intel's driver doesn't implement it), so there's no way this patch can
> make things any worse. On the other hand, if anyone ships an OS with
> this hack *and* a native psb driver, I'm going to look sad for some
> time.
>

Please then me add the MSI U110/U115 support in msi-laptop driver. I am
sure the acpi baclight method works fine on U110/U115 and I hope the
_REAL_ opensource kernel user will not have a invalid backlight control
function.

For the native psb driver, if have anyone want to ship it with newest
msi-laptop driver, then he must need take care anything in KMP, like:
disable msi-laptop or put it to modprobe blacklist.
Because the native psb driver doesn't not included in kernel mainline.

On the other hand, the Poulsbo already stop to chip, there will not have
many machine ship the native psb driver with newest msi-laptop.


Thank's a lot!
Joey Lee


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
 | 
Pages: 1
Prev: [PATCH] remove unnecesary while loop in ext2_xattr_get
Next: [PATCH 1/3] trivial: fix typos concerning "empty"