CONFIG_VIDEO_DEV=m
CONFIG_VIDEO_BT848=m
CONFIG_BUS_I2C=m
CONFIG_MISC_RADIO=y
which I think includes all the right stuff(?). I then checked out
http://www.thp.uni-koeln.de/~rjkm/linux/bttv.html
and
http://roadrunner.swansea.uk.linux.org/v4l.shtml
and found very little Howto info (once I figure out what to do, perhaps I will
write a mini HowTo). So I plowed ahead, read the source, etc, and then did a:
mknod /dev/bttv c 81 0
mknod /dev/bttv0 c 81 0
chmod go+rw /dev/bttv*
(I still havn't looked into making the radio work so I havn't made
device files for that yet) and then I added this to my /etc/conf.modules
file:
alias char-major-81 bttv
which seemed to do no good when running aps, so I had to manually do a:
sudo modprobe bttv
and indeed I then saw in my kernel log:
bttv: Brooktree Bt848 (rev 18) bus: 0, devfn: 88, irq: 9, memory: 0xe1004000.
bttv: 1 Bt848 card(s) found.
bttv: model: HAUPPAUGE
i2c: bus registered: bt848-0
So far so good. I then compiled up xawtv, but when trying to run it I see:
andersee@dillweed% xawtv
X-Server supports DGA
X-Server supports VidMode
video mode: 1280x1024 640x480
dga: base=0xe0000000
v4l: base=0xe1000000
v4l and dga disagree about the framebuffer address
you probably want to check out the vidmem argument of the bttv module
and this shows up in my kernel logs:
bttv: PCI display adapter: Matrox Mystique.
Ok, so they disagree about where the framebuffer is supposed to be. Fine.
So I read the source, find the vidmem argument, and add this to my
conf.modules file:
options bttv vidmem=0xe0000000
and then I remove and then re-insert the bttv module. I then see the
_exact_ same message in the kernel log. Runing xawtv now gives me:
andersee@dillweed% xawtv
X-Server supports DGA
X-Server supports VidMode
video mode: 1280x1024 640x480
dga: base=0xe0000000
v4l: base=0xfff00000
v4l and dga disagree about the framebuffer address
you probably want to check out the vidmem argument of the bttv module
Now it seems to me that when I specify a particular address for the
card's vidmem, it should not pick some other arbitrary address, right?
Has anybody had more success then I am having with these things? Any
hints would be helpful.
-Erik
--
Erik B. Andersen Web: http://www.inconnect.com/~andersen/
email: andersee@debian.org
--This message was written using 73% post-consumer electrons--
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu