All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jon Smirl <jonsmirl@gmail.com>
To: James Simmons <jsimmons@infradead.org>
Cc: "Antonino A. Daplas" <adaplas@gmail.com>,
	Linux Fbdev development list
	<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: Move softcursor out of fbdev to fbcon
Date: Wed, 27 Jul 2005 20:42:47 -0400	[thread overview]
Message-ID: <9e473391050727174222690eea@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.56.0507272313530.4063@pentafluge.infradead.org>

On 7/27/05, James Simmons <jsimmons@infradead.org> wrote:
> > > It has always bugged me that there was no real interface between
> > > fbconsole and fbdev. For example I tried to write a wrapper for DRM so
> > > that fbconsole could use DRM for accelerated console. But fbconsole is
> > > so tied into the fbdev data structures writing the wrapper required me
> > > to build most of an fbdev driver. I shouldn't need to do that,
> > > fbconsole should not be poking at fb_info, it should use an API for
> > > making changes.
> >
> > Yes. I think I'm planning to do that in small steps. I'm thinking first of
> > separating all fbcon-specific fields and place them in another structure,
> > ie, fbcon_info.  This struct will be registered separately from fb_info,
> > and only if fbcon is enabled.
> 
> Thats why its called the framebuffer console. It used the framebuffer api.
> Making a API between fbconsole and fbdev would be more bloat and whould
> have a performance it. The idea is to go as fast as possible.

A few extra instructions implementing an API won't make much of a
difference. We can only update the screen 70 times a second or so.
Wouldn't it be better to make an API than have me copy fbconsole,
rename it driconsole and then edit it to make it work? An API makes
the code more maintainable and reusable.

-- 
Jon Smirl
jonsmirl@gmail.com


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO September
19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf

  reply	other threads:[~2005-07-28  0:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-27  7:49 Move softcursor out of fbdev to fbcon Antonino A. Daplas
2005-07-27 14:32 ` Jon Smirl
2005-07-27 18:50   ` Antonino A. Daplas
2005-07-27 19:05     ` Jon Smirl
2005-07-27 22:17     ` James Simmons
2005-07-28  0:42       ` Jon Smirl [this message]
2005-07-28  2:12       ` Antonino A. Daplas
2005-07-28 18:39         ` James Simmons
2005-07-28 22:22           ` Antonino A. Daplas
2005-07-27 22:04 ` James Simmons
2005-07-28  2:12   ` Antonino A. Daplas

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=9e473391050727174222690eea@mail.gmail.com \
    --to=jonsmirl@gmail.com \
    --cc=adaplas@gmail.com \
    --cc=jsimmons@infradead.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    /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.