linux1394-user

Re: Error when running dvgrab and gscanbus

[Dan D. <dde...@co...>]

Do you have kernel headers installed on your system? The asm/types.h is a
part of the standard linux includes.

From: "Morten Minke" <mm...@cl...>
> When I try a make with the libraw I get:
>
> make  all-recursive
> make[1]: Entering directory `/usr/src/libraw1394-0.8.2'
> Making all in src
> make[2]: Entering directory `/usr/src/libraw1394-0.8.2/src'
> /bin/sh ../libtool --mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I..     -g
> -O2 -Wall -Wunused -c main.c
> rm -f .libs/main.lo
> gcc -DHAVE_CONFIG_H -I. -I. -I.. -g -O2 -Wall -Wunused -c  -fPIC -DPIC
> main.c -o .libs/main.lo
> In file included from main.c:19:
> kernel-raw1394.h:49:23: asm/types.h: No such file or directory
> make[2]: *** [main.lo] Error 1
> make[2]: Leaving directory `/usr/src/libraw1394-0.8.2/src'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/usr/src/libraw1394-0.8.2'
> make: *** [all-recursive-am] Error 2
>
>
>
>
>
> after
>
> insmod ohci1394
> insmod raw1394
> lsmod
>
> I get the following:
> Module                  Size  Used by
> raw1394                 6608   0  (unused)
> ohci1394               23040   0  (unused)
> hisax                 137168   3
> ne2k-pci                4800   1  (autoclean)
> 8390                    6352   0  (autoclean) [ne2k-pci]
> es1371                 25712   0
> soundcore               3952   4  [es1371]
> ac97_codec              7824   0  [es1371]
>
> Now, when I try to run ./gscanbus I get:
> successfully got handle
> current generation number: 1
> using first card found: 1 nodes on bus, local ID is 0
> Error: invalid or unsupported selfid format!
>
> and when I try dvgrab test:
> raw1394 - couldn't get card info: Invalid argument
>
> a cat /proc/ohci1394 gives:
>
> IEEE-1394 OHCI Driver status report:
>   bus number: 0x3ff Node ID: 0x0
>
>   ### Host data ###
>   node_count:        2  node_id   : 0000FFC0
>   irm_id    : 0000FFC1  busmgr_id : 0000FFFF
>   initialized
>
>
>   ---Iso Receive DMA---
>   Current buf: 0 offset: 0
>
>   ---Async Receive DMA---
>   Ar req current buf: 0 offset: 112
>   AR resp current buf: 0 offset: 0
>
>   ---Async Transmit DMA---
>   AT req prg: 3 sent: 3 free: 32 branchAddrPtr: caa82008
>   AT req queue: first: 00000000 last: 00000000
>   AR resp prg: 0 sent: 0 free: 32 branchAddrPtr: 00000000
>   AT resp queue: first: 00000000 last: 00000000
>
>   ### HC Register dump ###
>   Version     : 01010000  GUID_ROM    : 00000000  ATRetries   : 00000822
>   CSRData     : 00000000  CSRCompData : 00000000  CSRControl  : 80000000
>   ConfigROMhdr: 04047d8a  BusID       : 31333934  BusOptions  : f07da002
>   GUIDHi      : 08002856  GUIDLo      : 00000075  ConfigROMmap: 07d3c000
>   PtdWrAddrLo : 00000000  PtdWrAddrHi : 00000000  VendorID    : 00000000
>   HCControl   : 000e0000  SelfIDBuffer: 07d4c000  SelfIDCount : 0007001c
>   IRMuChMaskHi: 00000000  IRMuChMaskLo: 00000000  IntEvent    : 00700000
>   IntMask     : 840300ff  IsoXmIntEvnt: 00000000  IsoXmIntMask: 00000000
>   IsoRcvIntEvt: 00000000  IsoRcvIntMsk: 00000001  FairnessCtrl: 00000000
>   LinkControl : 00300200  NodeID      : 8800ffc0  PhyControl  : 000001ff
>   IsoCyclTimer: 400c5242  AsRqFilterHi: ffffffff  AsRqFilterLo: ffffffff
>   PhyReqFiltHi: ffffffff  PhyReqFiltLo: ffffffff  PhyUpperBnd : 00000000
>   AsRqTrCxtCtl: 0000801e  AsRqTrCmdPtr: 0aa82002  AsRsTrCtxCtl: 00000000
>   AsRsTrCmdPtr: 00000000  AsRqRvCtxCtl: 00008409  AsRqRvCmdPtr: 07d50001
>   AsRsRvCtxCtl: 00008400  AsRsRvCmdPtr: 07e2b001  IntEvent    : 00700000
>   IsoRCtxCtl00: d0008400  IsoRCmdPtr00: 01ac3001  IsoRCxtMch00: f0000000
>   IsoRCtxCtl01: 00000000  IsoRCmdPtr01: 00000000  IsoRCxtMch01: 00000000
>   IsoRCtxCtl02: 00000000  IsoRCmdPtr02: 00000000  IsoRCxtMch02: 00000000
>   IsoRCtxCtl03: 00000000  IsoRCmdPtr03: 00000000  IsoRCxtMch03: 00000000
>   IsoTCtxCtl00: 00000000  IsoTCmdPtr00: 00000000
>   IsoTCtxCtl01: 00000000  IsoTCmdPtr01: 00000000
>   IsoTCtxCtl02: 00000000  IsoTCmdPtr02: 00000000
>   IsoTCtxCtl03: 00000000  IsoTCmdPtr03: 00000000
>   IsoTCtxCtl04: 00000000  IsoTCmdPtr04: 00000000
>   IsoTCtxCtl05: 00000000  IsoTCmdPtr05: 00000000
>   IsoTCtxCtl06: 00000000  IsoTCmdPtr06: 00000000
>   IsoTCtxCtl07: 00000000  IsoTCmdPtr07: 00000000
>
> Does anybody know what's wrong?
>
> _______________________________________________
> mailing list Lin...@li...
> http://lists.sourceforge.net/lists/listinfo/linux1394-user
>

Error when running dvgrab and gscanbus

[Morten M. <mm...@cl...>]

When I try a make with the libraw I get:

make  all-recursive
make[1]: Entering directory `/usr/src/libraw1394-0.8.2'
Making all in src
make[2]: Entering directory `/usr/src/libraw1394-0.8.2/src'
/bin/sh ../libtool --mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I..     -g
-O2 -Wall -Wunused -c main.c
rm -f .libs/main.lo
gcc -DHAVE_CONFIG_H -I. -I. -I.. -g -O2 -Wall -Wunused -c  -fPIC -DPIC
main.c -o .libs/main.lo
In file included from main.c:19:
kernel-raw1394.h:49:23: asm/types.h: No such file or directory
make[2]: *** [main.lo] Error 1
make[2]: Leaving directory `/usr/src/libraw1394-0.8.2/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/usr/src/libraw1394-0.8.2'
make: *** [all-recursive-am] Error 2





