From: Matt Keenan <tank.en.mate@gmail.com>
To: Nathan Cline <nathan.cline@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Patch to framebuffer
Date: Thu, 24 Nov 2005 09:08:57 +0000 [thread overview]
Message-ID: <43858329.8050300@gmail.com> (raw)
In-Reply-To: <656113ee0511232208n6948c364ke6103b3ef0a54f@mail.gmail.com>
Nathan Cline wrote:
>Hello, this is my first time posting to this list so please forgive me
>if I'm violating protocol in some way. :) I've written a patch to the
>framebuffer code to modify its behavior a bit. I am running on a
>dual-headed system and I noticed when I was working in one console on
>one monitor, the console on the other monitor was "frozen", not
>updating itself. After some digging through the code I realized this
>is because the two framebuffer drivers share the same framebuffer code
>which stores a single pointer to the "current" virtual console. If a
>VC is not current it is considered invisible and is not updated. So I
>patched the code to store a pointer for each framebuffer to the
>"foreground" VC on each one. It seems to work well but I'd like to get
>others' input as this is my first time writing any kernel code, and to
>be honest there is so much code it's difficult to get a clear picture
>in my head of how the whole system works.
>I've attached the patches to this message, a small one to
>drivers/video/console/fbcon.h, and a larger one to fbcon.c. I would
>appreciate it if some of you guys could look over this code and look
>for any obvious errors, or better yet, hopefully someone else has a
>multihead system they can try it on. The patches are against the
>latest GIT source tree (torvalds, main branch, 2.6.15rc2) as of last
>night.
>Any replies to this message should be CC'ed directly to my e-mail
>account (nathan dot cline .. gmail dot com) as I am not currently
>subscribed to this list. I look forward to getting this patch of high
>enough quality to submit to Linus. Thanks!
>
>
[PATCH SNIPPED]
Nathan you may also want to send a copy of your cleaned up patch to the
folks at linuxconsole-dev@lists.sourceforge.net as that is list that
deals with multihead development / issues. We also have patches for
getting multiheaded X working as well.
Matt Keenan
next prev parent reply other threads:[~2005-11-24 9:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-24 6:08 Patch to framebuffer Nathan Cline
2005-11-24 7:43 ` Antonino A. Daplas
2005-11-24 8:49 ` Antonino A. Daplas
2005-11-24 9:08 ` Matt Keenan [this message]
2005-11-24 9:46 ` Pekka Enberg
-- strict thread matches above, loose matches on Subject: below --
2005-11-24 17:21 Knut Petersen
2005-11-24 17:21 ` Knut Petersen
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=43858329.8050300@gmail.com \
--to=tank.en.mate@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nathan.cline@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.