All of your questions are answered in the Wiki. Try clicking the link at the top of the page that says "Got a question? - Search this first!".
But you can find Font rendering code here: http://wiki.osdev.org/Drawing_In_Protec ... awing_Text
Kernel Developing using UEFI Booloader
Re: Kernel Developing using UEFI Booloader
Project: OZone
Source: GitHub
Current Task: LIB/OBJ file support
"The more they overthink the plumbing, the easier it is to stop up the drain." - Montgomery Scott
Source: GitHub
Current Task: LIB/OBJ file support
"The more they overthink the plumbing, the easier it is to stop up the drain." - Montgomery Scott
-
Combuster
- Member
- Posts: 9301
- Joined: Wed Oct 18, 2006 3:45 am
- Libera.chat IRC: [com]buster
- Location: On the balcony, where I can actually keep 1½m distance
- Contact:
Re: Kernel Developing using UEFI Booloader
Prior to ExitBootServices, you can use the output protocol to render text. After that, you need to render text a pixel at a time.
Re: Kernel Developing using UEFI Booloader
I know of course, the point is that I want render text after I call exitbootservices. I have a pointer to the graphics buffer and can draw/put pixel at any location, so what would be the best method for drawing text?Combuster wrote:Prior to ExitBootServices, you can use the output protocol to render text. After that, you need to render text a pixel at a time.
Re: Kernel Developing using UEFI Booloader
Hi,
Beyond that; "best" needs to be defined. For best speed it'd be hard to improve on the optimised method on that same wiki page. For best quality (e.g. scalable vector fonts, proportional fonts, anti-aliasing, etc) things get much more complicated.
Cheers,
Brendan
The "Drawing in Protected Mode" wiki page (that you've been linked to twice now) contains a section called drawing text.albus95 wrote:I have a pointer to the graphics buffer and can draw/put pixel at any location, so what would be the best method for drawing text?
Beyond that; "best" needs to be defined. For best speed it'd be hard to improve on the optimised method on that same wiki page. For best quality (e.g. scalable vector fonts, proportional fonts, anti-aliasing, etc) things get much more complicated.
Cheers,
Brendan
For all things; perfection is, and will always remain, impossible to achieve in practice. However; by striving for perfection we create things that are as perfect as practically possible. Let the pursuit of perfection be our guide.
Re: Kernel Developing using UEFI Booloader
Linked twice about peotected mode but I AM NOT IN PROTECTED MODE! Read the thread.
Anyway i can write this buffer.
But any way i want some more general way so i can set the text width and color. It is more complex right?
Anyway i can write this buffer.
But any way i want some more general way so i can set the text width and color. It is more complex right?
-
Combuster
- Member
- Posts: 9301
- Joined: Wed Oct 18, 2006 3:45 am
- Libera.chat IRC: [com]buster
- Location: On the balcony, where I can actually keep 1½m distance
- Contact:
Re: Kernel Developing using UEFI Booloader
That doesn't mean that the information you need isn't in there.
And since you're so insistent about it, you hereby have a homework task to prove that you actually are.albus95 wrote:I AM NOT IN PROTECTED MODE! Read the thread.
Re: Kernel Developing using UEFI Booloader
albus95 wrote:Linked twice about peotected mode but I AM NOT IN PROTECTED MODE! Read the thread.
Anyway i can write this buffer.
But any way i want some more general way so i can set the text width and color. It is more complex right?
Protected mode and long mode are almost the same by the perspective you watch them.
If you want to use protected mode you have to put the CPU in that mode, if not keep the long mode.
If you like to implement basic font management (offline of course) you just need to convert the font in a "convenient" way (c array).
You can use a tool like bdf2c...
Try to use google anyway instead of asking stupid question