31 ms·
A little HN story. Prompts are italicized > You open your browser to hacker news and find an article at the top of the page with the headline "Raspberry Pi 4 V
by bluehex 6y ago
A little HN story. Prompts are italicized
> You open your browser to hacker news and find an article at the top of the page with the headline "Raspberry Pi 4 V3DV graphics driver achieves Vulkan 1.0 conformance". You think to yourself:
"I can't believe I didn't know this before. This is going to be so much easier now!
> You immediately go grab your Raspberry Pi and plug it in...
You turn on your PC and get your Raspberry Pi ready. You power on the device and immediately you have a successful boot no issues from there. You navigate to the folder with the vk.
> "VK" you remember, was the directory where you were conducting your vulkan 1.0 driver tests, but now that full conformance has been announced you realize:
"Now I can start working on a vulkan 1.0 conforming game engine!!!" You copy and paste the contents of the folder you made in step 2 into a new folder called "Boom"
> You've been waiting to work on this for a while... You open a file called vk_1.c and begin typing in the code:
VK_ DECLARE_STATIC_DNS_FUNCTIONS;
VK_DECLARE_FORMAT_SIDES_IN_DEPTH_P3;
VK_DECLARE_SERIAL_BITMAP_TYPE;
VK_DECLARE_PATCHABLE_BUFFER_PIXELS;
VK_DECLARE_PATCHABLE_STENCIL_PIXEL;
VK_DECLARE_PATCHABLE_STENCIL_DIMENSIONS;
Vulkan is a very powerful graphics API, but it's probably one of the most cryptic, especially since they seem to be fond of using ambiguous names for things. You'll have to look up all these obscure APIs you're declaring at the beginning of the file.