From: Andreas Bombe <andreas.bombe@munich.netsurf.de>
To: Wolfgang Spraul <wspraul@q-ag.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.0: ieee1394: got invalid ack 3 from node 65473 (tcode 4)
Date: Sat, 13 Jan 2001 01:39:19 +0100 [thread overview]
Message-ID: <20010113013919.A1321@storm.local> (raw)
In-Reply-To: <979098522.3a5bdb9aa7a72@ssl.local>
In-Reply-To: <979098522.3a5bdb9aa7a72@ssl.local>; from wspraul@q-ag.de on Wed, Jan 10, 2001 at 04:48:42AM +0100
On Wed, Jan 10, 2001 at 04:48:42AM +0100, Wolfgang Spraul wrote:
> Incompatibility with "Sarotech FHD-352F/U Rev 1.0"
>
> Using an external IDE drive in the Sarotech FireWire enclosure fails, even
> though the Sarotech unit works with Win2K and other SBP2 drives work for me
> (with Linux).
>
> I'm using 2.4.0 together with sbp2_1394_122300.tar.gz.
> ACK code 3 is not even mentioned in ieee1394.h.
That's because it's defined as reserved in the standard and therefore it
says "invalid ack". The interesting would be whether we really get
that code or if there is a bug in the driver somewhere.
> I understand that the SBP2 driver is not (yet) included, but it will be shortly.
> Also, I guess the same problem applies to raw1394.o together with the Sarotech
> enclosure.
Could you test that with testlibraw? (This program is built with libraw
and not installed currently.)
--
Andreas E. Bombe <andreas.bombe@munich.netsurf.de> DSA key 0x04880A44
http://home.pages.de/~andreas.bombe/ http://linux1394.sourceforge.net/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2001-01-13 0:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-10 3:48 2.4.0: ieee1394: got invalid ack 3 from node 65473 (tcode 4) Wolfgang Spraul
2001-01-13 0:39 ` Andreas Bombe [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=20010113013919.A1321@storm.local \
--to=andreas.bombe@munich.netsurf.de \
--cc=linux-kernel@vger.kernel.org \
--cc=wspraul@q-ag.de \
/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