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]

Date:	Sat, 9 Sep 2006 17:21:12 -0700
From:	Greg KH <greg@...ah.com>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
Cc:	Daniel Drake <dsd@...too.org>, akpm@...l.org, torvalds@...l.org,
	sergio@...giomb.no-ip.org, jeff@...zik.org, cw@...f.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 Sun, Sep 10, 2006 at 01:31:12AM +0100, Alan Cox wrote:
> VIA have always told me that "ACPI handles this" and we don't need
> quirks. Various chips have different IRQ routing logic and it's all a
> bit weird if we don't use ACPI and/or BIOS routing.

So why isn't acpi handling all of this for us?  Do people not want to
use acpi for some reason?

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/