From: Eduard Hasenleithner <[EMAIL PROTECTED]>
Here is a patch for test11 which modifies the datafab driver according
to my understanding of the datafab device. I completely removed the lun
detection but left this work up to the operating system, namely
sd_mod.ko. sd_mod can decide which lun is available by means of checking
the media presence flag which is reported from the datafab_id_device
function. Now the driver works with _my_ datafab device.
Yes, but I think you broke some other devices.
One can arbitrarily choose info->lun = 0 or, as you do here,
info->lun = srb->device->lun, but that may be true or not.
A CF+SM reader has a CF part, and it has a srb->device->lun,
and it has a SM part, with a different srb->device->lun.
If probing has shown that srb->device->lun == 0 belongs
to the SM half, with a different driver, then datafab.c
will be called only for srb->device->lun == 1,
but still it may need info->lun = 0.
Andries
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
