Hooray, it works... minus 2 scenarios :(

With both Philips USB and Mushkin USB attached, and I perform a cold boot

1. YES - USB 3 & USB 3 - once each (Philips & Mushkin)

cbmem.yes.both.USB3.USB3.gz

2. NO - USB 3 & USB 3 - once each (Philips & Muskin) - but double
Philips showing

cbmem.yes.both.USB3.USB3.DoublePhilips.gz

3. YES - USB 3 & Type C - once each (Philips & Mushkin)

cbmem.yes.both.USB3.TypeC.gz

I can't get a double Philips to appear

4. YES - Type C & Type C - once each (Philips & Mushkin)

cbmem.yes.both.TypeC.TypeC.gz

5. NO - Type C & Type C - one Philiips & no Mushkin

I forgot to save

$ cbmem -c

and now can't replicate it. :(

When I do, I will post output.

Edward.

On Sun, Dec 13, 2015 at 7:53 PM, Kevin O'Connor <ke...@koconnor.net> wrote:
> On Sun, Dec 13, 2015 at 10:49:30AM +0000, edward wandasiewicz wrote:
>> With both the Philips USB and Mushkin USB plugged in on boot, I'm
>> still getting 4 different scenarios appearing.
>>
>> 1. Philips Only
>> 2. Mushkin Only
>> 3. Both recognised - listed once and once only
>> 4. Both recognised - Mushkin once, but the Philips listed twice
>>
>> I've attached
>>
>> $cbmem -c
>>
>> for each scenario
>
> Thanks.  It looks like the usb code wasn't waiting for USB3 devices to
> be "enabled" before trying to talk to them.  Can you pull down the
> "testing" branch again and retry?
>
> Also, the logs are quite large and they are exceeding the mailing list
> limits - going forward can you gzip the logs and attach them to your
> emails.
>
> -Kevin

Attachment: cbmem.yes.both.USB3.USB3.gz
Description: GNU Zip compressed data

Attachment: cbmem.yes.both.USB3.USB3.DoublePhilips.gz
Description: GNU Zip compressed data

Attachment: cbmem.yes.both.USB3.TypeC.gz
Description: GNU Zip compressed data

Attachment: cbmem.yes.both.TypeC.TypeC.gz
Description: GNU Zip compressed data

_______________________________________________
SeaBIOS mailing list
SeaBIOS@seabios.org
http://www.seabios.org/mailman/listinfo/seabios

Reply via email to