From: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-fbdev-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [RESEND] fbcon: simple text blinking implementation
Date: Fri, 08 Aug 2008 10:54:11 +0100 [thread overview]
Message-ID: <489C17C3.6060006@eu.citrix.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0807172047340.20605@anakin>
Geert Uytterhoeven wrote:
> On Thu, 17 Jul 2008, Stefano Stabellini wrote:
>> at the moment blinking is not supported in fbcon but it is supported in
>> vgacon.
>> Since userspace applications don't distinguish between the two, they just
>> assume that the linux terminal is always capable of blinking text.
>> However implementing blinking in fbcon is not so difficult: this patch
>> provides a very simple (too simple?) implementation of that.
>> I am using the flashcursor function to scan the buffer for blinking text.
>> For the sake of efficiency I added a simple flag mechanism to disable the scan
>> when I am sure that there are no blinking characters on the screen.
>
> Ehrm, there's already blinking support on some platforms?
>
are you sure?
fbcon isn't supposed to be a software implementation?
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
prev parent reply other threads:[~2008-08-08 9:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-17 13:50 [PATCH] [RESEND] fbcon: simple text blinking implementation Stefano Stabellini
2008-07-17 18:50 ` Geert Uytterhoeven
2008-08-08 9:54 ` Stefano Stabellini [this message]
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=489C17C3.6060006@eu.citrix.com \
--to=stefano.stabellini@eu.citrix.com \
--cc=geert@linux-m68k.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@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).