Re: Not enough host controller resources for new device state

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sat, November 21, 2015 9:35 am, Peter Stuge wrote:
> Patrick Shirkey wrote:
>> > You essentially have to educate yourself on silicon level (ie. what
>> > hardware IP is being used in which consumer products) to sustain a
>> > dependency on 127 possible devices per bus.
>> >
>> > I guess you'll find that there are only very few xHCI IPs out there,
>> > probably just three or four. I wouldn't be surprised if they all have
>> > the same, or similar, limitations.
>>
>> Is there anything I can do at the system level to avoid disabling xHCI
>> at
>> the BIOS level?
>
> Unfortunately not. The number of supported devices is now very much
> hardwired in the host controller hardware. Each connected device
> requires its own set of registers in xHCI, so when there is a limit
> it is a hard limit.
>
>

That's a bit of a let down as it seems to make it even more difficult to
rely on USB for my specific use case in the future.

In case anyone else comes across this thread do you mind giving a little
more detail on why xHCI overrides EHCI and why it is not possible to
disable or work around xHCI at the system level?




--
Patrick Shirkey
Boost Hardware Ltd
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux Media]     [Linux Input]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Old Linux USB Devel Archive]

  Powered by Linux