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: <DBFABB80F7FD3143A911F9E6CFD477B00E48D33E@hqemmail02.nvidia.com>
Date:	Fri, 27 Oct 2006 14:28:14 -0700
From:	"Allen Martin" <AMartin@...dia.com>
To:	"Robert Hancock" <hancockr@...w.ca>,
	"linux-kernel" <linux-kernel@...r.kernel.org>
Cc:	<linux-ide@...r.kernel.org>, "Andrew Morton" <akpm@...l.org>,
	"Andi Kleen" <ak@...e.de>, <pitt@...fault.info>
Subject: RE: [PATCH] sata_nv ADMA/NCQ support for nForce4 (v7)

> Another update to this patch, now version 7. This greatly 
> simplifies the 
> interrupt handler and gets rid of some of the weird code 
> relating to the 
> notifier clear registers (as well as a potential uninitialized value 
> usage that was in version 6). There still seems to be the 
> need to do a 
> notifier clear in the interrupt handler even when the notifiers are 
> empty. I'm not sure why that is, it would be nice to get some 
> input from 
> NVIDIA or those with the hardware specs as to what writing values 
> (including zero values) to the notifier clear registers actually does.

You always have to write both notifiers even if one is 0, no interrupt
ack takes place until both are written. 

-----------------------------------------------------------------------------------
This email message is for the sole use of the intended recipient(s) and may contain
confidential information.  Any unauthorized review, use, disclosure or distribution
is prohibited.  If you are not the intended recipient, please contact the sender by
reply email and destroy all copies of the original message.
-----------------------------------------------------------------------------------
-
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