after

insmod ohci1394
insmod raw1394
lsmod

I get the following:
Module                  Size  Used by
raw1394                 6608   0  (unused)
ohci1394               23040   0  (unused)
hisax                 137168   3 
ne2k-pci                4800   1  (autoclean)
8390                    6352   0  (autoclean) [ne2k-pci]
es1371                 25712   0 
soundcore               3952   4  [es1371]
ac97_codec              7824   0  [es1371]

Now, when I try to run ./gscanbus I get:
successfully got handle
current generation number: 1
using first card found: 1 nodes on bus, local ID is 0
Error: invalid or unsupported selfid format!

and when I try dvgrab test:
raw1394 - couldn't get card info: Invalid argument

a cat /proc/ohci1394 gives:

IEEE-1394 OHCI Driver status report:
  bus number: 0x3ff Node ID: 0x0
  
  ### Host data ###
  node_count:        2  node_id   : 0000FFC0
  irm_id    : 0000FFC1  busmgr_id : 0000FFFF
  initialized  
     
  
  ---Iso Receive DMA---
  Current buf: 0 offset: 0
  
  ---Async Receive DMA---
  Ar req current buf: 0 offset: 112
  AR resp current buf: 0 offset: 0
  
  ---Async Transmit DMA---
  AT req prg: 3 sent: 3 free: 32 branchAddrPtr: caa82008
  AT req queue: first: 00000000 last: 00000000
  AR resp prg: 0 sent: 0 free: 32 branchAddrPtr: 00000000
  AT resp queue: first: 00000000 last: 00000000
  
  ### HC Register dump ###
  Version     : 01010000  GUID_ROM    : 00000000  ATRetries   : 00000822
  CSRData     : 00000000  CSRCompData : 00000000  CSRControl  : 80000000
  ConfigROMhdr: 04047d8a  BusID       : 31333934  BusOptions  : f07da002
  GUIDHi      : 08002856  GUIDLo      : 00000075  ConfigROMmap: 07d3c000
  PtdWrAddrLo : 00000000  PtdWrAddrHi : 00000000  VendorID    : 00000000
  HCControl   : 000e0000  SelfIDBuffer: 07d4c000  SelfIDCount : 0007001c
  IRMuChMaskHi: 00000000  IRMuChMaskLo: 00000000  IntEvent    : 00700000
  IntMask     : 840300ff  IsoXmIntEvnt: 00000000  IsoXmIntMask: 00000000
  IsoRcvIntEvt: 00000000  IsoRcvIntMsk: 00000001  FairnessCtrl: 00000000
  LinkControl : 00300200  NodeID      : 8800ffc0  PhyControl  : 000001ff
  IsoCyclTimer: 400c5242  AsRqFilterHi: ffffffff  AsRqFilterLo: ffffffff
  PhyReqFiltHi: ffffffff  PhyReqFiltLo: ffffffff  PhyUpperBnd : 00000000
  AsRqTrCxtCtl: 0000801e  AsRqTrCmdPtr: 0aa82002  AsRsTrCtxCtl: 00000000
  AsRsTrCmdPtr: 00000000  AsRqRvCtxCtl: 00008409  AsRqRvCmdPtr: 07d50001
  AsRsRvCtxCtl: 00008400  AsRsRvCmdPtr: 07e2b001  IntEvent    : 00700000
  IsoRCtxCtl00: d0008400  IsoRCmdPtr00: 01ac3001  IsoRCxtMch00: f0000000
  IsoRCtxCtl01: 00000000  IsoRCmdPtr01: 00000000  IsoRCxtMch01: 00000000
  IsoRCtxCtl02: 00000000  IsoRCmdPtr02: 00000000  IsoRCxtMch02: 00000000
  IsoRCtxCtl03: 00000000  IsoRCmdPtr03: 00000000  IsoRCxtMch03: 00000000
  IsoTCtxCtl00: 00000000  IsoTCmdPtr00: 00000000
  IsoTCtxCtl01: 00000000  IsoTCmdPtr01: 00000000
  IsoTCtxCtl02: 00000000  IsoTCmdPtr02: 00000000
  IsoTCtxCtl03: 00000000  IsoTCmdPtr03: 00000000
  IsoTCtxCtl04: 00000000  IsoTCmdPtr04: 00000000
  IsoTCtxCtl05: 00000000  IsoTCmdPtr05: 00000000
  IsoTCtxCtl06: 00000000  IsoTCmdPtr06: 00000000
  IsoTCtxCtl07: 00000000  IsoTCmdPtr07: 00000000
  
