On Wed, Jun 23, 2004 at 09:59:31AM -0400, Alan Stern wrote:
> On Tue, 22 Jun 2004, Tommy Faasen wrote:


I tried the patch, unfortunatley it didn't work, the joystick got
detected ok however the wifi stick didn't, I only tested with the
descriptor patch..

Output below

uhci_hcd 0000:00:07.2: port 2 portsc 0093
hub 1-0:1.0: port 2, status 0101, change 0001, 12 Mb/s
hub 1-0:1.0: debounce: port 2: delay 100ms stable 4 status 0x101
usb 1-2: new full speed USB device using address 3
uhci_hcd 0000:00:07.2: uhci_result_control: failed with status 440000
[d3058240] link (130581e2) element (16d1f040)
  0: [d6d1f040] link (16d1f080) e0 Stalled CRC/Timeo Length=7 MaxLen=7
  DT0 EndPt=0 Dev=0, PID=2d(SETUP) (buf=26d55388)
    1: [d6d1f080] link (16d1f0c0) e3 SPD Active Length=0 MaxLen=7 DT1
    EndPt=0 Dev=0, PID=69(IN) (buf=273ddf14)
      2: [d6d1f0c0] link (00000001) e3 IOC Active Length=0 MaxLen=7ff
      DT1 EndPt=0 Dev=0, PID=e1(OUT) (buf=00000000)

      uhci_hcd 0000:00:07.2: uhci_result_control: failed with status
      440000
      [d3058240] link (130581e2) element (16d1f040)
        0: [d6d1f040] link (16d1f080) e0 Stalled CRC/Timeo Length=7
        MaxLen=7 DT0 EndPt=0 Dev=0, PID=2d(SETUP) (buf=26d6afa8)
          1: [d6d1f080] link (00000001) e3 IOC Active Length=0
          MaxLen=7ff DT1 EndPt=0 Dev=0, PID=69(IN) (buf=00000000)

          uhci_hcd 0000:00:07.2: uhci_result_control: failed with status
          440000
          [d3058240] link (130581e2) element (16d1f040)
            0: [d6d1f040] link (16d1f080) e0 Stalled CRC/Timeo Length=7
            MaxLen=7 DT0 EndPt=0 Dev=0, PID=2d(SETUP) (buf=26d6a928)
              1: [d6d1f080] link (00000001) e3 IOC Active Length=0
              MaxLen=7ff DT1 EndPt=0 Dev=0, PID=69(IN) (buf=00000000)

              usb 1-2: device not accepting address 3, error -71
              usb 1-2: new full speed USB device using address 4
              uhci_hcd 0000:00:07.2: uhci_result_control: failed with
              status 440000
              [d3058240] link (130581e2) element (16d1f040)
                0: [d6d1f040] link (16d1f080) e0 Stalled CRC/Timeo
                Length=7 MaxLen=7 DT0 EndPt=0 Dev=0, PID=2d(SETUP)
                (buf=0c8efe28)
                  1: [d6d1f080] link (16d1f0c0) e3 SPD Active Length=0
                  MaxLen=7 DT1 EndPt=0 Dev=0, PID=69(IN) (buf=273ddf14)
                    2: [d6d1f0c0] link (00000001) e3 IOC Active Length=0
                    MaxLen=7ff DT1 EndPt=0 Dev=0, PID=e1(OUT)
                    (buf=00000000)

                    uhci_hcd 0000:00:07.2: uhci_result_control: failed
                    with status 440000
                    [d3058240] link (130581e2) element (16d1f040)
                      0: [d6d1f040] link (16d1f080) e0 Stalled CRC/Timeo
                      Length=7 MaxLen=7 DT0 EndPt=0 Dev=0, PID=2d(SETUP)
                      (buf=12168528)
                        1: [d6d1f080] link (00000001) e3 IOC Active
                        Length=0 MaxLen=7ff DT1 EndPt=0 Dev=0,
                        PID=69(IN) (buf=00000000)

                        uhci_hcd 0000:00:07.2: uhci_result_control:
                        failed with status 440000
                        [d3058240] link (130581e2) element (16d1f040)
                          0: [d6d1f040] link (16d1f080) e0 Stalled
                          CRC/Timeo Length=7 MaxLen=7 DT0 EndPt=0 Dev=0,
                          PID=2d(SETUP) (buf=26d6a288)
                            1: [d6d1f080] link (00000001) e3 IOC Active
                            Length=0 MaxLen=7ff DT1 EndPt=0 Dev=0,
                            PID=69(IN) (buf=00000000)

                            usb 1-2: device not accepting address 4,
                            error -71
> 
> > >I don't understand -- if the stick is known to need to transfer a
> > >descriptor before setting its address, how come it works on machine 2 when
> > >you set the address first?
> > >
> > >  
> > >
> > Several people indicated that they needed that patch before getting the 
> > stick to work, I guess that intel/via hardware is the most common. A 
> > person on the forum uses an intel board with the patch to get it to 
> > work. So I guess it is indeed needed, I can't explain why, nor am I 
> > aware of differences between uhci and ohci except for the fact that I 
> > read that ohci does more in hardware.
> 
> Yes, the differences are internal.  As far as the bus communication goes, 
> the two types of controller should be pretty much the same.
> 
> You might try using the patch below, both with and without the 
> broken-descriptor-fetch patch.  This is just a shot in the dark, but maybe 
> it will help.  In technical terms, the patch makes full-speed bandwidth 
> reclamation apply only to bulk transfers, not control transfers.
> 
> Alan Stern
> 
> 
> ===== drivers/usb/host/uhci-hcd.c 1.114 vs edited =====
> --- 1.114/drivers/usb/host/uhci-hcd.c Mon Jun 21 12:58:46 2004
> +++ edited/drivers/usb/host/uhci-hcd.c        Wed Jun 23 09:56:08 2004
> @@ -683,7 +683,7 @@
>       if ((!(urb->transfer_flags & URB_NO_FSBR)) && !urbp->fsbr) {
>               urbp->fsbr = 1;
>               if (!uhci->fsbr++ && !uhci->fsbrtimeout)
> -                     uhci->skel_term_qh->link = 
> cpu_to_le32(uhci->skel_fs_control_qh->dma_handle) | UHCI_PTR_QH;
> +                     uhci->skel_term_qh->link = 
> cpu_to_le32(uhci->skel_bulk_qh->dma_handle) | UHCI_PTR_QH;
>       }
>  }
>  


-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel

Reply via email to