From: Ira Weiny <iweiny@acm.org>
To: Linux1394dev <linux1394-devel@lists.sourceforge.net>,
linuxppc-dev <linuxppc-dev@lists.linuxppc.org>
Subject: 1394(sbp2) working on TiBook
Date: Fri, 22 Jun 2001 11:34:49 -0700 [thread overview]
Message-ID: <3B338FC9.558D2753@acm.org> (raw)
Sorry I have been away for a bit...
Thanks to Ben Collins, your sbp2 patch worked great in getting my
Firewire drive up on the TiBook.
Therefore, I have a patch which _I_ _think_ makes the TiBook work with
sbp2. I have mounted the drive copied files to it and rebooted to MacOS
and the files are fine.
However, my company has an anylizer on loan and I still think there are
endianess issues... I see a lot of byte swapping in the sbp2 driver,
and I have not tried this on my x86 machine yet. Sorry really busy
right now.
If anyone out there would like to do some testing I can give you a patch
against the current 1394 cvs tree. This would include the sbp2 patches
from Ben as I did not separate them out... Sorry for those on 2.2
kernels, I think this breaks you?
Still working,
Ira Weiny
iweiny@acm.org
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
reply other threads:[~2001-06-22 18:34 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=3B338FC9.558D2753@acm.org \
--to=iweiny@acm.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 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).