Thread: FCP handling
Brought to you by:
aeb,
bencollins
From: Andreas B. <and...@mu...> - 2000-03-16 04:06:25
|
I added highlevel handling of the FCP_COMMAND and FCP_RESPONSE registers to the subsystem. Reads to those registers are unimplemented, written data will be passed to a highlevel fcp request stream (similarily to the way iso data is handled). raw1394 uses this to pass requests to libraw1394, which has the following new interfaces: typedef int (*fcp_handler_t)(raw1394handle_t, nodeid_t nodeid, int response, size_t length, unsigned char *data); fcp_handler_t raw1394_set_fcp_handler(raw1394handle_t, fcp_handler_t); int raw1394_start_fcp_listen(raw1394handle_t handle); int raw1394_stop_fcp_listen(raw1394handle_t handle); I haven't tested them so far, but everything compiles. That's good. You can get both subsystem and libraw1394 with the changes from CVS (remember, SourceForge CVS repository). -- Andreas E. Bombe <and...@mu...> http://home.pages.de/~andreas.bombe/ DSA key 0x04880A44 |
From: Manfred W. <e95...@st...> - 2000-03-16 18:21:57
|
Andreas Bombe wrote: > I added highlevel handling of the FCP_COMMAND and FCP_RESPONSE > registers to the subsystem. Reads to those registers are > unimplemented, written data will be passed to a highlevel fcp request > stream (similarily to the way iso data is handled). Great! I will test this in the next few weeks! Manfred Weihs |
From: Jeffrey B. M. <jb...@vi...> - 2000-03-16 20:00:25
|
Hi, I posted a few days ago with some problems, the software is seeing 1 card but no nodes. I am working with kernel 2.2.14, and upgraded to the 2/21 patch to get the latest drivers. Right now I am just working with testlibraw, because gscanbus hangs are requires a reboot to clear. (see postscript for notes on odd gscanbus behavior.) I have been trying to understand how the driver works by inserting printk's in every function to get an idea of the sequence of events. I have figured out that host->node_count gets set after a selfIDComplete interrupt, which is never occurring. I have not been able to determine where is the event or request that is supposed to trigger this... My card is ADS Pyro (TI chip?), I have a Canon DV camera connected... thanks in advance, Jeff p.s. gscanbus draws some stuff to its window that is badly sheared, as if the image data being loaded has the wrong dimensions for the window. (This is when I use a sun workstation running an old version of sunOS as my X server; I tried it on the linux PC host that has the card, and just got a black window...) I have traced the execution to the call to gtk_main(). |
From: Andreas B. <and...@mu...> - 2000-03-16 22:41:46
|
On Thu, Mar 16, 2000 at 07:16:35PM +0100, Manfred Weihs wrote: > Andreas Bombe wrote: > > I added highlevel handling of the FCP_COMMAND and FCP_RESPONSE > > registers to the subsystem. Reads to those registers are > > unimplemented, written data will be passed to a highlevel fcp request > > stream (similarily to the way iso data is handled). > > Great! I will test this in the next few weeks! I just fixed a bug in libraw where it never started FCP monitoring, so do a new checkout if you did already. I also added a small FCP test to testlibraw. -- Andreas E. Bombe <and...@mu...> http://home.pages.de/~andreas.bombe/ DSA key 0x04880A44 |
From: Manfred W. <e95...@st...> - 2000-03-17 17:23:16
|
Andreas Bombe wrote: > ..., so > do a new checkout if you did already. I used the cvs server the first time (before I only downloaded the tarballs), and I have a problem to compile libraw1394. Do I need special versions of automake and autoconf (I have automake 1.4 and autoconf 2.13). I called "automake -a" (because automake without options complained about missing files) and then "autoconf". Afterwards I tried to start ./configure, but it said: ./configure: line 524: syntax error near unexpected token `AM_INIT_AUTOMAKE(libraw1394,' ./configure: line 524: `AM_INIT_AUTOMAKE(libraw1394, 0.5)' Manfred Weihs |
From: Andreas B. <and...@mu...> - 2000-03-18 02:02:01
|
On Fri, Mar 17, 2000 at 06:18:07PM +0100, Manfred Weihs wrote: > Andreas Bombe wrote: > > ..., so > > do a new checkout if you did already. > > I called "automake -a" (because automake without options complained > about missing files) and then "autoconf". > Afterwards I tried to start ./configure, but it said: > ./configure: line 524: syntax error near unexpected token > `AM_INIT_AUTOMAKE(libraw1394,' > ./configure: line 524: `AM_INIT_AUTOMAKE(libraw1394, 0.5)' Run aclocal and then again autoconf. I know, I will put a GNOME style autogen.sh script into the repository that automates that... -- Andreas E. Bombe <and...@mu...> http://home.pages.de/~andreas.bombe/ DSA key 0x04880A44 |
From: Manfred W. <e95...@st...> - 2000-03-18 13:52:35
|
Andreas Bombe wrote: > Run aclocal and then again autoconf. aclocal says: aclocal: configure.in: 7: macro `AM_PROG_LIBTOOL' not found in library The problem remains. Manfred Weihs |
From: Andreas B. <and...@mu...> - 2000-03-18 18:08:18
|
On Sat, Mar 18, 2000 at 02:47:20PM +0100, Manfred Weihs wrote: > Andreas Bombe wrote: > > Run aclocal and then again autoconf. > > aclocal says: > aclocal: configure.in: 7: macro `AM_PROG_LIBTOOL' not found in library Seems the correct sequence would be aclocal, automake --add-missing and then autoconf. There is an autogen.sh script in the repository now, it created Makefiles from a bare CVS checkout from me just fine. Running that should do the right thing (the script is taken from GLib, so it's well tested). -- Andreas E. Bombe <and...@mu...> http://home.pages.de/~andreas.bombe/ DSA key 0x04880A44 |
From: Manfred W. <e95...@st...> - 2000-03-19 14:31:28
|
Andreas Bombe wrote: > There is an autogen.sh script in the repository now, it created > Makefiles from a bare CVS checkout from me just fine. Running that > should do the right thing (the script is taken from GLib, so it's well > tested). First: the script in the reopsitory does not have the correct permissions, so one has to do "chmod a+x autogen.sh" in order to make it work. Second: it still does not work for me. Same problem (error messages) as before. Which versions of automake/autoconf do you have (or would I need)? Manfred Weihs |
From: Andreas B. <and...@mu...> - 2000-03-19 15:47:22
|
On Sun, Mar 19, 2000 at 03:26:09PM +0100, Manfred Weihs wrote: > Andreas Bombe wrote: > > There is an autogen.sh script in the repository now, it created > > Makefiles from a bare CVS checkout from me just fine. Running that > > should do the right thing (the script is taken from GLib, so it's well > > tested). > > First: the script in the reopsitory does not have the correct > permissions, so one has to do "chmod a+x autogen.sh" in order to make it > work. That's dependent on the permission on the CVS server and I don't have direct access to that. I'll see what I can do. > Second: it still does not work for me. Same problem (error messages) as > before. Which versions of automake/autoconf do you have (or would I > need)? Do you have libtool then? It's also required if you configure for yourself. [andreasb@storm andreasb]$ autoconf --version Autoconf version 2.13 [andreasb@storm andreasb]$ automake --version automake (GNU automake) 1.4 Copyright (C) 1999 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Written by Tom Tromey <tr...@cy...> [andreasb@storm andreasb]$ libtoolize --version libtoolize (GNU libtool) 1.3.3 -- Andreas E. Bombe <and...@mu...> http://home.pages.de/~andreas.bombe/ DSA key 0x04880A44 |
From: Manfred W. <e95...@st...> - 2000-03-20 20:17:18
|
Andreas Bombe wrote: > Do you have libtool then? It's also required if you configure for > yourself. Yes. It's even more current than yours (see below)... > [andreasb@storm andreasb]$ autoconf --version > Autoconf version 2.13 > [andreasb@storm andreasb]$ automake --version > automake (GNU automake) 1.4 > > Copyright (C) 1999 Free Software Foundation, Inc. > This is free software; see the source for copying conditions. There is NO > warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. > > Written by Tom Tromey <tr...@cy...> > [andreasb@storm andreasb]$ libtoolize --version > libtoolize (GNU libtool) 1.3.3 I have esentially the same: manfred@Proton:~ > autoconf --version Autoconf version 2.13 manfred@Proton:~ > automake --version automake (GNU automake) 1.4 Copyright (C) 1999 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Written by Tom Tromey <tr...@cy...> manfred@Proton:~ > libtoolize --version libtoolize (GNU libtool) 1.3.4 That's very strange. I hope I find out why it works on your pc and does not work on mine. Anyway, I saw that you created a new tarball and that works. Manfred Weihs |
From: Manfred W. <e95...@st...> - 2000-03-24 17:24:59
|
Manfred Weihs wrote: > Andreas Bombe wrote: > > Run aclocal and then again autoconf. > > aclocal says: > aclocal: configure.in: 7: macro `AM_PROG_LIBTOOL' not found in library Maybe some of you are interested in my solution. The reason for that problem was that I installed the automake-rpm of my distribution (including aclocal) which put its m4-files into /usr/share/aclocal. But I installed libtool from a tar.gz, which (since I used the default directories) put its libtool.m4 into /usr/local/share/aclocal (where aclocal does not search for m4-files). If I used "aclocal -I /usr/local/share/aclocal", it would work. In fact my solution is a bit more general: I adopted my /usr/bin/aclocal to look into /usr/local/share/aclocal, too (without "-I"-option). Manfred Weihs |