>>> the western CCIR range 88 - 108 MHz. Myself I think no artificial
>>> limits should be set for the receiving frequency, and just let
>>> the hardware do what it can.
>> The API return is supposed to be what the card can take. Of course
>> most radio cards are reverse engineering jobs so its not always
>> clear
> Indeed. The best way IMO to establish exactly what the card can
> handle would be to generate audio signals on arbitrary frequencies
> and then try to tune them.
If one has the card and a signal generator covering the appropriate
range, one should be able to sweep across the range and find both end
frequencies with reliable accuracy...
> Sometimes the data sheets lie ... also, I've found that a board's
> implementation of the design often excludes a feature or two that's
> technically available on the tuner chip or similar.
More likely, the data sheets are 'politically correct' - many
countries prohibit reception of radio signals outside of 88-108 by
those not licensed to do so, and the data sheets are usually written
with one eye open for possible sales problems...
> If someone finds that they can pick up a signal outside the range
> in the kernel reliably, then expansion of that range is probably
> warranted. Anything else is just guesswork unless it's based on
> some authoritative source of information for the hardware in
> question.
Probably a better choice would be for the kernel to assume that it
can, and report an error if the hardware says otherwise, at least as
far as that is possible...
Best wishes from Riley.
--- * ftp://ftp.MemAlpha.cx/pub/rhw/Linux * http://www.MemAlpha.cx/~rhw/kernel.versions.html
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/