linux-kernel - Re: [PATCH 001/001] i386/pci: fix nibble permutation and add Cyrix 5530 IRQ router

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: <20061124133544.5334f789@localhost.localdomain>
Date:	Fri, 24 Nov 2006 13:35:44 +0000
From:	Alan <alan@...rguk.ukuu.org.uk>
To:	Juergen Beisert <juergen127@...uzholzen.de>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 001/001] i386/pci: fix nibble permutation and add Cyrix
 5530 IRQ router

> Hmmmm, as I understand the source, it let the routing register entries 
> unchanged if the BIOS did it before. This is why it (IMHO) works. But if this 

The 5530 isn't matched by the PCI router code so we fall back to the PCI
BIOS32 services which do know what they are doing.

> routine tries to set a new route it fails due to it writes the wrong register 
> nibble. But maybe I'm wrong, I will read the source again (and try to get a 
> CS5520 datasheet).

I have the 5520 data sheet. For IRQ routing the 5520 and 5530 are
identical according to the docs and code according to the docs doens't
generally work ..

If you need to set these for LinuxBIOS then perhaps matching and setting
it up only if LinuxBIOS is present would be the better choice ?

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