From: Samuel Rydh <samuel@ibrium.se>
To: geert@linux-m68k.org
Cc: linuxppc-dev@lists.linuxppc.org, bh40@calva.net,
linux-fbdev@vuser.vu.union.edu
Subject: Re: [linux-fbdev] Re: Video driver bug
Date: Sat, 21 Oct 2000 15:22:16 +0200 [thread overview]
Message-ID: <20001021152216.A706@ibrium.se> (raw)
In-Reply-To: <Pine.LNX.4.10.10010171332540.394-100000@cassiopeia.home>; from geert@linux-m68k.org on Tue, Oct 17, 2000 at 01:37:58PM +0200
On Tue, Oct 17, 2000 at 01:37:58PM +0200, Geert Uytterhoeven wrote:
> Alternatively you can get the info once and store it in a config file in the
> user's homedir. If it later turns out to be invalid (e.g. due to dual-head
> issues, or because you changed your video card), you can offer to reprobe when
> restarting MOL the next time.
OK, I'll settle for this solution. It is good to force manual confirmation
of each video mode anyway.
However, I discovered another bug in aty128fb.c. The aty_128_encode_var
sets var->activate to zero (preventing FB_ACTIVATE_TEST from
working). A simple fix:
+ int activate;
aty128_encode_var(var, &par, info);
- if ((var->activate & FB_ACTIVATE_MASK) != FB_ACTIVATE_NOW)
+ if ((activate & FB_ACTIVATE_MASK) != FB_ACTIVATE_NOW)
return 0;
(the bug is present in both 2.2 and 2.4).
Cheers,
/Samuel
----------------------------------------------------------
E-mail <samuel@ibrium.se> WWW: <http://www.ibrium.se>
Phone/fax: (home) +46 8 4418431, (work) +46 8 7908470
----------------------------------------------------------
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-10-21 13:22 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-07 11:38 Video driver bug Samuel Rydh
2000-10-07 17:56 ` Geert Uytterhoeven
2000-10-07 18:50 ` Takashi Oe
2000-10-07 23:34 ` Samuel Rydh
2000-10-10 1:43 ` [linux-fbdev] " James Simmons
2000-10-10 8:04 ` Geert Uytterhoeven
2000-10-10 13:45 ` Geert Uytterhoeven
2000-10-11 3:18 ` James Simmons
2000-10-13 20:43 ` Benjamin Herrenschmidt
2000-10-13 22:42 ` Takashi Oe
2000-10-14 16:41 ` Geert Uytterhoeven
2000-10-17 0:22 ` James Simmons
2000-10-16 22:20 ` Samuel Rydh
2000-10-17 11:37 ` Geert Uytterhoeven
2000-10-18 4:09 ` James Simmons
2000-10-21 13:22 ` Samuel Rydh [this message]
2000-10-14 6:36 ` James Simmons
2000-10-14 10:09 ` Geert Uytterhoeven
2000-10-14 12:24 ` Samuel Rydh
2000-10-11 0:05 ` James Simmons
2000-10-10 19:53 ` Geert Uytterhoeven
2000-10-11 5:23 ` James Simmons
2000-10-14 16:21 ` Geert Uytterhoeven
2000-10-14 17:18 ` Benjamin Herrenschmidt
2000-10-15 11:38 ` Geert Uytterhoeven
2000-10-17 0:03 ` James Simmons
-- strict thread matches above, loose matches on Subject: below --
2000-10-16 18:21 Brad Douglas
2000-10-17 1:31 ` James Simmons
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=20001021152216.A706@ibrium.se \
--to=samuel@ibrium.se \
--cc=bh40@calva.net \
--cc=geert@linux-m68k.org \
--cc=linux-fbdev@vuser.vu.union.edu \
--cc=linuxppc-dev@lists.linuxppc.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 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).