From: "Antonino A. Daplas" <adaplas@hotpop.com>
To: linux-fbdev-devel@lists.sourceforge.net,
Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Eric Pretorious <eric@pretorious.net>
Subject: Re: /usr/src/linux/Documentation/fb/aty128fb.txt (fwd)
Date: Tue, 5 Oct 2004 11:01:01 +0800 [thread overview]
Message-ID: <200410051101.01409.adaplas@hotpop.com> (raw)
In-Reply-To: <Pine.GSO.4.61.0410042119240.19047@waterleaf.sonytel.be>
On Tuesday 05 October 2004 03:19, Geert Uytterhoeven wrote:
> ---------- Forwarded message ----------
> Date: Mon, 4 Oct 2004 11:59:47 -0700
> From: Eric Pretorious <eric@pretorious.net>
> To: Brad Douglas <brad@neruo.com>
> Cc: geert@linux-m68k.org
> Subject: /usr/src/linux/Documentation/fb/aty128fb.txt
>
> Hi, Brad:
>
> One other nitpick: In the "Configuration" section you wrote...
>
> >Accepted options:
> >
> ><XxX@X> - selects startup videomode. See modedb.txt for detailed
> > explanation. Default is 640x480x8bpp.
>
> Should the values be enclosed - as illustrated - in brackets? (I've been
No. Parameters in brackets are meant to be optional.
> passing the value using the "vga=0x317".) The framebuffer.txt file
> describes it like this...
The option "vga=xxx" is only for drivers that lets the BIOS do the mode
setup for them. Some of these drivers are vesafb and matroxfb.
Tony
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
next prev parent reply other threads:[~2004-10-05 3:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-04 19:19 /usr/src/linux/Documentation/fb/aty128fb.txt (fwd) Geert Uytterhoeven
2004-10-05 3:01 ` Antonino A. Daplas [this message]
2004-10-05 6:57 ` Eric Pretorious
2004-10-05 8:42 ` Geert Uytterhoeven
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=200410051101.01409.adaplas@hotpop.com \
--to=adaplas@hotpop.com \
--cc=eric@pretorious.net \
--cc=geert@linux-m68k.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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.