firewire driver
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 files
required (0x8027).
The problem is when booting I get "could not map memory" error
in this part of code:
---
fwohci.c:
#define DEF_CACHE_LINE 0x10
cache_line = DEF_CACHE_LINE;
pci_write_config(dev, PCIR_CACHELNSZ, cache_line, 1);
/**/
fun = pci_read_config(dev, 0xf0, 4);
fun |= 7;
pci_write_config(dev, 0xf0, fun, 4);
/**/
rid = PCI_MAP_REG_START;
sc->fc.mem = bus_alloc_resource(dev, SYS_RES_MEMORY, &rid,
0, ~0, 1, RF_ACTIVE);
if (!sc->fc.mem) {
device_printf(dev, "could not map memory\n");
error = ENXIO;
goto fail;
}
sc->base = rman_get_virtual(sc->fc.mem);
#endif /* __FreeBSD__ */
ifp->if_flags &= ~IFF_UP;
/* Stop all DMA operation db.immediately */
fwohci_stop_dma(sc, -1);
---
I tried to use
#define PCI_ENABLE_IO_MODES
in pci/pci.c but got no difference. I've noticed there is
a option PCI_ENABLE_IO_MODES in -CURRENT kernel, but I'm
not able to use it since this machine is a production one.
I think this option can help somehow - at least it seems so
from the description of this option in LINT. But I haven't
seen it in 4-STABLE.
What I'm suspicious about is this part of dmesg:
found-> vendor=0x104c, dev=0x8027, revid=0x00
class=0c-00-10, hdrtype=0x00, mfdev=1
subordinatebus=0secondarybus=0
cmdreg=0x0006, statreg=0x0210, cachelnsz=8 (dwords)
lattimer=0x40 (1920 ns), mingnt=0x02 (500 ns), maxlat=0x04 (1000 ns)
intpin=a, irq=11
which seems to me like BIOS forgot to allocate some memory for
this card.
Just to mention: card itself is OK since it's working on the same machine
in Windows 2000 (e.g. in Adobe Premiere 6.0). But it's possible
Windows driver does the allocation on its own (btw: Windows drivers
are the default ones: 1394bus.sys and ohci1394.sys).
Does anybody have some idea how to move on?
With best regards,
Petr Holub
Petr Holub
CESNET z.s.p.o. Supercomputing Center Brno
Zikova 2 Institute of Compt. Science
10200 Praha, CZ Masaryk University
Czech Republic Botanicka 68a, 60200 Brno, CZ
e-mail: [EMAIL PROTECTED] phone: +420-5-41512278
e-mail: [EMAIL PROTECTED]
dmesg.KLOBOUCEK
Description: Binary data
Re: Firewire driver is updated
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 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 effort > > to A/V functions of the firewire. So,I release the SBP-2 code for the > > start point of somebody who would loves storage on the firewire. > > > > The URL of the latest code is: > > > > ftp://ftp.uec.ac.jp/pub/firewire/beta/firewire-freebsd-5.0-20010918 > > Can't build fresh -CURRENT kernel with this patch: > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Firewire driver is updated
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 after busreset. However, I would like to use my effort > to A/V functions of the firewire. So,I release the SBP-2 code for the > start point of somebody who would loves storage on the firewire. > > The URL of the latest code is: > > ftp://ftp.uec.ac.jp/pub/firewire/beta/firewire-freebsd-5.0-20010918 Can't build fresh -CURRENT kernel with this patch: vbook#/usr/src.local/sys/i386/compile/VBOOK 168_> make kernel cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../../.. -I../../../dev -I../../../contrib/dev/acpica -I../../../contrib/ipfilter -I/usr/include -D_KERNEL -include opt_global.h -elf -O3 -mpentiumpro -mpreferred-stack-boundary=2 ../../../dev/firewire/firewire.c ../../../dev/firewire/firewire.c:133: warning: initialization makes pointer from integer without a cast ../../../dev/firewire/firewire.c:142: conflicting types for `fw_open' ../../../dev/firewire/firewire.c:85: previous declaration of `fw_open' ../../../dev/firewire/firewire.c:170: conflicting types for `fw_close' ../../../dev/firewire/firewire.c:86: previous declaration of `fw_close' ../../../dev/firewire/firewire.c:698: conflicting types for `fw_ioctl' ../../../dev/firewire/firewire.c:87: previous declaration of `fw_ioctl' ../../../dev/firewire/firewire.c: In function `fw_rcv': ../../../dev/firewire/firewire.c:2129: warning: long unsigned int format, __uint32_t arg (arg 3) ../../../dev/firewire/firewire.c: In function `fw_vmaccess': ../../../dev/firewire/firewire.c:2247: warning: long unsigned int format, __uint32_t arg (arg 5) ../../../dev/firewire/firewire.c:2247: warning: long unsigned int format, __uint32_t arg (arg 6) ../../../dev/firewire/firewire.c:2247: warning: long unsigned int format, __uint32_t arg (arg 7) ../../../dev/firewire/firewire.c:2247: warning: long unsigned int format, __uint32_t arg (arg 8) ../../../dev/firewire/firewire.c:2248: warning: long unsigned int format, __uint32_t arg (arg 2) ../../../dev/firewire/firewire.c:2248: warning: long unsigned int format, __uint32_t arg (arg 3) ../../../dev/firewire/firewire.c:2248: warning: long unsigned int format, __uint32_t arg (arg 4) ../../../dev/firewire/firewire.c:2248: warning: long unsigned int format, __uint32_t arg (arg 5) *** Error code 1 Stop in /usr/src.local/sys/i386/compile/VBOOK. Any suggestions ? Will my Sony Firewire controller (in VAIO Z505S) work with these drivers ? # dmesg | grep FireWire pci0: at device 9.0 (no driver attached) # sudo pciconf -l | grep pci0:9 none1@pci0:9:0: class=0x0c card=0x8054104d chip=0x8009104d rev=0x01 hdr=0x00 # -- TSB Russian Express, Moscow Vladimir B. Grebenschikov, [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Firewire driver is updated
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 effort to A/V functions of the firewire. So,I release the SBP-2 code for the start point of somebody who would loves storage on the firewire. The URL of the latest code is: ftp://ftp.uec.ac.jp/pub/firewire/beta/firewire-freebsd-5.0-20010918 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
+ <[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
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
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
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
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
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: (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
+ 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: (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
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
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
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
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
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 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
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
