Hi all!
I'm struggling my FireWire OHCI based card in my notebook.
I'm using driver from DVTS project (that's what I finally
want to have up and running). I'm running FreeBSD 4.4 Release.
dmesg of my machine is in the attachement (using boot -v).
I've already added proper id for my card in both
I have made a minor correction and updated it to the same site.
"Vladimir B. Grebenschikov" wrote:
Katsushi Kobayashi writes:
Hello,
I have made a quick hack for SBP-2 (known as SCSI over firewire)
for my driver code.
I know this code is testted on my limited environment (only
Katsushi Kobayashi writes:
Hello,
I have made a quick hack for SBP-2 (known as SCSI over firewire)
for my driver code.
I know this code is testted on my limited environment (only verified
fat32 file system), and also lacks a lot of function, e.g. device detach
and reconnect
Hello,
I have made a quick hack for SBP-2 (known as SCSI over firewire)
for my driver code.
I know this code is testted on my limited environment (only verified
fat32 file system), and also lacks a lot of function, e.g. device detach
and reconnect after busreset. However, I would like to use my
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
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
0010 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 Free
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
://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
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
,
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
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
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
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
19 matches
Mail list logo
