linux1394-user Mailing List for IEEE 1394 for Linux (Page 418)
Brought to you by:
aeb,
bencollins
You can subscribe to this list here.
2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(29) |
Nov
(36) |
Dec
(46) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2001 |
Jan
(60) |
Feb
(82) |
Mar
(46) |
Apr
(50) |
May
(89) |
Jun
(60) |
Jul
(80) |
Aug
(130) |
Sep
(104) |
Oct
(105) |
Nov
(123) |
Dec
(107) |
2002 |
Jan
(142) |
Feb
(105) |
Mar
(63) |
Apr
(117) |
May
(136) |
Jun
(75) |
Jul
(105) |
Aug
(103) |
Sep
(149) |
Oct
(149) |
Nov
(98) |
Dec
(144) |
2003 |
Jan
(161) |
Feb
(100) |
Mar
(118) |
Apr
(126) |
May
(157) |
Jun
(173) |
Jul
(156) |
Aug
(89) |
Sep
(83) |
Oct
(106) |
Nov
(84) |
Dec
(69) |
2004 |
Jan
(119) |
Feb
(233) |
Mar
(232) |
Apr
(104) |
May
(113) |
Jun
(132) |
Jul
(87) |
Aug
(129) |
Sep
(186) |
Oct
(88) |
Nov
(148) |
Dec
(180) |
2005 |
Jan
(223) |
Feb
(176) |
Mar
(148) |
Apr
(193) |
May
(188) |
Jun
(236) |
Jul
(144) |
Aug
(89) |
Sep
(44) |
Oct
(86) |
Nov
(114) |
Dec
(89) |
2006 |
Jan
(94) |
Feb
(97) |
Mar
(57) |
Apr
(117) |
May
(46) |
Jun
(63) |
Jul
(51) |
Aug
(72) |
Sep
(50) |
Oct
(142) |
Nov
(70) |
Dec
(52) |
2007 |
Jan
(60) |
Feb
(67) |
Mar
(80) |
Apr
(81) |
May
(78) |
Jun
(52) |
Jul
(64) |
Aug
(55) |
Sep
(40) |
Oct
(87) |
Nov
(70) |
Dec
(44) |
2008 |
Jan
(80) |
Feb
(12) |
Mar
(82) |
Apr
(64) |
May
(33) |
Jun
(53) |
Jul
(41) |
Aug
(26) |
Sep
(35) |
Oct
(21) |
Nov
(30) |
Dec
(42) |
2009 |
Jan
(17) |
Feb
(32) |
Mar
(10) |
Apr
(19) |
May
(19) |
Jun
(28) |
Jul
(41) |
Aug
(14) |
Sep
(5) |
Oct
(46) |
Nov
(23) |
Dec
(20) |
2010 |
Jan
(46) |
Feb
(13) |
Mar
(9) |
Apr
(2) |
May
(19) |
Jun
(28) |
Jul
(37) |
Aug
(23) |
Sep
(5) |
Oct
(32) |
Nov
(19) |
Dec
(18) |
2011 |
Jan
(23) |
Feb
(9) |
Mar
(19) |
Apr
(38) |
May
(83) |
Jun
(30) |
Jul
(46) |
Aug
(32) |
Sep
(6) |
Oct
(3) |
Nov
(25) |
Dec
(31) |
2012 |
Jan
(21) |
Feb
(12) |
Mar
(19) |
Apr
(7) |
May
(27) |
Jun
(7) |
Jul
(2) |
Aug
(15) |
Sep
(8) |
Oct
(11) |
Nov
|
Dec
(3) |
2013 |
Jan
|
Feb
|
Mar
(2) |
Apr
(1) |
May
(1) |
Jun
(14) |
Jul
(1) |
Aug
(3) |
Sep
(4) |
Oct
(5) |
Nov
|
Dec
|
2014 |
Jan
(14) |
Feb
(2) |
Mar
(1) |
Apr
(3) |
May
(2) |
Jun
(7) |
Jul
(2) |
Aug
(1) |
Sep
|
Oct
(14) |
Nov
(5) |
Dec
(18) |
2015 |
Jan
(3) |
Feb
(1) |
Mar
(3) |
Apr
(5) |
May
|
Jun
(3) |
Jul
(4) |
Aug
|
Sep
(2) |
Oct
(11) |
Nov
(2) |
Dec
|
2016 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
(5) |
Jul
(1) |
Aug
(1) |
Sep
(2) |
Oct
(2) |
Nov
|
Dec
|
2017 |
Jan
|
Feb
(5) |
Mar
(7) |
Apr
|
May
(4) |
Jun
|
Jul
(1) |
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
2018 |
Jan
|
Feb
(4) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
(1) |
Dec
|
2019 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
2020 |
Jan
|
Feb
(1) |
Mar
(2) |
Apr
|
May
(1) |
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(6) |
2021 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2023 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Dan D. <dde...@co...> - 2001-02-06 05:52:50
|
Aleksandr Milewski wrote: > > Has anyone done any work on MPEG-2 capture from 1394? Not that we are aware of. Most us are capturing DV and uncompressed video. > > I'm looking for a simple, dumb, strip off the 1394 headers and write > the MPEG-2 packets to disk kind of utility. > > The application is capturing MPEG-2 broadcasts that have been > recorded with a D-VHS deck. Once I get the MPEG-2 captured, I can > drag it into the NLE of my choice. > > Unfortunately, these devices (Panasonic PV-HD1000, Hughes Platinum > set-tops and HDR-205 D-VHS deck, &c) implement what I've heard called > "Brain Dead 1394" My understanding is that they simply spew > isochronous 1394 packets that encapsulate MPEG-2 TS 188-byte packets. > No device control, etc. > > I admit that I haven't built linux1394 yet, so if this is as simple as > > cat /dev/video1394 >> file.mpeg Not that simple until someone brings video1394 up to video4linux compliancy. However, you can certainly call a few ioctls and dump the iso packets to disk. If it is that braindead, then maybe it will be as simple as that, but I would not be so optimistic. > feel free to point that out. > > Thanks in advance, > -Zandr > -- > --------------------------------------------------------------------- > Aleksandr Milewski N6MOD > n6...@mi... http://www.milewski.org/ > > _______________________________________________ > mailing list Lin...@li... > http://lists.sourceforge.net/lists/listinfo/linux1394-user |
From: Aleksandr M. <n6...@mi...> - 2001-02-05 23:41:52
|
Has anyone done any work on MPEG-2 capture from 1394? I'm looking for a simple, dumb, strip off the 1394 headers and write the MPEG-2 packets to disk kind of utility. The application is capturing MPEG-2 broadcasts that have been recorded with a D-VHS deck. Once I get the MPEG-2 captured, I can drag it into the NLE of my choice. Unfortunately, these devices (Panasonic PV-HD1000, Hughes Platinum set-tops and HDR-205 D-VHS deck, &c) implement what I've heard called "Brain Dead 1394" My understanding is that they simply spew isochronous 1394 packets that encapsulate MPEG-2 TS 188-byte packets. No device control, etc. I admit that I haven't built linux1394 yet, so if this is as simple as cat /dev/video1394 >> file.mpeg feel free to point that out. Thanks in advance, -Zandr -- --------------------------------------------------------------------- Aleksandr Milewski N6MOD n6...@mi... http://www.milewski.org/ |
From: Marcel J. <mph...@ho...> - 2001-02-05 20:57:38
|
Hi, This is my first try with ieee1394 and I seem to get my card going. My card is a Texas Instruments OHCI campliant one and I use kernel 2.4.0 with the CVS fix (05-02-2001). When I leave the camera switched off, the modules load fine. When I power up the camera, my whole box hangs (no mouse/keyboard/network etc). No matter if I first load the modules and power up the camera afterwards or the other way round. I've got no idea where to start looking for a solution. Since my box locks immediately after switching on the camera, I have no report to my log files. I included the kernel log of my modules (when camera switched off) at the bottom of this mail. My camera is a sony DCR-PC5E. Can the use of devfs be a problem ? thanks, Marcel Janssen Feb 5 19:00:44 korgull kernel: ieee1394: registered ohci1394 driver, initializing now Feb 5 19:00:44 korgull kernel: ohci1394: looking for Ohci1394 cards Feb 5 19:00:44 korgull kernel: PCI: Found IRQ 9 for device 00:0a.0 Feb 5 19:00:44 korgull kernel: ohci1394_0: remapped memory spaces reg 0xcd8d0000 Feb 5 19:00:44 korgull kernel: ohci1394_0: allocated interrupt 9 Feb 5 19:00:44 korgull kernel: ohci1394_0: soft reset finished Feb 5 19:00:44 korgull kernel: ohci1394_0: max packet size = 2048 bytes Feb 5 19:00:44 korgull kernel: ohci1394_0: 4 iso receive contexts available Feb 5 19:00:44 korgull kernel: ohci1394_0: 8 iso transmit contexts available Feb 5 19:00:44 korgull kernel: ohci1394_0: Receive DMA ctx=0 initialized Feb 5 19:00:44 korgull kernel: ohci1394_0: Receive DMA ctx=1 initialized Feb 5 19:00:44 korgull kernel: ohci1394_0: AT dma ctx=0 initialized Feb 5 19:00:44 korgull kernel: ohci1394_0: AT dma ctx=1 initialized Feb 5 19:00:44 korgull kernel: ohci1394_0: Receive DMA ctx=2 initialized Feb 5 19:00:44 korgull kernel: ohci1394_0: resetting bus on request Feb 5 19:00:44 korgull kernel: ieee1394: detected 1 ohci1394 adapter Feb 5 19:00:44 korgull kernel: ohci1394_0: SelfID process finished (phyid 0, root) Feb 5 19:00:44 korgull kernel: ohci1394_0: selfid packet 0x807f8c56 rcvd Feb 5 19:00:44 korgull kernel: ohci1394_0: This node self-id is 0x807f8c56 Feb 5 19:00:44 korgull kernel: ohci1394_0: calling self-id complete Feb 5 19:00:44 korgull kernel: ohci1394_0: Got phy packet ctx=0 ... discarded Feb 5 19:00:56 korgull kernel: devfs: devfs_register(): device already registered: "raw1394" Feb 5 19:00:56 korgull kernel: raw1394: /dev/raw1394 device initialized Feb 5 19:01:00 korgull CROND[6021]: (root) CMD (run-parts /etc/cron.hourly) Feb 5 19:01:01 korgull kernel: ohci1394_0: Bus reset Feb 5 19:01:01 korgull kernel: ohci1394_0: SelfID process finished (phyid 0, not root) Feb 5 19:01:01 korgull kernel: ohci1394_0: selfid packet 0x807f8c94 rcvd Feb 5 19:01:01 korgull kernel: ohci1394_0: This node self-id is 0x807f8c94 Feb 5 19:01:01 korgull kernel: ohci1394_0: selfid packet 0x813f08c2 rcvd Feb 5 19:01:01 korgull kernel: ohci1394_0: calling self-id complete Feb 5 19:01:01 korgull kernel: ohci1394_0: Bus reset Feb 5 19:01:01 korgull kernel: ohci1394_0: SelfID process finished (phyid 0, not root) Feb 5 19:01:01 korgull kernel: ohci1394_0: selfid packet 0x807f8c94 rcvd Feb 5 19:01:01 korgull kernel: ohci1394_0: This node self-id is 0x807f8c94 Feb 5 19:01:01 korgull kernel: ohci1394_0: selfid packet 0x813f08c2 rcvd Feb 5 19:01:01 korgull kernel: ohci1394_0: calling self-id complete Feb 5 19:01:01 korgull kernel: ohci1394_0: Got phy packet ctx=0 ... discarded |
From: Ichiro S. <ic...@fn...> - 2001-02-05 17:15:12
|
Hi, I've been trying ISO packet transmission without any success. I attach my code below, 's.cc' for the sender side and 'r.cc' for the receiver. These are running on two machines, sender and receiver each. What am I missing? (Bus reset handling and FCP transmission worked fine with similar code.) System info.: kernel: Linux 2.2.16 ieee1394: 2.2.17-20001012 libraw: 0.8.2 NIC: D-Link DFW-500 (OHCI compat.) Thanks a lot ----------------------------------------------------------------- Ichiro Suzuki ic...@fn..., http://home.fnal.gov/~ichiro/ PPD/EPP, Fermi National Accelerator Laboratory, Batavia, Illinois ----------------------------------------------------------------- ---- 8< ---- s.cc ---- 8< ---- #include "libraw1394/ieee1394.h" #include "libraw1394/raw1394.h" #include "libraw1394/csr.h" int main(int argc, char *argv[]) { raw1394handle_t handle = raw1394_get_handle(); raw1394_set_port(handle, 0); const unsigned int CHANNEL = 1; const int DATASIZE = 512; unsigned char buf[DATASIZE]; raw1394_iso_write(handle, CHANNEL, 0, 0, L1394_SPEED_400, DATASIZE, (quadlet_t *)buf); raw1394_destroy_handle(handle); exit(0); } ---- 8< ---- r.cc ---- 8< ---- #include <iostream> #include "libraw1394/raw1394.h" #include "libraw1394/csr.h" int ISOHandler(raw1394handle_t handle, int channel, size_t length, quadlet_t *data) { cout << "ISO received on channel " << channel << endl; return 0; } int main(int argc, char *argv[]) { raw1394handle_t handle = raw1394_get_handle(); raw1394_set_port(handle, 0); const unsigned int CHANNEL = 1; raw1394_set_iso_handler(handle, CHANNEL, ISOHandler); raw1394_start_iso_rcv(handle, CHANNEL); raw1394_loop_iterate(handle); raw1394_stop_iso_rcv(handle, CHANNEL); raw1394_destroy_handle(handle); exit(0); } |
From: Dan D. <dde...@co...> - 2001-02-04 20:11:30
|
"Michael Spiceland (aka Mike Spice)" wrote: > > I finally got my computer capturing DV movies using IEEE1394 and dvgrab. > They are saved as .avi files (type 1 I believe). I can play them back on > windows machines, but not in linux. My question is multi-part. > > What can I use to play them in Linux? I cannot get Kino or xdvplay to > compile. WE mostly use Kino or xdvplay. You should work on compiling them. Kino uses autotools, so it should alert you during the configure step as to what may be missing on your system. You'll probably need all of a gnome-dev collection of packages. I use Ximian Gnome on Debian, so I apt-get install task-hexlix-gnome-dev (the name might include ximian now). > Is there any way to convert them to another format that I can play in linux, > such as MPEG 1/2 or DIVX? Not yet. Broadcast creates MPEG2. For Kino, we're looking into interoperability with Broadcast. > Thanks, > Mike > > _______________________________________________ > mailing list Lin...@li... > http://lists.sourceforge.net/lists/listinfo/linux1394-user |
From: Dan D. <dde...@co...> - 2001-02-04 20:11:22
|
"Michael Spiceland (aka Mike Spice)" wrote: > > Has anyone gotten the IEEE1394 to work in Broadcast 2000? I am using the > latest version. I can capture fine using dvgrab, but I cannot get Broadcast > 2000 to work! I have been able to use 2000b, but I have not tried the recently released 2000c. > When trying to record/capture directly using Broadcast2000, I get a messed up > picture wit lots of horizontial lines, but it is apparently a very distorted > picture of the input because it changes related to what is being played. > > When I try to append or load a dvgrab created .avi file, it adds it as 116 or > so tracks of audio! Broadcast does not work with AVIs. > If there is a Broadcast2000 mailing list, please let me know. Not that I know of. > -- > Thank you in advance, > Mike Spice (Michael Spiceland) - http://www.mikespice.com > KLUG President (Knoxville Linux User Group) - http://web.utk.edu/~klug > IgWig Solutions (owner) - http://www.mikespice.com/igwig/ > > _______________________________________________ > mailing list Lin...@li... > http://lists.sourceforge.net/lists/listinfo/linux1394-user |
From: Michael S. (a. M. S. <mi...@mi...> - 2001-02-04 07:02:31
|
Has anyone gotten the IEEE1394 to work in Broadcast 2000? I am using the latest version. I can capture fine using dvgrab, but I cannot get Broadcast 2000 to work! When trying to record/capture directly using Broadcast2000, I get a messed up picture wit lots of horizontial lines, but it is apparently a very distorted picture of the input because it changes related to what is being played. When I try to append or load a dvgrab created .avi file, it adds it as 116 or so tracks of audio! If there is a Broadcast2000 mailing list, please let me know. -- Thank you in advance, Mike Spice (Michael Spiceland) - http://www.mikespice.com KLUG President (Knoxville Linux User Group) - http://web.utk.edu/~klug IgWig Solutions (owner) - http://www.mikespice.com/igwig/ |
From: Michael S. (a. M. S. <mi...@mi...> - 2001-02-04 06:58:08
|
I finally got my computer capturing DV movies using IEEE1394 and dvgrab. They are saved as .avi files (type 1 I believe). I can play them back on windows machines, but not in linux. My question is multi-part. What can I use to play them in Linux? I cannot get Kino or xdvplay to compile. Is there any way to convert them to another format that I can play in linux, such as MPEG 1/2 or DIVX? Thanks, Mike |
From: Dan D. <dde...@co...> - 2001-02-02 22:42:16
|
Yes, this is a known issue that some developers are working on. I will add a status message to our website to let visitors know that it does not currently work, and then we will announce it when it does work. Subscribe to the linux1394-announce list to be auto-informed of new releases so you know when it is ready. From: "Ken Offer" <ko...@ar...> > I've been trying to get the linux1394 driver to work under > LiunxPPC 2.4.1-pre9 kernel, but I haven't had much success. > Anybody else out there been working on this? I suspect there > is an endian-ness problem here. > > Apologies go to everyone if this is a "very dead horse..." > > -- > ______________________________________________________________ > Kenneth Ray Offer, II > Sr. Systems Analyst, Sonar Development Division > Applied Research Laboratories: University of Texas at Austin > Office (512) 835-3859 FAX (512) 835-3259 > > Any opinions expressed above are mine and not necessarily > those of my employer. > > _______________________________________________ > mailing list Lin...@li... > http://lists.sourceforge.net/lists/listinfo/linux1394-user > |
From: Ken O. <ko...@ar...> - 2001-02-02 22:08:20
|
I've been trying to get the linux1394 driver to work under LiunxPPC 2.4.1-pre9 kernel, but I haven't had much success. Anybody else out there been working on this? I suspect there is an endian-ness problem here. Apologies go to everyone if this is a "very dead horse..." -- ______________________________________________________________ Kenneth Ray Offer, II Sr. Systems Analyst, Sonar Development Division Applied Research Laboratories: University of Texas at Austin Office (512) 835-3859 FAX (512) 835-3259 Any opinions expressed above are mine and not necessarily those of my employer. |
From: Dan D. <dde...@co...> - 2001-02-02 17:16:07
|
This has come up several times. I think the directions on the website need to fixed or made more clear. That's my job, will do. From: "Matteo Morini" <mat...@ti...> > "Michael Spiceland (aka Mike Spice)" wrote: > > > I am using RedHat Linux 7.0 with a 2.2.16 kernel. > > > > following the instructions exactly, I have: > > cd /usr/src/ > > downloaded ieee1394-2.2.18-20001223 > > ln -s linux-2.2.16/ linux-2.2 > > zcat ieee1394-2.2.18-20001223 | patch -p1 > > > > It tells me: > > [root@pancakes src]# zcat ieee1394-2.2.18-20001223 | patch -p1 > > can't find file to patch at input line 4 > > Perhaps you used the wrong -p or --strip option? > > > > Dang! :-) ...he's just told you what the problem is: wrong -p option. Either > you go: > > [root@pancakes src]# zcat ../ieee1394-2.2.18-20001223 | patch -p1 > > from within /usr/src/linux or > > [root@pancakes src]# zcat ieee1394-2.2.18-20001223 | patch -p0 > from /usr/src but after symlinking your linux source directory to linux-2.2.orig > (see below why) too. > > Greetings , Matteo > > PS: Be sure to use a "vanilla" kernel source, not a distribution-customized one. > > > The text leading up to this was: > > -------------------------- > > |diff -ruN linux-2.2.orig/CREDITS linux-2.2/CREDITS > > |--- linux-2.2.orig/CREDITS Sat Dec 23 03:54:34 2000 > > |+++ linux-2.2/CREDITS Sat Dec 23 03:56:18 2000 > > -------------------------- > > > > See? The patch expects to be applied on a tree named "linux-2.2.orig", which > isn't the usual name for a linux source directory. That's why everyone patches > using the -p1 option from "one step forward" down the directory tree. > > > File to patch: > > > > What do I do? Here is what I have in my directory. > > [root@pancakes src]# ls -l > > total 108 > > -rw-rw-r-- 1 mike mike 87909 Feb 1 17:31 ieee1394-2.2.18-20001223 > > lrwxrwxrwx 1 root root 12 Sep 25 13:49 linux -> linux-2.2.16 > > lrwxrwxrwx 1 root root 13 Feb 1 17:43 linux-2.2 -> linux-2.2.16/ > > drwxr-xr-x 18 root root 4096 Jan 31 23:02 linux-2.2.16 > > drwxr-xr-x 18 root root 4096 Jan 31 23:02 linux-2.2.16.old > > drwxr-xr-x 7 root root 4096 Sep 25 13:54 redhat > > > > -- > > Thank you in advance, > > Mike Spice (Michael Spiceland) - http://www.mikespice.com > > KLUG President (Knoxville Linux User Group) - http://web.utk.edu/~klug > > IgWig Solutions (owner) - http://www.mikespice.com/igwig/ > > > > _______________________________________________ > > mailing list Lin...@li... > > http://lists.sourceforge.net/lists/listinfo/linux1394-user > > > _______________________________________________ > mailing list Lin...@li... > http://lists.sourceforge.net/lists/listinfo/linux1394-user > |
From: Matteo M. <mat...@ti...> - 2001-02-02 10:05:53
|
"Michael Spiceland (aka Mike Spice)" wrote: > I am using RedHat Linux 7.0 with a 2.2.16 kernel. > > following the instructions exactly, I have: > cd /usr/src/ > downloaded ieee1394-2.2.18-20001223 > ln -s linux-2.2.16/ linux-2.2 > zcat ieee1394-2.2.18-20001223 | patch -p1 > > It tells me: > [root@pancakes src]# zcat ieee1394-2.2.18-20001223 | patch -p1 > can't find file to patch at input line 4 > Perhaps you used the wrong -p or --strip option? > Dang! :-) ...he's just told you what the problem is: wrong -p option. Either you go: [root@pancakes src]# zcat ../ieee1394-2.2.18-20001223 | patch -p1 from within /usr/src/linux or [root@pancakes src]# zcat ieee1394-2.2.18-20001223 | patch -p0 from /usr/src but after symlinking your linux source directory to linux-2.2.orig (see below why) too. Greetings , Matteo PS: Be sure to use a "vanilla" kernel source, not a distribution-customized one. > The text leading up to this was: > -------------------------- > |diff -ruN linux-2.2.orig/CREDITS linux-2.2/CREDITS > |--- linux-2.2.orig/CREDITS Sat Dec 23 03:54:34 2000 > |+++ linux-2.2/CREDITS Sat Dec 23 03:56:18 2000 > -------------------------- > See? The patch expects to be applied on a tree named "linux-2.2.orig", which isn't the usual name for a linux source directory. That's why everyone patches using the -p1 option from "one step forward" down the directory tree. > File to patch: > > What do I do? Here is what I have in my directory. > [root@pancakes src]# ls -l > total 108 > -rw-rw-r-- 1 mike mike 87909 Feb 1 17:31 ieee1394-2.2.18-20001223 > lrwxrwxrwx 1 root root 12 Sep 25 13:49 linux -> linux-2.2.16 > lrwxrwxrwx 1 root root 13 Feb 1 17:43 linux-2.2 -> linux-2.2.16/ > drwxr-xr-x 18 root root 4096 Jan 31 23:02 linux-2.2.16 > drwxr-xr-x 18 root root 4096 Jan 31 23:02 linux-2.2.16.old > drwxr-xr-x 7 root root 4096 Sep 25 13:54 redhat > > -- > Thank you in advance, > Mike Spice (Michael Spiceland) - http://www.mikespice.com > KLUG President (Knoxville Linux User Group) - http://web.utk.edu/~klug > IgWig Solutions (owner) - http://www.mikespice.com/igwig/ > > _______________________________________________ > mailing list Lin...@li... > http://lists.sourceforge.net/lists/listinfo/linux1394-user |
From: Michael S. (a. M. S. <mi...@mi...> - 2001-02-01 22:54:17
|
I am using RedHat Linux 7.0 with a 2.2.16 kernel. following the instructions exactly, I have: cd /usr/src/ downloaded ieee1394-2.2.18-20001223 ln -s linux-2.2.16/ linux-2.2 zcat ieee1394-2.2.18-20001223 | patch -p1 It tells me: [root@pancakes src]# zcat ieee1394-2.2.18-20001223 | patch -p1 can't find file to patch at input line 4 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |diff -ruN linux-2.2.orig/CREDITS linux-2.2/CREDITS |--- linux-2.2.orig/CREDITS Sat Dec 23 03:54:34 2000 |+++ linux-2.2/CREDITS Sat Dec 23 03:56:18 2000 -------------------------- File to patch: What do I do? Here is what I have in my directory. [root@pancakes src]# ls -l total 108 -rw-rw-r-- 1 mike mike 87909 Feb 1 17:31 ieee1394-2.2.18-20001223 lrwxrwxrwx 1 root root 12 Sep 25 13:49 linux -> linux-2.2.16 lrwxrwxrwx 1 root root 13 Feb 1 17:43 linux-2.2 -> linux-2.2.16/ drwxr-xr-x 18 root root 4096 Jan 31 23:02 linux-2.2.16 drwxr-xr-x 18 root root 4096 Jan 31 23:02 linux-2.2.16.old drwxr-xr-x 7 root root 4096 Sep 25 13:54 redhat -- Thank you in advance, Mike Spice (Michael Spiceland) - http://www.mikespice.com KLUG President (Knoxville Linux User Group) - http://web.utk.edu/~klug IgWig Solutions (owner) - http://www.mikespice.com/igwig/ |
From: Miha S. <mih...@so...> - 2001-02-01 19:09:55
|
Did anyone check if FISHER(RH 7.1) has the latest fixes of the 1394 subsystem? |
From: Dan D. <dde...@co...> - 2001-02-01 17:39:00
|
Originally, this was just a playtoy to see my iBot camera actually do something under linux and get broader experience with 1394 and video programming under Linux as I still consider myself a beginner. It deals with such things as libdc1394, video1394, X, color space conversions, sampling rate conversions, Xv, XvShm, and libjpeg. I am not really proud of the code, and cringe everytime I pass it along. I am more interested in applying some of these functions to Kino and Coriander. Kino is making good progress, so this weekend I hope to contribute to Coriander by making its video scope window work. Perhaps we can make Coriander save pics and feed RealServer. Capture of uncompressed video with Kino is a low priority task as well. It will probably be encoded/compressed to DV since that's the only format Kino currently deals with. I have also been looking deeply into making video1394 video4linux compliant. This would make it more open to applications like OpenH.323 for video conferencing and Broadcast (currently only supporting DV over 1394), and possibly an RTSP product for webcam streaming. From: "Damien Douxchamps" <ddo...@te...> > Hello Kurt, > > No problem to share it: I did not write that part! ;-) I just adapted a > sample capture program using DMA (xv_video1394) posted some time ago on > the devel list. It's Dan Kennedy who wrote it. Also, I'm using the > latest CVS for libdc1394, libraw1394, ieee1394 and I'm running kernel > 2.4.1. > > Damien > > > Are you willing to share your quick hack (at least the capture part)? > > I don't want to setup a live cam, but we are using the same Sony camera for > > an industrial machine vision project > > within the same environment than you. And we have substantial problems to > > get stable pictures. > > > > -- > 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-user > |
From: Karthikeyan M. <kma...@ho...> - 2001-02-01 16:21:31
|
Moral: If all else fails, go read the kernel sources, and check your .config. In the latest of my numerous 2.4.0 kernel compiles, I'd turned the idedma flag off. dvgrab works much better now. Thanks to everyone who replied. >From: "Karthikeyan Madathil" <kma...@ho...> >To: mih...@so... >CC: lin...@li... >Subject: Re: (no subject) >Date: Tue, 30 Jan 2001 23:16:11 -0000 > > >>first use hdparm -i /dev/hdx to get the info if the c1 and m16 are >>allowed. > >They are, because they work (and I did run hdparm -i to determine >what the max on the -m was: 16). I know they don't turn on dma, but >they do improve disk performance. > > > I can't turn dma on. I get an 'operation not permitted' >> >>WERE YOU ROOT? > >Most definitely. > >_________________________________________________________________________ >Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. > > >_______________________________________________ >mailing list Lin...@li... >http://lists.sourceforge.net/lists/listinfo/linux1394-user _________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. |
From: Damien D. <ddo...@te...> - 2001-02-01 15:58:44
|
Hello Kurt, No problem to share it: I did not write that part! ;-) I just adapted a sample capture program using DMA (xv_video1394) posted some time ago on the devel list. It's Dan Kennedy who wrote it. Also, I'm using the latest CVS for libdc1394, libraw1394, ieee1394 and I'm running kernel 2.4.1. Damien > Are you willing to share your quick hack (at least the capture part)? > I don't want to setup a live cam, but we are using the same Sony camera for > an industrial machine vision project > within the same environment than you. And we have substantial problems to > get stable pictures. > -- Damien Douxchamps URL : http://www.tele.ucl.ac.be/MEMBERS/Douxchamps_Damien_e.html |
From: <Kur...@pr...> - 2001-02-01 10:09:17
|
Hi Damien, nice hack :-)) You are looking busy over the web ;-) Are you willing to share your quick hack (at least the capture part)? I don't want to setup a live cam, but we are using the same Sony camera = for an industrial machine vision project within the same environment than you. And we have substantial problems = to get stable pictures. Best regards, Kurt H=E4usler -----Original Message----- From: Damien Douxchamps [mailto:ddo...@te...] Sent: Donnerstag, 01. Februar 2001 11:08 To: lin...@li...; lin...@li... Subject: From a 1394 camera to the web: a complete linux pipe Hi all, I have designed a quick hack to broadcast the images from my DFW-VL500 on the web using a Real server. This webcam system is working all under Linux thanks to all the work done by all of us! You can get a view of my office by going there: http://draco.tele.ucl.ac.be:8080/ramgen/encoder/LinuxFireCam.rm The purpose of this it to check the stability of the ieee1394 linux subsystem so it will stay online until it breaks down. (I use = video1394, libdc1394 (latest CVS), libraw1394 (latest CVS) and Coriander). Note that the Real Server I use is the free evaluation version so there's a limit of 25 users. Have fun! Damien --=20 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-user |
From: Damien D. <ddo...@te...> - 2001-02-01 09:17:55
|
Hi all, I have designed a quick hack to broadcast the images from my DFW-VL500 on the web using a Real server. This webcam system is working all under Linux thanks to all the work done by all of us! You can get a view of my office by going there: http://draco.tele.ucl.ac.be:8080/ramgen/encoder/LinuxFireCam.rm The purpose of this it to check the stability of the ieee1394 linux subsystem so it will stay online until it breaks down. (I use video1394, libdc1394 (latest CVS), libraw1394 (latest CVS) and Coriander). Note that the Real Server I use is the free evaluation version so there's a limit of 25 users. Have fun! Damien -- Damien Douxchamps URL : http://www.tele.ucl.ac.be/MEMBERS/Douxchamps_Damien_e.html |
From: Dan D. <dde...@co...> - 2001-01-31 22:23:53
|
dvgrab only works with compressed DV video data. The iBot outputs non-DV uncompressed video. I have an iBot myself. There is not much you can do with it right now under Linux. I can provide a sample program to generate jpeg pictures or display the video in a window. You can use the jpeg output in a website. Here are some other potential uses: 1. Either I or someone else enhances video1394 to be video4linux compatible, but that is not high a priority for me. You would be able to use this with the Open H.323 project (http://www.openh323.org/). 2. A medium priority is to add video in a window to Coriander (http://sourceforge.net/projects/coriander/). Maybe this weekend? 3. A medium-to-low priority is to add support for uncompressed video to Kino. Right now, Kino is only for editing DV, but I am looking to use my iBot to do stop motion animation within Kino. With this scenario you would be able to create AVIs with full motion video or stop motion animation with your iBot (or Pyro WebCam or other uncompressed video cam). FYI, most users around here are using uncompressed video cameras in robotics, machine vision, and other industrial applications. Most of the other users who are into entertainment, art, or hobby applications have DV minicams. So, those factors tend to drive the priorities. +-DRD-+ From: "Bill Paulson" <wpa...@lu...> > I'm having trouble getting 1394 running. It seems to be installed > correctly, as gscanbus runs and shows both the adapter and the camera on > the bus. Whenever I try a dvgrab, however, it blocks on a read trying > to get frames (I used gdb to check dvgrab's status). All the software > seems to be the latest. > Linux 2.4.0 with most recent 1394 updates applied > dvgrab 0.89 > libraw1394 0.8.2 > libdv-2001-01-07.patched > > Hardware is a Kouwell 582V adapter card, which uses a TI TSB41LV03 > physical layer chip, and a VIA Technologies VT6305 Link layer chip. The > adapter is supposed to be OHCI compliant. The camera is an Orange Micro > iBot. > > I have a vague suspicion that the camera needs something before it > starts up, but I've got no idea what (and I'm probably barking up the > wrong tree anyway). Any ideas? > Bill Paulson > > > > > > > _______________________________________________ > mailing list Lin...@li... > http://lists.sourceforge.net/lists/listinfo/linux1394-user > |
From: Jurgen K. <GTM...@in...> - 2001-01-31 22:02:38
|
Hi, Unfortunately the iBot is not a DV camera but a DC camera. It transmits only uncompressed video. To use it you need the libdc library. There already some work done on getting it to send some video. See the devel-mailinglist for examples (e.g. Coriander) Cheers, Jurgen Bill Paulson wrote: > I'm having trouble getting 1394 running. It seems to be installed > correctly, as gscanbus runs and shows both the adapter and the camera on > the bus. Whenever I try a dvgrab, however, it blocks on a read trying > to get frames (I used gdb to check dvgrab's status). All the software > seems to be the latest. > Linux 2.4.0 with most recent 1394 updates applied > dvgrab 0.89 > libraw1394 0.8.2 > libdv-2001-01-07.patched > > Hardware is a Kouwell 582V adapter card, which uses a TI TSB41LV03 > physical layer chip, and a VIA Technologies VT6305 Link layer chip. The > adapter is supposed to be OHCI compliant. The camera is an Orange Micro > iBot. > > I have a vague suspicion that the camera needs something before it > starts up, but I've got no idea what (and I'm probably barking up the > wrong tree anyway). Any ideas? > Bill Paulson > > > > _______________________________________________ > mailing list Lin...@li... > http://lists.sourceforge.net/lists/listinfo/linux1394-user |
From: Bill P. <wpa...@lu...> - 2001-01-31 21:44:08
|
I'm having trouble getting 1394 running. It seems to be installed correctly, as gscanbus runs and shows both the adapter and the camera on the bus. Whenever I try a dvgrab, however, it blocks on a read trying to get frames (I used gdb to check dvgrab's status). All the software seems to be the latest. Linux 2.4.0 with most recent 1394 updates applied dvgrab 0.89 libraw1394 0.8.2 libdv-2001-01-07.patched Hardware is a Kouwell 582V adapter card, which uses a TI TSB41LV03 physical layer chip, and a VIA Technologies VT6305 Link layer chip. The adapter is supposed to be OHCI compliant. The camera is an Orange Micro iBot. I have a vague suspicion that the camera needs something before it starts up, but I've got no idea what (and I'm probably barking up the wrong tree anyway). Any ideas? Bill Paulson |
From: Mark <to...@de...> - 2001-01-31 03:21:26
|
Make sure you are root as you do this. Karthikeyan Madathil wrote: > > >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. -- Mark to...@de... |
From: Karthikeyan M. <kma...@ho...> - 2001-01-30 23:16:32
|
>first use hdparm -i /dev/hdx to get the info if the c1 and m16 are allowed. They are, because they work (and I did run hdparm -i to determine what the max on the -m was: 16). I know they don't turn on dma, but they do improve disk performance. > I can't turn dma on. I get an 'operation not permitted' > >WERE YOU ROOT? Most definitely. _________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. |
From: Dan D. <dde...@co...> - 2001-01-30 18:15:42
|
If you do not have much of a development system setup, then try the RPM or Debian packages. 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 > |