Alan & others:
Does anyone know off-hand if the string for iConfiguration is freed
anywhere in the new code in 2.6.13-rc3? This is the allocation:
int usb_set_configuration(struct usb_device *dev, int configuration)
{
struct usb_host_config *cp = NULL;
for (i = 0; i < dev->descriptor.bNumConfigurations; i++) {
if (dev->config[i].desc.bConfigurationValue == configuration) {
cp = &dev->config[i];
break;
}
}
if ((cp->desc.iConfiguration) &&
(cp->string == NULL)) {
cp->string = kmalloc(256, GFP_KERNEL);
if (cp->string)
usb_string(dev, cp->desc.iConfiguration,
cp->string, 256);
}
I only noticed because Pixar is having a problem with some of their
Intel/HP kit which is unable to transfer a very long string, and they
use a color calibrator with a long iConfiguration string.
What is that string for anyway? Everything worked fine until 2.6.11.
-- Pete
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO September
19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
[email protected]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
