All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marco Gerards <mgerards@xs4all.nl>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Video subsystem draft
Date: Fri, 09 Dec 2005 23:44:19 +0100	[thread overview]
Message-ID: <87ek4lq4ak.fsf@xs4all.nl> (raw)
In-Reply-To: <43891089.1050403@nic.fi> (Vesa Jääskeläinen's message of "Sun, 27 Nov 2005 03:48:57 +0200")

Vesa Jääskeläinen <chaac@nic.fi> writes:

> Vincent Pelletier wrote:
>> By the way, I think we should start a discussion on the API common to
>> all architectures for framebuffer handling.
>
> Currently there is a terminal implementation that uses video subsystem
> to render screen. So basicly in every arch there must be a video driver
> if you want graphical console.
>
> You can see my current idea how to use video driver in grub wiki:
> http://grub.enbug.org/VideoSubsystem

As I still can't log in on the wiki, I better reply here :-)

First of all I'd like to see some double buffering feature.  Will that
be somehow possible?  In that case we need functions like:

- Switching to a buffer, making it visible.
- Selecting which buffer is used for output.
What is the emulation you talk about for set palette?

Why are viewports needed?

Have you thought about how to load bitmaps?

I don't like using grub_uint*_t for parameters.  Just use normal
integers instead.  These types just have to be used for ABIs and
network and disk access.  In the case of APIs such types should be
avoided.

So better use "int height" instead of "grub_uint32_t height".  This is
especially important for portability and it serves no purpose.

Is it possible to pass parameters like depth to grub_video_setup?

Will it be possible for other users than the terminal to use these
functions?  I think that would be nice.  But in that case a function
should be used to redraw the screen.

How would scrolling work if a background picture was used?

Thanks,
Marco




  reply	other threads:[~2005-12-09 22:44 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-23 11:24 Video subsystem draft Vesa Jääskeläinen
2005-10-23 15:03 ` Timothy Baldwin
2005-10-23 15:24   ` Vesa Jääskeläinen
2005-10-28  3:21 ` Yoshinori K. Okuji
2005-10-28 13:59   ` Vesa Jääskeläinen
2005-11-17 23:19     ` Vesa Jääskeläinen
2005-11-18 11:06       ` Yoshinori K. Okuji
2005-11-22 19:06         ` Vesa Jääskeläinen
2005-11-25 20:25           ` Yoshinori K. Okuji
2005-11-26  0:28             ` Vesa Jääskeläinen
2005-11-26 14:36               ` Vincent Pelletier
2005-11-26 19:54                 ` Yoshinori K. Okuji
2005-11-27  1:48                 ` Vesa Jääskeläinen
2005-12-09 22:44                   ` Marco Gerards [this message]
2005-12-10  0:19                     ` Yoshinori K. Okuji
2005-12-10 10:31                     ` Vesa Jääskeläinen
2005-12-10 21:01                       ` Marco Gerards
2005-12-10 21:23                         ` Vesa Jääskeläinen
2005-12-10 20:48                     ` Vesa Jääskeläinen
2005-12-10 21:15                       ` Marco Gerards
2005-12-10 22:14                         ` Vesa Jääskeläinen
2005-12-10 22:32                           ` Marco Gerards
2005-12-10 23:11                             ` Vesa Jääskeläinen
2005-11-27  2:00                 ` Vesa Jääskeläinen
2005-11-26 19:52               ` Yoshinori K. Okuji
2005-11-27  2:09                 ` Vesa Jääskeläinen
2005-12-09 22:33                   ` Marco Gerards
2005-11-28 21:29               ` Vesa Jääskeläinen
2005-12-06 15:18                 ` 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=87ek4lq4ak.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.