linux-kernel - Re: [PATCH] Support MSI Poulsbo netbook U110/U115

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]

Message-Id: <4C6B2FBC020000230001ED68@novprvlin0050.provo.novell.com>
Date:	Tue, 17 Aug 2010 08:56:28 -0600
From:	"Joey Lee" <jlee@...ell.com>
To:	<mjg59@...f.ucam.org>
Cc:	<gregkh@...e.de>, <trenn@...e.de>, <linux-kernel@...r.kernel.org>,
	<platform-driver-x86@...r.kernel.org>, <Dennis.Jansen@....de>
Subject: Re: [PATCH] Support MSI Poulsbo netbook U110/U115

Hi Matthew, 

First, thank's for your kindy suggestion, it's good to us.

於 一，2010-08-16 於 16:56 +0100，Matthew Garrett 提到：
> On Fri, Aug 13, 2010 at 03:05:58AM -0600, Joey Lee wrote:
> > Hi Matthew, 
> > 
> > Dennis help me to ported this patch to 2.6.35, and it works as expected.
> > Could you please give me any suggestions for this patch?
> 
> I've thought about this a bit more and now lean towards thinking that 
> putting the PCI IDs in the ACPI video driver is the best way to go. The 
> alternative is to only fix it for MSI, which isn't the best option. On 

OK! Got it!
I will try to put the PCI IDs in ACPI video driver then send out the
patch for review ASAP.

> the other hand, I looked at adding support to the Poulsbo driver and it 
> actually seems pretty easy, so to be honest I'd prefer it if that got 
> done instead.
> 

I am not good for video driver, but will also try to look at it.


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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/