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: <60E77EBF.2020605@gmail.com>
Date:   Fri, 09 Jul 2021 01:39:59 +0300
From:   Nikolai Zhubr <zhubr.2@...il.com>
To:     "Maciej W. Rozycki" <macro@...am.me.uk>
CC:     Bjorn Helgaas <bhelgaas@...gle.com>,
        Thomas Gleixner <tglx@...utronix.de>,
        Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
        "H. Peter Anvin" <hpa@...or.com>, Arnd Bergmann <arnd@...nel.org>,
        x86@...nel.org, linux-pci@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] x86/PCI: Handle PIRQ routing tables with no router
 device given

08.07.2021 23:45, Maciej W. Rozycki:
>   Have you tried contacting Nvidia about your ALI chipset?  Back in the day
> I tried to avoid undocumented stuff and Intel was reasonably open about
> most of their chipsets.

Well, being neither their customer nor a kernel developer, I'm not sure 
my request would be considered serious. Anyway, probably I'll give it a 
try a bit later when I have an opportunity to dismount this board for 
more comfortable testing. I was also going to try to modify its BIOS to 
remove some unwanted behaviour unrelated to IRQs, and it might happen 
that I also discover something about PCI handling along with (It is just 
64k size, after all, and I have a 8086 debugger)


Thank you,

Regards,
Nikolai


>    Maciej
>

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