On Sun, 21 Sep 2003, David Brownell wrote:
Alan Stern wrote:
Here's a piece from my system log, when I did apm --suspend. The
usb_device_suspend/resume messages are things I added for debugging.
Why was this routine called twice? (Don't be fooled by the timestamps; I
think
=106340167723122w=2
Patrick Mansfield later beefed it up to the version you were looking at.
I don't care which version of the patch gets accepted, so long as
_something_ is done. Patrick, what do you think?
Alan Stern
---
This sf.net email is sponsored
On Mon, 22 Sep 2003, Patrick Mansfield wrote:
On Mon, Sep 22, 2003 at 11:50:47AM -0400, Alan Stern wrote:
I don't care which version of the patch gets accepted, so long as
_something_ is done. Patrick, what do you think?
I would rather we can modify the flags for any broken device
, and
it's clear that no single strategy will work with every device. The
variety of ways in which these things fail is truly amazing.
Alan Stern
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
asked
to send 128 bytes of m-s page 8 they apparently forget that the connection
is only full-speed with a 64-byte packet maximum, and they try to send all
128 bytes in a single packet. But other failure modes have cropped up as
well.
Alan Stern
just worked.
Alan Stern
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https
On Mon, 22 Sep 2003, David Brownell wrote:
Alan Stern wrote:
Well, the code path is easy enough to find. If you look at suspend() in
arch/i386/kernel/apm.c, you'll see calls to pm_send_all() and
device_suspend(). They both end up filtering down to the USB HC drivers.
The bad one
place. And as Andries says,
there's no real point in trying to determine the cache type for a
hot-pluggable device in the first place. Furthermore, this will get rid
of some annoying Can't SYNCHRONIZE messages from sd.c.
Alan Stern
.
Is there any harm in sending a SYNCHRONIZE command to a device that
doesn't need it (write-through cache)? Maybe doing that is less dangerous
than trying to read mode-sense page 8 on these buggy USB devices.
(Although I'm not aware of anyone who has tried the experiment.)
Alan Stern
drivers/usb/host/uhci-hcd.c
Alan Stern
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
[EMAIL PROTECTED]
To unsubscribe, use the last form field
is synchronous; everything is defined in terms of frames and
micro-frames, and everything is timed by the host controller (not the
device controllers).
Alan Stern
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http
to 2.4 and 2.6.
Alan Stern
= unusual_devs.h 1.69 vs edited =
--- 1.69/drivers/usb/storage/unusual_devs.h Thu Sep 18 17:13:27 2003
+++ edited/drivers/usb/storage/unusual_devs.h Thu Sep 25 11:17:23 2003
@@ -542,10 +542,16 @@
* - They don't like the INQUIRY command. So we must handle
-- speeding up our cleanup work here.
I'm with Oliver on this one. What if a usb_reset_configuration() call was
going on at the same time? The code here would set the state to
NOTATTACHED and then reset_config would set it to ADDRESS. Not what we
want.
Alan Stern
has a valid refcount.
Yes.
Alan Stern
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
[EMAIL PROTECTED]
To unsubscribe, use the last form field
. There
are perfectly valid reasons for a device not to respond to a USB message.
Alan Stern
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
[EMAIL
with it? It's a lot simpler than the patch I
proposed before.
Alan Stern
= unusual_devs.h 1.70 vs edited =
--- 1.70/drivers/usb/storage/unusual_devs.h Mon Sep 22 12:37:51 2003
+++ edited/drivers/usb/storage/unusual_devs.h Thu Sep 25 17:11:46 2003
@@ -542,7 +542,7 @@
* - They don't like
.
Thanks for the patch, and I hope that helps.
If I can do anything else, please let me know.
Phil, thanks a lot for your help.
Greg, please merge the patch below for 2.4 and 2.6.
Alan Stern
= unusual_devs.h 1.70 vs edited =
--- 1.70/drivers/usb/storage/unusual_devs.h Mon Sep 22 12:37
applies to 2.6.0-test5-bk10.
Alan Stern
= include/scsi/scsi_device.h 1.5 vs edited =
--- 1.5/include/scsi/scsi_device.h Fri Sep 5 07:48:41 2003
+++ edited/include/scsi/scsi_device.h Fri Sep 26 11:41:48 2003
@@ -85,6 +85,7 @@
* because we did
that normally, provided that you unplug the reader (just
changing the card might not be enough).
Can you post a system log with verbose SCSI debugging turned on, showing
what happens when you plug the reader in, unplug it, and then plug it in
again?
Alan Stern
and he ought to be able to help.
Alan Stern
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
[EMAIL PROTECTED]
To unsubscribe, use the last form field
considered using bulk transfers rather than interrupt? If you're
not sharing the bus with any other devices then latency won't be a
issue, and bulk isn't subject to the same bandwidth limitations as
interrupt.
Alan Stern
---
This sf.net
bytes.
Alan Stern
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https
happens. Alternatively, try applying the patch that's available in
http://linux.bkbits.net:8080/linux-2.5/[EMAIL
PROTECTED]|src/|src/drivers|src/drivers/usb|src/drivers/usb/host|related/drivers/usb/host/uhci-hcd.c|[EMAIL
PROTECTED]
if it hasn't already been applied.
Alan Stern
is
using the bus they will receive nearly 100% of the bandwidth. That's a
lot more than the amount guaranteed for interrupt transfers.
Alan Stern
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
, be
sure to capture the debugging messages -- either configure your syslog
daemon or use dmesg.
Alan Stern
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
in there is where the problem
lies, and it may take a little work to track it down exactly.
Alan Stern
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
Alan Stern
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net
On Sat, 4 Oct 2003, Matthias Urlichs wrote:
Hi,
Alan Stern wrote:
For comparison, here is the corresponding log I got when I unplugged a USB
CD-RW device, minus several lengthy and uninformative stack dumps
following the Badness lines -- did you enable debugging in
lib/kobject.c
semaphore is supposed to prevent that sort of thing
from happening. So I don't see how this could have happened.
Alan Stern
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
reset_device() do a port reset, then read the device
and configuration descriptors and compare them to the previously-stored
values. If they disagree, the old drivers will be unbound and a complete
re-enumeration will take place.
So far as I know, no versions of the 2.4 driver do this.
Alan Stern
to
strange things like using an interface number it made up rather than the
one in the descriptor.
Sergio, if you can send us that information it will help a lot.
Alan Stern
---
This SF.net email is sponsored by: SF.net Giveback Program
and post the debugging log from
both sides. Comparing the host's idea of what happened with the gadget's
(you _do_ have verbose debugging enabled on the gadget side, don't you?)
will go a long way towards finding the cause of the problem.
Alan Stern
is usefull for you. If you have need or
interest in additional information, feel free to tell me.
Running kernel 2.6.0 test7.
Thanks for sending the message. An appropriate change has been adopted
into the newest development kernels.
Alan Stern
no configurations stored, it's hard to see how
the device could have worked under 2.4.20.
So Greg, the new code is technically correct. But since it's causing
problems with non-compliant hardware, maybe it should be changed. What do
you think?
Alan Stern
the two modules that would account for it?
Alan Stern
---
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click
that refers to the device in question. It also reports
one interface, numbered 1. The reason it works with the earlier software
is that the code did not check for invalid numbering.
Alan Stern
---
This SF.net email is sponsored by: SF.net
On Wed, 15 Oct 2003, Alan Stern wrote:
On Mon, 13 Oct 2003, Johannes Jordan wrote:
usb-storage: This device (07cf,1001,1000 S 05 P 01) has unneeded
SubClass and Protocol entries in unusual_devs.h Please send a copy of
this message to [EMAIL PROTECTED]
snip
when connecting my casio
On Fri, 17 Oct 2003, Phil Dibowitz wrote:
Alan Stern wrote:
| Could you try running this with verbose usb-storage debugging turned on,
| and post the debugging log? It may have some clues.
Erm... is that a kernel compile option or an option to the driver...
Sorry to be ignorant here, I've
.
Ultimately the best solution is for the manufacturer to fix the device.
Maybe a firmware upgrade would do the trick.
Alan Stern
---
This SF.net email sponsored by: Enterprise Linux Forum Conference Expo
The Event For Linux Datacenter Solutions
indicate whether this is a problem with the UHCI
driver. Second, try debugging the 2.6.0 version of uhci-hcd.c rather than
the 2.4 version. Fixes for things like this are generally applied to the
more advanced kernel for testing and afterward adopted into the older
stable branch.
Alan Stern
this happening before though...
Thoughts?
It is a SCSI bug, and it was recently tracked down by Matthias Urlichs.
See
http://sourceforge.net/mailarchive/message.php?msg_id=6252693
Alan Stern
---
This SF.net email sponsored by: Enterprise
invalid interface numbers.)
Alan Stern
---
This SF.net email sponsored by: Enterprise Linux Forum Conference Expo
The Event For Linux Datacenter Solutions Strategies in The Enterprise
Linux in the Boardroom; in the Front Office; in the Server
to interfaces. It also won't hurt to add considerably more
locking code (dev-serialize).
Alan Stern
---
This SF.net email sponsored by: Enterprise Linux Forum Conference Expo
The Event For Linux Datacenter Solutions Strategies in The Enterprise
, is it accepted that dev-serialize is the
correct lock for 3?
Alan Stern
---
This SF.net email sponsored by: Enterprise Linux Forum Conference Expo
The Event For Linux Datacenter Solutions Strategies in The Enterprise
Linux in the Boardroom
On Sun, 19 Oct 2003, Greg KH wrote:
On Sun, Oct 19, 2003 at 11:16:37AM -0400, Alan Stern wrote:
Greg:
Do you have any idea when serious new development will re-commence?
Has it ever really stopped? :)
Sometimes I wish it would, just for a little while...
There's a bunch
disk drive several times. It worked perfectly,
showing up as /dev/sda each time.
On Sun, 19 Oct 2003, Gene Heskett wrote:
On Sunday 19 October 2003 11:00, Alan Stern wrote:
It is a SCSI bug, and it was recently tracked down by Matthias
Urlichs. See
http://sourceforge.net/mailarchive
think this probably should be applied, but I'm not certain.
Alan Stern
= unusual_devs.h 1.73 vs edited =
--- 1.73/drivers/usb/storage/unusual_devs.h Mon Oct 6 13:46:12 2003
+++ edited/drivers/usb/storage/unusual_devs.h Mon Oct 20 14:17:35 2003
@@ -548,10 +548,10 @@
* - They don't
, which is available as a PDF file somewhere
on Intel's web site.
Alan Stern
---
This SF.net email is sponsored by OSDN developer relations
Here's your chance to show off your extensive product knowledge
We want to know what you know. Tell us
reports about this unusual_devs entry. I think the best thing is to
apply the patch I sent yesterday (as117) and then see if anyone complains.
Alan Stern
---
This SF.net email is sponsored by OSDN developer relations
Here's your chance to show
, though.
Alan Stern
---
This SF.net email is sponsored by OSDN developer relations
Here's your chance to show off your extensive product knowledge
We want to know what you know. Tell us and you have a chance to win $100
http://www.zoomerang.com
.
It's getting very annoying since the disk stays for more than 10 seconds
without responding.
Can you send more of the debugging log? The portion you included didn't
contain any context, making it hard to judge what the problem was.
Alan Stern
On Wed, 22 Oct 2003, Matthew Dharm wrote:
On Wed, Oct 15, 2003 at 03:04:11PM -0400, Alan Stern wrote:
Whoops! I spoke a little too hastily. I didn't notice that this device
has a release number that's at the _lower_ end of the range selected by
the unusual_devs.h entry. Perhaps
of reports recently about oopses occuring during
device disconnect processing. One from yesterday had usbdev-bus set to
some funny value and this looks like it may be similar.
It seems like a ripe area for someone to check out. Maybe a reference
count is getting decremented too soon.
Alan
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?
Alan Stern
there's no easy way to tell what the source of that problem is.
Maybe someone who knows more about ACPI and interrupt handling can help.
Alan Stern
---
This SF.net email is sponsored by: The SF.net Donation Program.
Do you like what
the next can begin.
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
On Sat, 25 Oct 2003, Phil Dibowitz wrote:
Alan Stern wrote:
Could be. My most recent attempt to fix this is in
http://sourceforge.net/mailarchive/message.php?msg_id=6315588
It sets the upper release limit to 0x and removes everything but
the FIX_INQUIRY flag. It seemed
of usb modules in this
session).
USB controller is VIA Technologies, Inc. USB 2.0 (rev 51).
Thanks
Vedran
Try applying this patch and see if it helps.
Alan Stern
--- a/drivers/usb/storage/scsiglue.cThu Oct 16 16:22:50 2003
+++ b/drivers/usb/storage/scsiglue.cSat Oct 25 10:59:45
On Sun, 26 Oct 2003, Alan Stern wrote:
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 129
bNumInterfaces 1
bConfigurationValue 0
iConfiguration 0
bmAttributes 0x80
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
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
Greg:
This patch helped Jon Wilson. It allows devices to have a configuration
numbered 0, in spite of the standard convention that config #0 really
means unconfigured. Please apply.
Alan Stern
--- a/drivers/usb/core/message.c.orig Fri Oct 24 13:10:05 2003
+++ b/drivers/usb/core/message.c
to the locations in the usb_host_config-interface[] array and
telling them they should use usb_ifnum_to_if().
Lauri, can you try this out and see if it helps with your prism2_usb?
Alan Stern
= drivers/usb/core/config.c 1.28 vs edited =
--- 1.28/drivers/usb/core/config.c Fri Sep 26 12:37:44 2003
with a pointer to a function that does nothing in some place like
lib/kobject.c:kset_init(). But I don't pretend to understand the details
of kobjects and such well enough to really track this down. Maybe you
can.
Alan Stern
---
This SF.net email
. But at least we're no worse off than we
were before, so things that used to work before the config.c alterations
should now work again.
Alan Stern
---
This SF.net email is sponsored by: The SF.net Donation Program.
Do you like what SourceForge.net
the possibility of adding a no-stall option to the
storage gadget, but it seemed like such an obscure sort of thing that
nobody would ever want to have to worry about it.
Are you quite sure there's no way to halt endpoints sensibly on your UDC?
Alan Stern
that to
limit its uses pretty severely.
Alan Stern
---
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU
vendor-specific message, in addition
to simply sending a Clear Feature command. You have to wonder why they
designed their controller that way.
This doesn't bode well for the SuperH's ability to cope with flash BBB.
Alan Stern
list can enlighten us. As far as I can tell, the host
number is simply incremented every time a new host, of whatever sort, is
added. The numbers never get reused.
Alan Stern
---
This SF.net email is sponsored by: SF.net Giveback Program
with
list_del_init().
Alan Stern
On Wed, 29 Oct 2003, Daniel Dorau wrote:
Hello,
I have an Oops here on Linux 2.6.0test8. Hardware is ThinkPad X31, USB
2.0 hub connected. There was no device connected to that hub and no
other device connected to the ThinkPad.
After I booted Linux, I waited
On Wed, 29 Oct 2003, Pete Zaitcev wrote:
From: Alan Stern [EMAIL PROTECTED]
Date: Wed, 29 Oct 2003 16:01:06 -0500 (EST)
+ spin_lock(hub_event_lock);
+ hub-urb_active = 0;
+ if (hub-urb_complete) {/* disconnect or rmmod */
+ complete(hub-urb_complete
CAN_STALL_CONTROL_OUT --
I've decided that doesn't need to be a compile-time option. Also, I'm
about to implement non-stalling BBB transfers, but it won't be called
PAD_SHORT_REPLIES. It will be called NO_BULK_STALL, so please rename
that #define.
Alan Stern
On Wed, 29 Oct 2003, Greg KH wrote:
On Mon, Oct 27, 2003 at 11:10:22AM -0500, Alan Stern wrote:
This patch makes config.c more liberal about the sorts of interface
numbering it will accept when reading interface descriptors. The current
code only allows interfaces numbered 0
On Wed, 29 Oct 2003, Greg KH wrote:
On Wed, Oct 29, 2003 at 04:01:06PM -0500, Alan Stern wrote:
This patch should fix the problem reported below by Daniel Dorau. The
oops was caused by inadequate synchronization between khubd and
hub_disconnect(). The hub interface-data pointer
(). It's nothing more than a minor optimization.
Alan Stern
= hub.c 1.123 vs edited =
--- 1.123/drivers/usb/core/hub.cMon Sep 22 12:37:50 2003
+++ edited/drivers/usb/core/hub.c Wed Oct 29 15:51:32 2003
@@ -126,7 +126,6 @@
static void hub_irq(struct urb *urb, struct pt_regs *regs
completion routine has finished. This patch can wait until after
2.6.0-final.
Alan Stern
= hub.c 1.123 vs edited =
--- 1.123/drivers/usb/core/hub.cMon Sep 22 12:37:50 2003
+++ edited/drivers/usb/core/hub.c Wed Oct 29 15:51:32 2003
@@ -128,11 +128,18 @@
struct usb_hub *hub
know to whom. Maybe someone on
the linux-kernel mailing list can help.
Alan Stern
---
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE
-current limiting.
Alan Stern
---
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http
On Tue, 4 Nov 2003, Jens Axboe wrote:
On Sat, Nov 01 2003, Alan Stern wrote:
There's no need. The output from that diagnostic is definitive -- this
isn't a USB problem. It's got to be a problem higher up, maybe in the
SCSI layer but more likely in the block layer or the file system
value when the reset is over. This fixes
that problem.
Alan Stern
= hub.c 1.123 vs edited =
--- 1.123/drivers/usb/core/hub.cMon Sep 22 12:37:50 2003
+++ edited/drivers/usb/core/hub.c Tue Nov 4 15:55:56 2003
@@ -1260,6 +1260,7 @@
kfree(descriptor
On Tue, 4 Nov 2003, Luke Kenneth Casson Leighton wrote:
It was added, and just once. I don't remember in what release, so it's
possible that in the original reply I should have said has been
incorporated in the current release.
Alan Stern
it was added due to someone posting i
will be interested in fixing it.
Alan Stern
---
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http
On Wed, 5 Nov 2003, Jens Axboe wrote:
On Tue, Nov 04 2003, Alan Stern wrote:
1. No, the sg entry was DMA-mapped previously and then unmapped.
The problem Nicholas encountered is an oops that occurs later during a
memcpy, not during a DMA operation. Apparently the page is not locked
On Wed, 5 Nov 2003, Johannes Erdfelt wrote:
On Wed, Nov 05, 2003, Alan Stern [EMAIL PROTECTED] wrote:
On Tue, 4 Nov 2003, Prageeth wrote:
thanks for the reply.
after the timeout, if i call usb_clear_halt(), it
works fine. is there any better method?
am suspecting some D0/D1
that they may not be located in mapped memory.
So I will need to learn the proper way of doing that. Is it as simple as
calling page_address(), and if the result is 0 then calling kmap()
followed by kunmap()?
Alan Stern
---
This SF.net email
think about implementing that change to have the
response checker retry when it gets ILLEGAL REQUEST from a
TEST-UNIT-READY?
Alan Stern
---
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more
usual fake
response. That would remove the need to have a special entry in
unusual_devs.h, which would be a Good Thing since lots of USB devices
share this particular flaw.
Alan Stern
---
This SF.net email is sponsored by: SF.net Giveback
communications problem.
Alan Stern
---
This SF.Net email sponsored by: ApacheCon 2003,
16-19 November in Las Vegas. Learn firsthand the latest
developments in Apache, PHP, Perl, XML, Java, MySQL,
WebDAV, and more! http://www.apachecon.com
On Fri, 7 Nov 2003, Greg KH wrote:
On Tue, Nov 04, 2003 at 04:52:05PM -0500, Alan Stern wrote:
Greg and all:
(I've lost track of patches that have been submitted in the last few
weeks, so it's possible that something incorporating this change is
already somewhere in the queue
Patrick:
For a usb-storage debugging trace of what appears to be exactly the same
problem, look at
http://bugme.osdl.org/show_bug.cgi?id=1501
Alan Stern
---
This SF.Net email sponsored by: ApacheCon 2003,
16-19 November in Las Vegas. Learn
-device information saying not
to send the MODE-SENSE commands at all.
I don't see any other way of coping. Even trying to send a command and
then trying to recover if it fails is not a viable approach if recovery
requires the user to cycle the power on the device (or to unplug its
cable).
Alan
protocols the device doesn't tell us how many LUNs it has, and
the only way to find out is by probing all of them and seeing which ones
respond.
Alan Stern
---
This SF.Net email sponsored by: ApacheCon 2003,
16-19 November in Las Vegas. Learn
On Sat, 8 Nov 2003, Patrick Mansfield wrote:
On Sat, Nov 08, 2003 at 11:28:37AM -0500, Alan Stern wrote:
The fake sense is a compromise. It lets us give a clear indication to
the higher layers that something is wrong and asks them not to send the
same command again. But it doesn't do
allocated in high memory.
There's a whole bunch of similar things in usb-storage that I'll have to
fix, however it seemed worth bringing this to your attention.
Alan Stern
---
This SF.Net email sponsored by: ApacheCon 2003,
16-19 November in Las
On Mon, 10 Nov 2003, Patrick Mansfield wrote:
On Sat, Nov 08, 2003 at 10:47:26PM -0500, Alan Stern wrote:
For CB and CBI devices, babble causes a DID_ERROR return. For Bulk-only
it causes a Check-Condition status to be returned along with Invalid
Command sense data. Like I said
On Mon, 10 Nov 2003, Patrick Mansfield wrote:
On Mon, Nov 10, 2003 at 01:46:44PM -0500, Alan Stern wrote:
On Mon, 10 Nov 2003, Patrick Mansfield wrote:
How could anyone attempt to find out why the reset failed? The only
externally visible state is the device's response to incoming USB
in some UHCI controllers.
Alan Stern
---
This SF.Net email sponsored by: ApacheCon 2003,
16-19 November in Las Vegas. Learn firsthand the latest
developments in Apache, PHP, Perl, XML, Java, MySQL,
WebDAV, and more! http://www.apachecon.com
to see more information, edit the source file for your HCD to
leave DEBUG and dbg defined.
Alan Stern
---
This SF.Net email sponsored by: ApacheCon 2003,
16-19 November in Las Vegas. Learn firsthand the latest
developments in Apache, PHP, Perl
familiar with the EHCI controller may be able to
suggest more things to try.
Alan Stern
---
This SF.Net email sponsored by: ApacheCon 2003,
16-19 November in Las Vegas. Learn firsthand the latest
developments in Apache, PHP, Perl, XML, Java
it? If so, does anyone have any
helpful hints as to what might be going on here?
You certainly should be able to reuse it. What version of Linux and which
host controller driver are you using? If you aren't using 2.6, try it out
and see if it works any better.
Alan Stern
401 - 500 of 6192 matches
Mail list logo
