my solution to the flakiness of EHCI on Haswell ChromeOS devices was to
route everything to the XHCI controller / use XHCI finalization
(CONFIG_FINALIZE_USB_ROUTE_XHCI=y), and to use Broadwell's XHCI init code.
Obv doesn't help if you need ECHI debug (eg), but perhaps a a slightly
different
I guess, Konstantin... My take on this investigation. ;-)
I recommend to you to apply to be deployed/employed with INTEL IOTG PED
directorate in USA (Chandler)... But not less than grade 9/10 (initial base
salary in USA perhaps $200K USD per annum). Everything else will be more
than insult.
And
On Wed, Oct 18, 2017 at 07:27:50PM -0400, [799] via coreboot wrote:
> I like that idea, I think I'll just choose a cheap one and in case it
> breaks I just use another one.
I've tried the really cheap ones and found that they do not work very
well at all. Even brand new this one required
No, unfortunately this option by itself doesn’t help.
I guess my minimal hammer is ‘noapictimer’
But I wonder how these 3 boot parameters (‘noapictimer’ ‘nolapic’ and
‘acpi=off’) separately help to solve my issue.
What part is wrong in ACPI and correct in MP-table? Maybe the problem is
we had a similar problem and we set
pci=nocrs
which means 'ignore what ACPI tells you and probe it again"
It's much less of a big hammer than 'acpi=off' :-)
On Thu, Oct 19, 2017 at 7:22 AM Аладышев Константин
wrote:
> I've found one more parameter that helps me boot
I've found one more parameter that helps me boot without USB problem:
'noapictimer'
-Original Message-
From: Аладышев Константин [mailto:aladys...@nicevt.ru]
Sent: Wednesday, October 18, 2017 3:58 PM
To: 'Julius Werner'
Cc: 'Coreboot'
Subject: Re: [coreboot] USB problem with
6 matches
Mail list logo