Thread: [libdc] on which bus (ohci adapter) is my camera ?
Capture and control API for IIDC compliant cameras
Brought to you by:
ddouxchamps,
gordp
From: Philippe De M. <ph...@ma...> - 2008-04-17 22:39:36
|
Hello everybody, Is there a function, or a field in a struct, in libdc1394, which can answer the following question : assuming that the busses (ohci adapters) are numbered 0, 1, 2 .., on which bus is actually the camera I work with ? Answer may be linux-specific. The bus number should be the one that can be used as parameter for gscanbus -p N or firecontrol N. Thanks in advance Philippe |
From: David M. <dcm@MIT.EDU> - 2008-04-18 02:11:45
|
On Fri, 2008-04-18 at 00:39 +0200, Philippe De Muyter wrote: > Hello everybody, > > Is there a function, or a field in a struct, in libdc1394, which can > answer the following question : assuming that the busses (ohci > adapters) are numbered 0, 1, 2 .., on which bus is actually the > camera I work with ? > > Answer may be linux-specific. The bus number should be the one > that can be used as parameter for gscanbus -p N or firecontrol N. > Yes, the linux-specific answer is: #include <dc1394/linux/control.h> uint32_t port; dc1394_camera_get_linux_port (camera, &port); This function was added very recently, so it is in SVN only and will appear in the next release, which hopefully Damien will do soon. Note that this function does not exist for juju, only the legacy linux stack. -David |
From: Philippe De M. <ph...@ma...> - 2008-04-18 07:46:40
|
Thanks, David Philippe On Thu, Apr 17, 2008 at 10:11:34PM -0400, David Moore wrote: > On Fri, 2008-04-18 at 00:39 +0200, Philippe De Muyter wrote: > > Hello everybody, > > > > Is there a function, or a field in a struct, in libdc1394, which can > > answer the following question : assuming that the busses (ohci > > adapters) are numbered 0, 1, 2 .., on which bus is actually the > > camera I work with ? > > > > Answer may be linux-specific. The bus number should be the one > > that can be used as parameter for gscanbus -p N or firecontrol N. > > > > Yes, the linux-specific answer is: > > #include <dc1394/linux/control.h> > > uint32_t port; > dc1394_camera_get_linux_port (camera, &port); > > This function was added very recently, so it is in SVN only and will > appear in the next release, which hopefully Damien will do soon. Note > that this function does not exist for juju, only the legacy linux stack. |
From: Stefan R. <st...@s5...> - 2008-04-18 13:59:28
|
David Moore wrote: > On Fri, 2008-04-18 at 00:39 +0200, Philippe De Muyter wrote: >> The bus number should be the one >> that can be used as parameter for gscanbus -p N or firecontrol N. ... > uint32_t port; > dc1394_camera_get_linux_port (camera, &port); > > This function was added very recently, so it is in SVN only and will > appear in the next release, which hopefully Damien will do soon. Note > that this function does not exist for juju, only the legacy linux stack. It might be possible to come up with a Juju version of this too. This port number, in the context of Philippe's question, is actually a libraw1394 API element and evidently also supported by a jujufied libraw1394. AFAICS it matches struct fw_cdev_get_info.card in the firewire-core API. -- Stefan Richter -=====-==--- -=-- =--=- http://arcgraph.de/sr/ |
From: Damien D. <dd...@do...> - 2008-04-18 13:54:16
|
Hi David, On Thu, 2008-04-17 at 22:11 -0400, David Moore wrote: > This function was added very recently, so it is in SVN only and will > appear in the next release, which hopefully Damien will do soon. Note > that this function does not exist for juju, only the legacy linux stack. I finished my relocation and got my home internet connection (83Mbps!) so I'm back to work ;) But IIRC you still had to commit some changes before the release? OTOH, if everything is ready I will release it ASAP. -- Damien 高原 Douxchamps http://damien.douxchamps.net/ |