From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Takashi Oe <toe@unlserve.unl.edu>
Cc: Benjamin Herrenschmidt <bh40@calva.net>,
Linux/PPC Development <linuxppc-dev@lists.linuxppc.org>,
Linux Frame Buffer Device Development
<linux-fbdev@vuser.vu.union.edu>, Samuel Rydh <samuel@ibrium.se>
Subject: Re: [linux-fbdev] Re: Video driver bug
Date: Sat, 14 Oct 2000 18:41:49 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.10.10010141839280.570-100000@cassiopeia.home> (raw)
In-Reply-To: <Pine.A41.3.96LJ1.1b7.1001013173038.60708A-100000@unlserve.unl.edu>
On Fri, 13 Oct 2000, Takashi Oe wrote:
> On Fri, 13 Oct 2000, Benjamin Herrenschmidt wrote:
>
> > >That's for 2.5.0. I think the first thing we need to do in 2.5.0 is to remove
> > >all `mess with non-visible VCs' support, so /dev/fb* works on the _current_
> > >video mode.
> >
> > Well, my understanding is that MOL needs to be able to "probe" for all
> > supported mode. Doing so on a visible console would definitely be hell.
> > It does that in order to setup the MacOS-side driver mode list.
>
> According to Samuel's last post, MOL needs both var and fix for probing.
> If there is something like:
>
> struct fb_probe_info {
> struct fb_var_screeninfo var;
> struct fb_fix_screeninfo fix;
> };
Why does it need fix? Relying on data from fix for a mode that is not yet
really set is not wise: there's no guarantee that fix will be the same when the
mode is really set later.
Example: dual-head cards, where the resolution on one head is changed so the
card's memory management is changed.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-10-14 16:41 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 [this message]
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
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=Pine.LNX.4.10.10010141839280.570-100000@cassiopeia.home \
--to=geert@linux-m68k.org \
--cc=bh40@calva.net \
--cc=linux-fbdev@vuser.vu.union.edu \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=samuel@ibrium.se \
--cc=toe@unlserve.unl.edu \
/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).