On 8/9/07, Michael Krufky <mkrufky@xxxxxxxxxxx> wrote: > Manu Abraham wrote: > > >On 8/9/07, Michael Krufky <mkrufky@xxxxxxxxxxx> wrote: > > > > > >>I apologize for my delayed response -- I had to leave town unexpectedly. > >> > >>The above is OK with me. As I understand it, we cannot remove > >>fe->ops.info.frequency_max|min because it is part of the userspace API. > >>I wasn't thinking about that fact when I wrote my last email in this > >>thread. We should keep this in mind, for whenever the time comes that > >>we do have to break API compat. > >> > >> > >> > > > >That one (the frontend definition) is still needed. The max/min in the > >tuner is the one that which is redundant for the moment (It would be > >needed internally though, for better drivers). > > > OK. In that case, what Oliver has proposed seems completely appropriate. See the other mail what i wrote, in reply to Oliver: "Currently, with our status that's the best we can do. Probably, we can hope to have better drivers in the future." _______________________________________________ linux-dvb mailing list linux-dvb@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb