2005-01-03 07:40:48

by Mark Hindley

Subject: 2.6.{9,10}: VIA DRM undefined symbols

Hi,

I have just tried to use the kernel via module for my CLE266 and get a
whole load of undefined symbols:


Jan 3 03:08:11 mercury kernel: Uniform CD-ROM driver Revision: 3.20
Jan 3 03:12:48 mercury kernel: via: Unknown symbol viadrv_sg_alloc
Jan 3 03:12:48 mercury kernel: via: Unknown symbol viadrv_sg_free
Jan 3 03:12:48 mercury kernel: via: Unknown symbol viadrv_irq_by_busid
Jan 3 03:12:48 mercury kernel: via: Unknown symbol viadrv_control
Jan 3 03:12:48 mercury kernel: via: Unknown symbol viadrv_driver_register_fns
Jan 3 03:12:48 mercury kernel: via: Unknown symbol viadrv_sg_cleanup
Jan 3 03:12:48 mercury kernel: via: Unknown symbol DRM_FIND_MAP
Jan 3 03:12:48 mercury kernel: via: Unknown symbol viadrv_wait_vblank
Jan 3 03:12:48 mercury kernel: via: Unknown symbol viadrv_irq_uninstall

Looking back, this seems to have appeared in 2.6.9 with the introduction
of the capabilities bitmask. The via driver appears not to have been
converted.

I am still trying to understand the new structure. What else does the
missing viadrv_driver_register_fns need to set apart from
dev->driver_features?

Thanks

Mark

2005-01-03 08:37:37

by Dave Airlie

Subject: Re: 2.6.{9,10}: VIA DRM undefined symbols

>
> Looking back, this seems to have appeared in 2.6.9 with the introduction
> of the capabilities bitmask. The via driver appears not to have been
> converted.
>
> I am still trying to understand the new structure. What else does the
> missing viadrv_driver_register_fns need to set apart from
> dev->driver_features?

what via driver is this? where does it come from, the kernel doesn't
ship with via drivers yet... the DRM has been completely redesigned so
old modules won't work anymore...

Dave.