On Tue, Jan 14, 2014 at 02:24:23PM +0100, Jacob Erlbeck wrote:
> This commit adds the implementation of these range formats to the
> encoder. In addition, the work-around that tried range 512 first is
> removed, so that the selection is primarily based on the max distance
> between frequencies.

I know you spent a lot of work on separating commits. Somehow I think
we can skip the moving of the ARFCN_RANGE_512 code? What do you think?


Reply via email to