Thread: [libdc1394-devel] changes to libdc1394 and coriander
Capture and control API for IIDC compliant cameras
Brought to you by:
ddouxchamps,
gordp
From: Dan D. <da...@de...> - 2002-01-30 05:54:26
|
Recent (3 months ago) changes to video1394 require an updated kernel-video1394.h in the libdc1394 package. This change does appear in kernel 2.4.17 ieee1394. Also, since video1394 now supports devfs, the device node for devfs users changes to /dev/video1394/0 (0 = first host adapter). Therefore, I made changes to both libdc1394 and Coriander to accomodate these changes in video1394. For libdc1394, besides the updated kernel-video1394.h, I added a field to the dc1394_cameracapture struct called "dma_device_file." During capture initialization, if the application has not initialized this field, it defaults to "/dev/video1394" for most backwards compatibility with non-devfs users. Next, an application like Coriander should let the user specify their device file. I have modified Coriander preferences to do that. The result is a set of dependent changes to video1394, libdc1394, and Coriander, with essentially no going back! Users and developers using this stuff will have to upgrade the kernel or ieee1394 to get the new video1394 to use with the new libdc1394 to use with the next release of Coriander. I have not YET committed anything to libdc1394 or Coriander CVS. Please raise any objections now before I commit. +-DRD-+ P.S. The side benefit is that there is now a clean way to support mutliple Coriander processes accessing multiple camera on multiple host adapters, which is something some users have been looking for. Also, this confirms that all of this stuff is working with changes to video1394 including use of devfs. P.P.S. devfs users need to configure devfsd to get usable permissions on their device nodes. |
From: Damien D. <dou...@te...> - 2002-01-30 08:44:00
|
Hi Dan, It looks nice to me. This break compatibility with previous code but I don't mind since it adds a functionality that was badly missing. I will change the configure scripts to require latest libdc so people will know they have to upgrade.=20 Go ahead and commit! ;) Damien On Wed, 2002-01-30 at 06:56, Dan Dennedy wrote: > Recent (3 months ago) changes to video1394 require an updated > kernel-video1394.h in the libdc1394 package. This change does appear in > kernel 2.4.17 ieee1394. Also, since video1394 now supports devfs, the > device node for devfs users changes to /dev/video1394/0 (0 =3D first host > adapter). Therefore, I made changes to both libdc1394 and Coriander to > accomodate these changes in video1394.=20 >=20 > For libdc1394, besides the updated kernel-video1394.h, I added a field > to the dc1394_cameracapture struct called "dma_device_file." During > capture initialization, if the application has not initialized this > field, it defaults to "/dev/video1394" for most backwards compatibility > with non-devfs users.=20 >=20 > Next, an application like Coriander should let the user specify their > device file. I have modified Coriander preferences to do that. >=20 > The result is a set of dependent changes to video1394, libdc1394, and > Coriander, with essentially no going back! Users and developers using > this stuff will have to upgrade the kernel or ieee1394 to get the new > video1394 to use with the new libdc1394 to use with the next release of > Coriander. >=20 > I have not YET committed anything to libdc1394 or Coriander CVS. Please > raise any objections now before I commit. >=20 > +-DRD-+ >=20 > P.S. The side benefit is that there is now a clean way to support > mutliple Coriander processes accessing multiple camera on multiple host > adapters, which is something some users have been looking for. Also, > this confirms that all of this stuff is working with changes to > video1394 including use of devfs. >=20 > P.P.S. devfs users need to configure devfsd to get usable permissions on > their device nodes. >=20 >=20 >=20 >=20 >=20 >=20 > _______________________________________________ > Mailing list for libdc1394-devel > lib...@li... > https://lists.sourceforge.net/lists/listinfo/libdc1394-devel >=20 --=20 _ Damien Douxchamps (=B0- PhD Student / Research Assistant //\ Image Processing Group, Telecom Laboratory, UCL, Belgium V_/_ http://www.tele.ucl.ac.be/MEMBERS/Douxchamps_Damien_e.html |
From: Felix T. <ta...@ee...> - 2002-01-30 15:48:35
|
I'll test! ;) I need to figure out how to use devfs anyway (sideproject). Multiple cameras would be good.=20 Felix On 30 Jan 2002, Damien Douxchamps wrote: > Hi Dan, >=20 > It looks nice to me. This break compatibility with previous code but I > don't mind since it adds a functionality that was badly missing. >=20 > I will change the configure scripts to require latest libdc so people > will know they have to upgrade.=20 >=20 > Go ahead and commit! ;) >=20 > Damien >=20 > On Wed, 2002-01-30 at 06:56, Dan Dennedy wrote: > > Recent (3 months ago) changes to video1394 require an updated > > kernel-video1394.h in the libdc1394 package. This change does appear in > > kernel 2.4.17 ieee1394. Also, since video1394 now supports devfs, the > > device node for devfs users changes to /dev/video1394/0 (0 =3D first ho= st > > adapter). Therefore, I made changes to both libdc1394 and Coriander to > > accomodate these changes in video1394.=20 > >=20 > > For libdc1394, besides the updated kernel-video1394.h, I added a field > > to the dc1394_cameracapture struct called "dma_device_file." During > > capture initialization, if the application has not initialized this > > field, it defaults to "/dev/video1394" for most backwards compatibility > > with non-devfs users.=20 > >=20 > > Next, an application like Coriander should let the user specify their > > device file. I have modified Coriander preferences to do that. > >=20 > > The result is a set of dependent changes to video1394, libdc1394, and > > Coriander, with essentially no going back! Users and developers using > > this stuff will have to upgrade the kernel or ieee1394 to get the new > > video1394 to use with the new libdc1394 to use with the next release of > > Coriander. > >=20 > > I have not YET committed anything to libdc1394 or Coriander CVS. Please > > raise any objections now before I commit. > >=20 > > +-DRD-+ > >=20 > > P.S. The side benefit is that there is now a clean way to support > > mutliple Coriander processes accessing multiple camera on multiple host > > adapters, which is something some users have been looking for. Also, > > this confirms that all of this stuff is working with changes to > > video1394 including use of devfs. > >=20 > > P.P.S. devfs users need to configure devfsd to get usable permissions o= n > > their device nodes. > >=20 > >=20 > >=20 > >=20 > >=20 > >=20 > > _______________________________________________ > > Mailing list for libdc1394-devel > > lib...@li... > > https://lists.sourceforge.net/lists/listinfo/libdc1394-devel > >=20 > --=20 > _ Damien Douxchamps > (=B0- PhD Student / Research Assistant > //\ Image Processing Group, Telecom Laboratory, UCL, Belgium > V_/_ http://www.tele.ucl.ac.be/MEMBERS/Douxchamps_Damien_e.html >=20 >=20 > _______________________________________________ > Mailing list for libdc1394-devel > lib...@li... > https://lists.sourceforge.net/lists/listinfo/libdc1394-devel >=20 |