All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Vesa Jääskeläinen" <chaac@nic.fi>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: vesafb terminal for testing.
Date: Mon, 15 Aug 2005 18:52:56 +0300	[thread overview]
Message-ID: <4300BA58.1010706@nic.fi> (raw)
In-Reply-To: <200508150019.30101.okuji@enbug.org>

Yoshinori K. Okuji wrote:
> On Sunday 14 August 2005 23:48, Vesa Jääskeläinen wrote:
>> As far I know, GRUB 2 doesn't support dynamic loading of function entry
>> points, instead there are only two predefined entry points that can be
>> called from modules so there has to be some interface for those if they
>> are not implemented in kernel level. And it would be bad to duplicate
>> that code in several places.
> 
> Nope. GRUB 2 supports real dynamic loading. Entry points are used only when we 
> want to allow symbols to be missing. So you need to implement code in the 
> kernel only if it requires real mode or it is a critical function.

Impressive I must say :)

It was even transparent.

Now only problem is what is the best location for vbe.c that would
contain helper functions for modules that needs VBE. Currently I have it
in term/i386/pc/vbe.c but is there better location for this? And is
GRUB_MOD_INIT and GRUB_MOD_FINI mandory as I do not have need for those
in this module? Seems to work without them.

Is the file include/grub/i386/pc/vbe.h correct place to put function
prototypes?

Is directory commands/i386/pc/ correct place for commands vbe_list_modes
and vbe_test?

Thanks,
Vesa Jääskeläinen



  reply	other threads:[~2005-08-15 15:59 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-14 11:52 vesafb terminal for testing Vesa Jääskeläinen
2005-08-14 14:48 ` Yoshinori K. Okuji
2005-08-14 15:45   ` Vesa Jääskeläinen
2005-08-14 16:47     ` Vladimir Serbinenko
2005-08-14 19:25       ` Yoshinori K. Okuji
2005-08-15 15:23         ` Vincent Pelletier
2005-08-15 16:06           ` Vladimir Serbinenko
2005-08-15 17:02             ` Marco Gerards
2005-08-15 17:19             ` Yoshinori K. Okuji
2005-08-15 17:41               ` Marco Gerards
2005-08-15 18:55                 ` Yoshinori K. Okuji
2005-08-15 20:54                   ` Marco Gerards
2005-08-15 21:44               ` Vesa Jääskeläinen
2005-08-16  6:47               ` Vincent Pelletier
2005-08-16 10:20                 ` Marco Gerards
2005-08-15 17:07         ` Marco Gerards
2005-08-16  6:54           ` Vincent Pelletier
2005-08-14 21:48       ` Vesa Jääskeläinen
2005-08-14 22:19         ` Yoshinori K. Okuji
2005-08-15 15:52           ` Vesa Jääskeläinen [this message]
2005-08-15 16:13             ` Yoshinori K. Okuji
2005-08-15 15:42         ` Vladimir Serbinenko
2005-08-19  0:48   ` Yoshinori K. Okuji
2005-09-18 21:03     ` Vesa Jääskeläinen
2005-09-19 19:00       ` Yoshinori K. Okuji
2005-09-19 23:11         ` Vesa Jääskeläinen
2005-09-20 17:13           ` Yoshinori K. Okuji
2005-08-15 17:24 ` Marco Gerards
2005-08-15 21:05   ` Vesa Jääskeläinen
2005-08-15 21:21     ` Marco Gerards
2005-08-15 21:39       ` Vesa Jääskeläinen
2005-08-16 10:04         ` Marco Gerards
2005-08-16 18:36           ` Vesa Jääskeläinen

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=4300BA58.1010706@nic.fi \
    --to=chaac@nic.fi \
    --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.