From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Clemens Ladisch <clemens@ladisch.de>
Cc: "Joel bourrigaud" <joel@bourrigaud.info>,
"Bjørn Forbord" <bforbord@broadpark.no>,
linux1394-devel@lists.sf.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] firewire: ohci: do not bind to Pinnacle or Fujitsu HCI, prevent panic
Date: Mon, 11 Jul 2011 01:50:09 +0200 [thread overview]
Message-ID: <20110711015009.012a26d1@stein> (raw)
In-Reply-To: <20110711012422.1e585783@stein>
On Jul 11 Stefan Richter wrote:
> This device with link layer PCI IDs 11bd:0015 and 1394 PHY IDs
> 00000e:086613 is apparently a Fujitsu MB86613 --- hence the PHY IDs.
> Therefore, blacklist the MB86613 too
On the other hand, maybe the original MB86613 does not exhibit the issue.
The Pinnacle device is combined with another device or function, hence not
identical with MB86613:
0c:07.0 Multimedia controller [0480]: Pinnacle Systems Inc. AV/DV Studio Capture Card [11bd:bede]
Subsystem: Pinnacle Systems Inc. Device [11bd:0023]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort+ <MAbort+ >SERR- <PERR- INTx-
Latency: 64 (2000ns min, 4000ns max), Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 10
Region 0: Memory at fb7ff000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [40] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
0c:07.1 FireWire (IEEE 1394) [0c00]: Pinnacle Systems Inc. Device [11bd:0015] (prog-if 10 [OHCI])
Subsystem: Pinnacle Systems Inc. Device [11bd:0023]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 64 (8000ns min, 20000ns max), Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 10
Region 0: Memory at fb7fe800 (32-bit, non-prefetchable) [size=2K]
Capabilities: [44] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1+,D2+,D3hot+,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Kernel modules: firewire-ohci
BTW, I dimly remember hear-say about Fujitsu controllers, particularly
because they are among the few (or the only ones?) that featured a
programmable PhysicalUpperBound. So there was at least one Linux users who
had such a controller; perhaps as onboard controllers of a Fujitsu
notebook. (Which has got a shorter service life expectancy than a PCI
card...)
--
Stefan Richter
-=====-==-== -=== -=-==
http://arcgraph.de/sr/
prev parent reply other threads:[~2011-07-10 23:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110604002938.78c85881@stein>
[not found] ` <20110604010625.1a37638e@stein>
[not found] ` <4DEA697A.1090104@bourrigaud.info>
[not found] ` <20110612145303.2099aa81@stein>
[not found] ` <4DF4FF4F.4020607@bourrigaud.info>
[not found] ` <20110612210111.3e979131@stein>
[not found] ` <4DF528CF.50407@bourrigaud.info>
[not found] ` <20110709235410.08004e5d@stein>
2011-07-09 22:23 ` [PATCH] firewire: ohci: do not bind to Pinnacle cards, prevent panic Stefan Richter
[not found] ` <4E1A161D.1050304@ladisch.de>
2011-07-10 23:24 ` [PATCH] firewire: ohci: do not bind to Pinnacle or Fujitsu HCI, " Stefan Richter
2011-07-10 23:30 ` Bjørn Forbord
2011-07-10 23:50 ` Stefan Richter [this message]
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=20110711015009.012a26d1@stein \
--to=stefanr@s5r6.in-berlin.de \
--cc=bforbord@broadpark.no \
--cc=clemens@ladisch.de \
--cc=joel@bourrigaud.info \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sf.net \
/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