From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Paul Mackerras <paulus@samba.org>
Cc: Jarod Wilson <jwilson@redhat.com>,
benh@kernel.crashing.org, Kristian Hoegsberg <krh@bitplanet.net>,
linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org,
sparclinux@vger.kernel.org,
linux1394-devel@lists.sourceforge.net,
Sam Ravnborg <sam@ravnborg.org>,
Harvey Harrison <harvey.harrison@gmail.com>
Subject: Re: [PATCH 1/2] firewire: endianess fix
Date: Fri, 29 Feb 2008 12:52:41 +0100 [thread overview]
Message-ID: <47C7F209.9030907@s5r6.in-berlin.de> (raw)
In-Reply-To: <18375.60394.166769.540668@cargo.ozlabs.ibm.com>
Paul Mackerras wrote:
> Jarod Wilson writes:
>> I wonder how many people still actually 1) have a machine
>> with this controller, 2) are running Linux on it and 3) use firewire
>> devices with it. Both of you, please speak up, we're trying to help you!
>> (if only out of morbid curiosity to see this mythical goofy controller).
>
> I have a first-generation titanium powerbook that has this controller
> (assuming we're talking about vendor/device id = 0x106b / 0x18), and
> yes I run Linux (only) on it and use firewire disks. :)
I actually have a TiBook 400 myself, but so far without Linux, and its
FireWire PHY is dead. But I can use CardBus FireWire cards on it to do
basic testing on a big endian PC, and I can test the selfID
byte-swapping by the PHY-less onboard controller.
I now started a Fedora 8 live CD (self-test says the medium is
corrupt... need to burn another one) and dmesg says:
firewire_ohci: Added fw-ohci device 0002:24:0e.0, OHCI version 1.0
firewire_ohci: recursive bus reset detected, discarding self ids
[...]
The second line looks like this is indeed one of those which needs the
header byte-swap workaround which ohci1394 has but firewire-ohci hasn't yet.
On the weekend I'm going to attempt to put Linux on this PowerBook, at last.
--
Stefan Richter
-=====-==--- --=- ===-=
http://arcgraph.de/sr/
next prev parent reply other threads:[~2008-02-29 11:55 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-20 22:03 sparse - make __CHECK_ENDIAN__ default enabled? Sam Ravnborg
2008-02-20 22:18 ` Harvey Harrison
2008-02-23 11:23 ` [PATCH 0/2] firewire: endinaness warnings (was Re: sparse - make __CHECK_ENDIAN__ default enabled?) Stefan Richter
2008-02-23 11:24 ` [PATCH 1/2] firewire: endianess fix Stefan Richter
2008-02-23 11:36 ` Stefan Richter
2008-02-23 12:12 ` Stefan Richter
2008-03-01 12:36 ` Stefan Richter
2008-02-27 19:58 ` Jarod Wilson
2008-02-27 20:08 ` Stefan Richter
2008-02-27 20:21 ` Jarod Wilson
2008-02-28 2:40 ` Benjamin Herrenschmidt
2008-02-28 3:21 ` Jarod Wilson
2008-02-28 6:25 ` Benjamin Herrenschmidt
2008-02-28 18:42 ` Jarod Wilson
2008-02-28 23:26 ` Benjamin Herrenschmidt
2008-02-29 5:48 ` Jarod Wilson
2008-02-29 6:00 ` Benjamin Herrenschmidt
2008-02-29 11:26 ` Paul Mackerras
2008-02-29 11:52 ` Stefan Richter [this message]
2008-02-29 21:49 ` Benjamin Herrenschmidt
2008-02-29 15:34 ` Jarod Wilson
2008-03-03 9:19 ` Gabriel Paubert
2008-03-03 14:35 ` Stefan Richter
2008-03-05 22:59 ` Gabriel Paubert
2008-03-05 23:26 ` Stefan Richter
2008-03-06 20:23 ` Gabriel Paubert
2008-02-28 3:33 ` Jarod Wilson
2008-02-28 2:41 ` Benjamin Herrenschmidt
2008-02-28 8:41 ` Stefan Richter
2008-02-23 11:24 ` [PATCH 2/2] firewire: endianess annotations Stefan Richter
2008-03-01 5:23 ` [PATCH 0/2] firewire: endinaness warnings (was Re: sparse - make __CHECK_ENDIAN__ default enabled?) Jarod Wilson
2008-02-20 22:39 ` sparse - make __CHECK_ENDIAN__ default enabled? Harvey Harrison
2008-02-20 22:51 ` Sam Ravnborg
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=47C7F209.9030907@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=benh@kernel.crashing.org \
--cc=harvey.harrison@gmail.com \
--cc=jwilson@redhat.com \
--cc=krh@bitplanet.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=sam@ravnborg.org \
--cc=sparclinux@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).