linux-kernel - Re: [PATCH V3] VIA IRQ quirk behaviour change

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

Message-ID: <20060910043741.GA21327@kroah.com>
Date:	Sat, 9 Sep 2006 21:37:41 -0700
From:	Greg KH <greg@...ah.com>
To:	Chris Wedgwood <cw@...f.org>
Cc:	Alan Cox <alan@...rguk.ukuu.org.uk>, Daniel Drake <dsd@...too.org>,
	akpm@...l.org, torvalds@...l.org, sergio@...giomb.no-ip.org,
	jeff@...zik.org, bjorn.helgaas@...com,
	linux-kernel@...r.kernel.org, harmon@....edu, len.brown@...el.com,
	vsu@...linux.ru, liste@...det.net
Subject: Re: [PATCH V3] VIA IRQ quirk behaviour change

On Sat, Sep 09, 2006 at 05:39:22PM -0700, Chris Wedgwood wrote:
> On Sat, Sep 09, 2006 at 05:21:12PM -0700, Greg KH wrote:
> 
> > So why isn't acpi handling all of this for us?
> 
> for some people it does...
> 
> > Do people not want to use acpi for some reason?
> 
> I was told that in the past VIA has buggy/broken ACPI, so we need to
> figure out what ACPI workaround Windows has and implement that (or
> maybe they do it in the driver(s)?)

Then that sounds like an ACPI issue, instead of trying to create a quirk
for the pci device itself.

Why not enable ACPI (which the manufacturer says is the way to go), and
then work from there?

thanks,

greg k-h
-
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/