So, being the clueless boi I am, I consulted Wikipedia for the basics of a framebuffer. It says there are three common ways of doing it, and the attached image is the list.
I know the first and last ones but what is a port command?
The hell's a port command?
-
CheeseBees
- Posts: 22
- Joined: Mon Nov 19, 2018 12:13 pm
- Libera.chat IRC: WhatIsThis
The hell's a port command?
- Attachments
-
- Mitchell Barnes the Confused Idiot
17 years old and programming assembly
“If you're going to tell me to give up then you're wasting time that you could be using to help someone else”
“Assembly is more readable and easy to use than c. Change my mind”
17 years old and programming assembly
“If you're going to tell me to give up then you're wasting time that you could be using to help someone else”
“Assembly is more readable and easy to use than c. Change my mind”
Re: The hell's a port command?
It probably refers to the I/O port address space, which you can access with the OUT instruction on x86:
https://c9x.me/x86/html/file_module_x86_id_222.html
https://c9x.me/x86/html/file_module_x86_id_222.html
-
Octocontrabass
- Member
- Posts: 5586
- Joined: Mon Mar 25, 2013 7:01 pm
Re: The hell's a port command?
It refers to systems where the CPU can't directly address the frame buffer at all. Instead, you access it through one or more "ports" where you can write commands and data. For example, you might write a command to address a particular pixel, then write some data to set a new value for that pixel.
It has nothing to do with x86-specific things like the I/O address space or IN/OUT instructions.
It has nothing to do with x86-specific things like the I/O address space or IN/OUT instructions.