From: "Timothy A. Seufert" <tas@mindspring.com>
To: Albrecht Dreß <ad@mpifr-bonn.mpg.de>,
LinuxPPC-Dev Liste <linuxppc-dev@lists.linuxppc.org>
Subject: Re: FireWire chip on PISMO?
Date: Thu, 4 May 2000 23:29:54 -0700 [thread overview]
Message-ID: <v04220803b5381a8fbf73@[10.0.0.42]> (raw)
In-Reply-To: <39111625.9D1FD101@mpifr-bonn.mpg.de>
At 8:18 AM +0200 5/4/00, Albrecht Dreß wrote:
>Does anyone know where I could find information about the FireWire controller
>chip which is used in the Apple PISMO Powerbook? lspci tells me that it was
>made by Apple, device id 0x0018, and I think this one is not (yet)
>supported by
>the FireWire-for-Linux stuff.
It's a OHCI FireWire controller inside of Apple's Uni-N custom ASIC.
Since it's OHCI, support should theoretically be a matter of just
letting the FireWire code know about its device ID (if it doesn't
already).
Tim Seufert
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2000-05-05 6:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-04 6:18 FireWire chip on PISMO? Albrecht Dre_
2000-05-04 6:53 ` David A. Gatwood
2000-05-04 9:36 ` Albrecht Dre_
2000-05-05 6:29 ` Timothy A. Seufert [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='v04220803b5381a8fbf73@[10.0.0.42]' \
--to=tas@mindspring.com \
--cc=ad@mpifr-bonn.mpg.de \
--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).