On Wed, 11 Oct 2006, Alex Corcoles wrote: > Hi, > > Sorry, my mails to the list are rejected because my domain has no > postmaster account, it seems, so I'm afraid this will reach just you. > > Alan Stern wrote: > > On Wed, 11 Oct 2006, Alex Corcoles wrote: > > > > > >> Hi, > >> > >> Concerning the setting max_sectors to 64 on a Nokia 6131, I have a Nokia > >> 6234 (which is a rebranded 6233) and I have the same problem and the > >> same solution, so maybe the patch could be extended to include this model? > >> > > > > The patch has already been accepted, but there certainly could be another > > patch adding the 6234. You'll have to provide the device information in > > /proc/bus/usb/devices or from "lsusb -v". > > > > > Ah, thank you. I think the relevant section from lsusb is: > > Bus 002 Device 011: ID 0421:0495 Nokia Mobile Phones > Device Descriptor: > bLength 18 > bDescriptorType 1 > bcdUSB 2.00 > bDeviceClass 0 (Defined at Interface level) > bDeviceSubClass 0 > bDeviceProtocol 0 > bMaxPacketSize0 64 > idVendor 0x0421 Nokia Mobile Phones > idProduct 0x0495 > bcdDevice 3.70
> Should I send this somewhere else or take further action? This is good enough. > >> (BTW, I'm sorry if this has been asked before and rebutted, but why not > >> make the default max_sectors like Windows? It would surely help with > >> compatibility) > >> > > > > I'd be willing to do that if you can tell me how Windows decides what > > max_sectors should be set to. I don't have any idea how Windows works > > internally. > > > > On the other hand, it may turn out that the value used by Windows is too > > pessimistic for many devices and reduces their throughput unnecessarily. > > So maybe imitating Windows wouldn't be such a good idea after all. > > > > > Ah, thanks for the explanation. The linux-usb faq seemed to imply that > Windows chose 64 automatically and that it was well-observed and known- That FAQ entry talks about devices from Genesys Logic only. I haven't checked what values Windows uses for other kinds of devices. > but yeah, probably there's no way to know that. Well, if there are not > so many devices that barf with >64, no problem- but having to list them > all is also probably not ideal. I understand it's not a clear decision. See if the patch below does what you want. Alan Stern Index: usb-2.6/drivers/usb/storage/unusual_devs.h =================================================================== --- usb-2.6.orig/drivers/usb/storage/unusual_devs.h +++ usb-2.6/drivers/usb/storage/unusual_devs.h @@ -189,6 +189,13 @@ UNUSUAL_DEV( 0x0421, 0x047c, 0x0370, 0x US_SC_DEVICE, US_PR_DEVICE, NULL, US_FL_MAX_SECTORS_64 ), +/* Reported by Alex Corcoles <[EMAIL PROTECTED]> */ +UNUSUAL_DEV( 0x0421, 0x0495, 0x0370, 0x0370, + "Nokia", + "6234", + US_SC_DEVICE, US_PR_DEVICE, NULL, + US_FL_MAX_SECTORS_64 ), + /* Reported by Olaf Hering <[EMAIL PROTECTED]> from novell bug #105878 */ UNUSUAL_DEV( 0x0424, 0x0fdc, 0x0210, 0x0210, "SMSC", ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel