Bug 1553 - bad detection of the slots in a transcend usb multi-card reader
bad detection of the slots in a transcend usb multi-card reader
Status: REJECTED INSUFFICIENT_DATA
Product: Drivers
Classification: Unclassified
Component: USB
i386 Linux
: P2 low
Assigned To: Greg Kroah-Hartman
:
Depends on:
Blocks: USB
  Show dependency treegraph
 
Reported: 2003-11-18 11:55 UTC by Jordi Irazuzta Card
Modified: 2006-07-10 13:33 UTC (History)
2 users (show)

See Also:
Kernel Version: 2.4.22
Tree: Mainline
Regression: ---


Attachments

Description Jordi Irazuzta Card 2003-11-18 11:55:47 UTC
Distribution:Gentoo
Hardware Environment:
Software Environment:
Problem Description:
I purchased a transcend usb multicard reader, the question is that when I
configured the device, the system only found one of the three slots (Yes!! I
enable the option 'probe all LUNS in each scsi device' in the kernel).
To get the problem solved, I edited the usb-storage driver (usb.c), and changed:

case US_SC_8020:
                        ss->protocol_name = "8020i";
                        ss->proto_handler = usb_stor_ATAPI_command;
                        ss->max_lun = 0;
                        break;
                                                                               
                                              
for  
 case US_SC_8020:
                        ss->protocol_name = "8020i";
                        ss->proto_handler = usb_stor_ATAPI_command;
                        ss->max_lun = 2;
                        break;
                                                                               
                                              
when i change the zero for the two and recompile, it works.
I don't know why the number by default of max_lun is zero. Because of this i
report this fact.







Steps to reproduce:
Comment 1 Nishanth Aravamudan 2005-07-17 21:36:06 UTC
I noticed that this same max_lun initial value exists in 2.6.12. David, should
this be changed or is it actually not a bug?

Thanks,
Nish
Comment 2 Adrian Bunk 2006-03-17 20:49:08 UTC
Is this issue still present in recent 2.6 kernels?
Comment 3 Adrian Bunk 2006-07-10 13:33:46 UTC
Please reopen this bug if it's still present in kernel 2.6.17.

Note You need to log in before you can comment on or make changes to this bug.