Does anybody know what's wrong?

Re: (no subject)

[Karthikeyan M. <kma...@ho...>]

>Do you have DMA turned on? /sbin/hdparm -d1 /dev/hdx

I can't turn dma on. I get an 'operation not permitted'
error. I did a hdparm -c1 -m16 /dev/hda, for what it's
worth.
_________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.

Re: (no subject)

[Mark <to...@de...>]

Karthikeyan Madathil wrote:
> 
> Hi,
> 
> I've been consistently running into this
> problem while trying to capture DV: after
> a few frames (20 seconds or so), dvgrab
> hangs. I see a message in /var/log/message
> saying
> ohci1394_0: waking up dma cxt 2, processing
> is probably too slow.
> 
> I tried increasing the iso buffer to 16MB,
> with no improvement.
> 
> I tried compiling the drivers with 1394_VERBOSE_DEBUG on.
> 
> The problem goes away,
> but I see a lot of frames dropped and buffer
> underrun messages from dvgrab. I tried compiling
> without VERBOSE_DEBUG, and changed the DBGMSG
> in insert_dma_buffer to always
> print a message. This time, the problem appears
> later (after 3 minutes or so). In the meanwhile,
Do you have DMA turned on? /sbin/hdparm -d1 /dev/hdx


> I still see occasional "waking up dma cxt 2" messages
> interspersed with normal dma insertion messages.

-- 
Mark
to...@de...

-- Support your government, give Echelon / Carnivore something to parse
--
classfield top-secret government restricted data information project CIA
KGB GRU DISA DoD defense systems military systems spy steal terrorist
Allah Natasha Gregori destroy destruct attack democracy will send
Russia bank system compromise international own rule the world ATSC RTEM
warmod ATMD force power enforce sensitive directorate TSP NSTD ORD DD2-N
AMTAS STRAP warrior-T presidental elections policital foreign embassy 
takeover

(no subject)

[Karthikeyan M. <kma...@ho...>]

Hi,

I've been consistently running into this
problem while trying to capture DV: after
a few frames (20 seconds or so), dvgrab
hangs. I see a message in /var/log/message
saying
ohci1394_0: waking up dma cxt 2, processing
is probably too slow.

I tried increasing the iso buffer to 16MB,
with no improvement.

I tried compiling the drivers with 1394_VERBOSE_DEBUG on.

The problem goes away,
but I see a lot of frames dropped and buffer
underrun messages from dvgrab. I tried compiling
without VERBOSE_DEBUG, and changed the DBGMSG
in insert_dma_buffer to always
print a message. This time, the problem appears
later (after 3 minutes or so). In the meanwhile,
I still see occasional "waking up dma cxt 2" messages
interspersed with normal dma insertion messages.
The messages in /var/log/messages stop all of a
sudden, and dvgrab hangs.

Any idea what could be happening?

