From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: linux-mips@vger.kernel.org
Subject: Loongson3 PCI/EHCI
Date: Tue, 7 Dec 2021 17:29:19 +0100 [thread overview]
Message-ID: <20211207162919.GB19327@alpha.franken.de> (raw)
Hi,
I'm getting lots of
[ 2.940587] pci 0000:00:04.1: EHCI: unrecognized capability ff
[ 2.946478] pci 0000:00:04.1: EHCI: unrecognized capability ff
[ 2.952374] pci 0000:00:04.1: EHCI: unrecognized capability ff
[ 2.958270] pci 0000:00:04.1: EHCI: unrecognized capability ff
[ 2.964166] pci 0000:00:04.1: EHCI: unrecognized capability ff
[ 2.970062] pci 0000:00:04.1: EHCI: unrecognized capability ff
while booting on a Loongson-3A R4 (Loongson-3A4000) @ 1800MHz system.
What I'm missing ?
I'm also seeing
[ 1.222546] pci_bus 0000:00: 2-byte config write to 0000:00:00.0 offset 0x4 m
ay corrupt adjacent RW1C bits
[ 1.232314] pci_bus 0000:00: 2-byte config write to 0000:00:00.0 offset 0x4 m
ay corrupt adjacent RW1C bits
which look suspicous...
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
next reply other threads:[~2021-12-07 16:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-07 16:29 Thomas Bogendoerfer [this message]
2021-12-08 1:49 ` Loongson3 PCI/EHCI Huacai Chen
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=20211207162919.GB19327@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=linux-mips@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox