From: John Zielinski <grim@undead.cc>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux Frame Buffer Device Development
<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: fbutils
Date: Wed, 07 Jan 2004 21:26:05 -0500 [thread overview]
Message-ID: <3FFCBFBD.1010806@undead.cc> (raw)
In-Reply-To: <Pine.LNX.4.58.0401061420420.1856@callisto>
Geert Uytterhoeven wrote:
>--- fbutils-john-2/etc/modes 2004-01-04 15:38:38.000000000 +0100
>+++ fbutils/etc/modes 2004-01-04 15:33:21.000000000 +0100
>@@ -14,7 +14,7 @@
> "640x480@75" # 640x480 @ 75 Hz, 37.50 kHz hsync
> { 640 480 31746 120 16 16 1 64 3 }
> "800x600@60" # 800x600 @ 60 Hz, 37.8 kHz hsync
>- { 800 600 25000 88 40 23 1 128 4 0 hsync+ vsync+ }
>+ { 800 600 25000 88 40 23 1 128 4 hsync+ vsync+ }
> "640x480@85" # 640x480 @ 85 Hz, 43.27 kHz hsync
> { 640 480 27777 80 56 25 1 56 3 }
> "1152x864@89" # 1152x864 @ 89 Hz interlaced, 44 kHz hsync
>
>
Woops. I changed that in my /etc/fb/modes file but forgot to update the
one in the source package.
>--- fbutils-john-2/fbset/fbset.C 2004-01-04 15:38:38.000000000 +0100
>+++ fbutils/fbset/fbset.C 2004-01-04 15:42:02.000000000 +0100
>@@ -259,8 +259,8 @@
>
> // Parse the Options
>
>- while (id = GetNextOption(argc, argv, Options,
>- sizeof(Options)/sizeof(*Options))) {
>+ while ((id = GetNextOption(argc, argv, Options,
>+ sizeof(Options)/sizeof(*Options)))) {
> switch (id) {
> case ID_HELP:
> Usage();
>
>
>
Already cought that one. Don't know why I changed it in the first
place. That must have been a late night session or something. :)
I still have a couple of command line options that need finishing.
I'll have another updated patch with those in the next few days. I've
been extremely busy lately: holidays, email server dying, Prince of
Persia....
John
-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
next prev parent reply other threads:[~2004-01-08 2:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-22 1:32 fbutils John Zielinski
2003-12-22 22:42 ` fbutils Alexander Kern
2003-12-22 16:21 ` fbutils Geert Uytterhoeven
2003-12-22 22:12 ` fbutils John Zielinski
2003-12-22 21:42 ` fbutils John Zielinski
2003-12-23 6:11 ` fbutils John Zielinski
2004-01-06 13:22 ` fbutils Geert Uytterhoeven
2004-01-08 2:26 ` John Zielinski [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-06-22 15:52 fbutils Andrew Walrond
2004-06-22 19:51 ` fbutils Geert Uytterhoeven
2004-06-23 11:25 ` fbutils Andrew Walrond
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=3FFCBFBD.1010806@undead.cc \
--to=grim@undead.cc \
--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 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).