BTW, I've been able to successfully burn a CD
using a Que CD writer using the same 1394 setup
and the sbp2_1394 drivers (thats raw mode, I guess, so if
it's a driver problem I'm seeing,
It's probably limited to iso mode)

I'm using pcmcia-cs, kernel 2.4.0 the patched 1394 drivers
for 2.4.0 on a Vaio F-250 with a pyro DV for notebooks
adapter.

Karthik
_________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.

RE: Problems trying to run a sample program

[<Kur...@pr...>]

Hi!

> We have a ieee-1394 connection kit with:
> -a Sony DFW-VL500
> -A Host adapter card 200 Mpbs for PCI bus,
>  Texas Instrument PCILynx compatible.
>
> we are for long time trying to run a simple program just to capture =
an
> image
> but in the function:
> dc1394_single_capture, the program halts (in a read function) and it
> doesn't continue.
>
> We have tested with various kernels, libs version, etc, but it keeps =
not
> working.
>
> Now, we have 2.2.18 kernel, with the last libraw1394 and libdc1394, =
(we
> have obtained it from cvs). The sample program is showed at the end =
of
> this message.
>
> Is there anybody using the same card and camera (or very similar)
> that can help us?
>
> We want to know:
> -Kernel version, and which patch.
> -libraw1394 version
> -libdc1394 version
> -A sample program, we want capture only one frame.
>
> can Anybody help us?
>
> Thanks a lot.

Since a few days we have the same camera (Sony DFW-VL500), but a =
different
host adapter card (Exsys 6500, ohci).

- kernel 2.2.17 (Suse 7.0)
- latest patch for ieee1394 module, libraw1394 (0.8.2) and libdc1394 =
(0.2)
(+ download of CVS sources)
- coriander 0.0.8 (very nice GUI for using libdc1394)
- samplegrab application from Chris Urmson=20

Be careful about the following when using samplegrab:=20
libdc1394 has been split up recently into a capture part and a control =
part
(and also .c files)! This change is not yet considered in samplegrab.c! =
You
have to replace the function call to dc1394_setup_camera with
dc1394_setup_capture !!!

With all this bleeding edge code we succeeded in capturing pictures =
from the
Sony camera. Interestingly we didn't succeed under Win2000/WinNT so far =
:-()

Now it would be nice to do that with DMA access (via video1394 rather =
than
raw1394), but there are no samples for using video1394 together with =
libdc
(coriander will do that in the future???)

Regards,

Kurt H=E4usler

Re: Problems trying to run a sample program

[Michiel R. <Mic...@ru...>]

Raul Montoliu wrote:
>
> Hi!
>
> We have a ieee-1394 connection kit with:
> -a Sony DFW-VL500
> -A Host adapter card 200 Mpbs for PCI bus,
>  Texas Instrument PCILynx compatible.
>
> we are for long time trying to run a simple program just to capture an
> image
> but in the function:
> dc1394_single_capture, the program halts (in a read function) and it
> doesn't continue.
>

We have the same camera and also a PCILynx, and we also use the same
test application 'samplegrab' and we also encounter the same problem ...

However, running the test application a few times, and each time the
applications
hangs disconnecting the camera solves the problem after a while. Each
time
you reconnect the camera, there occurs a bus reset. Just keep trying
till
there is a successfull reset.


Michiel Ronsse.

+-- Michiel Ronsse ------- mi...@ro... --+
| Parallel Information Systems Group            |
| ELIS - Ghent University  - Ghent, Belgium     |
| Phone: +32/9/264.33.67   Fax: +32/9/264.35.94 |
+-------- http://www.michiel.ronsse.com --------+

In a train station the train stops, in a work station
...

Problems trying to run a sample program

[Raul M. <mon...@sg...>]

Hi!

We have a ieee-1394 connection kit with:
-a Sony DFW-VL500
-A Host adapter card 200 Mpbs for PCI bus,
 Texas Instrument PCILynx compatible.

we are for long time trying to run a simple program just to capture an
image
but in the function:
dc1394_single_capture, the program halts (in a read function) and it
doesn't continue.

We have tested with various kernels, libs version, etc, but it keeps not
working.

Now, we have 2.2.18 kernel, with the last libraw1394 and libdc1394, (we
have obtained it from cvs). The sample program is showed at the end of
this
message.

Is there anybody using the same card and camera (or very similar)
that can help us?

We want to know:
-Kernel version, and which patch.
-libraw1394 version
-libdc1394 version
-A sample program, we want capture only one frame.

can Anybody help us?

Thanks a lot.

The results of testlibraw are:
-------------------------------
successfully got handle
current generation number: 1
1 card(s) found
  nodes on bus:  2, card name: pcilynx
using first card found: 2 nodes on bus, local ID is 0, IRM is 0

doing transactions with custom tag handler
trying to send read request to node 0... completed with 0x00100000,
value 0x634b9e50
trying to send read request to node 1... completed with 0x00020000,
value 0xc60bcfa1

using standard tag handler and synchronous calls
trying to read from node 0... completed with 0x00100000, value
0x83a89e50
trying to read from node 1... failed with error -1100

testing FCP monitoring on local node
got fcp command from node 0 of 8 bytes: 01 23 45 67 89 ab cd ef
got fcp response from node 0 of 8 bytes: 01 23 45 67 89 ab cd ef

polling for leftover messages  
-----------------------------

What can we test besides testlibraw?

-----------------------------
The sample is next:
The program prints "mensaje 1" but it doesn't print "mensaje2"
------------------------------
/*
 * Sample of how to use the 1394-Based Digital Camera Control Library
 * (libdc1394)
 *
 * Written by Chris Urmson <cu...@ri...>
 *
 * This library is free software; you can redistribute it and/or
 * modify it under the terms of the GNU Lesser General Public
 * License as published by the Free Software Foundation; either
 * version 2.1 of the License, or (at your option) any later version.
 *
 * This library is distributed in the hope that it will be useful,
 * but WITHOUT ANY WARRANTY; without even the implied warranty of
 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
 * Lesser General Public License for more details.
 *
 * You should have received a copy of the GNU Lesser General Public
 * License along with this library; if not, write to the Free Software
 * Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307 
USA
 */

#include <stdio.h>
#include <libraw1394/raw1394.h>
#include <libdc1394/dc1394_control.h>
#include <stdlib.h>

/*macro used to convert a YUV pixel to RGB format
  from Bart Nabbe
*/
#define YUV2RGB(y, u, v, r, g, b)\
  r = y + ((v * 1434) / 2048);\
  g = y - ((u * 406) / 2048) - ((v * 595) / 2048);\
  b = y + ((u * 2078) / 2048);\
  r = r < 0 ? 0 : r;\
  g = g < 0 ? 0 : g;\
  b = b < 0 ? 0 : b;\
  r = r > 255 ? 255 : r;\
  g = g > 255 ? 255 : g;\
  b = b > 255 ? 255 : b

/*routine to convert an array of YUV data to RGB format
  from Bart Nabbe
*/
int yuv422torgb (char *YUV, char *RGB, int NumPixels) {  
 int i, j;
  register int y0, y1, u, v;
  register int r, g, b;

  for (i = 0, j = 0; i < 2 * NumPixels; i += 4, j += 6)
    {
      u = (unsigned char) YUV[i + 0] - 128;
      y0 = (unsigned char) YUV[i + 1];
      v = (unsigned char) YUV[i + 2] - 128;
      y1 = (unsigned char) YUV[i + 3];
      YUV2RGB (y0, u, v, r, g, b);
      RGB[j + 0] = r;
      RGB[j + 1] = g;
      RGB[j + 2] = b;
      YUV2RGB (y1, u, v, r, g, b);
      RGB[j + 3] = r;
      RGB[j + 4] = g;
      RGB[j + 5] = b;
    }
  return 0;
}

int main(int argc, char *argv[])
{
    char *rgb;
    FILE * imagefile;
    dc1394_cameracapture camera;
    int numCameras;
    raw1394handle_t handle;
    nodeid_t * camera_nodes;
    dc1394_feature_set features;
    /*first we need to get access to the raw1394subsystem*/
    handle = dc1394_create_handle(0);
    if (handle==NULL) {
        printf("Unable to aquire a raw1394 handle\n");
        printf("did you insmod the drivers?\n");
        exit(1);
    }                                                  
 /*get the camera nodes and describe them as we find them*/
    camera_nodes = dc1394_get_camera_nodes(handle,&numCameras,1);
    fflush(stdout);
    if (numCameras<1) {
        printf("no cameras found :(\n");
        raw1394_destroy_handle(handle);
        exit(1);
    }
    printf("working with the first camera on the bus\n");


    /* if (dc1394_setup_camera(handle,camera_nodes[0],0,
                           
FORMAT_VGA_NONCOMPRESSED,MODE_320x240_YUV422,
                           
SPEED_400,FRAMERATE_7_5,&camera)!=DC1394_SUCCESS) */
    if (dc1394_setup_capture(handle,camera_nodes[0],0,
                            
FORMAT_VGA_NONCOMPRESSED,MODE_320x240_YUV422,
                            
SPEED_400,FRAMERATE_7_5,&camera)!=DC1394_SUCCESS)
    {
        printf("unable to setup camera- check line %d of %s to make
sure\n",
               __LINE__,__FILE__);
        printf("that the video mode,framerate and format are
supported\n");
        printf("is one supported by your camera\n");
        dc1394_release_camera(handle,&camera);
        raw1394_destroy_handle(handle);
        exit(1);
    }

    if(dc1394_get_camera_feature_set(handle, camera.node,&features)
       !=DC1394_SUCCESS)
    {
        printf("unable to get feature set\n");
    } else {
        dc1394_print_feature_set(&features);
    }



    /*have the camera start sending us data*/
    if (dc1394_start_iso_transmission(handle,camera.node)
        !=DC1394_SUCCESS)
    {
        printf("unable to start camera iso transmission\n");
        dc1394_release_camera(handle,&camera);
        raw1394_destroy_handle(handle);
        exit(1);
    }                                       

  printf("mensaje 1\n");

    if (dc1394_single_capture(handle,&camera)!=DC1394_SUCCESS)     //
<<<<<<<<<<<<< HERE is the problem
    {
        printf("unable to capture a frame\n");
        dc1394_release_camera(handle,&camera);
        raw1394_destroy_handle(handle);
        exit(1);
    }

    printf("mensaje 2\n"); 

    if
(dc1394_stop_iso_transmission(handle,camera.node)!=DC1394_SUCCESS)
    {
        printf("couldn't stop the camera?\n");
    }

    printf("mensaje 3\n");

    /* allocate an RGB buffer that is big enough*/
    rgb = (char *)malloc(camera.frame_height*camera.frame_width*3);

    yuv422torgb((char *)camera.capture_buffer, rgb,
                camera.frame_height*camera.frame_width);

    printf("mensaje 4\n");

    imagefile=fopen("Image.pgm","w");

    fprintf(imagefile,"P6\n%u %u 255\n", camera.frame_width,
            camera.frame_height );
    fwrite(rgb, 1, 3*camera.frame_height*camera.frame_width, imagefile
);
    fclose(imagefile);
    printf("wrote: Image.pgm\n");

    dc1394_release_camera(handle,&camera);
    raw1394_destroy_handle(handle);
    free(rgb);
    exit(0);
}    

------------

Re: problems gettings things running

[Andreas M. <and...@iv...>]

Hiho,

On Thu, Jan 25, 2001 at 02:17:17PM +0100, Morten Minke wrote:
> patch. I was able to compile everything and insmod the ohci1394 and raw1394
> modules. When I do a cat /proc/ohci1394 I get all kinds of information and

You also need to insmod ieee1394, but I guess you already did that.

> But now I want to do something with it, so I downloaded the gscanbus source
> and tried to compile it. With no success. Apparently I need all kinds of
> include files which I do not have installed, and I do not know where to get
> them!!
> I've also downloaded the dvgrab binaries (rpm) and installed those. However
> when I try to run this program it gives an error that mentions that
> /dev/raw1394 device does not exist.

You need libraw1394, which is a shared library applications use to access the
1394 kernel modules. During the installation of libraw1394 the missing device
file will also be created. You can get libraw1394 here:

http://sourceforge.net/projects/libraw1394/

-- 
Andreas Micklei
IVISTAR Kommunikationssysteme AG
Ehrenbergstr. 19 / 10245 Berlin
http://www.ivistar.de

problems gettings things running

[Morten M. <mm...@cl...>]

I'm trying to get my firewire-card / dv-camcorder combination working on
Linux.
I'm using RedHat7.0 and I installed the 2.4Kernel sources and the 2.4 ieee
patch. I was able to compile everything and insmod the ohci1394 and raw1394
modules. When I do a cat /proc/ohci1394 I get all kinds of information and
it also mentions the correct number of nodes connected to the bus (2).
So I guess things are working.

But now I want to do something with it, so I downloaded the gscanbus source
and tried to compile it. With no success. Apparently I need all kinds of
include files which I do not have installed, and I do not know where to get
them!!
I've also downloaded the dvgrab binaries (rpm) and installed those. However
when I try to run this program it gives an error that mentions that
/dev/raw1394 device does not exist.

Can anyone tell me how to get this device working?

I've done a ls /dev/*1394* which resulted in 0 files, so I guess I'm missing
some device files.

Re: Sample code for video1394

[Dan D. <dde...@co...>]

You should be happy to see that libdc1394 now integrates video1394
capture functionality to provide a higher level interface. There are no
examples I am aware of that make use of these new functions, but the
Coriander project on sourceforge seems like an obvious application to
eventually use it. (I have been thinking about adding the scope display
functions to Coriander if Damien has not started it himself.)
Personally, I have a play/test program called xv_video1394 that displays
the video from a digital camera in an Xv window. You can change
resolutions, fps, pause,  and save a frame to disk. I will send it, but
it purely experimental.

Häusler Kurt wrote:
> 
> Hi there!
> 
> I am looking for sample applications which make use of video1394 rather than
> the libraw API and if possible also use libdc?!
> 
> Anybody out there to share some code before I start hacking for myself?
> 
> Kurt Häusler
> 
> _______________________________________________
> mailing list Lin...@li...
> http://lists.sourceforge.net/lists/listinfo/linux1394-user

Sample code for video1394

[<Kur...@pr...>]

Hi there!

I am looking for sample applications which make use of video1394 rather =
than
the libraw API and if possible also use libdc?!

Anybody out there to share some code before I start hacking for myself?

Kurt H=E4usler

1394 DV problems

[Karthikeyan M. <kma...@ho...>]

<html><P><FONT face=Arial size=2>Hi,</FONT></P>
<P><FONT face=Arial size=2>I'm running kernel2.4.0&nbsp; (installed over Mandrake 7.1) on a laptop with pcmcia-cs-3.1.23 and the latest fixed version of the 1394 modules. With IEEE1394_VERBOSE_DEBUG enabled, I'm able to capture using dvgrab, but with a good deal of frame loss. WIth verbose debug turned off, I get about a second's worth of frames before I see&nbsp;a message like this from ohci1394&nbsp;in /var/log/messages:</FONT></P>
<P><FONT face=Arial size=2>Waking up dma cxt 2: processing is probably too slow</FONT></P>
<P><FONT face=Arial size=2>dvgrab gets no more data. Any ideas what could be happening ? (Is it&nbsp;some sort of buffer overrun in the driver ...?)</FONT></P>
<P><FONT face=Arial size=2>BTW, thanks for the quick fix for the 2.4.0 modules!</FONT></P>
<P><FONT face=Arial size=2>Cheers,</FONT></P>
<P><FONT face=Arial size=2>Karthik Madathil</FONT></P><br clear=all><hr>Get Your Private, Free E-mail from MSN Hotmail at <a href="http://www.hotmail.com">http://www.hotmail.com</a>.<br></p></html>

Some questions... - not yet answered clear enough for me.

[Herbert W. <Herbert@Wengatz.de>]

Hi there!

I'm a Unix/Linux professional, but I'm new at the digital video stuff
(which
I use as hobby). I've just recently bought me some hardware and I pray
that
this combination will work not only under M$, but also under Linux.

I've done some extensive research and I only need somebody who can tell
me
"yes this will probably/sure work" - or not...

I have a Sony TVR110E, for which I'll receive soon the cable and
software
to enable the DV-in port. It has a iLink/Firewire port.

On the PC side I bought me a Pinnacle Studio DV card, which seem to have
three Firewire-Ports, based on the chips from TI.

The rest of my hardware should be OK, too:
650 MHz Athlon, 20 GB UDMA-Harddisk, or if that should fail: 2x 4 GB
UW-SCSI Disks, with a Riva TNT-2 Ultra graphics card (AGP 2x) and 382 MB
RAM. 

I've licensed Main Actor as well. I've read about Kino and dvgrab.

Does anybody has some experiences with all this?

Since I know the Studio DV card has three IEEE1394 ports, I guess it may
be possible to mix two firewire datastreams into one. The symbol on the
package proposes that ( two dashed lines approaching a circle, a third
line (no longer dashed) leaves the circle ), as well as two ports are
external (for the camcorder and an VCR, perhaps) and one port is
internal,
which proposes that there may be a firewire disk or so.

Any software available for mixing two firewire datastreams into one?

Furthermore: I do plan to use my TNT2-Ultra-Card with XFree 4.0 and GLX.
I also (more or less) need (!) the new Kernel (2.4.x), because it seems
to fix a lot issues with my Athlon board (makes it faster, etc.) but I
heard that the firewire-driver for the new kernel is not yet stable
working.
Is that true? - Will this be fixed soon?

Another point is: I've filmed my last vacation with the new videocam.
Since it allowed filming in 16:9 format, I tried it and it looks nice.
But: can I - or how can I cut this format under Linux? Does any of the
mentioned software-packages support the 16:9 format?

Maybe I can offer some help here. - I'm willing to support anybody
who says: "OK, I'll try to make this work..." - I've never written a
hardware driver before, but I know some C - if this helps?!

Help me to help you to help us all! (Should be the motto of the open 
source community! ;-) )


Best regards,

Herbert

dv avi to mpeg?

[Felix T. <ta...@ee...>]

Is there a program that will convert dv avi to mpeg? Kino is great... I
really like the vi style keys for editing... much easier to use.
Everything has been working great for me. ;)

