vice paths is done by the platform, I
> wouldn’t worry too much about that at this point.
>
> Cheers,
> Tom
>
> From: Kumar G mailto:kumarg27061...@gmail.com>>
> Sent: 08 June 2020 19:10
> To: Tomas Pilar mailto:tomas.pi...@arm.com>>
> Cc: devel@edk2.groups.io <mailto:deve
re it resides. The early chapters of the UEFI spec describe this
> process in more detail. Also, the enumeration of devices and creating the
> controller handles with low lever IO protocols and hardware device paths is
> done by the platform, I wouldn’t worry too much about that at this
: [edk2-devel] Device and driver
Thanks Tom,
I really appreciate your reply,
I didn't get 100% but I went through ~3K pages of UEFI specification.
I understand a bit of protocols and handles now.
Handle is an identifier on which some sort of function pointers (protocol in
UEFI world) are inst
ve to get stuck in and play
> around until you get comfortable with things. I appreciate that the
> paradigm is quite different to for example Linux, but there are (usually)
> quite good reasons for many of the differences. Cheers, Tom From:
> devel@edk2.groups.io > On Be
] Device and driver
Hi Edk2 expert folks,
I am starting on UEFI coming from Linux background,
In Linux,
There is clear identification of device and driver, platform code adds the
device into system and
later OS code binds driver for the same.
With UEFI driver writer guide, I am bit confused,
please
Hi Edk2 expert folks,
I am starting on UEFI coming from Linux background,
In Linux,
There is clear identification of device and driver, platform code adds the
device into system and
later OS code binds driver for the same.
With UEFI driver writer guide, I am bit confused,
please help me, how device
