Alan Stern wrote:
> Please post the contents of this file:
>
> After first inserting the flash device;
>
> After unplugging the device;
>
> After plugging the device back in.
>
> If the second and third copies are identical then you don't need to
> include both of them.
>
> Alan Stern
Alan Stern wrote:
>Please post the contents of this file:
>
> After first inserting the flash device;
>
> After unplugging the device;
>
> After plugging the device back in.
>
>If the second and third copies are identical then you don't need to
>include both of them.
>
>Alan Ste
On Wed, 28 Mar 2007, Girish wrote:
> But now kernel is unable to detect the insertion and removal event of
> the USB device. Driver detects the device only for the first time and
> there is no activity even if the device is removed and re inserted. When
> I tested the registers in the USB Host sys
Girish wrote:
>Hi all,
>I am trying to enable usb support on PXA27x board using
>linux-2.6.20. Inserted the following modules successfully
>usbcore.ko
>ohci_hcd.ko
>usb-storage.ko
>and inserted the flash drive(1GB) on USB port.
>but "/sys/bus/usb/devices/" directory is e
Hi Alan,
On 2/26/07, Alan Stern <[EMAIL PROTECTED]> wrote:
[...]
>
> That looks fine. Below is that actual patch I propose for 2.6.20. Can
> you please try it out and make sure that it really does fix the problem?
> Be sure to remove the test patch first, since this wants to go on top of
> plain
On Sun, 25 Feb 2007, Guilherme Salgado wrote:
> On 2/25/07, Alan Stern <[EMAIL PROTECTED]> wrote:
> > On Sun, 25 Feb 2007, Guilherme Salgado wrote:
> >
> > > I had some problems with the 2.6.20 kernel on my distribution and so I
> > > wasn't able to test the patch for some time. Fortunately, every
On 2/25/07, Alan Stern <[EMAIL PROTECTED]> wrote:
> On Sun, 25 Feb 2007, Guilherme Salgado wrote:
>
> > I had some problems with the 2.6.20 kernel on my distribution and so I
> > wasn't able to test the patch for some time. Fortunately, everything
> > is working now and I'm running 2.6.20 with the
On Sun, 25 Feb 2007, Guilherme Salgado wrote:
> I had some problems with the 2.6.20 kernel on my distribution and so I
> wasn't able to test the patch for some time. Fortunately, everything
> is working now and I'm running 2.6.20 with the patch you provided, and
> the "can't resume" problem is gon
Hi,
On 2/14/07, Alan Stern <[EMAIL PROTECTED]> wrote:
> On Tue, 13 Feb 2007, Guilherme Salgado wrote:
[...]
> > so I did the
> > changes manually and used upper case characters on the message passed
> > to dev_info(), to make sure the new module was loaded correctly, and I
> > seem to have got th
On Tue, 13 Feb 2007, Guilherme Salgado wrote:
> Hi Alan,
> > Below is a revised version of the diagnostic patch. Try using it instead
> > of the earlier one and let's see what happens.
> >
>
> This revised version didn't apply cleanly into my tree,
Maybe because you didn't remove the original
Hi Alan,
On 2/13/07, Alan Stern <[EMAIL PROTECTED]> wrote:
> On Mon, 12 Feb 2007, Guilherme Salgado wrote:
>
> > > On Thu, 11 Jan 2007, Jon Smirl wrote:
> > >
> > [...]
> > >
> > > Here we see a resume that failed. The key indicator is the 0x1000 bit in
> > > the portsc value; it means the port i
On Mon, 12 Feb 2007, Guilherme Salgado wrote:
> > On Thu, 11 Jan 2007, Jon Smirl wrote:
> >
> [...]
> >
> > Here we see a resume that failed. The key indicator is the 0x1000 bit in
> > the portsc value; it means the port is still suspended even after it was
> > supposed to have resumed. This is
> On Thu, 11 Jan 2007, Jon Smirl wrote:
>
[...]
>
> Here we see a resume that failed. The key indicator is the 0x1000 bit in
> the portsc value; it means the port is still suspended even after it was
> supposed to have resumed. This is the Intel hardware-resume bug I
> described earlier. I have
I tried the device with USBCV. Under WinXP the device behavior is
flaky and I can't get USBCV to work on it at all. On the other hand,
the device functions without problem on Win2K.
I'd say there is something wrong with the resume implementation on the
device. The device does not have updatable fi
On Fri, 12 Jan 2007, Jon Smirl wrote:
> On 1/12/07, Alan Stern <[EMAIL PROTECTED]> wrote:
> > On Fri, 12 Jan 2007, Jon Smirl wrote:
> >
> > > Attachment is too big for the list.
> > > It seems to be stuck in a resume loop with your debug patch installed.
> > >
> > > Device is plugged into a USB 1.
On Thursday 11 January 2007 9:21 pm, Jon Smirl wrote:
> So why does the device work when plugged into a powered hub? Do the
> ports on the powered hub not do suspend/resume?
All USB hubs (root and otherwise) are supposed to support suspend/resume,
and you'd probably observe they're using it during
On 1/12/07, Alan Stern <[EMAIL PROTECTED]> wrote:
> On Fri, 12 Jan 2007, Jon Smirl wrote:
>
> > Using 2.6.20-rc4 on a system with an ICH4, it fails the same way as
> > the device did on the ICH5. This is starting to point to a broken
> > resume capability in the device. I have more systems around b
On Fri, 12 Jan 2007, Jon Smirl wrote:
> Using 2.6.20-rc4 on a system with an ICH4, it fails the same way as
> the device did on the ICH5. This is starting to point to a broken
> resume capability in the device. I have more systems around but they
> are all ICH4/5.
>
> So why does the device work
On Thu, 11 Jan 2007, Jon Smirl wrote:
> On 1/11/07, Jon Smirl <[EMAIL PROTECTED]> wrote:
> > The default Ubuntu kernel, 2.6.17-10-generic has CONFIG_USB_SUSPEND=y.
> > I plugged the device into the laptop and it powered on fine at boot.
> > When the build finishes I'll try with 2.6.20-rc4 and verb
Using 2.6.20-rc4 on a system with an ICH4, it fails the same way as
the device did on the ICH5. This is starting to point to a broken
resume capability in the device. I have more systems around but they
are all ICH4/5.
So why does the device work when plugged into a powered hub? Do the
ports on th
On 1/11/07, Jon Smirl <[EMAIL PROTECTED]> wrote:
> The default Ubuntu kernel, 2.6.17-10-generic has CONFIG_USB_SUSPEND=y.
> I plugged the device into the laptop and it powered on fine at boot.
> When the build finishes I'll try with 2.6.20-rc4 and verbose USB
> debug.
Ubuntu 2.6.17 kernels with CO
On 1/11/07, Alan Stern <[EMAIL PROTECTED]> wrote:
> Have you got a different computer to try this on?
I just kicked off a kernel build with the right config for my laptop
which has an ICH4.
I have a few other computers I can try if we need to.
The default Ubuntu kernel, 2.6.17-10-generic has CONF
On Thu, 11 Jan 2007, Jon Smirl wrote:
> In this log I booted with it plugged in and let the usbhid drivers load.
> I then successively modprobe/rmmod them.
>
> There were only two ways I could get the device working once it went
> into suspend:
> rmmod/modprobe uhci_hcd;modprobe usbhid
> usbreset
On 1/11/07, Alan Stern <[EMAIL PROTECTED]> wrote:
Probably the new driver wasn't loaded. On my system (FC6) uhci-hcd is
loaded as part of the initrd image, not through the usual sort of
on-demand loading. You may need to rmmod uhci-hcd and then load the
modified driver.
I see now it is on ini
On Thu, 11 Jan 2007, Jon Smirl wrote:
> It doesn't appear to have hit your debug code but I am sure I built it
> into the driver.
The debug code did not run, but it should have.
Probably the new driver wasn't loaded. On my system (FC6) uhci-hcd is
loaded as part of the initrd image, not through
It doesn't appear to have hit your debug code but I am sure I built it
into the driver.
--
Jon Smirl
[EMAIL PROTECTED]
dmesg1
Description: Binary data
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.n
On Thu, 11 Jan 2007, Jon Smirl wrote:
> Attached dmesg may explain what is happening.
I don't think so.
> I renamed all my sound and usb input modules so that they wouldn't
> load at boot. I then manually modprobe'd usbhid in.
>
> The device implements two profiles, sound and hid. How is error
Attached dmesg may explain what is happening.
I renamed all my sound and usb input modules so that they wouldn't
load at boot. I then manually modprobe'd usbhid in.
The device implements two profiles, sound and hid. How is error
processing going to work if both of these modules attach to the dev
On Wed, 10 Jan 2007, Jon Smirl wrote:
> > What happened to the HID interface before the reset?
>
> How can I check it? The controls cause events, is there some way to see them?
Well, earlier you wrote:
> This doesn't help but it is complicated because the PSC805 also
> includes a USBHID compo
On 1/10/07, Alan Stern <[EMAIL PROTECTED]> wrote:
> On Wed, 10 Jan 2007, Jon Smirl wrote:
>
> > I just rebooted and all of the drivers loaded automatically but the
> > device didn't work.
> > Doing a usbreset of the device fixed everything.
> >
> > My best guess is that the "usb 2-1: usb auto-resum
On Wed, 10 Jan 2007, Jon Smirl wrote:
> I just rebooted and all of the drivers loaded automatically but the
> device didn't work.
> Doing a usbreset of the device fixed everything.
>
> My best guess is that the "usb 2-1: usb auto-resume" failed to enable
> power to the device.
The dmesg log for
I just rebooted and all of the drivers loaded automatically but the
device didn't work.
Doing a usbreset of the device fixed everything.
My best guess is that the "usb 2-1: usb auto-resume" failed to enable
power to the device.
Note that the failure only happens when the device is plugged into a
On 1/10/07, Alan Stern <[EMAIL PROTECTED]> wrote:
> There is no way to prevent a USB device without a driver from being
> suspended. Perhaps we need one. On the other hand, USB devices _are_
> supposed to be able to suspend and resume with no ill effects -- it's part
> of the spec.
>
> I still wo
Brief summary: After being suspended and resumed, Jon's USB sound device
remains in a useless powered-off state (the LEDs don't turn back on).
Clemens, if you have any ideas that might be relevant, please let us know.
On Tue, 9 Jan 2007, Jon Smirl wrote:
> Something has a refcount set into snd
On Tue, 9 Jan 2007, Jon Smirl wrote:
> I tried to unbind/bind with the device in the not working state:
> snd-usb-audio 2-1:1.0: usb_probe_interface
> snd-usb-audio 2-1:1.0: usb_probe_interface - got id
> USB device is in the shutdown state, cannot create a card instance
> snd-usb-audio: probe of
I turned off CONFIG_USB_SUSPEND and everything is working.
--
Jon Smirl
[EMAIL PROTECTED]
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opi
On 1/9/07, Alan Stern <[EMAIL PROTECTED]> wrote:
> On Tue, 9 Jan 2007, Jon Smirl wrote:
>
> > I tried to unbind/bind with the device in the not working state:
> > snd-usb-audio 2-1:1.0: usb_probe_interface
> > snd-usb-audio 2-1:1.0: usb_probe_interface - got id
> > USB device is in the shutdown sta
On 1/9/07, Alan Stern <[EMAIL PROTECTED]> wrote:
> On Tue, 9 Jan 2007, Jon Smirl wrote:
>
> > On 1/9/07, Alan Stern <[EMAIL PROTECTED]> wrote:
> > > On Tue, 9 Jan 2007, Jon Smirl wrote:
> > >
> > > > Is there some tool or sys variable that can toggle power to the
> > > > device? That will let me se
On Tue, 9 Jan 2007, Jon Smirl wrote:
> On 1/9/07, Alan Stern <[EMAIL PROTECTED]> wrote:
> > On Tue, 9 Jan 2007, Jon Smirl wrote:
> >
> > > Is there some tool or sys variable that can toggle power to the
> > > device? That will let me see if it is in sleep mode when it shouldn't
> > > be.
> >
> > I
On 1/9/07, Alan Stern <[EMAIL PROTECTED]> wrote:
> On Tue, 9 Jan 2007, Jon Smirl wrote:
>
> > Is there some tool or sys variable that can toggle power to the
> > device? That will let me see if it is in sleep mode when it shouldn't
> > be.
>
> If you turn on CONFIG_PM_SYSFS_DEPRECATED then you can
On 1/9/07, Alan Stern <[EMAIL PROTECTED]> wrote:
> On Tue, 9 Jan 2007, Jon Smirl wrote:
>
> > Is there some tool or sys variable that can toggle power to the
> > device? That will let me see if it is in sleep mode when it shouldn't
> > be.
>
> If you turn on CONFIG_PM_SYSFS_DEPRECATED then you can
On Tue, 9 Jan 2007, Jon Smirl wrote:
> Is there some tool or sys variable that can toggle power to the
> device? That will let me see if it is in sleep mode when it shouldn't
> be.
If you turn on CONFIG_PM_SYSFS_DEPRECATED then you can suspend your device
by doing:
echo -n 2 >/sys/bus/u
On Mon, 8 Jan 2007, Jon Smirl wrote:
> On 1/8/07, Alan Stern <[EMAIL PROTECTED]> wrote:
> > What shows up in dmesg?
> dmesg is the same when it works and when it doesn't
I bet if you compare a working and a non-working dmesg log now that you
have CONFIG_USB_DEBUG turned on, you'll find a differen
On 1/8/07, Jon Smirl <[EMAIL PROTECTED]> wrote:
> >What happens if you unplug the device and then plug it directly into
> the computer?
Is there some tool or sys variable that can toggle power to the
device? That will let me see if it is in sleep mode when it shouldn't
be.
--
Jon Smirl
[EMAIL PR
On 1/8/07, Alan Stern <[EMAIL PROTECTED]> wrote:
What shows up in dmesg?
dmesg is the same when it works and when it doesn't
What happens if you unplug the device and then plug it directly into
the computer?
it works. As far as I can tell the problem only occurs on boot
What do you get if
On Mon, 8 Jan 2007, Jon Smirl wrote:
> I have a Philips PSC805 external audio device. It is powered via USB.
> This device used to work plugged directly into my desktop. Now it is
> coming up, initializing, and then shutting down once user space
> starts. This happens about 90% of the time but not
On Wed, 8 Nov 2006, Sergei Organov wrote:
> Hello,
>
> My Canon photo camera is visible on USB bus only when I'm root, and
> invisible when I'm user:
>
> [EMAIL PROTECTED] ~$ lsusb
> Bus 001 Device 001: ID :
> Bus 001 Device 002: ID 046d:c03d Logitech, Inc.
> Bus 003 Device 001: ID :
On Fri, 10 Nov 2006, mahendra varman wrote:
> Hi Alan
>
> I tried to read data into the 1Gb transcend usb memory stick
> by using read(6) with LBA address 0...But iam not getting any values...
> I tried using read(10) also
>
> In what other way we can check whether the procedure is cor
On Saturday 04 November 2006 3:24 am, David Lee wrote:
>
> I am looking for USB device controllers that are ACM compliant. Please
> can you advise if you know any of them.
Pretty much any programmable peripheral controller can be made to
talk CDC ACM. If you're after one that does ACM in hardwar
On Sat, 4 Nov 2006 [EMAIL PROTECTED] wrote:
> Hi
>
> Iam using ISP 1161 usb device controller in my board
>
> If i give get descriptor request for 1.1 specification devices its
> giving only 8 byte info instead of 18 bytes and also the request is made
> 3 times..
This is more or less normal.
Hi
Iam using ISP 1161 usb device controller in my board
If i give get descriptor request for 1.1 specification devices its giving only
8 byte info instead of 18 bytes and also the request is made 3 times..
And some slower memory sticks get descriptor request is made twice to get the
descript
On Sat, 16 Sep 2006 10:39:33 -0400 (EDT), Alan Stern <[EMAIL PROTECTED]> wrote:
> with the latest kernels (definetly 2.6.17 and 1.6.8-rc*, I do now know off
> hand when this started) I can not access some (I think all USB 1) scanners
> via my SANE/Avision backend:
>[...]
> Try using usbmon to wa
On Sat, 16 Sep 2006, Rene Rebe wrote:
> Hi all,
>
> with the latest kernels (definetly 2.6.17 and 1.6.8-rc*, I do now know off
> hand when this started) I can not access some (I think all USB 1) scanners
> via my SANE/Avision backend:
>
> usb 3-1: new full speed USB device using uhci_hcd and a
On Tuesday 18 July 2006 7:27 am, Alan Stern wrote:
>When you export a filesystem as a USB mass-storage device, it
> is very important that the host and the device do _not_ try to access the
> filesystem at the same time. ...
>
> If this restriction is too strong, you also have the option o
On Tue, 18 Jul 2006, Ajay Jain wrote:
> Apologies, I could not make my point clear. We have a usb-function
> capability on our arm based board. We want to expose our device as a
> mass storage device. We understand that we will have to write a usb
> function driver for the same. The usb function c
On Tue, Jul 18, 2006 at 07:35:25PM +0530, Ajay Jain wrote:
> > > I have a usb hardware on my ARM based board. I want to develop a usb
> > > function driver so that I can view the file-system on the host side. I
> > > guess such kind of functionality is exposed in the mass-storage class.
> >
> > No.
> > I have a usb hardware on my ARM based board. I want to develop a usb
> > function driver so that I can view the file-system on the host side. I
> > guess such kind of functionality is exposed in the mass-storage class.
>
> No.
>
> > Can somebody guide me as to how to proceed? Are there any samp
On Tue, 18 Jul 2006, Ajay Jain wrote:
> Hello,
>
> I have a usb hardware on my ARM based board. I want to develop a usb
> function driver so that I can view the file-system on the host side. I
> guess such kind of functionality is exposed in the mass-storage class.
No.
> Can somebody guide me a
Mark Lord napsal(a):
> Jiri Slaby wrote:
>> Hello,
>>
>> I get this with 2.6.17-rc5-mm3 kernel:
> ..
>> usb-storage: device found at 10
>> usb-storage: waiting for device to settle before scanning
>> Vendor: Model: Rev:
>> Type: Direct-Access A
Jiri Slaby napsal(a):
> Mark Lord napsal(a):
>> Mmm.. okay, a quick glance at the USB storage code revealed one instance:
>>
>>/* Did we transfer less than the minimum amount required? */
>>if (srb->result == SAM_STAT_GOOD &&
>>srb->request_bufflen - srb->res
Mark Lord napsal(a):
> Mmm.. okay, a quick glance at the USB storage code revealed one instance:
>
>/* Did we transfer less than the minimum amount required? */
>if (srb->result == SAM_STAT_GOOD &&
>srb->request_bufflen - srb->resid < srb->underflow)
>
Jiri Slaby wrote:
> Jiri Slaby napsal(a):
>> Mark Lord napsal(a):
>>> Mmm.. okay, a quick glance at the USB storage code revealed one instance:
>>>
>>>/* Did we transfer less than the minimum amount required? */
>>>if (srb->result == SAM_STAT_GOOD &&
>>>srb->
Mark Lord wrote:
> Jiri Slaby wrote:
>> Mark Lord napsal(a):
>>> Jiri Slaby wrote:
..
---
sd 10:0:0:0: SCSI error: return code = 0x1007
end_request: I/O error, dev sdb, sector 1575
..
> The 0x1007000 is broken down as:
>
> 07 == "host byte" = DID_ERROR = "internal error"
> 10
Jiri Slaby wrote:
> Mark Lord napsal(a):
>> Jiri Slaby wrote:
>>> Hello,
>>>
>>> I get this with 2.6.17-rc5-mm3 kernel:
>> ..
>>> usb-storage: device found at 10
>>> usb-storage: waiting for device to settle before scanning
>>> Vendor: Model: Rev:
>>> Type: Direct-
Jiri Slaby wrote:
> Hello,
>
> I get this with 2.6.17-rc5-mm3 kernel:
..
> usb-storage: device found at 10
> usb-storage: waiting for device to settle before scanning
> Vendor: Model: Rev:
> Type: Direct-Access ANSI SCSI revision: 00
> SCSI de
On Fri, 31 Mar 2006, Oliver Neukum wrote:
> > > the bug it triggered is fixed in 2.6.16.1. But that doesn't explain
> > > that the buggy gamepad caused the modem to disconnect. This suggests
> > > a flaw at a deeper layer.
> >
> > What part of the log makes you think the modem was disconnected?
Am Freitag, 31. März 2006 00:09 schrieb Alan Stern:
> On Thu, 30 Mar 2006, Oliver Neukum wrote:
>
> > Am Donnerstag, 30. März 2006 07:02 schrieb Greg KH:
> > > On Wed, Mar 29, 2006 at 07:37:07PM +1030, Tony Cook wrote:
> > > > As a result of a power supply brownout, the usb game pad, a Logitech
>
Am Freitag, 31. März 2006 00:09 schrieb Alan Stern:
> On Thu, 30 Mar 2006, Oliver Neukum wrote:
>
> > Am Donnerstag, 30. März 2006 07:02 schrieb Greg KH:
> > > On Wed, Mar 29, 2006 at 07:37:07PM +1030, Tony Cook wrote:
> > > > As a result of a power supply brownout, the usb game pad, a Logitech
>
On Thu, 30 Mar 2006, Oliver Neukum wrote:
> Am Donnerstag, 30. März 2006 07:02 schrieb Greg KH:
> > On Wed, Mar 29, 2006 at 07:37:07PM +1030, Tony Cook wrote:
> > > As a result of a power supply brownout, the usb game pad, a Logitech
> > > WingMan Cordless Gamepad, connected to my machine, entere
Am Donnerstag, 30. März 2006 07:02 schrieb Greg KH:
> On Wed, Mar 29, 2006 at 07:37:07PM +1030, Tony Cook wrote:
> > As a result of a power supply brownout, the usb game pad, a Logitech
> > WingMan Cordless Gamepad, connected to my machine, entered a state of
> > incomplete reset and became parti
On Wed, Mar 29, 2006 at 07:37:07PM +1030, Tony Cook wrote:
> As a result of a power supply brownout, the usb game pad, a Logitech
> WingMan Cordless Gamepad, connected to my machine, entered a state of
> incomplete reset and became partially incommunicative. The following
> start-up log details
On Sat, 26 Nov 2005 17:49:37 +0530, "Savita H. Neelannava" <[EMAIL PROTECTED]>
wrote:
> I am writting USB driver in Slackware 10.2 i.e kernel 2.4.31 kernel.
> When i send a single command to my USB device it is responding multiple
> times( where it has to respond only once).
You aren't submittin
gerard klaver wrote:
> For some info about the 0x93a 0x2460/0x2468 (pac207c from Pixart) see my
> page (pac20x SANE Vidcam backend, under development):
Gerard,
have you tried contacting Pixart - are they helpful or?
--
/Per Jessen, Zürich
--
gerard klaver wrote:
> For some info about the 0x93a 0x2460/0x2468 (pac207c from Pixart) see my
> page (pac20x SANE Vidcam backend, under development):
>
> http://gkall.hobby.nl/pac20x.html
>
> its a single chip camera
Thanks Gerard,
I'll definitely have a look.
--
/Per Jessen, Zürich
On Tue, 2005-05-31 at 10:53 +0200, Per Jessen wrote:
> This is a small PC-camera, judging by the vendor id with a CCD imager by
> Pixart Imaging.
>
> I've been researching how to make this work, but I'm getting to a bit of a
> hard stop. I wanted
> to try out the sn9c102 usb driver (by Luca R
On Mon, 2005-02-07 at 11:37 +0530, MINI MOL wrote:
> Hi,
>
> My USB device needs a firmware download each time the device is plugged in.
> I have the hex firmware file, but do not have the firmware download details.
> I assume the device follows the "USB Device Class Specification for Device
> Fir
On Mon, 20 Dec 2004, Phil Dibowitz wrote:
> Torsten Pietsch wrote:
> > Hello Phil!
> > I have resolve this problem.
> > I removed the Flash Memory Card from the Camera.
> > The camera has an internal Memory of 12 MB.
> > When i only work with the internal memory the Camera works fine.No problems.
Torsten Pietsch wrote:
Hello Phil!
I have resolve this problem.
I removed the Flash Memory Card from the Camera.
The camera has an internal Memory of 12 MB.
When i only work with the internal memory the Camera works fine.No problems.
Is it possible that the flash memory card is corrupt or not reall
Try reproducing this with the latest 2.6.10-rc3-bk code.
- Dave
---
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Star
Torsten Pietsch wrote:
usb 1-1.4: new full speed USB device using address 3
usb 1-1.4: Product: CASIO QV DIGITAL
usb 1-1.4: Manufacturer: CASIO COMPUTER
Initializing USB Mass Storage driver...
usb-storage: This device (07cf,1001,1000 S 05 P 01) has an unneeded Protocol
entry in unusual_devs.h
P
On Thu, 8 Jul 2004, Roger Hartmann wrote:
> Hi there,
>
> the /var/log/messages o/p told me to send you an email about this. Hope
> it helps (see below).
>
> cheerz, Roger
>
>
> Jul 8 19:50:46 localhost kernel: sbpcd-0 [03]: Scanning 0x340
> (SoundBlaster)...
> Jul 8 19:51:14 localhost ke
On Sun, 9 May 2004, jack wrote:
> I don't understand the usage of the pipe member of this structure. The
> documentation says "The pipe element is used to encode the endpoint number
> and properties" - great ! what is an endpoint number ? and what properties
> are they talking about ?
>
> As you
On Sun, May 09, 2004 at 08:52:12AM +0100, jack wrote:
> My project is to write a character device drive for a "1-wire" network
> attached to a USB hub via a "1-wire" USB adapter.
FYI, there's a "public domain kit" (which is not actually public-domain,
but close: MIT/X11-style license):
http://w
Heiko Rosemann wrote:
Hi everyone,
I'm standing a little bit on the other side of the road - I am currently
developing a USB HID. Things work with Windows 98 and XP, but with Linux
(both 2.4.24 and 2.6.3) I get errors when it tries to receive the device
descriptor. 2.4.24 tells me:
usb.c: USB devi
On Wed, Mar 31, Greg KH wrote:
> Other than that, it looks sane. Let us know if there are any problems
> reported with it.
I will add this version.
diff -purNX /kernel_exclude.txt
linux-2.6.5-rc3-olh-usb.orig/drivers/usb/core/driverfs.c
linux-2.6.5-rc3-olh-usb/drivers/usb/core/driverfs.c
-
On Wed, Mar 31, 2004 at 06:05:32PM +0200, Olaf Hering wrote:
> diff -purNX /kernel_exclude.txt linux-2.6.5-rc3-olh-usb.orig/drivers/usb/core/usb.c
> linux-2.6.5-rc3-olh-usb/drivers/usb/core/usb.c
> --- linux-2.6.5-rc3-olh-usb.orig/drivers/usb/core/usb.c 2004-03-31
> 11:17:44.0 +
On Tue, Mar 30, Greg KH wrote:
> On Tue, Mar 30, 2004 at 08:15:52PM +0200, Olaf Hering wrote:
> >
> > No. make it static. Always.
>
> How about adding a patch that does this to your tree and see if any of
> your users's devices break? If such a patch lives successfully in a
> distro patch for
On Tue, Mar 30, Greg KH wrote:
> On Tue, Mar 30, 2004 at 08:15:52PM +0200, Olaf Hering wrote:
> >
> > No. make it static. Always.
>
> How about adding a patch that does this to your tree and see if any of
> your users's devices break? If such a patch lives successfully in a
> distro patch for
On Tue, Mar 30, 2004 at 08:15:52PM +0200, Olaf Hering wrote:
>
> No. make it static. Always.
How about adding a patch that does this to your tree and see if any of
your users's devices break? If such a patch lives successfully in a
distro patch for a release cycle or two, I'd be willing to add i
On Tue, Mar 30, Greg KH wrote:
> On Tue, Mar 30, 2004 at 08:18:12PM +0200, Olaf Hering wrote:
> > On Tue, Mar 30, Greg KH wrote:
> >
> > > On Tue, Mar 30, 2004 at 05:58:31PM +0200, Olaf Hering wrote:
> > > >
> > > > WHY is all the vendor, product, serial and what not info still dynamic?
> > >
On Tue, Mar 30, 2004 at 08:18:12PM +0200, Olaf Hering wrote:
> On Tue, Mar 30, Greg KH wrote:
>
> > On Tue, Mar 30, 2004 at 05:58:31PM +0200, Olaf Hering wrote:
> > >
> > > WHY is all the vendor, product, serial and what not info still dynamic?
> > > How can the info change during the "lifetime"
On Tue, Mar 30, Greg KH wrote:
> On Tue, Mar 30, 2004 at 05:58:31PM +0200, Olaf Hering wrote:
> >
> > WHY is all the vendor, product, serial and what not info still dynamic?
> > How can the info change during the "lifetime" of an attached USB device?
>
> Because the device can change those stri
On Tue, Mar 30, David Brownell wrote:
> Olaf Hering wrote:
> >
> >The current situation is, that reading the "serial" file of an USB
> >storage device leads to an empty serial file, in some situations.
>
> What are those situations?
There is some silly sort of media change polling. This keeps
Olaf Hering wrote:
The current situation is, that reading the "serial" file of an USB
storage device leads to an empty serial file, in some situations.
What are those situations?
I keep thinking the code to fetch string (and config, and device)
descriptors needs some fault handling and retry logi
On Tue, Mar 30, 2004 at 05:58:31PM +0200, Olaf Hering wrote:
>
> WHY is all the vendor, product, serial and what not info still dynamic?
> How can the info change during the "lifetime" of an attached USB device?
Because the device can change those strings at any time if it wants to
(and I've seen
Dmitri:
The usb_reset_device() function in 2.6.0 will get an overhaul in the near
future. I hope this will address the problems you raised.
On Tue, 19 Aug 2003, Dmitri Katchalov wrote:
> BTW while I am at it I have one particular issue with usb_reset_device():
> - If you want to reset the devi
Thanks Roger,
Quoting Roger Larsson <[EMAIL PROTECTED]>:
> On Monday 18 August 2003 18.18, Dmitri Katchalov wrote:
> > Hi,
> >
> > "USB device not accepting new address"
> >
> > I've got this Atmel AT76C503A based wireless USB adapter.
> > There is a driver for this wireless card (2 of them in f
On Monday 18 August 2003 18.18, Dmitri Katchalov wrote:
> Hi,
>
> "USB device not accepting new address"
>
> I keep getting these error messages. And looks like I'm not alone.
> I just did a quick google search on the subject and I've got about
> 6730 hits in google and about 1010 hits in newsgroup
Dmitri Katchalov wrote:
The answer in linux-usb.org FAQ is frankly just a lot of hand waving.
Clearly there is a long-standing problem which needs to be addressed.
PCI IRQ mapping is indeed a long-standing (non-USB) problem. It may
not be every major kernel release that has patches in that area,
I don't believe it is handwaving. The "user" comments might be, but the
actual answer is proven. THey may be other causes than mentioned though.
On Tue, 19 Aug 2003, Dmitri Katchalov wrote:
> Hi,
>
> "USB device not accepting new address"
>
> I keep getting these error messages. And looks like I'
1 - 100 of 121 matches
Mail list logo
