All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nikolai Zhubr <zhubr.2@gmail.com>
To: "Maciej W. Rozycki" <macro@orcam.me.uk>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
	"H. Peter Anvin" <hpa@zytor.com>, Arnd Bergmann <arnd@kernel.org>,
	x86@kernel.org, linux-pci@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] x86/PCI: Handle PIRQ routing tables with no router device given
Date: Fri, 09 Jul 2021 01:39:59 +0300	[thread overview]
Message-ID: <60E77EBF.2020605@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.21.2107082226040.6599@angie.orcam.me.uk>

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
>


  reply	other threads:[~2021-07-08 22:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-06 11:30 [PATCH v2] x86/PCI: Handle PIRQ routing tables with no router device given Maciej W. Rozycki
2021-07-08 16:25 ` Nikolai Zhubr
2021-07-08 20:45   ` Maciej W. Rozycki
2021-07-08 22:39     ` Nikolai Zhubr [this message]
2021-07-08 23:35       ` Maciej W. Rozycki

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=60E77EBF.2020605@gmail.com \
    --to=zhubr.2@gmail.com \
    --cc=arnd@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=bp@alien8.de \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=macro@orcam.me.uk \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.