Felix

Coriander 0.8 is out!

[Damien D. <ddo...@te...>]

Hi,

I just posted the new version of Coriander on SourceForge. Lots of new
features, many bug fixes.

http://sourceforge.net/projects/coriander

Enjoy,

Damien
-- 
Damien Douxchamps
URL  : http://www.tele.ucl.ac.be/MEMBERS/Douxchamps_Damien_e.html

Re: SBP-2 support

[Jurgen K. <GTM...@in...>]

Hi,

You probably have one of those VAIOs with a non OHCI compliant chipset onboard.
Maybe you
can check which part you actually have.

About the sbp2_1394.o part: yes you have to manually copy that to the module
directory.

Greetings,

Jurgen

Katsuhiro Inoue wrote:

> Hello,
>
> I had installed the IEEE1394 patch to my kernel-2.2.18, to make my 40G
> i.Link HDD (Sony PCVA-HD04 only sold in Japan) work with Linux. However,
> there were a few things I cannot get over it.
>
> (Sorry that it seems a basic problem with module installation but I need
> your help!)
>
> I used RedHat Distribution 7.0. I already removed gcc and ln -s kgcc gcc.
>
> There were two problems:
>
> 1 - One problems is module loading for ohci1394. It said that "no operable
> Ohci1394 cards found". This seems simply meaning that my i.Link cards built
> in my notebook (Sony VAIO PCG-Z505FX made in Japan) was not detected by the
> module. Is it a fundamental problem or is there anyone who could finally
> solve this problem?
>
> 2 - Another one is unpacking SBP-2 driver which I got from
> http://firewire.zawa.com/sbp2/ . Steps I took were:
> - downloaded sbp2_1394_122300.tar.gz and unpacked it
> - moves all file into /usr/src/linux/drivers/ieee1394
> - make -f Makefile.sbp2 clean, make -f Makefile.sbp2 (generated sbp2_1394.o)
> - make dep, make bzlilo, make modules, make modules_install
> That last command (make modules_install) did not copy the sbp2_1394.o into
> /lib/modules/2.2.18/ieee1394. Is it OK that I move this .o file into
> /lib/modules/2.2.18/ieee1394 directory manually?
>
> Thanks,
>
> Katsuhiro Inoue
>
> _______________________________________________
> mailing list Lin...@li...
> http://lists.sourceforge.net/lists/listinfo/linux1394-user

