Groups | Search | Server Info | Login | Register

Groups > comp.os.linux.hardware > #3620

Re: Intriguing issue

Show all headers | View raw

On 1/16/23 10:00, Eric Pozharski wrote:
> with <tq342s$f6$1@gioia.aioe.org> Andrew wrote:
>> Henrik Carlqvist wrote:
>>> On Sun, 15 Jan 2023 13:36:01 +0000, James H. Markowitz wrote:
> 
> *SKIP*
>>>> In the others, in which the diagnostic does appear, the ohci lines
>>>> are absent.
> *SKIP*
>>> Could it be that you connected the external USB hard drive to a
>>> USB1.1 port?
> *SKIP*
>> The USB2 specs were released in April 2000, how long would it have
>> taken before motherboards with 1.x were no longer being sold?
> 
> About a decade, apprently
> 
> % lsusb -t
> /:  Bus 07.Port 1: Dev 1, Class=root_hub, Driver=ohci_hcd/2p, 12M
> /:  Bus 06.Port 1: Dev 1, Class=root_hub, Driver=ohci_hcd/3p, 12M
> /:  Bus 05.Port 1: Dev 1, Class=root_hub, Driver=ohci_hcd/3p, 12M
> /:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=ohci_hcd/3p, 12M
>     |__ Port 1: Dev 3, If 0, Class=HID, Driver=usbhid, 1.5M
>     |__ Port 1: Dev 3, If 1, Class=HID, Driver=usbhid, 1.5M
> /:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=ohci_hcd/3p, 12M
> /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci_hcd/6p, 480M
>     |__ Port 2: Dev 2, If 0, Class=stor., Driver=usb-storage, 480M
> /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci_hcd/6p, 480M
>     |__ Port 1: Dev 2, If 0, Class=hub, Driver=hub/4p, 480M
> 
> When I've comprehended what that means I was shocked.  I repeat,
> SHOCKED.

Actually, that's just the way it worked back then.  EHCI didn't replace
OHCI/UHCI, it ran along side them.

From the Wikipedia "Host Controller Interface" article:

"Originally a PC providing high-speed ports had two controllers, one
handling low- and full-speed devices and the second handling high-speed
devices. Typically such a system had EHCI and either OHCI or UHCI drivers."

https://en.wikipedia.org/wiki/Host_controller_interface_(USB%2C_Firewire)#Enhanced_Host_Controller_Interface

Back to comp.os.linux.hardware | Previous | Next — Previous in thread | Next in thread | Find similar

Thread

Intriguing issue "James H. Markowitz" <noone@nowhere.net> - 2023-01-09 20:17 +0000
  Re: Intriguing issue Marco Moock <mo01@posteo.de> - 2023-01-09 21:36 +0100
  Re: Intriguing issue mjb@signal11.invalid (Mike) - 2023-01-10 20:57 +0000
  Re: Intriguing issue Theo <theom+news@chiark.greenend.org.uk> - 2023-01-11 22:23 +0000
    Re: Intriguing issue "David W. Hodgins" <dwhodgins@nomail.afraid.org> - 2023-01-11 18:31 -0500
      Re: Intriguing issue "James H. Markowitz" <noone@nowhere.net> - 2023-01-12 19:21 +0000
        Re: Intriguing issue "David W. Hodgins" <dwhodgins@nomail.afraid.org> - 2023-01-12 18:32 -0500
          Re: Intriguing issue "James H. Markowitz" <noone@nowhere.net> - 2023-01-13 15:03 +0000
            Re: Intriguing issue "David W. Hodgins" <dwhodgins@nomail.afraid.org> - 2023-01-13 16:23 -0500
      Re: Intriguing issue Theo <theom+news@chiark.greenend.org.uk> - 2023-01-13 12:51 +0000
  Re: Intriguing issue "James H. Markowitz" <noone@nowhere.net> - 2023-01-14 20:04 +0000
    Re: Intriguing issue Henrik Carlqvist <Henrik.Carlqvist@deadspam.com> - 2023-01-15 09:17 +0000
      Re: Intriguing issue "James H. Markowitz" <noone@nowhere.net> - 2023-01-15 13:36 +0000
        Re: Intriguing issue Henrik Carlqvist <Henrik.Carlqvist@deadspam.com> - 2023-01-16 07:14 +0000
          Re: Intriguing issue Andrew <Doug@hyperspace.vogon.gov> - 2023-01-16 10:06 +0100
            Re: Intriguing issue Eric Pozharski <whynot@pozharski.name> - 2023-01-16 15:00 +0000
              Re: Intriguing issue John-Paul Stewart <jpstewart@personalprojects.net> - 2023-01-16 15:28 -0500
            Re: Intriguing issue "Carlos E.R." <robin_listas@es.invalid> - 2023-01-16 20:47 +0100
              Re: Intriguing issue "David W. Hodgins" <dwhodgins@nomail.afraid.org> - 2023-01-16 17:08 -0500
      Re: Intriguing issue "Carlos E. R." <robin_listas@es.invalid> - 2024-11-08 13:57 +0100

csiph-web