linux-kernel - Re: [PATCH 3/3] PNP: add ISAPnP MPU option quirks

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

Message-ID: <48261A29.9020308@keyaccess.nl>
Date:	Sat, 10 May 2008 23:56:57 +0200
From:	Rene Herman <rene.herman@...access.nl>
To:	Bjorn Helgaas <bjorn.helgaas@...com>
CC:	Uwe Bugla <uwe.bugla@....de>, Takashi Iwai <tiwai@...e.de>,
	Len Brown <len.brown@...el.com>, Andrew Morton <akpm@...l.org>,
	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 3/3] PNP: add ISAPnP MPU option quirks

On 10-05-08 23:48, Rene Herman wrote:

> PNP: add ISAPnP MPU option quirks.
> 
> The AD181x and AZT230 chips don't support an IRQ-less MPU401 option
> but work fine without one. This adds (priority functional) IRQ-less
> options for each port option to help systems with few available IRQs.
> 
> The AD1815 quirk can't use pnp_register_irq_resource() due to doubly
> penalizing the IRQ. Also, while not a practical issue due to no IRQ
> option being present for the dependents, this needs to add in front,
> not back.
> 
> Doesn't use pnp_register_port_resource() for symetry with above.
> 
> This does not delete the AD1815 independent option even though it
> should be empty after the IRQ transfer due to AD1816 coming with an
> empty but still present independent option by default.
> 
> Was tested on AD1815, AD1816 and AZT230. The ALSA snd-ad1818a driver

Typo: AZT2320

> also support the AZT2002 ID for MPU401 but this doesn't as I was
> unable to test it.
> 
> Signed-off-by: Rene Herman <rene.herman@...il.com>

Rene.
--
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/