� ���, 13.03.2002, � 08:48, Doug McClendon �������: > Why yes! > > The only way I have found so far is to compile ide-cd as a module. > > The problem (without kernel arguments 'hdx=ide-scsi') is that if the ide-cd > driver is compiled in, then it will claim the device during > boot/initialization, and > AFAICT there is no way to tell the idecd driver to release the device so > that > the ide-scsi driver can take it. (the kernel argument is what prevents > the ide-cd > driver from claiming it at boot time) > > If however, ide-cd is a module, then it can be unloaded (or not loaded > in the first > place), after which loading ide-scsi will successfully take over the device. >
Have you actually tried it? When ide-scsi is loaded it takes over only those devices that declare they are using ide-scsi driver. And the only known to me way to set hdc to use ide-scsi driver is to pass hdc=ide-scsi on boot. ide-scsi driver is horrible hack. It badly needs rewrite. But I am always scared by the fact that it touches SCSI subsystem that is anything but easy to ubderstand. Ideally ide-scsi should be on top of IDE not replace original IDE driver. May be when I have enough courage :-) -andrej
