List: linux-video Subject: [video4linux] Hello everybody From: alexb () jetsuite ! com (Alex Bakaev) Date: 1998-07-23 17:19:25 Hi, Just wanted to introduce myself as a new subscriber to the list. My name is Alex Bakaev and I am the original developer of the Brooktree bt848 video capture drivers for Win95 and WDM driver for Win98/NT5. Recently I decided to port them to Linux and was pleasantly surprised that a whole community exists around bt848. As I'm coming up to speed with Linux, please excuse my possibly naive questions. Once again, hi everybody, Alex Bakaev ------------ To unsubscribe from this list send mail to majordomo@phunk.org with the line "unsubscribe video4linux" without the quotes in the body of the message.
List: linux-video Subject: Re: [video4linux] Hello everybody From: alexb () jetsuite ! com (Alex Bakaev) Date: 1998-07-23 21:25:39 829 has the same decoder as 848 does ( except that 848 can capture even and odd fields separately ), so if you control 848, you control ( almost 100% ) 829. 829 alone doesn't make much sense because it needs a 'host' to control it ( a gfx chip ). So, support for 829 should be added in the display drivers, really. The source base for this support may be the same, of course ( except the I2C specifics of the gfx chips ). Source code for the Bt848 WDM driver and Bt829 WDM driver ( for the ATI chip ) is available on Win98/NT5 DDK. I haven't looked at 829 code in a long while, but initially it borrowed from the 848 driver ( in the decoder area ) Alex Paulo Castro wrote: > > Hi Alex > > There is a lot about bt848 but few about bt829 (ATI AIW...) > > Can you focus both at once ? > > ATI say that they will not develop drivers for Linux... > > Now this Internet effort is the hope to do so... > > Best Regards > PCastro ------------ To unsubscribe from this list send mail to majordomo@phunk.org with the line "unsubscribe video4linux" without the quotes in the body of the message.
List: linux-video Subject: Re: [video4linux] Hello everybody From: Alan Cox <alan () cymru ! net> Date: 1998-07-23 21:31:35 > 829 has the same decoder as 848 does ( except that 848 can capture even > and odd fields separately ), so if you control 848, you control ( almost > 100% ) 829. 829 alone doesn't make much sense because it needs a 'host' The problem with ATI is that they don't document their external chip interfaces for i2c. The overlay and multimedia registers I do know the names and positions of in the memory map but they dont directly correlate to obvious i2c values or I'd have posted a few test hacks for people to try by now. > to control it ( a gfx chip ). So, support for 829 should be added in the > display drivers, really. The source base for this support may be the > same, of course ( except the I2C specifics of the gfx chips ). The XFree people want to put XFree support in for drivers going entirely via the video card. Obviously that keeps it nicely out of our hair. The alternative option - having X11 and the kernel arbitrate for the register is sufficiently insane to be impractical in those cases. Alan ------------ To unsubscribe from this list send mail to majordomo@phunk.org with the line "unsubscribe video4linux" without the quotes in the body of the message.
List: linux-video Subject: Re: [video4linux] Hello everybody From: alexb () jetsuite ! com (Alex Bakaev) Date: 1998-07-23 21:43:50 829 sample in the Win98 DDK should show how I2C is used in ATI's case. Also, I'm not sure I understand the connection between I2C registers and overlay and MM registers. They are completely independent ( but I might be wrong on this one - I left ATI too long ago :) Of course, both must be used to have anything useful come out of 829. Alex Alan Cox wrote: > > > 829 has the same decoder as 848 does ( except that 848 can capture even > > and odd fields separately ), so if you control 848, you control ( almost > > 100% ) 829. 829 alone doesn't make much sense because it needs a 'host' > > The problem with ATI is that they don't document their external chip > interfaces for i2c. The overlay and multimedia registers I do know the > names and positions of in the memory map but they dont directly correlate > to obvious i2c values or I'd have posted a few test hacks for people > to try by now. > > > to control it ( a gfx chip ). So, support for 829 should be added in the > > display drivers, really. The source base for this support may be the > > same, of course ( except the I2C specifics of the gfx chips ). > > The XFree people want to put XFree support in for drivers going entirely > via the video card. Obviously that keeps it nicely out of our hair. The > alternative option - having X11 and the kernel arbitrate for the register > is sufficiently insane to be impractical in those cases. > > Alan ------------ To unsubscribe from this list send mail to majordomo@phunk.org with the line "unsubscribe video4linux" without the quotes in the body of the message.