SBP-2 support

[Katsuhiro I. <kat...@fl...>]

Hello,

I had installed the IEEE1394 patch to my kernel-2.2.18, to make my 40G
i.Link HDD (Sony PCVA-HD04 only sold in Japan) work with Linux. However,
there were a few things I cannot get over it.

(Sorry that it seems a basic problem with module installation but I need
your help!)

I used RedHat Distribution 7.0. I already removed gcc and ln -s kgcc gcc.

There were two problems:

1 - One problems is module loading for ohci1394. It said that "no operable
Ohci1394 cards found". This seems simply meaning that my i.Link cards built
in my notebook (Sony VAIO PCG-Z505FX made in Japan) was not detected by the
module. Is it a fundamental problem or is there anyone who could finally
solve this problem?

2 - Another one is unpacking SBP-2 driver which I got from
http://firewire.zawa.com/sbp2/ . Steps I took were:
- downloaded sbp2_1394_122300.tar.gz and unpacked it
- moves all file into /usr/src/linux/drivers/ieee1394
- make -f Makefile.sbp2 clean, make -f Makefile.sbp2 (generated sbp2_1394.o)
- make dep, make bzlilo, make modules, make modules_install
That last command (make modules_install) did not copy the sbp2_1394.o into
/lib/modules/2.2.18/ieee1394. Is it OK that I move this .o file into
/lib/modules/2.2.18/ieee1394 directory manually?

