Hi, Mark Watson wrote:
I have my driver working now in that I can run dvbtraffic and see the
number of packets etc. However it seems I need to register a frontend to
do anything interesting (I hacked scan to work without, but don't really
want to do that to everything!). I tried getting the driver to work with
the dummy frontend, but am having no luck... I can't find any drivers with
useful comments on how this is done:-(
It appears that the DVB code always uses i2c to communicate? At least
dvb_register_frontend code seems to play with i2c always? Seems strange
since thats a a 2 wire inter chip thing. I don't know a great deal about
it besides writing a simple bit toggling thing to talk to the Maven chip
on the G400...
maybe you want to take a look on the cinergyT2 driver.
All I want from the frontend is to provide enough so that most DVBTuning ioctls make only sense if you are able to tune, not? The available transponders are listed in the NIT tables in the MPEG2 stream.
software things it is talking to a real frontend. Possibly later I want to
let it know which transponders are available and get a call to request
transponder change. Is that possible?
Can you please elaborate a little more in detail what your hardware is able to do? The "frontend" is basically the thing that fetches the signal from air or a network -- the frontend device is used to configure it. A simple MPEG2-Stream-Sniffer has nothing to set up, so you don't really need a frontend device.Would I be best off just writing a driver on the adaptor0/frontend0 major/minor to reply to the standard ioctls?
Or does calling
dvb_register_frontend etc. give me any benefit?
only if you have something like a frontend... hope that helps, Holger