From: Lionel Bouton <Lionel.Bouton@inet6.fr>
To: nn@broadcom.com
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: SiS pci target abort?
Date: Wed, 05 Jun 2002 00:30:30 +0200 [thread overview]
Message-ID: <3CFD3F86.7000302@inet6.fr> (raw)
> I'm running a linux 2.4.18 kernel on a PC with SiS glue chip:
>
> cubox2.sj.broadcom.com$ lspci
> 00:00.0 Host bridge: Silicon Integrated Systems [SiS]: Unknown device
0650 (rev 01)
> 00:01.0 PCI bridge: Silicon Integrated Systems [SiS] 5591/5592 AGP
> 00:02.0 ISA bridge: Silicon Integrated Systems [SiS] 85C503/5513
> 00:02.2 USB Controller: Silicon Integrated Systems [SiS] 7001 (rev 07)
> 00:02.3 USB Controller: Silicon Integrated Systems [SiS] 7001 (rev 07)
> 00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE]
(rev d0)
> 00:02.7 Multimedia audio controller: Silicon Integrated Systems [SiS]
SiS7012 PCI
> +Audio Accelerator (rev a0)
> 00:03.0 Ethernet controller: Silicon Integrated Systems [SiS] SiS900
10/100
> +Ethernet (rev 90)
> 00:0f.0 Network controller: BROADCOM Corporation: Unknown device 4301
> 01:00.0 VGA compatible controller: Silicon Integrated Systems [SiS]:
Unknown device
> +6325
>
> Reading a Broadcom device register which returns a pci target abort
> will return the last value read, the SiS chip actually cycles thru the
> last 4 recently read values, instead of returning 0xffffffff like all
> other PC system chips I've ever seen. Is this a known SiS chip bug?
>
> Thanks much for any info you could provide.
>
> neal nuckolls
> nn@broadcom.com
Not much info as I don't have the hardware here to reproduce your
config. From your e-mail address I assume you're developing Linux
drivers for your network cards or debugging a problem with existing ones.
I took the liberty of forwarding your e-mail to the linux-kernel mailing
list. If this problem is known there are chances one subscriber is aware
of it (there are SiS people around here).
LB.
reply other threads:[~2002-06-04 22:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3CFD3F86.7000302@inet6.fr \
--to=lionel.bouton@inet6.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=nn@broadcom.com \
/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