Thanks,

Katsuhiro Inoue

Re: IEEE1394 camera list

[Felix T. <ta...@ee...>]

Damien,

New camera to add.

http://www.ptgrey.com/products/firefly/index.htm

Felix

On Tue, 16 Jan 2001, Damien Douxchamps wrote:

> Hi all,
> 
> I have written a little page with all IEEE1394 digital cameras currently
> available on the market (not the DV type). The URL is:
> 
> http://www.tele.ucl.ac.be/PEOPLE/DOUXCHAMPS/ieee1394/cameras
> 
> If you know any other, please email me! :-)
> 
> Cheers,
> 
> Damien
> -- 
> Damien Douxchamps
> URL  : http://www.tele.ucl.ac.be/MEMBERS/Douxchamps_Damien_e.html
> 
> _______________________________________________
> mailing list lin...@li...
> http://lists.sourceforge.net/lists/listinfo/linux1394-devel
> 

Re: PowerPPC Firewire Support?

[Dan D. <dde...@co...>]

No one seems to be able to get it work, but it should be very close to
working. Someone that is not an official member of the project is working on
it, so we'll wait and see....

From: "Adam Chrystie" <at...@ti...>
>
>  Is there firewire support for Linux PPC on Apple hardware such as the
> cube or teh noteboks? Anyone had luck?

