From: Stefan Piger <piger@rvs.uni-hannover.de>
To: benh@kernel.crashing.org
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Again with the firewire
Date: 22 Nov 2001 08:15:02 +0100 [thread overview]
Message-ID: <1006413308.947.0.camel@grobi> (raw)
> Ask Apple what they did ... their chipset isn't documented and they
> didn't opensource their firewire driver for it.
>
> Note that working firewire for pismo/tipb exist in my rsync tree
> or in the linux1394 CVS. Linus and bk _devel aren't up-to-date yet.
>
> Ben.
I can't get firewire to work with your rsync tree on my Pismo (at least
with no one up to yesterday). When I load the modules all looks ok (to
me):
Nov 22 07:23:06 localhost kernel: ohci1394: $Revision: 1.79 $ Ben
Collins <bcollins@debian.org>
Nov 22 07:23:06 localhost kernel: ohci1394_0: OHCI-1394 1.0 (PCI):
IRQ=[40] MMIO=[f5000000-f5001000] Max Packet=[2048]
Nov 22 07:23:06 localhost kernel: ieee1394: sbp2: Driver forced to
serialize I/O (serialize_io = 1)
Nov 22 07:23:06 localhost kernel: scsi1 : IEEE-1394 SBP-2 protocol
driver
After loading the modules, there is no /proc/ohci1394 as I remember from
earllier versions of linux1394.
When I plug in a firewire device the keyboard becomes unusable, but the
machine doesn't crash, I can reboot it via ssh.
I get no error messages in /var/log/messages.
Do you have any idea why it doesn't work? I tried the same on a friends
Pismo an had the same effects!
regards, Stefan
--
Dipl.-Ing. Stefan Piger
Lehrgebiet Rechnernetze und Verteilte Systeme
Universität Hannover
Tel. 0511-762-79-4726
Fax 0511-762-3003
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2001-11-22 7:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-22 7:15 Stefan Piger [this message]
2001-11-22 8:28 ` Again with the firewire Derrik Pates
2001-11-22 11:00 ` benh
2001-11-22 15:18 ` Derrik Pates
2001-11-22 18:21 ` Benjamin Herrenschmidt
2001-11-24 2:08 ` Derrik Pates
2001-11-24 12:21 ` Benjamin Herrenschmidt
2001-11-24 23:32 ` Derrik Pates
2001-11-22 10:59 ` benh
-- strict thread matches above, loose matches on Subject: below --
2001-11-21 16:09 mocm
2001-11-21 18:27 ` benh
2001-11-22 6:31 ` Derrik Pates
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=1006413308.947.0.camel@grobi \
--to=piger@rvs.uni-hannover.de \
--cc=benh@kernel.crashing.org \
--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).