For the past five months I have used Cord Seele's fine v4l2 driver for
the Matrox Meteor2/MC frame grabber. For the past two weeks I have been
using version 1.0 of the driver which has worked nicely.
However, last week I upgraded from rh7.3 w/ a 2.4.19 to rh8.0 w/ a
similar 2.4.19 and now the driver fails to load. It seems that the main
change is an upgrade of gcc from 2.95 to (a rh variant of) 3.2.
When doing a 'insmod meteor2.o dmask=255' I get the following:
kernel: meteor2[via_module_init]: loading driver (dmask: 0xff)
kernel: meteor2[via_setup_pci]: p/v_base0: e8000000/d0a36000, p/v_base1:
e6000000/d0892000
kernel: meteor2[via_get_hwinfo]: unknown product id 248
kernel: V4L2: meteor2 (#0) initialize method failed
kernel: meteor2[via_register_card]: v4l2 device registration failed
The invalid product id is computed as
ci->product = ci->config & VIA_PRODUCT_ID_MASK;
where, in my case, ci->config has the suspicious value 0xff.
Has anyone (eg. Cord) experienced similar problems?
Thanks in advance,
- Christian
<gory_details>
kernel: meteor2[via_setup_pci]: VENDOR_ID: 102b
kernel: meteor2[via_setup_pci]: DEVICE_ID: 4536
kernel: meteor2[via_setup_pci]: COMMAND: 0004
kernel: meteor2[via_setup_pci]: STATUS: 0200
kernel: meteor2[via_setup_pci]: CLASS_REVISION: ff000000
kernel: meteor2[via_setup_pci]: CACHE_LINE_SIZE: 00
kernel: meteor2[via_setup_pci]: LATENCY_TIMER: 20
kernel: meteor2[via_setup_pci]: HEADER_TYPE: 00
kernel: meteor2[via_setup_pci]: BIST: 00
kernel: meteor2[via_setup_pci]: BASE_ADDRESS_0: e8000008
kernel: meteor2[via_setup_pci]: BASE_ADDRESS_1: e6000000
kernel: meteor2[via_setup_pci]: INTERRUPT_LINE: ff
kernel: meteor2[via_setup_pci]: INTERRUPT_PIN: 01
kernel: meteor2[via_setup_pci]: MIN_GNT: 00
kernel: meteor2[via_setup_pci]: MAX_LAT: 00
</gory_details>