IEEE1394 camera list

[Damien D. <ddo...@te...>]

Hi all,

I have written a little page with all IEEE1394 digital cameras currently
available on the market (not the DV type). The URL is:

http://www.tele.ucl.ac.be/PEOPLE/DOUXCHAMPS/ieee1394/cameras

If you know any other, please email me! :-)

Cheers,

Damien
-- 
Damien Douxchamps
URL  : http://www.tele.ucl.ac.be/MEMBERS/Douxchamps_Damien_e.html

PowerPPC Firewire Support?

[Adam C. <at...@ti...>]

 Is there firewire support for Linux PPC on Apple hardware such as the
cube or teh noteboks? Anyone had luck?

Re: Hardware compatibility list now online

[Dan D. <dde...@co...>]

Per Andreas Micklei's information about the CSR ROM GUID, the GUID field has
been removed from the HCL. Also, Andreas discovered a bug with editing
device entries that has been fixed now.
+-DRD-+

Re: Regarding webcams (pyro) and digital cameras.

[Felix T. <ta...@ee...>]

Dan,

Thanks for the info. Does your program work with just the orange micro
ibot? Is the source available?

Yeah, the nikon camera is a bit pricey. I think I might avoid getting that
to work for now. I'm more interested in getting a compressed/uncompressed
video stream from a webcam like camera.

Felix

On Mon, 15 Jan 2001, Dan Dennedy wrote:

> I have a little program that displays the web/desktop cameras' video in
> a window--whoopee! I personally have the Orange Micro iBot. I'm
> interested in making these cameras work with Kino, and adding a
> play-n-grab feature to Kino to do stop-motion animation. Also, I am
> thinking it would not be difficult to make the camera output a JPEG
> image for use on a website.
> 
> I just looked up the Nikon D1. In "Nikon Capture" mode it can out TIFF
> images. I'd have to view the raw isochronous stream in order to
> determine how it is packetizing the data. It's probably just a matter of
> taking consecutive packets of a single frame and wrapping it inside of a
> TIFF file. Right now, there is no app that can take advantage of it. I
> just saw it at a price of about US$5000; I can not afford that right
> now!
> 
> +-DRD-+
> 
> Felix Tang wrote:
> > 
> > All,
> > 
> > I'd like to clarify something... are video cameras like the pyro which
> > send uncompressed data supported by any applications? I understand that
> > Sony also makes quite a few of these video cameras as well. Secondly, how
> > about digital cameras like the Nikon D1? It takes still pictures but can
> > also capture video... although in what format I'm not sure.
> > 
> > Felix
> > 
> > _______________________________________________
> > mailing list Lin...@li...
> > http://lists.sourceforge.net/lists/listinfo/linux1394-user
> 

Re: Hardware compatibility list now online

[Andreas M. <and...@iv...>]

Hiho,

On Mon, Jan 15, 2001 at 05:47:43AM -0500, Dan Dennedy wrote:
> I've added a hardware compatibility list/application to the

Great! I will add my devices today.

>  - Please take the time to look up the CSR ROM GUIDs for your device
> using gscanbus. We can use this to make gscanbus' database of devices
> more complete, and I imagine other applications may make use of this to
> allow the user to select a device with which to work.

No, please do NOT do that.

The GUID of a device is the GLOBAL unique ID. Even if you have the exact same
model of a device like I do, they will have different GUIDs. The guid.conf
from gscanbus is an ugly dirty cludge, just to make it display your particular
devices correctly, and the IDs I put in are bogus. Finding a better way to
identify devices is already on my agenda, but I it is currently very hard for
me to get enough spare time to even fix the segfault.

Anyway: If someone has a device identification library in the works, I will
happily make use of it.

The key fields for identifying a device should probably be Vendor ID and
Model ID. Model ID seems to be 0 in many cases, so a combination of Vendor ID
and some other values (like Unit Spec ID, Unit SW Version, etc.) might be
appropriate. I am sure there is some document clarifying all this somewhere on
the net.

-- 
Andreas Micklei
IVISTAR Kommunikationssysteme AG
Ehrenbergstr. 19 / 10245 Berlin
http://www.ivistar.de