On Mon, Feb 16, 2009 at 1:39 PM, wk <handygewinnspiel@xxxxxx> wrote: > 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. Exactly! Should be entertaining to hear the answers to everything but the first 'what files do you edit', though the rest of the questions will likely continue to be ignored. It seems some think those not familiar with s2api technical structure should reverse engineer it and write the documentation rather then the people who actually created it. To even suggest such a thing is absurd in my humble opinion. Talk about counter-productive... -- 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
