Co-worker keeps cursing in Spanish and then smacking the table.

When it happens I have 2 choices:

1. Keep suppressing the rage until I can't take it anymore and book a meeting room just to get away.

2. Ask him to keep it down, to which he replies sorry followed immediately by "can you take a look at this?", which turns into 20 mins of teaching him how to use google.

I'm one bad day away from taking a swing at him.

what catching bugs be like.. you end up smacking your PM

Management bought snacks for everyone. Great, more mouth noises.

So over the past few weeks I have been smacking my head against the table tying to solve my work problem and failing to... Today I spend a few hours at work not working and playing with code making something fun and easy. After this I go back to the headache and if my magic get something working.

So I got a mice, and arm for it and etc.

Figured out how to do some noise cancelling.

All good for some voice overs!

ON the downside I didn't realize how much smacking and noise I make just opening my mouth ... I'm like some sort of uncouth barbarian via audio.... not just video.

VESA is driving me crazy.

I'm trying to set my video mode via VESA functions which works, the QEMU window size changes, ton of more space.

Problem now however is that I have no idea where in the name of god the goddamn framebuffer starts.

Apparently it's address is located withing the mode info block which I have successfully queried and stored in ES:DI.

Problem now is getting this info block into my 32-bit kernel.

I tried smacking it on the stack which only produces hot garbage.

Essentially it goes like this

[...make sure pointer to block is stored within ES:DI...]

mov ebx, [ES:DI]

[Switch to 32 bit mode, ebx is not erased by doing so]

;Set up stack
mov ebp, 0x90000
mov esp, ebp

call kernel_main
jmp $

kernel_main takes this pointer as an argument, hence why I've pushed it onto stack:
main(uint32_t *ptr);

When I try accessing it however by doing the following:
vbe_mode_info_block* info_block = (vbe_mode_info_block)ptr;

And then try accessing the in the member 'framebuffer' using 'info_block->framebuffer' it's giving me hot garbage.

I'm probably doing something obvious wrong.
Frustrating.
I'm gonna try passing ES and DI seperately and converting them to a real mode address by doing addr = (ES*0x10)+DI;

MAYBE MAYBE MAYBE