Re: [edk2] Driver Health Protocol, UI interaction and Intel DQ77MK vs. OVMF

2015-10-09 Thread Laszlo Ersek
On 10/09/15 05:04, Ni, Ruiyu wrote:
> On 2015-10-08 4:59, Bruce Cran wrote:
>> I have a controller which implements the Driver Health Protocol. Under
>> OVMF (built from latest edk2 master), when the controller isn't healthy
>> I can go into the 'Device Manager' menu, click the 'Some drivers are not
>> healthy' entry and on clicking the unhealthy controller it gets repaired.
>>
>> I'm wondering if anyone knows if this is recent behavior or if a bug was
>> fixed, since on my Intel DQ77MK system I have a similar menu, except
>> labeled "TPV EFI Device Manager" - but when I click the "Some drivers
>> are not healthy" item the screen just refreshes back to the same page
>> and nothing happens.
>>
> The OVMF behavior exists for a quite long time, like several years. I
> don't know why the DQ77MK system behaves like that.
>> I had also expected that if I selected a boot item that resides on the
>> unhealthy controller, the repair operation would get invoked and upon it
>> returning a healthy status the OS would boot. But that doesn't seem to
>> be the case.
>>
> OVMF used the old IntelFrameworkModulePkg/BDS.
> The new MdeModulePkg/BDS automatically invokes the reparation upon boot.
> I did a draft patch
> (http://article.gmane.org/gmane.comp.bios.edk2.devel/759) but do not
> have time to edit it to follow the review comments.
> I may not have time to do it in this year. If it's urgent to you, you
> can try this draft patch. It will be great if you can help to edit the
> patch and get it reviewed and checked in to the OVMF Pkg.

Thanks for the info, Ray. Perhaps I'll find the time to pick up that
patch myself. Regarding the individual (numbered) comments that I made
there: I can clearly fix them up. But, the main problem I had with that
patch is that there was a sequence of hunks that were completely
impenetrable to me. I'm unsure if I could "untangle" those.

Anyway, as I said above, thanks for the info -- it's great to know that
you haven't abandoned that patch series, just have more pressing
developments to deal with.

Cheers!
Laszlo


>> Can anyone tell me what I'm misunderstanding please?
>>
> 
> ___
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel

___
edk2-devel mailing list
edk2-devel@lists.01.org
https://lists.01.org/mailman/listinfo/edk2-devel


Re: [edk2] Driver Health Protocol, UI interaction and Intel DQ77MK vs. OVMF

2015-10-08 Thread Bruce Cran

On 10/8/15 9:04 PM, Ni, Ruiyu wrote:


OVMF used the old IntelFrameworkModulePkg/BDS.
The new MdeModulePkg/BDS automatically invokes the reparation upon boot.
I did a draft patch
(http://article.gmane.org/gmane.comp.bios.edk2.devel/759) but do not
have time to edit it to follow the review comments.
I may not have time to do it in this year. If it's urgent to you, you
can try this draft patch. It will be great if you can help to edit the
patch and get it reviewed and checked in to the OVMF Pkg.


Ah, thanks!
So currently if a device is required to boot, I guess the driver would 
need to automatically initiate the repair operation during the load 
process?   The card I'm working with is unfortunately rather easy to get 
into a state where a repair is needed; so it sounds as though I might 
need to wait until UEFI 2.6 or so until it will be safe to assume that 
the platform will automatically initiate a repair?


--
Bruce
___
edk2-devel mailing list
edk2-devel@lists.01.org
https://lists.01.org/mailman/listinfo/edk2-devel


[edk2] Driver Health Protocol, UI interaction and Intel DQ77MK vs. OVMF

2015-10-07 Thread Bruce Cran
I have a controller which implements the Driver Health Protocol. Under 
OVMF (built from latest edk2 master), when the controller isn't healthy 
I can go into the 'Device Manager' menu, click the 'Some drivers are not 
healthy' entry and on clicking the unhealthy controller it gets repaired.


I'm wondering if anyone knows if this is recent behavior or if a bug was 
fixed, since on my Intel DQ77MK system I have a similar menu, except 
labeled "TPV EFI Device Manager" - but when I click the "Some drivers 
are not healthy" item the screen just refreshes back to the same page 
and nothing happens.


I had also expected that if I selected a boot item that resides on the 
unhealthy controller, the repair operation would get invoked and upon it 
returning a healthy status the OS would boot. But that doesn't seem to 
be the case.


Can anyone tell me what I'm misunderstanding please?

--
Bruce
___
edk2-devel mailing list
edk2-devel@lists.01.org
https://lists.01.org/mailman/listinfo/edk2-devel