RE: [Unichrome-devel] Need help with v4l

[Thomas <uni...@sh...>]

Warren,

> Luc,
>
> The reason for doing so is this:
>
> This group is claiming that they are the better solution for VIA CLE266
> drivers.  VIA themselves are pushing their chipset to be used in this
> type of solution, where I2C input is used.  The boards that do this are
> appearing now and will be mass produced within the month.
>
> One of the main applications that will run on a board like this is
> MythTV, which as of the next release will exclusively run using your
> drivers.
>
> So, given that you want to be the de-facto standard for VIA/CLE266
> drivers and have convinced other software providers to exclusively use
> your software, there becomes a bit of a burden upon you to support the
> boards being made that use this chipset.
>
> Also, if you go back in the VIA arena forums (which until very recently
> I thought was the only place to ask questions about this stuff), I was
> asking questions about I2C (V4L) input a year ago.  I apologize for not
> asking here earlier, but as I stated, I did not know that this was the
> place to ask.
>
> Put simply: HELP!!!!!!!
>
> Regards,
> Warren
>

The patches and hints we've sent you is about what we can come up with at
the moment. Given the V4L source in the -epia patches and the patch I sen=
t
you yesterday should get you up running, but as Luc stated in his mail, w=
e
cannot se support for this going into the Unichrome driver in the
forseeable future.

We're all working on this project on our spare time. We have jobs and
other things to take care of and frankly, other stuff are higher up on th=
e
todo list, like CN400 support, modeline / proper i2c support, getting 3D
working with the new AGP and standard XvMC support.

Some smaller commercial companies are depending on us, that's true, but n=
o
company so far has ever donated back their own bugfixes or hardware unles=
s
they had to to get a bug fixed, while still making a lot of money on our
work. VIA won't even recognize us.

It's possible to port the full V4L / tuner stuff into our driver / DRM,
but it is at least a full 2-3 weeks including debugging as an initial
guess, And that would be worth about 2kEuros standard computer consultant
salary, and unfortunately I guess neither I nor Luc or Ivor have the time
currently.

Regards
Thomas