Re: Question about saa7115

[Mauro Carvalho Chehab <mchehab@xxxxxxxxxxxxx>]

On Thu, 14 Feb 2008 15:34:22 -0800
"Guillaume Quintard" <guillaume.quintard@xxxxxxxxx> wrote:

> Hello again,
> baby step after baby step, I managed to get the saa7115 driver working
> on my platform \o/ thank you for the help
> 
> but I have a question : is the driver complete ? because it doesn't
> respond to half the V4L2 commands described in the API, and for some,
> the structure isn't fully updated, is that normal ?
> (I'm not blaming anybody, as I am new to all this stuff I still trying
> to understand the V4L2 world :-), but it seems to me, after reading
> the datasheet of the chip that the driver could offer more
> possibility, am I right ?)


At the current drivers, most of the API functions are handled by the bridge
driver. So, only a subset of saa7115 features is needed for those devices. As a
rule, we generally try not to add code on kernel drivers that aren't used by
other kernel drivers.

Yet, some functions shouldn't be on saa7115, like, for example:
	buffer handling - specific to the way it is connected;
	audio control and decoding - should be associated to an audio chip;

I don't know the implementation details of your driver. If you intend to submit
your driver for its addition on kernel, feel free to propose the addition of
new features to saa7115, and post to the list. Maybe your job will help also
other users (for example, saa7115 driver doesn't work with Osprey 560
- I'm not sure where's the issue).

Cheers,
Mauro

--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@xxxxxxxxxx?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list