All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Millan <rmh@aybabtu.com>
To: grub-devel@gnu.org
Cc: 422794@bugs.debian.org, Jonny <jonny@csc.jp>,
	Otavio Salvador <otavio@debian.org>,
	422794-forwarded@bugs.debian.org
Subject: gfxterm and vesa
Date: Fri, 11 May 2007 16:07:35 +0200	[thread overview]
Message-ID: <20070511140734.GD3625@aragorn> (raw)
In-Reply-To: <87ps578rug.fsf@lab.ossystems.com.br>

On Fri, May 11, 2007 at 09:31:03AM -0300, Otavio Salvador wrote:
> Jonny <jonny@csc.jp> writes:
> 
> > Robert Millan <rmh@aybabtu.com> write:
> >
> >> Can you try 800x600x32 and 640x480x8 ?
> >
> > Since my machine is't supporting a 32-bit color, 800x600x32 can't be used. If 
> > it's 800x600x24, it works well.
> 
> Ah nice. Robert, I think we might reduce the color depth used by
> default. We might even use 16 instead of 24 IMHO. What do you think?

Not sure.. does 16 work on all machines?  What about old PCs that don't
support VESA at all?  I think we should have some way to probe all this
stuff before enabling gfxterm.

The X people use discover and xresprobe.  Perhaps we could do that too?

As short term, if you think 640x480x16 is a reasonable default, we could set
that.  But since this part of code belongs to upstream, I'd like to see if
they have some comments about it (forwarding).

GRUB maintainers (specialy daChaac), do you have any comments on this?

-- 
Robert Millan

My spam trap is honeypot@aybabtu.com.  Note: this address is only intended
for spam harvesters.  Writing to it will get you added to my black list.



       reply	other threads:[~2007-05-11 14:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20070511155339.85f69598.jonny@csc.jp>
     [not found] ` <87ps578rug.fsf@lab.ossystems.com.br>
2007-05-11 14:07   ` Robert Millan [this message]
2007-05-11 15:04     ` gfxterm and vesa Vesa Jääskeläinen
2007-05-12 23:00       ` Robert Millan
2007-05-15 20:23         ` Yoshinori K. Okuji
2007-05-16 15:37           ` Robert Millan

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=20070511140734.GD3625@aragorn \
    --to=rmh@aybabtu.com \
    --cc=422794-forwarded@bugs.debian.org \
    --cc=422794@bugs.debian.org \
    --cc=grub-devel@gnu.org \
    --cc=jonny@csc.jp \
    --cc=otavio@debian.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.