[bttv/tuner] Invalid hard-coded frequency in FM tuner driver(s).

From: Taisuke Yamada (tai@imasy.or.jp)
Date: Thu Mar 16 2000 - 23:06:27 EST

Next message: Scott Lurndal: "Re: If something is not stated in POSIX we should not bother even if 90%+ of Linux"
Previous message: Tim Waugh: "[patch] 2.3.99-pre2-3: remove duplicate ppp initialisation"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

I'm now trying to configure FM tuner that came in set with
fairly standard Bt848 + Phillips tuner (NTSC) card.

But it seems hard-coded frequency value in driver is preventing
me from using the tuner (I know I SHOULD be able to configure
this hardware, because I was able to do it on Windows).

When I looked into drivers/char/bttv.c (or any other tuner driver
source), all of them hard-coded frequency range to 87.5MHz - 108MHz.
So it's like this:

static int radio_ioctl(...) {

    struct video_tuner v;
    ...
    v.rangelow = (int)(87.5 * 16); /* 87.5MHz */
    v.rangehigh = (int)(108 * 16); /* 108MHz */

Unfortunately, this frequency range differs from region to region,
and range of 76.0MHz - 89.9MHz is used in my country.

Shouldn't these values be configurable by ioctl(2) call if they
can't be auto-configured from hardware information?

# It seems the author of bttv driver is aware of this possibility
# as comment "/* XXX - anything to do ??? */" was in that part of
# the code.

-- T. Yamada <tai@imasy.or.jp> PGP fingerprint = 6B 57 1B ED 65 4C 7D AE 57 1B 49 A7 F7 C8 23 46

- 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/

Next message: Scott Lurndal: "Re: If something is not stated in POSIX we should not bother even if 90%+ of Linux"
Previous message: Tim Waugh: "[patch] 2.3.99-pre2-3: remove duplicate ppp initialisation"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Thu Mar 23 2000 - 21:00:22 EST