User add-on driver does not have precedence over system add-on driver
|Reported by:||gerald zajac||Owned by:||axeld|
If two drivers support the same device, the one installed as a user add-on should take precedence over the one installed as a system add-on. For example, if there is a video card with a Savage chipset, it will normally cause the s3savage driver which is installed as a system add-on to be loaded and used. However, if another driver named S3 supports the same chip and is installed as a user add-on, it should take precedence and be loaded and used instead of the system add-on driver, but this does not happen. The following lines from the syslog shows both driver are loaded, and the one installed as a system add-on is opened.
KERN: savage: init_hardware - device supported KERN: savage: probe_devices: match found; name: graphics/5333_8A22_010000 KERN: savage: probe_devices: 1 supported devices KERN: loaded driver /boot/beos/system/add-ons/kernel/drivers/dev/graphics/s3savage KERN: vesa: init_hardware() KERN: vesa: init_driver() KERN: vesa: publish_devices() KERN: vesa: find_device() KERN: loaded driver /boot/beos/system/add-ons/kernel/drivers/dev/graphics/vesa KERN: S3: init_hardware() - device supported KERN: S3: probe_devices(): match found; name: graphics/5333_8A22_010000 KERN: S3: probe_devices(): 1 supported devices KERN: loaded driver /boot/home/config/add-ons/kernel/drivers/dev/graphics/s3 KERN: savage: open_hook(graphics/5333_8A22_010000, 0x90d59e70)