> The main discussion in this thread was about drivers in userspace
No. The focus is that userspace API is not needed at all, and the
community believe that this is a regression from all efforts that are
being done by the community to have good quality OSS software.
Please stop with personal attacks.
Markus, you are thinking that all the community are fool? You used to
state on your website that your intention were to release binary-only
xc5000 drivers. So, please stop with childish and assume what you've
said.
The basis for tuner-xc2028 driver is tea5767. The xc2028/xc3028 drivers
is very simple:
a) load the proper firmware;
b) send one 32 bits command to select frequency + the frequency divider.
All the rest is the common logic of a tuner driver.
If you take a look at my driver, you will see that the implementation is
different, providing also those functionalities:
- provides a sync during frequency setting, needed by tm6000;
- has the logic to retrieve signal status;
- part of the firmware need to be reload every time you change a freq
(tm6000 driver needs it);
- supports just the firmwares I've identified as being used by tm6000
driver;
The only thing I used is your usbreplay.pl, as properly stated at
README.first (properly pointing to your site).
Again, please stop with personal attacks. This leads to nowhere.
---
However, I keep open to accept your kernelspace em28xx/xc3028 drivers,
providing that they fits at the current V4L/DVB core.
Changes at common APIs, and especially at Kernel to userspace API should
be discussed with the community. If you accept this fact, you may also
propose improvements at the APIs.
If, after all that were discussed, you're willing to do a serious work,
please send us the patches for em28xx/xc3028 kernelspace drivers.
Otherwise, I'll kindly ask you to take your own way and stop with those
flamewars.
Cheers,
Mauro
-
