From: Marco Gerards <mgerards@xs4all.nl>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Need for VBE helper functions?
Date: Mon, 26 Dec 2005 11:10:33 +0100 [thread overview]
Message-ID: <87wths88yu.fsf@xs4all.nl> (raw)
In-Reply-To: <43AF483C.2080102@nic.fi> (Vesa Jääskeläinen's message of "Mon, 26 Dec 2005 03:32:44 +0200")
Vesa Jääskeläinen <chaac@nic.fi> writes:
Hi Vesa,
> I have been making video driver for VBE and currently at beginning of
> that file there are codes for those VBE helpers defined in
> (include/grub/i386/pc/vbe.h). As I had some issues with mixing them with
> each other I renamed all kernel stubs like from grub_vbe_* to
> grub_vbe_bios_* so they cannot be easily mixed.
>
> I was thinking that is there a still need to have those helper functions
> at all there? If they will be there I will use them from driver code, if
> not, I will integrate the functionality to driver code. By integrating
> the code to driver it would make that driver file more easier to read,
> but then we lose option to use those helpers directly. One option is to
> move them elsewhere, but then there is a problem what is the module name
> and where.
So what you have now is some VBE functions and a video driver and you
are wondering if they should be merged? I think that shouldn't be
done because multiboot should also use VBE to switch video modes.
> I will update shortly (tomorrow most likely) wiki with results of the
> newest API design round. After I think it is correct I will concentrate
> on enhancing the terminal code to make use of newly added functionality.
Cool!
Thanks,
Marco
prev parent reply other threads:[~2005-12-26 10:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-26 1:32 Need for VBE helper functions? Vesa Jääskeläinen
2005-12-26 10:10 ` Marco Gerards [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wths88yu.fsf@xs4all.nl \
--to=mgerards@xs4all.nl \
--cc=grub-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.