On Thu, Jan 17, 2019 at 07:58:17AM +0100, Heinrich Schuchardt wrote:
> On 1/17/19 6:33 AM, AKASHI Takahiro wrote:
> > You raised a couple of questions to me.
> >
> > On Tue, Jan 15, 2019 at 04:41:08AM +0100, Heinrich Schuchardt wrote:
> >> On 1/15/19 3:55 AM, AKASHI Takahiro wrote:
> >>> This new
On 1/17/19 6:33 AM, AKASHI Takahiro wrote:
> You raised a couple of questions to me.
>
> On Tue, Jan 15, 2019 at 04:41:08AM +0100, Heinrich Schuchardt wrote:
>> On 1/15/19 3:55 AM, AKASHI Takahiro wrote:
>>> This new field will be shown as a driver's name in "efitool drivers"
>>> command.
>>
>>
You raised a couple of questions to me.
On Tue, Jan 15, 2019 at 04:41:08AM +0100, Heinrich Schuchardt wrote:
> On 1/15/19 3:55 AM, AKASHI Takahiro wrote:
> > This new field will be shown as a driver's name in "efitool drivers"
> > command.
>
> We can have drivers supplied by U-Boot
I assume
On 1/15/19 3:55 AM, AKASHI Takahiro wrote:
> This new field will be shown as a driver's name in "efitool drivers"
> command.
We can have drivers supplied by U-Boot and drivers supplied by an EFI
binary that we recently installed via the bootefi command.
A driver installed via the bootefi command
This new field will be shown as a driver's name in "efitool drivers"
command.
Signed-off-by: AKASHI Takahiro
---
include/efi_driver.h| 1 +
lib/efi_driver/efi_uclass.c | 1 +
2 files changed, 2 insertions(+)
diff --git a/include/efi_driver.h b/include/efi_driver.h
index
5 matches
Mail list logo