From: Rui Saraiva <rmps@joel.ist.utl.pt>
To: linux-kernel@vger.kernel.org
Subject: 2.5.74-bk5 + IEEE1394: ohci1394 doesn't work.
Date: Wed, 9 Jul 2003 09:33:30 +0100 (WEST) [thread overview]
Message-ID: <Pine.LNX.4.44.0307090908260.1552-100000@joel.ist.utl.pt> (raw)
I can't get FireWire/IEEE1394 working on kernel 2.5 (on 2.4 works fine).
When I load ohci1394 module, I get:
ohci1394: $Rev: 986 $ Ben Collins <bcollins@debian.org>
ohci1394_0: OHCI-1394 1.1 (PCI): IRQ=[5] MMIO=[e4800000-e48007ff] Max Packet=[2048]
ieee1394: unsolicited response packet received - np
ieee1394: contents: ffc00160 ffc00000 00000000 e4cd0404
ieee1394: unsolicited response packet received - np
ieee1394: contents: ffc00560 ffc00000 00000000 e4cd0404
And /proc/bus/ieee1394/ is empty.
lspci -vv info:
--------------
00:0e.2 FireWire (IEEE 1394): Creative Labs SB Audigy FireWire Port (prog-if 10 [OHCI])
Subsystem: Creative Labs SB Audigy FireWire Port
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32 (500ns min, 1000ns max), cache line size 08
Interrupt: pin B routed to IRQ 5
Region 0: Memory at e4800000 (32-bit, non-prefetchable) [size=2K]
Region 1: Memory at e4000000 (32-bit, non-prefetchable) [size=16K]
Capabilities: [44] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME+
If you need more info (kernel .config, /proc output, etc), just ask.
Regards,
Rui Saraiva
PS: Please CC me any reply, as I'm not subscribed to LKML.
next reply other threads:[~2003-07-09 8:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-09 8:33 Rui Saraiva [this message]
2003-07-09 10:28 ` 2.5.74-bk5 + IEEE1394: ohci1394 doesn't work Rui Saraiva
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=Pine.LNX.4.44.0307090908260.1552-100000@joel.ist.utl.pt \
--to=rmps@joel.ist.utl.pt \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).