[linux-usb-devel] how to get the mount point for plugged mass-storage-device
My ultimate goal is to have different desktop icons for mass-storage devices automatically appear/disappear on the desktop as the devices are plugged/unplugged. Now, I've gotten the icons to appear correctly according to the different devices, but the removing issue is not working yet. The question is: Is the mount point for each mass-storage device stored somewhere in the /proc? Or somewhere else? If not, would it be possible to have it stored in /proc. I was thinking of using some /tmp/usb-mounts or /var/run/usb/mountpoints, but I think it would be better to have it in /proc. I'm not familiar with the /proc filesystem and don't know how to add stuff there. Does it need to be done in the kernel level or what? Currently, if I plug one usb mass-storage device, all usb storage devices get unmounted. So I would need to know what mount points get assigned to what devices. Of course I know this during the mounting, but I'd have to store the information to some file and then retrieve the information when device detaches. BR Tommi --- This SF.net email is sponsored by: The SF.net Donation Program. Do you like what SourceForge.net is doing for the Open Source Community? Make a contribution, and help us add new features and functionality. Click here: http://sourceforge.net/donate/ ___ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
Re: [linux-usb-devel] how to get the mount point for plugged mass-storage-device
Am Sonntag, 26. Oktober 2003 08:53 schrieb Tommi Sakari Uimonen: My ultimate goal is to have different desktop icons for mass-storage devices automatically appear/disappear on the desktop as the devices are plugged/unplugged. Now, I've gotten the icons to appear correctly according to the different devices, but the removing issue is not working yet. The question is: Is the mount point for each mass-storage device stored somewhere in the /proc? Or somewhere else? _All_ mountpoints are stored in /proc/mounts However, there is no way to tell whether a specific device corresponds to a USB device. If not, would it be possible to have it stored in /proc. I was Beyond what is already there, no. thinking of using some /tmp/usb-mounts or /var/run/usb/mountpoints, but I think it would be better to have it in /proc. I'm not familiar with the /proc filesystem and don't know how to add stuff there. Does it need to be done in the kernel level or what? Additions to /proc need to be done in kernel. Currently, if I plug one usb mass-storage device, all usb storage devices get unmounted. So I would need to know what mount points get assigned to If you unplug, you mean? what devices. Of course I know this during the mounting, but I'd have to store the information to some file and then retrieve the information when device detaches. Yes, you have to store it yourself. Usb-storage does not and cannot know about mounting. In 2.6 you can get this information from sysfs. There's no simple way to export such information, especially there is no 1:1 mapping here. Regards Oliver --- This SF.net email is sponsored by: The SF.net Donation Program. Do you like what SourceForge.net is doing for the Open Source Community? Make a contribution, and help us add new features and functionality. Click here: http://sourceforge.net/donate/ ___ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
Re: [linux-usb-devel] how to get the mount point for plugged mass-storage-device
Thanks very much for the (rapid) answers! Currently, if I plug one usb mass-storage device, all usb storage devices get unmounted. So I would need to know what mount points get assigned to If you unplug, you mean? Unplug, of course. what devices. Of course I know this during the mounting, but I'd have to store the information to some file and then retrieve the information when device detaches. Yes, you have to store it yourself. Usb-storage does not and cannot know about mounting. In 2.6 you can get this information from sysfs. There's no simple way to export such information, especially there is no 1:1 mapping here. Ok, I'll hack something up. Tommi --- This SF.net email is sponsored by: The SF.net Donation Program. Do you like what SourceForge.net is doing for the Open Source Community? Make a contribution, and help us add new features and functionality. Click here: http://sourceforge.net/donate/ ___ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
Re: [linux-usb-devel] recent USB programming doc?
Holger Schurig wrote: Is there any recent USB programming doc available (besides the USB 2.0 spec)? The Link from www.linux-usb.org to http://usb.in.tum.de/usbdoc/ points to some rather old code, from the year 2000. Yes that's rather dated now ... and it was always a bit specific to the usb-uhci HCD (for some significant details) in any case. The latest info is the 2.6 kerneldoc. Use that. - Dave --- This SF.net email is sponsored by: The SF.net Donation Program. Do you like what SourceForge.net is doing for the Open Source Community? Make a contribution, and help us add new features and functionality. Click here: http://sourceforge.net/donate/ ___ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
[linux-usb-devel] 2Wire Redhat Linux USB adapter
Hi - I need a driver for the 2Wire USB Wireless Adapter for Redhat Linux..an 802.11b device with the windows driver by Agere, there is no Linux driver. Have Redhat Linux 9.0 and can't connect t Internet because of this..tried downloading Orinoco thingy and it won't work..won't even unpack! HELP! __ Do you Yahoo!? Exclusive Video Premiere - Britney Spears http://launch.yahoo.com/promos/britneyspears/ --- This SF.net email is sponsored by: The SF.net Donation Program. Do you like what SourceForge.net is doing for the Open Source Community? Make a contribution, and help us add new features and functionality. Click here: http://sourceforge.net/donate/ ___ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
Re: [linux-usb-devel] 2Wire Redhat Linux USB adapter
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi - I need a driver for the 2Wire USB Wireless Adapter for Redhat Linux..an 802.11b device with the windows driver by Agere, there is no Linux driver. Then ship one of us one of these 2Wire USB Wireless Adapters. Have Redhat Linux 9.0 and can't connect t Internet because of this..tried downloading Orinoco thingy and it won't work..won't even unpack! Aha, the error message that you provided was very helpful to us solving it. I especially liked the precision that you used when you said that you downloaded Orinoco thingy. HELP! Ooh, capitals. It must be important; I'll get right on it. /joshua Didn't like my answer? Ask a better question next time. http://www.catb.org/~esr/faqs/smart-questions.html - -- Joshua Wise | www.joshuawise.com GPG Key | 0xEA80E0B3 Quote | lilo I akilled [EMAIL PROTECTED] by mistake -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/nEOMPn9tWOqA4LMRAv88AJ9LhjiT6oDYWVOvJ94tD6QLING98wCfT7sq 8mLAGOcNaoVDP8rq1k9E+i0= =8G5m -END PGP SIGNATURE- --- This SF.net email is sponsored by: The SF.net Donation Program. Do you like what SourceForge.net is doing for the Open Source Community? Make a contribution, and help us add new features and functionality. Click here: http://sourceforge.net/donate/ ___ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
Re: [linux-usb-devel] oops - kernel 2.6.0.test8
Alan Stern wrote: On Tue, 21 Oct 2003, Jon Wilson wrote: # dmesg give me this: hub 1-0:1.0: port 2, status 101, change 1, 12 Mb/s drivers/usb/host/uhci-hcd.c: 6420: wakeup_hc hub 1-0:1.0: debounce: port 2: delay 100ms stable 4 status 0x101 hub 1-0:1.0: new USB device on port 2, assigned address 2 usb 1-2: new device strings: Mfr=0, Product=0, SerialNumber=0 drivers/usb/core/usb.c: usb_hotplug usb 1-2: config 0 descriptor?? That last message is very odd. It indicates something might be wrong with your camera. Can you post the output from lsusb -v with your camera plugged in and turned on? Attached. This is with a 2.4.22 kernel, with which the cam works fine. I can boot into a 2.6.0-test8 kernel and redo this if needed. Jon Bus 001 Device 001: ID : Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 1.00 bDeviceClass9 Hub bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x idProduct 0x bcdDevice0.00 iManufacturer 0 iProduct2 USB UHCI Root Hub iSerial 1 6420 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 25 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x40 Self Powered MaxPower0mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 9 Hub bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes3 Transfer TypeInterrupt Synch Type none wMaxPacketSize 8 bInterval 255 Language IDs: (length=4) (null)((null)) Bus 001 Device 002: ID 0919:0100 Tiger Electronics Fast Flicks Digital Camera Language IDs: none (invalid length string descriptor bf; len=0) Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 1.00 bDeviceClass0 Interface bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x0919 Tiger Electronics idProduct 0x0100 Fast Flicks Digital Camera bcdDevice1.00 iManufacturer 0 iProduct0 iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 129 bNumInterfaces 1 bConfigurationValue 0 iConfiguration 0 bmAttributes 0x80 MaxPower 190mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass 0 Interface bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x01 EP 1 OUT bmAttributes3 Transfer TypeInterrupt Synch Type none wMaxPacketSize 16 bInterval 10 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes2 Transfer TypeBulk Synch Type none wMaxPacketSize 64 bInterval 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes2 Transfer TypeBulk Synch Type none wMaxPacketSize 64 bInterval 1 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 1 bNumEndpoints 3 bInterfaceClass 0 Interface bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x01 EP 1 OUT bmAttributes3 Transfer TypeInterrupt Synch Type none
Re: [linux-usb-devel] 2Wire Redhat Linux USB adapter
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 (cc:ed to the list, as `J' used the phrase 'One of you', implying that it was intended to be sent to multiple people. apologies if that was not the intent.) Hi there; Maybe it's because I've asked this question everywhere, and I'm getting pretty tired of this problem. That's still not an excuse for asking a piss-poor question. I provided you with a link at the end of my email to you; I at the very least expect that you read it. (As was said in the link: You shouldn't be offended by this; by hacker standards, he is showing you a rough kind of respect simply by not ignoring you. You should instead thank him for his grandmotherly kindness.) One of you (not an idiot like yourself) can answer the question. It is a 2Wire USB Wireless Adapter with a Windows driver based on the Agere Wavelan chipset - for the USB port, not for the PCMCIA card (they offer THAT driver for Linux on www.agere.com). 2Wire says they do NOT support Linux. Agere only has that one driver for the PCMCIA card on their website, so it leaves three options: 1) Someone wrote one or will write one. General rule is that if someone's written one, it'll be on Google. Learn to use it and love it. As to someone who is going to write it, there are two good ways to get something done: 1) Write it yourself, or 2) Pay someone else to do it. If you can't do either, then, well, it'll get done when it gets done. You can speed it up by sending a sample of the hardware that you're having issues with to someone. (Maybe you'll get credits in the driver, maybe you won't. Don't expect that you will, infact don't expect ANYTHING in return.) 2) They magically come out with one. Magically. Things don't just magically get written. Someone's gotta write it. 3) There is a workaround somehow. That would be someone writing a driver, right? At the very least, someone will need a sample of the device. You said that there are `three options'. That make it sound like you're imposing that we MUST do it, or else. There _is_ a fourth option: 4) Nothing happens. That's right. It might just happen that noone wants to write a driver, noone has the itme to write a driver, or (I know you don't want to hear this, but) No One Cares (tm). The USB Client is a Wireless Client Adapter that can be connected to computers with a USB port. Well duh. The USB Client has two LED indicators and two integrated antennas. Right, I'll get right on writing a driver for all devices with two LED indicators and two integrated antennae. (Oh how specific.) There is NO DRIVER for LINUX. I think you've told us this. © 2001-2002 Agere Systems Inc., All Rights Reserved Oh? News for you. Anything you send by email? Anyone's gonna copy it. /joshua (Don't like my response? Send a better question next time, namely, not one flaming me.) --- Joshua Wise [EMAIL PROTECTED] wrote: PS: Please don't top-post. It makes it really difficult. - -- Joshua Wise | www.joshuawise.com GPG Key | 0xEA80E0B3 Quote | lilo I akilled [EMAIL PROTECTED] by mistake -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/nHCpPn9tWOqA4LMRAvpfAJ9POdyasIWsy7YmTM009roAC3zFoQCeMANM fDMvthekNCwYh11IksR412Y= =sq5t -END PGP SIGNATURE- --- This SF.net email is sponsored by: The SF.net Donation Program. Do you like what SourceForge.net is doing for the Open Source Community? Make a contribution, and help us add new features and functionality. Click here: http://sourceforge.net/donate/ ___ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
Re: [linux-usb-devel] usb vfd request
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I've got a samsung 16T202DA VFD which (has a parallel interface and) is attached to a carrier board with a usb cable attached. I'm guessing the carrier board does some type of serial to parallel conversion. Are you sure it's a parallel interface, not a RS232 just over 25 pins? A google shows very little about the 16T202DA - do you have a link with more info? (Or do you mean that the LCD has a parallel interface?) Can't find much info on the carrier board. It's made by sasem.com and the silkscreen on the board says HTPC USB Rev 1.2. Their website doesn't seem to have anything and google has turned up zilch so far. Yeah, I'm not seeing anything at all about it even existing on their site. I'm hoping to use lcdproc or lcd4linux and am trying to figure out what modules to load (modify) to support this device. I'm thinking possibly usbserial. Anybody seen one of these and/or have any thoughts? What's its vendor ID and device ID? What endpoints does it have? If you're lucky, you'll just be able to jam data into it... I appologize in advance. I didn't go to the linux-usb-users list because a search of the archive for usblcd returned nothing, but there were some hits on linux-usb-devel. Ah, research in advance is greatly appreciated. :) No trouble at all. Thanks in advance -Henry Culver -Culver Consulting [EMAIL PROTECTED] /j - -- Joshua Wise | www.joshuawise.com GPG Key | 0xEA80E0B3 Quote | lilo I akilled [EMAIL PROTECTED] by mistake -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/nICwPn9tWOqA4LMRArckAJ0Vxofb/k6GxItZm0i8C+cTwVIMvgCgj+6l DkfVH5zCzlvqYL/HLTxKnpA= =3YB3 -END PGP SIGNATURE- --- This SF.net email is sponsored by: The SF.net Donation Program. Do you like what SourceForge.net is doing for the Open Source Community? Make a contribution, and help us add new features and functionality. Click here: http://sourceforge.net/donate/ ___ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
Re: [linux-usb-devel] UHCI: introducing delay between 2 TDs
On Fri, 24 Oct 2003, Manoj Sharma wrote: I have a low speed display device with just a control endpoint. When some large data is sent on the control endpoint, it is able to ACK for first data packet in a frame, but it NAKs for the next data packet so the rest of the frame goes waste because UHCI doesn't schedule any other TD in that frame. In UHCI driver (usb-uhci.c), I tried inserting TDs with 0 byte of data in between 2 genuine TDs for that device but the device NAKs even for a 0 byte data packet. Is there any way to introduce some sort of delay between 2 TDs so that the device gets time to process the first one? any other suggestion pls? Although you didn't say, it looks like you are running under Linux 2.4. Try using 2.6 and see if that makes any difference. So far as I know, the 2.6 version of the UHCI driver _will_ schedule other TDs in the same frame as a NAKed data packet for a control endpoint. That's correct, I am using 2.4.18 as well as 2.4.20 and it persists for both. I will check it out for 2.6 also. On the other hand, if you only have one USB device attached and it has only endpoint 0, what other TDs could there be for the driver to schedule? Different control messages for the same endpoint can't be intermixed; one has to finish completely before the next can begin. There is only one device connected to the host and it has only control endpoint. This is not to intermix different control messages, see there are some 10 TDs containing data from one control message, If the UHCI is scheduling them vertically, every second TD in the frame causes NAK hence there is only one TD getting trasacted per frame. If there is some delay introduced between 2 TDs (may be by using a dummy TD), the device may be able to finish the first one before it gets the second. Thanks manoj --- This SF.net email is sponsored by: The SF.net Donation Program. Do you like what SourceForge.net is doing for the Open Source Community? Make a contribution, and help us add new features and functionality. Click here: http://sourceforge.net/donate/ ___ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
Re: [linux-usb-devel] oops - kernel 2.6.0.test8
On Sun, 26 Oct 2003, Alan Stern wrote:
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 129
bNumInterfaces 1
bConfigurationValue 0
iConfiguration 0
bmAttributes 0x80
MaxPower 190mA
I won't bother with the rest. That bConfigurationValue = 0 is illegal;
your camera is not compliant with the USB 2.0 spec.
However, that doesn't explain what the problem is. 2.6.0-test8 should
work okay even with that illegal value there. Maybe it's indicative of
some other incompatibility that 2.6 is more strict about?
I just checked the source code again. It turns out that
bConfigurationValue = 0 _is_ the problem. The current USB code in 2.6.0
treats config 0 as meaning unconfigured (as per the USB spec). Under 2.4
that interpretation wasn't used.
The patch below may help. Try it out and let us know what happens.
Alan Stern
--- a/drivers/usb/core/message.c.orig Fri Oct 24 13:10:05 2003
+++ b/drivers/usb/core/message.cSun Oct 26 22:51:28 2003
@@ -1086,6 +1086,11 @@
ret = -EINVAL;
goto out;
}
+
+ /* The USB spec says configuration 0 means unconfigured.
+* But if a device includes a configuration numbered 0,
+* we will accept it as a correctly configured state.
+*/
if (cp configuration == 0)
dev_warn(dev-dev, config 0 descriptor??\n);
@@ -1101,7 +1106,7 @@
goto out;
dev-actconfig = cp;
- if (!configuration)
+ if (!cp)
dev-state = USB_STATE_ADDRESS;
else {
dev-state = USB_STATE_CONFIGURED;
---
This SF.net email is sponsored by: The SF.net Donation Program.
Do you like what SourceForge.net is doing for the Open
Source Community? Make a contribution, and help us add new
features and functionality. Click here: http://sourceforge.net/donate/
___
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
Re: [linux-usb-devel] UHCI: introducing delay between 2 TDs
On Mon, 27 Oct 2003, Manoj Sharma wrote: Although you didn't say, it looks like you are running under Linux 2.4. Try using 2.6 and see if that makes any difference. So far as I know, the 2.6 version of the UHCI driver _will_ schedule other TDs in the same frame as a NAKed data packet for a control endpoint. That's correct, I am using 2.4.18 as well as 2.4.20 and it persists for both. I will check it out for 2.6 also. On the other hand, if you only have one USB device attached and it has only endpoint 0, what other TDs could there be for the driver to schedule? Different control messages for the same endpoint can't be intermixed; one has to finish completely before the next can begin. There is only one device connected to the host and it has only control endpoint. This is not to intermix different control messages, see there are some 10 TDs containing data from one control message, If the UHCI is scheduling them vertically, every second TD in the frame causes NAK hence there is only one TD getting trasacted per frame. If there is some delay introduced between 2 TDs (may be by using a dummy TD), the device may be able to finish the first one before it gets the second. I'm not sure how 2.4 works. Under 2.6 the UHCI driver uses horizontal scheduling, not vertical. It also uses full-speed bandwidth reclamation, so it would make many attempts to send the TDs during each frame if your device was full-speed. Since the device is low-speed, that explains your difficulty. If your device is so slow that it can't handle two TDs in a row, what makes you think it will be able to handle two TDs that are separated by some sort of dummy? Modifying the driver to create such dummy TDs would be a very non-trivial task, and the result probably wouldn't be accepted into the kernel. Alan Stern --- This SF.net email is sponsored by: The SF.net Donation Program. Do you like what SourceForge.net is doing for the Open Source Community? Make a contribution, and help us add new features and functionality. Click here: http://sourceforge.net/donate/ ___ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
Re: [linux-usb-devel] usb vfd request
On Sun, 2003-10-26 at 19:19, Joshua Wise wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I've got a samsung 16T202DA VFD which (has a parallel interface and) is attached to a carrier board with a usb cable attached. I'm guessing the carrier board does some type of serial to parallel conversion. Are you sure it's a parallel interface, not a RS232 just over 25 pins? A google shows very little about the 16T202DA - do you have a link with more info? (Or do you mean that the LCD has a parallel interface?) A google for 16T202 (leaving off the DA) returned a couple of hits, one of which was: http://www.apollodisplays.com/pdf/16202da2j.pdf The connector on the vfd is a 14 pin header which includes 8 data, pwr, gnd and a few other signals (I need to review info on a standard parallel bus). Can't find much info on the carrier board. It's made by sasem.com and the silkscreen on the board says HTPC USB Rev 1.2. Their website doesn't seem to have anything and google has turned up zilch so far. Yeah, I'm not seeing anything at all about it even existing on their site. I'm hoping to use lcdproc or lcd4linux and am trying to figure out what modules to load (modify) to support this device. I'm thinking possibly usbserial. Anybody seen one of these and/or have any thoughts? What's its vendor ID and device ID? What endpoints does it have? If you're lucky, you'll just be able to jam data into it... The info returned by usbview is: Sasem Remote Controller V1.1 Manufacturer: Sasem Serial Number: Serial #0001 Speed: 1.5Mb/s (low) USB Version: 1.10 Device Class: 00(ifc ) Device Subclass: 00 Device Protocol: 00 Maximum Default Endpoint Size: 8 Number of Configurations: 1 Vendor Id: 11ba Product Id: 0101 Revision Number: 1.00 Config Number: 1 Number of Interfaces: 1 Attributes: a0 MaxPower Needed: 100mA Interface Number: 0 Name: (none) Alternate Number: 0 Class: 00(ifc ) Sub Class: 00 Protocol: 00 Number of Endpoints: 2 Endpoint Address: 81 Direction: in Attribute: 3 Type: Int. Max Packet Size: 8 Interval: 50ms Endpoint Address: 02 Direction: out Attribute: 3 Type: Int. Max Packet Size: 8 Interval: 50ms I appologize in advance. I didn't go to the linux-usb-users list because a search of the archive for usblcd returned nothing, but there were some hits on linux-usb-devel. Ah, research in advance is greatly appreciated. :) No trouble at all. Thanks in advance -Henry Culver -Culver Consulting [EMAIL PROTECTED] /j - -- Joshua Wise | www.joshuawise.com GPG Key | 0xEA80E0B3 Quote | lilo I akilled [EMAIL PROTECTED] by mistake -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/nICwPn9tWOqA4LMRArckAJ0Vxofb/k6GxItZm0i8C+cTwVIMvgCgj+6l DkfVH5zCzlvqYL/HLTxKnpA= =3YB3 -END PGP SIGNATURE- --- This SF.net email is sponsored by: The SF.net Donation Program. Do you like what SourceForge.net is doing for the Open Source Community? Make a contribution, and help us add new features and functionality. Click here: http://sourceforge.net/donate/ ___ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
Re: [linux-usb-devel] oops - kernel 2.6.0.test8
On Sun, 26 Oct 2003, Jon Wilson wrote: Alan Stern wrote: That last message is very odd. It indicates something might be wrong with your camera. Can you post the output from lsusb -v with your camera plugged in and turned on? Attached. This is with a 2.4.22 kernel, with which the cam works fine. I can boot into a 2.6.0-test8 kernel and redo this if needed. Jon Bus 001 Device 002: ID 0919:0100 Tiger Electronics Fast Flicks Digital Camera Language IDs: none (invalid length string descriptor bf; len=0) Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 1.00 bDeviceClass0 Interface bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x0919 Tiger Electronics idProduct 0x0100 Fast Flicks Digital Camera bcdDevice1.00 iManufacturer 0 iProduct0 iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 129 bNumInterfaces 1 bConfigurationValue 0 iConfiguration 0 bmAttributes 0x80 MaxPower 190mA I won't bother with the rest. That bConfigurationValue = 0 is illegal; your camera is not compliant with the USB 2.0 spec. However, that doesn't explain what the problem is. 2.6.0-test8 should work okay even with that illegal value there. Maybe it's indicative of some other incompatibility that 2.6 is more strict about? Alan Stern --- This SF.net email is sponsored by: The SF.net Donation Program. Do you like what SourceForge.net is doing for the Open Source Community? Make a contribution, and help us add new features and functionality. Click here: http://sourceforge.net/donate/ ___ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
