Re: Question about saa7115

[Mauro Carvalho Chehab <mchehab@xxxxxxxxxxxxx>]

On Fri, 15 Feb 2008 10:22:25 -0800
"Guillaume Quintard" <guillaume.quintard@xxxxxxxxx> wrote:

> On Fri, Feb 15, 2008 at 4:49 AM, Mauro Carvalho Chehab
> <mchehab@xxxxxxxxxxxxx> wrote:
> > On Thu, 14 Feb 2008 15:34:22 -0800
> >  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.
> >
> 
> uh, sorry, but what is a bridge driver ? I've never heard of it, and
> could find any help on the web.

It is the driver that works as a bridge between PCI or USB and I2C ;)

In the case of saa7115, the current bridge drivers that uses it are ivtv,
em28xx, pvrusb2 and usbvision.
> 
> >  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).
> 
> sure, I'll do that, once it'll be ready, and there's a long way to go
> before that happens :-)

:)



Cheers,
Mauro

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