On 27-12-2011 18:47, Andreas Oberritter wrote: > On 27.12.2011 18:26, Mauro Carvalho Chehab wrote: >> One usage of such call would be to retrieve the autodetected properties, >> after having a frontend lock. > > Btw., dvb_frontend already refreshes the cache whenever the lock status > changes, i.e. when generating frontend events. Btw, the event ioctl is DVBv3 only. It probably makes sense to add one DTV command to implement it. In a matter of fact, IMO, the better is to implement a set of DTV read status commands, plus one command for event. This way, a status call could return the events that are specific for each delivery system, instead of returning something that will require the userspace to do a FE_GET_PROPERTY call, in order to get the real parameters for the newer delivery systems. The current status API has some limits for some new delivery systems. For example, on ISDB-T, devices can produce both consolidated and per-layer status. > -- > 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 -- 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
