Re: [libdc1394-devel] libdc1394 doesn't handle hubs

[Jon S. <jon...@ho...>]

Maybe we don't need it.  I wouldn't be using it, except the only way I
know to find the cameras is with dc1394_find_cameras, which in the end
calls the topology stuff.

On Sat, 2007-01-27 at 00:51 -0500, David Moore wrote:
> Playing devil's advocate for a moment...
> 
> Do we really need those topology functions in libdc1394?  It adds a lot
> of complexity to the code, and the only benefit that I can see is that
> it sets three variables:
> 
> phy_delay, phy_speed, power_class
> 
> These variables are for informational purposes only and are in fact
> never used by any other libdc1394 function.  Are they really needed?
> 
> Coriander uses them, but again, only for informational purposes.
> 
> -David
> 
> On Thu, 2007-01-25 at 16:49 +0900, Damien Douxchamps wrote:
> > I just checked the sources of libraw1394 but the topology functions have
> > disappeared.  Actually, I also fail to find cooked1394_read in
> > libraw-1.2.0. Weird. I suppose this could be replaced by raw1394_read().
> > In any case the whole thing needs a rewrite...
> > 
> 
> 
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Mailing list for libdc1394-devel
> lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libdc1394-devel

________________________________________________________________________
http://lug.htc.honeywell.com/people/jschewe [Honeywell Intranet Only]
*My views may not represent those of my employers