All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrey Borzenkov <arvidjaar@mail.ru>
To: linux-hotplug@vger.kernel.org
Subject: Re: Warning! ehci_hcd should always be loaded before uhci_hcd and ohci_hcd
Date: Mon, 22 Feb 2010 07:30:19 +0000	[thread overview]
Message-ID: <201002221030.19671.arvidjaar@mail.ru> (raw)
In-Reply-To: <200811211554.17452.toralf.foerster@gmx.de>

[-- Attachment #1: Type: Text/Plain, Size: 1399 bytes --]

On Monday 22 of February 2010 10:00:53 Robby Workman wrote:
> On Mon, 22 Feb 2010 09:42:31 +0300
> 
> Andrey Borzenkov <arvidjaar@mail.ru> wrote:
> > ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
> > Warning! ehci_hcd should always be loaded before uhci_hcd and
> > ohci_hcd, not after
> > 
> > [snipped]
> > 
> > So my question is - is the warning still true? How serious problems
> > can result if uhci is loaded before ehci?
> > 
> > Does it make sense to workaround it in udev or may be trivial
> > 
> > install uhci_hcd mdprobe ehci_hcd; modprobe --ignore-install
> > uhci_hcd
> > 
> > would be enough?
> 
> That's basically what we did:
> 
> $ cat /etc/modprobe.d/usb-controller.conf
> # Make sure that ehci-hcd is always loaded before uhci-hci
> # # or ohci-hcd to prevent a kernel warning:
> install uhci-hcd /sbin/modprobe ehci-hcd ; /sbin/modprobe -i uhci-hcd
> install ohci-hcd /sbin/modprobe ehci-hcd ; /sbin/modprobe -i ohci-hcd
> 

The problem is this dependency strikes back in other places as well. 
E.g. I want to find out drivers for my USB keyboard to be loaded in 
initrd. Natural way is to walk up device tree collecting them - which 
leaves me with uhci (or ohci). Now I must manually do not forget to put 
in ehci, although strictly speaking I do not need it (in initrd) at all.

Kernel based solution would really be nice ...

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  parent reply	other threads:[~2010-02-22  7:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-21 14:54 Warning! ehci_hcd should always be loaded before uhci_hcd and ohci_hcd, not after Toralf Förster
2008-11-21 16:25 ` Warning! ehci_hcd should always be loaded before uhci_hcd and Greg KH
2008-11-21 16:25 ` Bryan Kadzban
2008-11-21 16:47 ` Warning! ehci_hcd should always be loaded before uhci_hcd and ohci_hcd, not after Toralf Förster
2008-11-21 17:35 ` Warning! ehci_hcd should always be loaded before uhci_hcd and Greg KH
2008-11-22  2:46 ` Bryan Kadzban
2010-02-22  6:42 ` Warning! ehci_hcd should always be loaded before uhci_hcd and ohci_hcd Andrey Borzenkov
2010-02-22  7:00 ` Warning! ehci_hcd should always be loaded before uhci_hcd and Robby Workman
2010-02-22  7:30 ` Andrey Borzenkov [this message]
2010-02-22 15:35 ` Alan Stern
2010-02-22 15:37 ` Alan Stern
2010-02-28 17:16 ` Pozsar Balazs
2010-02-28 21:46 ` Alan Stern

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201002221030.19671.arvidjaar@mail.ru \
    --to=arvidjaar@mail.ru \
    --cc=linux-hotplug@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.