*grin* Yes, I know what the initials stand for, I have read the web pages, you know. I changed the subject of the thread, since the conversation leads to a different issue. What I do not understand is the connection between card drivers and V4L(2) API(s). Why some driver works with V4L and not for V4L2, for example. The code example that you mentioned is exactly what I need to do, so it will at least be a good starting point (once I get a frame grabber, that is). However, the fancy stuff you mention, do they happen to be ROI capture, i.e. cropping? I will need that for my application. -- Georgios Kapetanakis Department of Computer Science University of York ----- Original Message ----- From: "Alan Cox" <alan@xxxxxxxxxx> To: <video4linux-list@xxxxxxxxxx> Sent: Tuesday, October 22, 2002 7:02 PM Subject: Re: Frame grabbers with bt8x8 chipset > > Well, unlike all of you guys, I'm not a guru in either Linux or frame > > grabbers. I am forced to learn because of my work requirements. I'll > > probably need someone to "hold my hand" while I make my first steps in this > > field. > > V4L "Video4Linux" > > Thats the current interface. It works, its pretty easy to use but its not > as complete as people would like and some of the more fancy stuff is a bit > odd in places. > > V4L2 "Video4Linux2" > > extends and fixes up the API, makes it more powerful and more logical. > > > There are some nice code examples around which do nothing but grab > frames continually. If your main area of interest is to process the data > then the examples probably do all you need to capture it. > > > > _______________________________________________ > Video4linux-list mailing list > Video4linux-list@xxxxxxxxxx > https://listman.redhat.com/mailman/listinfo/video4linux-list
