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: <200611161300.27005.dhazelton@enter.net>
Date:	Thu, 16 Nov 2006 13:00:26 -0500
From:	"D. Hazelton" <dhazelton@...er.net>
To:	"Lu, Yinghai" <yinghai.lu@....com>
Cc:	"Olivier Nicolas" <olivn@...llprod.org>,
	"Linus Torvalds" <torvalds@...l.org>,
	"Mws" <mws@...sted-brains.org>, "Jeff Garzik" <jeff@...zik.org>,
	"Krzysztof Halasa" <khc@...waw.pl>,
	"David Miller" <davem@...emloft.net>, linux-kernel@...r.kernel.org,
	tiwai@...e.de
Subject: Re: [PATCH] ALSA: hda-intel - Disable MSI support by default

On Wednesday 15 November 2006 23:25, Lu, Yinghai wrote:
> I think the root cause in hda_intel driver's self.
>
> It gets io-apic irq initialized at first, and it will use
> azx_acquire_irq to install handler after check if MSI can be enabled.
> And when it try to enable the MSI, that will start the int in the chip.
> Even handler for MSI is not installed.
>
> YH

That seems rather stupid. Perhaps installing a conditional handler before 
doing anything with MSI will solve that problem... The problem then just 
revolves around replacing the conditional handler with the real one when MSI 
is fully enabled. If I understood the code for this driver better I'd try to 
make this work. As it stands I'm still trying to recover from the loss of the 
work I did on another project. (DRM based uniform kernel graphics interface - 
had a blackout here that caused my devel machine to crash and left me with a 
trashed drive)

DRH
-
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