From: Bill Fink <billfink@mindspring.com>
To: Ben Collins <bcollins@debian.org>
Cc: linux1394-devel@lists.sourceforge.net, linuxppc-dev@lists.linuxppc.org
Subject: Re: Firewire Disk Broken in 2.4.19-pre8-ben0 kernel (was working fine with 2.4.18-ben0)
Date: Mon, 13 May 2002 12:07:48 -0400 [thread overview]
Message-ID: <20020513120748.654bcbc0.billfink@mindspring.com> (raw)
In-Reply-To: <20020513151319.GI494@blimpo.internal.net>
On Mon, 13 May 2002, Ben Collins wrote:
> > ohci1394: $Revision: 1.101 $ Ben Collins <bcollins@debian.org>
>
> Try the SVN code base (check the website for how to download).
Hi Ben,
As I indicated in my earlier message, I already tried the latest
ieee1394-473 tarball (dated May 13). I gave the output from the
ieee1394-444 tarball (dated April 4), since that was the earliest
point I knew it to be broken. For completeness, here is the dmesg
output from the ieee1394-473 tarball:
ohci1394: $Rev: 460 $ Ben Collins <bcollins@debian.org>
ohci1394_0: OHCI-1394 1.0 (PCI): IRQ=[63] MMIO=[80080000-80080800] Max Packet=[2048]
ieee1394: received packet during reset; ignoring
ohci1394_0: Unexpected tcode 0xf(0x6001c1ff) in AR ctx=0, length=-1: dma prg stopped
ieee1394: ConfigROM quadlet transaction error for node 00:1023
ieee1394: Host added: Node[01:1023] GUID[00000000feeb324a] [Linux OHCI-1394]
I know it is reporting "$Rev: 460" but it is in fact from the ieee1394-473
tarball.
-Bill
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-05-13 16:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-13 14:55 Firewire Disk Broken in 2.4.19-pre8-ben0 kernel (was working fine with 2.4.18-ben0) Bill Fink
2002-05-13 15:13 ` Ben Collins
2002-05-13 16:07 ` Bill Fink [this message]
2002-05-13 16:09 ` Ben Collins
2002-05-13 17:29 ` benh
2002-05-14 4:40 ` Bill Fink
2002-05-14 5:57 ` Michel Lanners
2002-05-14 13:09 ` Ben Collins
2002-05-15 2:49 ` Bill Fink
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=20020513120748.654bcbc0.billfink@mindspring.com \
--to=billfink@mindspring.com \
--cc=bcollins@debian.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=linuxppc-dev@lists.linuxppc.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.