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]
Message-Id: <1212509143.22357.23.camel@londonpacket.bos.redhat.com>
Date:	Tue, 03 Jun 2008 12:05:43 -0400
From:	Jon Masters <jonathan@...masters.org>
To:	Olaf Dabrunz <od@...e.de>
Cc:	Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...e.hu>,
	"H. Peter Anvin" <hpa@...or.com>, linux-kernel@...r.kernel.org,
	Stefan Assmann <sassmann@...e.de>
Subject: Re: [PATCH 4/7] disable broadcomm legacy boot interrupt generation


On Tue, 2008-06-03 at 17:59 +0200, Olaf Dabrunz wrote:
> On 03-Jun-08, Jon Masters wrote:
> > On Mon, 2008-06-02 at 14:45 +0200, Olaf Dabrunz wrote:
> > 
> > > Add a quirk to disable legacy boot interrupt generation on broadcomm HT1000.
> > 
> > This one interests me, because I got access to the Broadcom HT-1000
> > datasheet and could not find this feature mentioned in there. I'd
> > appreciate knowing how you figured this one out :)
> 
> I had a sharp look at it... ;)

Me too. It's ***NOT*** mentioned in there :)

> Actually, I looked through the datasheet three times, and did not find
> anything. Then I looked at the IRQ routing picture until I had an idea
> of how it is supposed to work and the solution was becoming clear. The
> register descriptions made me believe it could work, and testing
> confirmed this.

Oh, ok, now that takes some inordinate amount of dedication (on the
level of commitable...I mean dude, WTF? :P). Someone should call the LHC
and let them know you've got a way to detect the undetectable.

Jon.


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