Devin Heitmueller wrote:
As always we continue to welcome patches, including for the
documentation. Instead of bitching and moaning, how about you roll up
your sleeves and actually help out?
Let's try to remember that pretty much all the developers here are
volunteers, so berating them for not doing things fast enough for your
personal taste is not really very productive.
Regards,
Devin
Devin,
can you please explain, how others should contribute to an dvb api if
- the only DVB API file to be found is a pdf file, and therefore not
editable. Which files exactly to be edited you are writing of?
- one doesn't know which ioctls exist for what function, which return
codes and arguments, how to understand and to use..?
What you suggest is almost impossible to someone not perfectly familiar
with the drivers, only for dvb experts who have written at least a bunch
of drivers.
Its something different than sending patches for one single driver where
some bug/improvement was found.
On the other hand, in principle a driver without existing api doc is
useless. Nobody can use it, the same for drivers with undocumented new
features.
Regards,
Winfried
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html