On 12/26/2012 09:56 PM, Alan Stern wrote:
This looks like a matter of getting modules to load in the right order.
Apparently your OHCI controller doesn't work right if the EHCI driver
isn't present. Before the troublesome commit, this meant ehci-hcd had
to be loaded before ohci-hcd. Now it
On Thu, 27 Dec 2012, Larry Finger wrote:
I could not do exactly the experiment that you wanted, as ehci-hcd was loaded
even though it was blacklisted. Rather than solve that problem, I generated a
kernel from just before commit adfa79d with ohci-hcd built in and ehci-hcd as
a
module.
On 12/27/2012 05:18 PM, Alan Stern wrote:
On Thu, 27 Dec 2012, Larry Finger wrote:
I could not do exactly the experiment that you wanted, as ehci-hcd was loaded
even though it was blacklisted. Rather than solve that problem, I generated a
kernel from just before commit adfa79d with ohci-hcd
On Tue, 25 Dec 2012, Larry Finger wrote:
On 12/25/2012 10:26 AM, Alan Stern wrote:
On Mon, 24 Dec 2012, Larry Finger wrote:
The problem has been bisected to commit adfa79d entitled USB: EHCI: make
ehci-pci a separate driver. The symptom is that my NVIDIA controller again
reverts to
On 12/26/2012 10:45 AM, Alan Stern wrote:
I see. Do you happen to have CONFIG_USB_EHCI_HCD=y and
CONFIG_USB_EHCI_PCI=m in your .config? If you do, try changing
EHCI_PCI to y.
No, they are both m. My configuration parameters with EHCI in them are
CONFIG_USB_ARCH_HAS_EHCI=y
On 12/26/2012 10:45 AM, Alan Stern wrote:
I see. Do you happen to have CONFIG_USB_EHCI_HCD=y and
CONFIG_USB_EHCI_PCI=m in your .config? If you do, try changing
EHCI_PCI to y.
One additional data point: When the EHCI and HCD parameters are set to y rather
than m as in the list that follows,
On Wed, 26 Dec 2012, Larry Finger wrote:
On 12/26/2012 10:45 AM, Alan Stern wrote:
I see. Do you happen to have CONFIG_USB_EHCI_HCD=y and
CONFIG_USB_EHCI_PCI=m in your .config? If you do, try changing
EHCI_PCI to y.
One additional data point: When the EHCI and HCD parameters are set
