linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Bruno Prémont" <bonbons@linux-vserver.org>
To: linux-fbdev@vger.kernel.org
Subject: vt & fbcon changes
Date: Mon, 28 Mar 2011 14:38:39 +0000	[thread overview]
Message-ID: <20110328163839.16e66a6f@neptune.home> (raw)

Hi James,

How is your refactoring of vt (and fbcon) progressing?

Last commit visible in your GIT tree [1] dates back to last November...

I'm looking at resuming my ref-counted framebuffer work though would
like to avoid duplicate work with your vt changes (and/or big merging
conflicts).

From first glance registered_fb[] is the biggest source of conflict,
in your patches you are dropping (most) of its use as you kill con2fb_map[]
in fbcon.c -- on my side I am planning to convert con2fb_map from char
to struct fb_info*

Thanks,
Bruno


[1] http://git.infradead.org/users/jsimmons/linuxconsole-2.6.git

                 reply	other threads:[~2011-03-28 14:38 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20110328163839.16e66a6f@neptune.home \
    --to=bonbons@linux-vserver.org \
    --cc=linux-fbdev@vger.kernel.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).