Andrew de Quincey wrote: >On Monday 21 Nov 2005 13:06, Johannes Stezenbach wrote: > > >>On Mon, Nov 21, 2005, Andrew de Quincey wrote: >> >> >>>These are all good points. I'm going to start prototyping now - it'll be >>>obvious during that which API calls are the best all round from an API >>>and an implementation point of view. >>> >>> >>Have you had a look at the data sheet of demodulators which >>support scanning in firmware, like the mt352 and mt312? >>(Are there others?) >> >>I believe the mt3xx data sheets are available from the Zarlink website. >> >>I wanted to check them myself and comment on your API proposal, but >>again failed to find the time to do so. :-( >> >> > >yeah - I did. That was why I agreed with having frequency range scanning in >the kernel since the mt352 can do that entirely in hardware. > > Probably the best thing to do is to implement it in the frontend specific way for the time being, and later on we can have a common way of factoring the code out to make all frontends adhere to something in common. Manu
