On Thu, Sep 06, 2001 at 12:43:59PM +0900, Katsushi Kobayashi wrote:
I believe the name iLink is not popular in outside of Japan.
AFAIK that is Sony's name for it.
Mark
--
Mark Santcroos RIPE Network Coordination Centre
http://www.ripe.net/home/mark/ New
In message [EMAIL PROTECTED] Toshihiko
ARAI-san writes:
: By the way, alias of firewire was i.LINK and IEEE1394, but the FreeBSD
: people selected it as firewire?
FreeBSD hasn't selected a name, but lots of folks here call it
firewire. I'd be strongly inclined to use the same name that NetBSD
In message [EMAIL PROTECTED] Mark Santcroos writes:
: On Thu, Sep 06, 2001 at 12:43:59PM +0900, Katsushi Kobayashi wrote:
: I believe the name iLink is not popular in outside of Japan.
:
: AFAIK that is Sony's name for it.
IT is. Firewire is Apple's name.
Warner
To Unsubscribe: send mail to
On Thu, Sep 06, 2001 at 09:55:17AM -0600, Warner Losh wrote:
In message [EMAIL PROTECTED] Mark Santcroos writes:
: On Thu, Sep 06, 2001 at 12:43:59PM +0900, Katsushi Kobayashi wrote:
: I believe the name iLink is not popular in outside of Japan.
:
: AFAIK that is Sony's name for it.
IT
+ [EMAIL PROTECTED], Warner Losh wrote:
: By the way, alias of firewire was i.LINK and IEEE1394, but the FreeBSD
: people selected it as firewire?
FreeBSD hasn't selected a name, but lots of folks here call it
firewire. I'd be strongly inclined to use the same name that NetBSD
uses.
Do
In message [EMAIL PROTECTED] Toshihiko ARAI writes:
: : By the way, alias of firewire was i.LINK and IEEE1394, but the FreeBSD
: : people selected it as firewire?
:
: FreeBSD hasn't selected a name, but lots of folks here call it
: firewire. I'd be strongly inclined to use the same name
+ Katsushi Kobayashi wrote:
Anyway, I can add the new chipset to the liist of supporting chipset,
if we get volunteer.
I have small data, device of vendor=0x104c, dev=0x8021 seems to be
TSB43AA22 Integrated 1394a-2000 OHCI PHY/Link Layer Controller.
The plathome developing the driver is used the same chipset. So,
the latest driver support TSB43AA22. Since the exact chipset name
I had not known, the kernel will probe the chipset as "TSBXX".
Thanks for offerring the information.
I believe the name iLink is not popular in outside of
In article [EMAIL PROTECTED]
[EMAIL PROTECTED] writes:
Is there any chance that the OHCI code inthe firewire driver and the OHCI
code in the USB drivers might be rationalised?
There is a IEEE1394 patch for 4.4RC1. It works on my N/B IEEE1394 4-port I/F,
that uses VIA VT6306 chip. I bought it
I have read the specification of OHCI USB only once.
I guess the OHCI specification for firewire and USB has no
concern, even if both basic concept to reduce driver developing
effort for each vender's products are the same.
You can obtain an OHCI chipset specification from
Hello,
I have to notice you that the latest version driver I offered at yesterday
does not have any compatibolity with the base-code of your patch.
Also, I have once offered FreeBSD folks with the former version
at monthes ago. But, they did not accept that one.
Anyway, I can add the new chipset
For thiose of us that are not firewire experts
can you guys tell us:
Are we talking about two completely different firewire implementations
here?
Or ar they based on each other? Are there any major incompatibilities
in the designs?
It's time to import firewire so I'd like to get one or the
Yes, we talk about two implementations. Also both implementations are
written by me. The former one is designed for socket basis API for
firewire. I have once proposed with the former version. Unfortunately,
FreeBSD folks did not accept it. The socket mechanism was pnly one
reason, in that time.
Moved to current:
Is there any chance that the OHCI code inthe firewire driver and the OHCI
code in the USB drivers might be rationalised?
Both seem to talk with the CAM system (from quick reading) as well,
so it might seem that there is some common functionality.
BTW is the struct ahb_softc{}
I haven't looked at the OHCI spec for firewire at all, but it seems that
it was intended to be one specification. The OHCI spec puts a lot of
processing into the hands of the chip and the interaction is smart
enough to not require weird locking or delays (like the UHCI requires),
so it could be
15 matches
Mail list logo
