> > Pinnacle/Miro DC10(seriously old): > > * Zoran zr36057 PCI controller > > * Zoran zr36050 MJPEG codec > > * Fuji md0211 Video Front End > > * Micronas vpx3216b TV decoder > > * Analog Devices adv7176 TV encoder > > OMG! How many different DC10 boards are out there?!?
Yes, another DC10. *sigh* > > Drivers I used: videodev, i2c-core, i2c-algo-bit, videocodec, vpx3220, >> adv7175, zr36050, zr36016(works for the fuji md0211), zoran > Are the md0211 and the zr36016 similar in how they're being operated? I > doubt... I mean, the fact that zr36016 loads doesn't tell us much. > zr36016 isn't supposed to work yet anyway (some small glitches), so we > can't even compare... Hrm... Once we get the zr36016 working (it might already be working, but we can't check as long as the zr36050 is not working as well), it should be pretty straightforward to support the md0211, *if* we can find the chip datasheet. After all, two raster-to-block converter chips with the same electrical interface can't be *that* different. Or can they ? :-) > > Do I need a driver for the tea6415c and what does this chip doo. > > It multiplies the output over the svideo and the composite output. I > think no driver is needed, at most some standard reg settings. Anyway, > we don't know yet. I don't think the chip is worth writing a driver. A single function in zoran.c would do the job. Anyway the chip is only needed for the output, and as all we have now is overlay there's no need to worry about it now. > I'd suggest to just add a new entry, and use names/macros like > 'DC10_old_mse' and 'DC10_old_md0211' or so... I don't know, it's just > confusing to see that so many different versions exist. :-(. Yes, that's not good news. And those boards use a zoran chip which does not implement the PCI subsystem ID feature, so we'll have to detect the differences manually. > > file vpx3220.c > > removed all the '__func__' so it compiled on redhat 8 > > I noticed the same thing... Use #define __func__ __FUNCTION__ and it'll > compile (with a lot of warnings). Which version of gcc are you using ? A redhat gcc-2.96 ?__func__ works fine in gcc 2.95.3. > If you want to help out (i.e. develop) with getting the JPEG recording > running (the code is basically there, something is just wrong in the > JPEG codec or VFE settings or so - we don't receive interrupts), please > consider yourself invited! If you plan to just wait, I'd advise to > subscribe to this mailinglist, you'll hear when it works. :-). Please be wanting to help us. Pleeeaase :-) Laurent Pinchart ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ Mjpeg-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/mjpeg-users
