On Wed, 2008-10-22 at 15:44 -0500, Carl Karsten wrote:
> Francesco Romani wrote:
> > On Wed, 2008-10-22 at 11:37 -0500, Carl Karsten wrote:
> >> Getting back to my vga2usb project that I left off 6 months ago.  I am 
> >> starting
> >> with what is simple, and expecting to be told "build from current source" 
> >> and
> >> "those options don't make sense" 
> > 
> > It may be the case (and it can be the case) but one way or another a
> > segfault or anything else as serious as that is not acceptable,
> > especially in beta or later releases.
> > 
> > As always, please be patient if my feedback comes late and don't be
> > afraid to remind to the list/bugtracker (berlios!)/me the still unsolved
> > issues.
> http://developer.berlios.de/bugs/?group_id=10094

Yep

> >>  I don't need this to work until march, so I have some time to help debug 
> >> whatever
> >> is active development.
> > 
> > I hope the debug will take much less time :)
> 
> well, that depends on how much time I can spare, and how quick the usb2vga
> driver dev reacts.  I just hit him with
> 
> What: Video4Linux API 1 ioctls and video_decoder.h from Video devices.
> When: December 2008
> http://www.kernel.org/doc/Documentation/feature-removal-schedule.txt

Of course the best thing for all of us is to cope with v4l2 API only,
but if the device will stay v4l1 we can still work on that.
Anyway, I'll prefer v4l2.

> >> [26944.623816] Linux video capture interface: v2.00
> >> [26944.732571] Epiphan Systems VGA frame grabber driver version 
> >> 3.19.2.0000 loaded
> >> [26944.733692] usbcore: registered new interface driver vga2usb
> >> [27202.812026] usb 5-4: new high speed USB device using ehci_hcd and 
> >> address 3
> >> [27202.944605] usb 5-4: configuration #1 chosen from 1 choice
> >> [27202.979123] VGA2USB is now attached to vga2usb-192
> >>
> >> Is there some way to figure out that vga2usb-192 is /dev/video0?  (I need 
> >> to
> >> submit a report to vga2usb dev and tell him to log what /dev/videoX gets 
> >> used.)
> > 
> > You can just use the driver name reported by transcode's import module.
> I don't understand.

When starting, the transcode's import_v4l2 module by default report a
line like this:

[import_v4l2.so] v4l2 video grabbing, driver = saa7134, card = Pinnacle
PCTV 310i

So you can verify what is connected to the device node. 
Unfortunately, this is printed out at the end of the setup, so we must
fix the colorspace issue before (or use a different tool).

Bests,

-- 
Francesco Romani // Ikitt
http://fromani.exit1.org  ::: transcode homepage
http://tcforge.berlios.de ::: transcode experimental forge

Reply via email to