From: Brad Douglas <Brad@NERUO.com>
To: "'James Simmons '" <jsimmons@suse.com>,
"'Benjamin Herrenschmidt '" <bh40@calva.net>
Cc: "'Geert Uytterhoeven '" <geert@linux-m68k.org>,
"'Linux Frame Buffer Device Development '"
<linux-fbdev@vuser.vu.union.edu>,
"'Linux/PPC Development '" <linuxppc-dev@lists.linuxppc.org>
Subject: RE: [linux-fbdev] Re: Video driver bug
Date: Mon, 16 Oct 2000 14:21:29 -0400 [thread overview]
Message-ID: <6BAD6986DF8FD211AB8300A0C931D85514E030@mail.neruo.com> (raw)
Most of us still have a need to know the last (previous) active console.
Maybe change info->currcon to info->lastcon? Or does the API already give
us the info we need?
I apologize in advance for not looking into this myself.
Brad Douglas
brad@neruo.com
http://www.linux-fbdev.org
-----Original Message-----
From: James Simmons
> While we are at it, I beleive we should also change atyfb.c so that
> currcon is no longer a global. My understanding is that can break
multihead.
That is not the only thing broken for multihead support. The softback code
is severly broken. Also why don't we use the display_fg field in fb_info
instead. display_fg->vc_num is already their is it's more multihead
friendly. IMO real multihead support shoudl wait until 2.5.X since it
needs a pretty big cleanup.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2000-10-16 18:21 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-16 18:21 Brad Douglas [this message]
2000-10-17 1:31 ` [linux-fbdev] Re: Video driver bug James Simmons
-- strict thread matches above, loose matches on Subject: below --
2000-10-07 17:56 Geert Uytterhoeven
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
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
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=6BAD6986DF8FD211AB8300A0C931D85514E030@mail.neruo.com \
--to=brad@neruo.com \
--cc=bh40@calva.net \
--cc=geert@linux-m68k.org \
--cc=jsimmons@suse.com \
--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).