netdev - Re: Realtek 8139 problem on 486.

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]

Date:   Sat, 17 Jul 2021 01:48:07 +0200 (CEST)
From:   "Maciej W. Rozycki" <macro@...am.me.uk>
To:     Nikolai Zhubr <zhubr.2@...il.com>
cc:     Arnd Bergmann <arnd@...nel.org>,
        Thomas Gleixner <tglx@...utronix.de>,
        Heiner Kallweit <hkallweit1@...il.com>,
        netdev <netdev@...r.kernel.org>,
        the arch/x86 maintainers <x86@...nel.org>,
        Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
        "H. Peter Anvin" <hpa@...or.com>
Subject: Re: Realtek 8139 problem on 486.

Hello Nikolai,

> >   I have actually tracked a datasheet down now, so I'll see what I can do.
> > The southbridge has a separate edge/level trigger mode control register
> > for PIRQ lines in addition to the usual ELCR register, so it will require
> > extra handling and the wording is not as clear as with Intel documentation
> > (understandably), so it may require further experimentation.
> 
> Thank you very much for investigating this! Tomorrow I'll likely be able 
> to pull this motherboard out and arrange it for whatever testing might 
> be necessary. However I'll be in a trip for a couple of weeks soon so 
> please excuse some possible delay in my replies. I'm definitely willing 
> to make all efforts to get it supported.

 I have preliminary code ready for submission, so I only need to wrap it 
up for posting.  However it requires some additional infrastructure shared 
with other parts of the kernel, so it will be a small patch series again, 
and due to code dependencies I'll include support for another PIRQ router 
as well as some clean-ups, because they all need to be applied in order.  
With that in place we should have complete coverage for Intel chipsets.

 Moreover based on the ALi M1533 datasheet I have also tracked down I have 
noticed we have bugs in the handling for the other ALi chipsets, which I 
seem unable to satisfactorily resolve without a copy of the ALi M1563 
datasheet I don't have.  I've noticed Nvidia does continue having at least 
some ALi-related stuff online, so chances are they have retained the ALi 
legacy internally.  I have therefore requested a copy of the M1563 
datasheet and will likely extend the patch series accordingly, whether I 
do or do not receive the document.

 Stay tuned.

  Maciej