linux-kernel - Re: [PATCH] Add intel drm blacklist to intel_opregion

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>] [day] [month] [year] [list]

Date:	Tue, 24 Aug 2010 01:03:54 -0600
From:	"Joey Lee" <jlee@...ell.com>
To:	<mjg59@...f.ucam.org>
Cc:	<gregkh@...e.de>, <trenn@...e.de>, <linux-acpi@...r.kernel.org>,
	<linux-kernel@...r.kernel.org>, <Dennis.Jansen@....de>
Subject: Re: [PATCH] Add intel drm blacklist to intel_opregion_present
 detect

Hi Matthew, 

於 一，2010-08-23 於 18:51 +0100，Matthew Garrett 提到：
> On Mon, Aug 23, 2010 at 07:53:21PM +0200, Thomas Renninger wrote:
> 
> > Hm, needing a module option to get a system running is not what the user expects.
> > By default, the system should run fine and a module option should be added
> > as a workaround or for debugging only.
> 
> How about we do this instead: add a psb stub driver that does nothing 
> other than call acpi_backlight_register()?
> 

The attached file is a draft stub driver for poulsbo. Like you said, it
will only call acpi_video_register and acpi_video_unregister when
initial and exit.
And I added the Poulsbo pci id in the module alias.

It's works to me, where can we put the driver? in driver/staging ? or
put in driver/gpu/stub ?


Thank's a lot!
Joey Lee


View attachment "poulsbo.c" of type "text/plain" (563 bytes)