Hi Christian,
On Thu, 21 Nov 2002, Christian Schmidt-Madsen wrote:
> 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.
I had one similar report before and it turned out to be a bad board.
Though I haven't tested gcc 3.2 yet I doubt that's the cause. Can you
downgrade to gcc 2.95 to see if it runs again?
Cord
