DragonFly bugs List (threaded) for 2006-08
Re: kernel panic during boot for ata trouble
:ata.h has already been renamed nata.h, and I guess you're talking about
:opt_ata.h for the other one, which can be renamed to opt_nata.h without
:too much of a problem. Then the only 'conflict' keeping both drivers
:from being in the same system is that the new ATA driver supports the
:same hardware as the old one besides new hardware it also supports,
:meaning it depends on who attaches first; we could just let config(8)
:bail out as soon as it finds both ata and nata devices in the kernel
:config. Also, it's possible to have both drivers attach only a set of
:devices which don't overlap with eachother. I'm not sure if that's
:something worth having?
: Thomas E. Spanjaard
Generally speaking it should be one or the other, but it might actually
be a good idea to add an exception variable in the kernel environment
that can be specified in /boot/loader.conf to allow both drivers to
attach to different ATA controllers for testing purposes. Lost of
machines have normal devices and SATA devices (with different PCI IDs).
This way we could boot a test machine with the old driver talking to
the boot disk and the new driver talking to a disk on the other
controller. Again, just for testing.