I have also noticed this delay and have through instrumenting code
have found that every block in the device gets read in. I never
checked if it was something in the df, filesystem, SCSI, or USB
subsystems that was causing this. I am usually doing df on USB
storage devices formated as FAT 32 w/ a
On 7/18/07, Alan Stern <[EMAIL PROTECTED]> wrote:
> On Wed, 18 Jul 2007, Branden Sletteland wrote:
>
> > Doesn't seem like anyone has implemented quirks for ehci controllers,
> > but this ability is setup for ohci controllers. Would it be best to
> > make one g
On 7/17/07, Alan Stern <[EMAIL PROTECTED]> wrote:
> On Tue, 17 Jul 2007, Branden Sletteland wrote:
>
> > This results in the device being detected as a Full speed device as
> > before. (Actually a High speed device plugged into a Full speed hub,
> > with warnings fr
On 7/17/07, Alan Stern <[EMAIL PROTECTED]> wrote:
> On Tue, 17 Jul 2007, Branden Sletteland wrote:
>
> > With that code added I just see the print out for each of the four
> > ports three times, and the device is not detected.
>
> Try this patch instead.
>
> Al
I was able to get my usb storage devices to be recognized as High
speed devices by commenting out these lines in ehci-hcd.c in a
2.6.21.5 kernel:
in function ehci_run:
hcd->uses_new_polling = 1;
in function ehci_irq:
if (pcd_status & STS_PCD)
usb_hcd_poll_rh_status(hcd);
Any
I went back and tried this power cycling method with a 2.6.21.5 kernel
and a 2.6.22 kernel with the same results as my 2.6.20.11 kernel with
the 2.6.21.5 drivers/usb/host directory. Now I just need to figure
out how to get the storage devices to come up as high speed devices
when they are powered
On 7/11/07, Branden Sletteland <[EMAIL PROTECTED]> wrote:
> On 7/11/07, Alan Stern <[EMAIL PROTECTED]> wrote:
> > On Wed, 11 Jul 2007, Branden Sletteland wrote:
> >
> > > None of these patches exhibited the problem. The third one couldn't
> > >
On 7/11/07, Alan Stern <[EMAIL PROTECTED]> wrote:
> On Wed, 11 Jul 2007, Branden Sletteland wrote:
>
> > None of these patches exhibited the problem. The third one couldn't
> > read the USB device descriptor, but the 4th patch fixed that.
> >
> > I no
On 7/11/07, Alan Stern <[EMAIL PROTECTED]> wrote:
> On Tue, 10 Jul 2007, Branden Sletteland wrote:
>
> > Just tried 2.6.21-rc1 and I get the same problem. Are there snap shots
> > before this?
> >
> > Attached is a dmesg dump from a 2.6.20.11 kernel on the same
Just tried 2.6.21-rc1 and I get the same problem. Are there snap shots
before this?
Attached is a dmesg dump from a 2.6.20.11 kernel on the same hardware config.
Branden
On 6/30/07, Alan Stern <[EMAIL PROTECTED]> wrote:
On Sat, 30 Jun 2007, Branden Sletteland wrote:
> Yes, we have b
wrote:
> On Fri, 29 Jun 2007, Branden Sletteland wrote:
>
> > On 6/28/07, Alan Stern <[EMAIL PROTECTED]> wrote:
> > > On Thu, 28 Jun 2007, Branden Sletteland wrote:
> > >
> > > > I am seeing an issue when going from kernel version 2.6.20.14 to
> >
On 6/28/07, Alan Stern <[EMAIL PROTECTED]> wrote:
On Thu, 28 Jun 2007, Branden Sletteland wrote:
> I am seeing an issue when going from kernel version 2.6.20.14 to
> 2.6.21 through 2.6.21.5 were my high speed devices are only being
> recognized as full speed devices, with er
I am seeing an issue when going from kernel version 2.6.20.14 to
2.6.21 through 2.6.21.5 were my high speed devices are only being
recognized as full speed devices, with error output on a 2.6.21 kernel
stating:
usb 3-1: new full speed USB device using ohci_hcd and address 11
usb 3-1: not running a
13 matches
Mail list logo
