All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Framebuffer address and kernel video mode
Date: Sat, 7 Feb 2009 23:54:37 +0100	[thread overview]
Message-ID: <20090207225437.GV6343@thorin> (raw)
In-Reply-To: <498B4FCB.6090106@gmail.com>

On Thu, Feb 05, 2009 at 09:44:59PM +0100, phcoder wrote:
> Hello. First of all some good news: I managed to boot xnu kernel. To do 
> so I need to set it to video mode and pass video mode info to kernel. 
> Now I do it in adapter-specific way which is bad and ugly. So I would 
> like to propose an interface to set video mode before loading kernel and 
> then retrieve information:
> For this I propose to put grub_gfxterm_init lines 253 (modevar = 
> grub_env_get ("gfxmode"))-482 (grub_video_fill_rect (...)) into video.c as
> grub_video_setup_by_var (char *varname)
> The informations I need is:
> 
> framebuffer address, bytes_per_scan_line, resolution, color depth
> 
> Unfortunately framebuffer_address and bytes_per_scanline is missing from 
>  struct grub_video_mode_info. I propose to add it to this structure

This is VERY nice.  Maybe we can make the Linux loader do the same, once we
switch to loader/i386/linux.c (current loader is loader/i386/pc/linux.c).

-- 
Robert Millan

  The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
  how) you may access your data; but nobody's threatening your freedom: we
  still allow you to remove your data and not access it at all."



      parent reply	other threads:[~2009-02-07 22:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-05 20:44 Framebuffer address and kernel video mode phcoder
2009-02-05 22:54 ` Colin D Bennett
2009-02-06  6:11   ` phcoder
2009-02-07 22:56   ` Robert Millan
2009-02-07 22:54 ` Robert Millan [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=20090207225437.GV6343@thorin \
    --to=rmh@aybabtu.com \
    --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.