All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marco Gerards <metgerards@student.han.nl>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Graphic calls portability
Date: Wed, 24 Aug 2005 11:54:17 +0200	[thread overview]
Message-ID: <87irxvwth2.fsf@student.han.nl> (raw)
In-Reply-To: <430C286B.5050302@yahoo.fr> (Vincent Pelletier's message of "Wed, 24 Aug 2005 09:57:31 +0200")

Vincent Pelletier <subdino2004@yahoo.fr> writes:

Hi Vincent,

> Now the point of my mail :
> Couldn't we make a common interface for all graphic calls, so the
> graphic commands would be in /commands ?
> The needed commands would be the ones already defined in
> video/i386/pc/vbe.c with those changes :
> -Add a function to list the available framebuffers

Agreed.

> -Allow to specify the framebuffer to open

We need a framebuffer terminal.  It should be possible to pass a
argument to it which framebuffer it uses.  Some systems have multiple
framebuffers, or multiple ways to access the same video hardware (for
example VGA, ATI and OF, those can be all used to access the same
hardware).

> -Add a framebuffer handles (like file handles) for later use in
> framebuffer functions

Can you explain this?  You mean we need an object for this?

> Exact prototypes to be defined, but if someone works on them, please
> consider 64 bits archs :) .

What makes 64 bits archs special?

--
Marco




  reply	other threads:[~2005-08-24 10:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-24  7:57 Graphic calls portability Vincent Pelletier
2005-08-24  9:54 ` Marco Gerards [this message]
2005-08-24 10:59   ` Vincent Pelletier

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=87irxvwth2.fsf@student.han.nl \
    --to=metgerards@student.han.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.