A bit late to the party xD but if I followed along correctly shouldn't the buffer in the print number function be size 12 because if the integer turns out to be -2,147,483,648 that is 11 characters without the null termination but 12 would include the null. Probably won't show up in more than half the use cases as a bug so thought I would bring it up preemptively.
It should be 12 yes, to handle the null byte. Otherwise can get the length in digits and make a length specifier for printf, .*s or $1 or similar. I expanded the buffers later on to char[24], int64_t is around 21 or 22 with the sign character and a null byte.
I've already compiled the example from the first video and running on a hardware, It's work as same as the version on Qemu, thanks for this videos series. With some little modifications all process can made on a Raspberry Pi, I have to use a cross compiler and run the Write_GPT.exe on my laptop, but I think use wine on Raspberry pi could do the same results, I had problems with the ID to boot again on my laptop after use UEFI-Shell, I got a old motherboard with UEFI to test without fear to break something
Hi, I am new to your channel and i like them. Can u tell me where to start? I have experience in C programming. But not that much low level development experience. I am an Android developer.
Where to start with UEFI? Low level development? It's a lot of reading and programming to a spec, or finding examples and adapting them to your understanding and needs. Start off simple, get some input and print something, and go from there; input, graphics, advanced processing, drivers, emulation, embedded, whatever you want to do. Generally, project based learning works well for me, I need a reason and actionable goals to be motivated, I can't study for the sake of studying. For UEFI I tried to cover how to start with the intro video in this playlist: ua-cam.com/video/t3iwBQg_Gik/v-deo.html You mainly need an emulator (QEMU/OVMF firmware), C compiler, and documentation uefi.org/specs/UEFI/2.10/
A bit late to the party xD but if I followed along correctly shouldn't the buffer in the print number function be size 12 because if the integer turns out to be -2,147,483,648 that is 11 characters without the null termination but 12 would include the null. Probably won't show up in more than half the use cases as a bug so thought I would bring it up preemptively.
It should be 12 yes, to handle the null byte. Otherwise can get the length in digits and make a length specifier for printf, .*s or $1 or similar.
I expanded the buffers later on to char[24], int64_t is around 21 or 22 with the sign character and a null byte.
I've already compiled the example from the first video and running on a hardware, It's work as same as the version on Qemu, thanks for this videos series. With some little modifications all process can made on a Raspberry Pi, I have to use a cross compiler and run the Write_GPT.exe on my laptop, but I think use wine on Raspberry pi could do the same results, I had problems with the ID to boot again on my laptop after use UEFI-Shell, I got a old motherboard with UEFI to test without fear to break something
I finish to code this chapter, I am follow the series, thank you for your effort and gratitude to post this kind of information
Dude did the "giggity" 💀
Sir, this is a moai house 🗿
Hi, I am new to your channel and i like them. Can u tell me where to start? I have experience in C programming. But not that much low level development experience. I am an Android developer.
Where to start with UEFI? Low level development?
It's a lot of reading and programming to a spec, or finding examples and adapting them to your understanding and needs.
Start off simple, get some input and print something, and go from there; input, graphics, advanced processing, drivers, emulation, embedded, whatever you want to do.
Generally, project based learning works well for me, I need a reason and actionable goals to be motivated, I can't study for the sake of studying.
For UEFI I tried to cover how to start with the intro video in this playlist: ua-cam.com/video/t3iwBQg_Gik/v-deo.html
You mainly need an emulator (QEMU/OVMF firmware), C compiler, and documentation uefi.org/specs/UEFI/2.10/