List: linux-video
Subject: Audio
From: Pauline Middelink <middelin () polyware ! nl>
Date: 1999-12-21 8:49:20
Ok, list...
I'm ready to work on audio stuff in the zoran driver, since
more and more ppl want it to work :(
I just got one question, why does the bttv handle all the
tea6300, tea6320, tda8425, tda9840 and tda9850 chips
hardcoded and not through the normal i2c attachment
procedures? (and seperate drivers for the stuff, since
those can be reused by the zoran and/or other framegrabbers!)
Atleast there is a single audio function, which gets called
with different parameters. This could be seperated out and
appended to (not only [MUTE_]ON/OFF, but also VOLUME, TREBLE
BASS, BALANS, STEREO, LANG?) Just like the video_decoder.h
standard, so we end up having a compatible driver with a
common API to talk to...
Ok, where did i go wrong? :)
Met vriendelijke groet,
Pauline Middelink
--
PGP Key fingerprint = DE 6B D0 D9 19 AD A7 A0 58 A3 06 9D B6 34 39 E2
For more details look at my website http://www.polyware.nl/~middelin
--
To unsubscribe: mail video4linux-list-request@redhat.com with
"unsubscribe" as the Subject.
List: linux-video
Subject: Re: Audio
From: Adam Fritzler <mid () auk ! cx>
Date: 1999-12-21 9:20:43
On Tue, 21 Dec 1999, Pauline Middelink wrote:
> I just got one question, why does the bttv handle all the
> tea6300, tea6320, tda8425, tda9840 and tda9850 chips
> hardcoded and not through the normal i2c attachment
> procedures? (and seperate drivers for the stuff, since
> those can be reused by the zoran and/or other framegrabbers!)
The kernel bttv does this rather badly. See Ralph's and Gerd's bttv
packages. They have a seperate module per sound chip.
af
---
Adam Fritzler
{ mid@auk.cx, afritz@iname.com}
http://www.auk.cx/~mid/
"You may call me Lor." -- Lor
--
To unsubscribe: mail video4linux-list-request@redhat.com with
"unsubscribe" as the Subject.
List: linux-video
Subject: Re: Audio
From: Alan Cox <alan () redhat ! com>
Date: 1999-12-21 13:58:52
>
> I just got one question, why does the bttv handle all the
> tea6300, tea6320, tda8425, tda9840 and tda9850 chips
> hardcoded and not through the normal i2c attachment
> procedures? (and seperate drivers for the stuff, since
> those can be reused by the zoran and/or other framegrabbers!)
Because it was hacked on nto done properly. The folks doing the non
kernel bttv did it properly. Its now done properly in 2.3.34pre as I
merged Gerd's bttv 0.7.10 work and the new i2c bus code
--
To unsubscribe: mail video4linux-list-request@redhat.com with
"unsubscribe" as the Subject.
List: linux-video
Subject: Re: Audio
From: Pauline Middelink <middelin () polyware ! nl>
Date: 1999-12-21 22:13:50
On Tue, Dec 21, 1999 at 08:58:52AM -0500, Alan Cox wrote:
> >
> > I just got one question, why does the bttv handle all the
> > tea6300, tea6320, tda8425, tda9840 and tda9850 chips
> > hardcoded and not through the normal i2c attachment
> > procedures? (and seperate drivers for the stuff, since
> > those can be reused by the zoran and/or other framegrabbers!)
>
> Because it was hacked on nto done properly. The folks doing the non
> kernel bttv did it properly. Its now done properly in 2.3.34pre as I
> merged Gerd's bttv 0.7.10 work and the new i2c bus code
I noticed. I'm already working on a improved zr36120 driver
and changing the saa*.c modules :)
Now all i need is a way to do alloc_bootmem() without crashing
my computer at startup :(
Met vriendelijke groet,
Pauline Middelink
--
PGP Key fingerprint = DE 6B D0 D9 19 AD A7 A0 58 A3 06 9D B6 34 39 E2
For more details look at my website http://www.polyware.nl/~middelin
--
To unsubscribe: mail video4linux-list-request@redhat.com with
"unsubscribe" as the Subject.