Arjan,
because it seems that if sd driver attach the device as first one, other Upper Level Drivers will not be called anymore from mid layer scsi.We cannot denied to load different drivers than sd for type MOD.
why not?
And they will result not attached. Is this my fault or this is the real behaviour of kernel 2.6 ?
This behaviour will generate other troubles in developper community.
which community?
Anyone is developping SCSI driver to pilot type MOD.
again I asked you a question which you didn't bother to answer yet:Sorry for this. Here is my answer.
Did you write your closed module with linux in mind or even specifically
for linux? Because if so it *really* is better for everyone if you could
show code on how to deal with your device instead, so that generic linux
will work with it. (and it also avoids a big mess wrt GPL issues)
We are developping driver to be inserted in a software suite that will pilot optical drive with Write Once disk.
We have no problem to publish our driver source code.
In any case we think that could be not interesting inserting in sd driver our private code and in case it will take very long time.
We are thinking about the best solution for this issue.
Thanks Aldo
--
Aldo Gavioli
Product Manager
NetStorage Software s.r.l
Viale Europa,74 - 20090 Cusago (Milan) Italy - Web: www.netstorage.it
- : send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
