Re: Firewire driver available
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 Projects Group/TTM To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Firewire driver available
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 uses. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Firewire driver available
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 [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Firewire driver available
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 is. Firewire is Apple's name. I believe that it is also an Apple trademark, that's why no one but Apple sells 1394 components under the Firewire name. Adopting the same name could get FreeBSD into trouble irregardless of who works there. Scott To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Firewire driver available
+ [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 you know the current situation of development by NetBSD? If development is separate, power has dispersed. It will become a loss for BSD. -- Toshihiko ARAI To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Firewire driver available
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 that NetBSD : uses. : : Do you know the current situation of development by NetBSD? : If development is separate, power has dispersed. It will become a : loss for BSD. I do not have a laptop running NetBSD that has a ieee1394 device on it. However, looking at their sys/dev/ieee1394, it appears that they have a fairly complete setup. I don't know if it works or not, but it is there for anyone to see. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Firewire driver available
+ 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. http://focus.ti.com/docs/prod/productfolder.jhtml?genericPartNumber=TSB43AA22 It is used with the following machine at least: VAIO PCG-R505/ABW /kernel: pci1: unknown card (vendor=0x104c, dev=0x8021) at 0.0 irq 3 VAIO PCG-C1VS none2@pci0:8:0: class=0x0c0010 card=0x80b2104d chip=0x8021104c rev=0x02 hdr=0x00 Because both added it to probe routine of fwohci, the device was recognized. As for PCG-C1VS, DVTS seems to have worked. However, both is firewire driver of 4.x base. By the way, alias of firewire was i.LINK and IEEE1394, but the FreeBSD people selected it as firewire? -- Toshihiko ARAI To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Firewire driver available
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 Japan. I prefer the name as firewire. Toshihiko ARAI wrote: + 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". http://focus.ti.com/docs/prod/productfolder.jhtml?genericPartNumber=TSB43AA22 It is used with the following machine at least: VAIO PCG-R505/ABW /kernel: pci1: unknown card (vendor=0x104c, dev=0x8021) at 0.0 irq 3 VAIO PCG-C1VS none2@pci0:8:0: class=0x0c0010 card=0x80b2104d chip=0x8021104c rev=0x02 hdr=0x00 Because both added it to probe routine of fwohci, the device was recognized. As for PCG-C1VS, DVTS seems to have worked. However, both is firewire driver of 4.x base. By the way, alias of firewire was i.LINK and IEEE1394, but the FreeBSD people selected it as firewire? -- Toshihiko ARAI To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Firewire driver available
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 2980 yen(about $25) in KOBE. Please port this patch to 5-current. http://kobe1995.net/~kaz/FreeBSD/IEEE1394.html Enjoy IEEE1394! -- mailto:[EMAIL PROTECTED] NAKAMURA Kazushi@KOBE http://kobe1995.net/~kaz/index-e.html To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Firewire driver available
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
http://developer.intel.com/technology/1394/download/ohci_11.htm
Of cource I refered USB driver code before rewriting the firewire
driver. However, I believe it is difficult to merge USB and fiirewire
OHCI.
Julian Elischer wrote:
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{} seems to suggest it's from the ahb driver
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Firewire driver available
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 to the liist of supporting chipset, if we get volunteer. NAKAMURA Kazushi wrote: 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 2980 yen(about $25) in KOBE. Please port this patch to 5-current. http://kobe1995.net/~kaz/FreeBSD/IEEE1394.html Enjoy IEEE1394! -- mailto:[EMAIL PROTECTED] NAKAMURA Kazushi@KOBE http://kobe1995.net/~kaz/index-e.html To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Firewire driver available
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 other (or even better, a merged version if there are things each does not do) into the tree soon. Can you clear the situation? I have the USENIX paper here (I actually attended) and am reading it now. Julian On Wed, 5 Sep 2001, Katsushi Kobayashi wrote: 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 to the liist of supporting chipset, if we get volunteer. NAKAMURA Kazushi wrote: 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 2980 yen(about $25) in KOBE. Please port this patch to 5-current. http://kobe1995.net/~kaz/FreeBSD/IEEE1394.html Enjoy IEEE1394! -- mailto:[EMAIL PROTECTED] NAKAMURA Kazushi@KOBE http://kobe1995.net/~kaz/index-e.html To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Firewire driver available
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. However, noone supported this version, and also I have no intention to use socket I/F for firewire.So, I offered with the updated version. Anyway, I cannot find any advantage to merge it. If FreeBSD folks support the former version, someone will maintain it. BTW, my USENIX paper based on the former one, and I can write an updated paper, if necessary. Julian Elischer wrote: 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 other (or even better, a merged version if there are things each does not do) into the tree soon. Can you clear the situation? I have the USENIX paper here (I actually attended) and am reading it now. Julian On Wed, 5 Sep 2001, Katsushi Kobayashi wrote: 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 to the liist of supporting chipset, if we get volunteer. NAKAMURA Kazushi wrote: 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 2980 yen(about $25) in KOBE. Please port this patch to 5-current. http://kobe1995.net/~kaz/FreeBSD/IEEE1394.html Enjoy IEEE1394! -- mailto:[EMAIL PROTECTED] NAKAMURA Kazushi@KOBE http://kobe1995.net/~kaz/index-e.html To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Firewire driver available
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{} seems to suggest it's from the ahb driver
--
++ __ _ __
| __--_|\ Julian Elischer | \ U \/ / hard at work in
| / \ [EMAIL PROTECTED] +--x USA\ a very strange
| ( OZ)\___ ___ | country !
+- X_.---._/presently in San Francisco \_/ \\
v
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Firewire driver available
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 worthwhile to have a look whether we could integrate the
two.
Nick
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{} seems to suggest it's from the ahb driver
--
++ __ _ __
| __--_|\ Julian Elischer | \ U \/ / hard at work in
| / \ [EMAIL PROTECTED] +--x USA\ a very strange
| ( OZ)\___ ___ | country !
+- X_.---._/presently in San Francisco \_/ \\
v
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
