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  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:	Fri, 14 Jul 2006 15:26:45 -0400
From:	"Brown, Len" <len.brown@...el.com>
To:	"Daniel Drake" <dsd@...too.org>, "Chris Wedgwood" <cw@...f.org>
Cc:	"Andrew Morton" <akpm@...l.org>, "Jeff Garzik" <jeff@...zik.org>,
	<greg@...ah.com>, <harmon@....edu>, <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH] Add SATA device to VIA IRQ quirk fixup list

I've been trying very hard to stay away from VIA quirks,
but there are some things to be aware of.

1. quirks are independent of ACPI on/off

Note that ACPI PCI Interrupt Link Devices
are just a wrapper around the same legacy PIRQ router
seen in legacy mode.

The added twist is that it is possible for VIA
to do quirks in ACPI automatically if they want to --
since all it takes is a few lines of AML where we set the link
to a new state.  (we should go see if they're doing this now --
in the past I don not think they did, and so quirks are probably
still needed in ACPI mode on at least old machines)

2. quirks are independent of PIC/IOAPIC

In both ACPI on and ACPI off modes, we tend to touch PIC
interrupts as _little_ as possible.  So it may be that
our system boots up just fine in PIC mode w/o quirks --
but the reason may be because we didn't try to invoke any irq mappings
--
we found we could live with what the BIOS left us and we
used it untouched.

As the IOAPIC is disabled in the default BIOS mode,
we always have to set that up, and a good part of the time
we have to choose our own mappings, so quirks are more likely
to be noticed to be ncessary in IOAPIC mode.

hope this helps,
-Len
-
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/

Powered by blists - more mailing lists