linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Pretorious <eric@pretorious.net>
To: Brad Douglas <brad@neruo.com>
Cc: Linux Frame Buffer Device Development
	<linux-fbdev-devel@lists.sourceforge.net>
Subject: /usr/src/linux/Documentation/fb/aty128fb.txt
Date: Mon, 4 Oct 2004 15:03:05 -0700	[thread overview]
Message-ID: <200410041503.05154.eric@pretorious.net> (raw)

Hi, Brad:

Thanks for creating aty128fb. It works nicely on my Dell Lattitude.

In reading the kernel documentation, I believe that I may have found a minor 
error regarding vesafb: In the "How to use it" secition, you wrote...

>You should compile in both vgacon (to boot if you remove your Rage128 from
>box) and aty128fb (for graphics mode). You should not compile-in vesafb
>unless you have primary display on non-Rage128 VBE2.0 device (see
>Documentation/vesafb.txt for details).

...and later, in the "Configuration" section you wrote...

>You can pass kernel command line options to vesafb with
>`video=aty128fb:option1,option2:value2,option3' (multiple options should
>be separated by comma, values are separated from options by `:').
>Accepted options:

I believe that the second passage should read...

>You can pass kernel command line options to aty128fb with...

-- 
Eric P.,
Sunnyvale, CA


-------------------------------------------------------
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

             reply	other threads:[~2004-10-04 22:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-04 22:03 Eric Pretorious [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-10-04 22:03 /usr/src/linux/Documentation/fb/aty128fb.txt Eric Pretorious

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=200410041503.05154.eric@pretorious.net \
    --to=eric@pretorious.net \
    --cc=brad@neruo.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).