Johannes Stezenbach wrote:
On Mon, May 22, 2006, Manu Abraham wrote:
Johannes Stezenbach wrote:
Anyway, one last try. Let's go back to the very beginning:
- we need to extend frontend API for DVB-S2, DVB-H etc.
- we cannot do so without breaking backward compatibility
because of mistakes made when defining the current API
- so now that we define new API, we don't want to repeat
the same mistake, but design in a way that make future
extensions possible without too much pain for
driver and application developers
- right from the beginning my position was to do the
*minimal* work necessary to support the *current*
requirements -- keep it simple and stupid
- and add other stuff later when the need arises
- and all along you totally ignored this and instead
want to cram every last detail into the API that
you think *might* be necessary
- wrt requirements: you need to think through how
an application will work (how does dvbscan discover
DVB-S2 transmission? where do the tuning parameters
come from?)
currently the tuning parameters come from the
s2_satellite_delivery_system_descriptor
what i have in there is the sis-mis flag and the transport stream
identifier to select the streams
Anyone seen a s2_satellite_delivery_system_descriptor in any broadcast?
There are DVB-S2 braodcasts on Astra 19.2E, do they have
s2_satellite_delivery_system_descriptors?
Well, there was another great question how can Conditional Access be
used, but there aren't any CA descriptors..
Manu
_______________________________________________
linux-dvb@xxxxxxxxxxx
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
