On Tue, Oct 21, 2003 at 01:26:21PM +0100, Jon Wilson wrote:
>
> # This gives me the following in dmesg, and an oops (attached)
> hub 1-0:1.0: port 2, status 100, change 3, 12 Mb/s
> usb 1-2: USB disconnect, address 2
> usb 1-2: usb_disable_device nuking all URBs
> usb 1-2: unregistering interface
We are working on a Host Controller Driver for the onboard host
controller of the Renesas SH7760 chip (SH4 CPU). We are using the
2.4.21 kernel.
This controller is OHCI compatible but:
1. It is not PCI
2. It uses an 8Kb on-chip shared memory area rather than main memory
for descriptors a
On Tue, 21 Oct 2003, Greg KH wrote:
> > Hmm... The interface number fix means making adjustments to a number of
> > drivers. Here's the idea: Up to now the USB stack has supported the
> > notion, explicitly stated in the USB specification, that interface numbers
> > are 0-based array indexes
On Wed, 22 Oct 2003, Pedro Larroy wrote:
> Hi
>
>
> I experience aborts with external usb hd, that also pause all disk
> operations for some seconds.
>
> It doesn't happen with 2.4.21 kernel.
>
> Please tell me if I can do anything useful to debug the problem. I can use
> kgdb or other techniq
We are developing a new device that enumerates correctly under winXP, but it is not
working with linux.
With 2.6.0-test8 we are getting this output in dmesg:
hub 2-2:1.0: enabling power on all ports
hub 2-2:1.0: port 3, status 301, change 1, 1.5 Mb/s
hub 2-2:1.0: debounce: port 3: delay 10
Julian Back wrote:
We are working on a Host Controller Driver for the onboard host
controller of the Renesas SH7760 chip (SH4 CPU). We are using the
2.4.21 kernel.
This controller is OHCI compatible but:
1. It is not PCI
2. It uses an 8Kb on-chip shared memory area rather than main memory
Is it just me? I'm getting anywhere from 5 to 12 copies of any
message you post, Dave.
Every message or just that one? I've contacted my Internet Spam Provider
and reported the bug.
Looked to me like they had a broken server that kept retransmitting that
one message. And that they eventually f
usb-storage isn't very picky about the response at all... what exactly was
happening without the patch?
Matt
On Mon, Oct 20, 2003 at 04:42:56PM -0700, Stephen Hemminger wrote:
> This fixes the memory stick SCSI access for Sony Clie SJ33 with SanDisk
> memory stick. It worked in 2.4 because the u
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. Per
On Wed, 22 Oct 2003 10:37:28 -0700
Matthew Dharm <[EMAIL PROTECTED]> wrote:
> usb-storage isn't very picky about the response at all... what exactly was
> happening without the patch?
>
usb-storage: *** thread awakened.
usb-storage: Command INQUIRY (6 bytes)
usb-storage: 12 00 00 00 24 00
usb-s
Sari Connard wrote:
We are developing a new device that enumerates correctly under winXP, but it is not working with linux.
With 2.6.0-test8 we are getting this output in dmesg:
hub 2-2:1.0: enabling power on all ports
hub 2-2:1.0: port 3, status 301, change 1, 1.5 Mb/s
hub 2-2:1.0: debounc
On Wed, Oct 15, 2003 at 03:04:11PM -0400, Alan Stern wrote:
> 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 c
Stephen Hemminger wrote:
> On Wed, 22 Oct 2003 10:37:28 -0700
> Matthew Dharm <[EMAIL PROTECTED]> wrote:
>
>
>>usb-storage isn't very picky about the response at all... what exactly was
>>happening without the patch?
>>
>
>
> usb-storage: *** thread awakened.
> usb-storage: Command INQUIRY (6 b
Looking at this, I'm more tempted to remove the test for bType in the IRQ
-- this isn't the first device I've seen broken like this. It's using a
UFI-style CBI interrupt for a non-UFI device. This is, apparently, one of
many spec violations that windows silently ignores.
Stephen, what happens if
Greg KH wrote:
On Tue, Oct 21, 2003 at 01:26:21PM +0100, Jon Wilson wrote:
# This gives me the following in dmesg, and an oops (attached)
hub 1-0:1.0: port 2, status 100, change 3, 12 Mb/s
usb 1-2: USB disconnect, address 2
usb 1-2: usb_disable_device nuking all URBs
usb 1-2: unregistering inte
I've configured, built, and installed kernel 2.6.0-test8 (with one non-USB
patch to make test8 compile). I then followed the hints at
http://thomer.com/linux/migrate-to-2.6.html to get hotplugging to work, which
it seems to do for both a Sanyo Xacti-S1 camera and a Canon PowerShot A80
camera. But
On Wed, 22 Oct 2003, Jon Wilson wrote:
> Greg KH wrote:
>
> >On Tue, Oct 21, 2003 at 01:26:21PM +0100, Jon Wilson wrote:
> >
> >
> >># This gives me the following in dmesg, and an oops (attached)
> >>hub 1-0:1.0: port 2, status 100, change 3, 12 Mb/s
> >>usb 1-2: USB disconnect, address 2
> >>u
On Wed, 22 Oct 2003 12:11:18 -0700
Matthew Dharm <[EMAIL PROTECTED]> wrote:
> Looking at this, I'm more tempted to remove the test for bType in the IRQ
> -- this isn't the first device I've seen broken like this. It's using a
> UFI-style CBI interrupt for a non-UFI device. This is, apparently, o
I think this is the answer then -- if you clean up this patch, I'll bless
it for Greg to send on for 2.4/5/6
Matt
On Wed, Oct 22, 2003 at 03:03:40PM -0700, Stephen Hemminger wrote:
> On Wed, 22 Oct 2003 12:11:18 -0700
> Matthew Dharm <[EMAIL PROTECTED]> wrote:
>
> > Looking at this, I'm more tem
Nevermind. We resolved this problem because we had a bad chip.
Sari
We are developing a new device that enumerates correctly under winXP, but it is not
working with linux.
With 2.6.0-test8 we are getting this output in dmesg:
hub 2-2:1.0: enabling power on all ports
hub 2-2:1.0: port 3, st
Hi,
fighting with a storage deivce which babbles bady under certian error
contitions, I stumbled over the open issue with VIA Chips + Babble (they
freeze internally).
Somwhere along 2.5.15 the alternate uhci driver got a watchdog feature to
reanimate dead uhci's. The two 2.4 uhci's and the rem
Hi al,
I call usb_bulk_write to write data to usb printer, code as following:
usb_claim_interface(usbdev,0);
int fd_prt;
fd_prt = open("/tmp/printout", O_RDONLY);
if (fd_prt < 0) return -1;
int rtnvalue = 0;
int rtnwrite = 0;
On Tuesday 21 October 2003 12:47, David Brownell wrote:
>Richard Reich wrote:
>> I'm currently using test-8, with no patches. When I mount a usb
>> storage device using the EHCI driver I get about 128MB copied and
>> then one of the HT CPUs gets locked into a 100% IO wait. At least
>> this is wha
Alan Stern wrote:
Johannes and Phil, could you try the experiment of commenting out or
removing the entire UNUSUAL_DEV entry for device 0x07cf in unusual_devs.h?
It may turn out that it's not needed any more.
I'm happy to, but it will have to wait until this weekend.
--
Phil Dibowitz
24 matches
Mail list logo
