linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Antonino Daplas <adaplas@pol.net>
To: Sven Luther <luther@dpt-info.u-strasbg.fr>
Cc: Linux Fbdev development list <linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: Feature Freeze?
Date: 05 Mar 2003 23:25:49 +0800	[thread overview]
Message-ID: <1046877877.1291.186.camel@localhost.localdomain> (raw)
In-Reply-To: <20030305144947.GA3946@iliana>

On Wed, 2003-03-05 at 22:49, Sven Luther wrote:
> On Wed, Mar 05, 2003 at 10:46:37PM +0800, Antonino Daplas wrote:
> > > I thought that the new API, separating the fbcon layer from the fbdev
> > > drivers would add support for this more easily. I guess it would be easy
> > > for the Appian Jeronimo 2000 board, which has two permedia3 chips, and
> > > thus can be seen as two separate devices. Cards with two ramdacs per
> > > chip, like the G400, the later radeon's and most recent cards would need
> > > driver level support, that is understandable, but is all there for fbcon
> > > to take advantage of it ? What about multi-seat, with two full consoles,
> > > with mouse and keyboard for each ?
> > > 
> > 
> > This was one of the goals of the Ruby project, but I think it's mostly 
> > the input layer that got into the kernel. 
> 
> :(((
> 
> > Fbcon needs to be cleaned up, a lot. It still implements the "current
> > console or foreground console" concept (only one console active at a
> > time).  Also, this is more of a job for linuxconsole than fbdev.  I may
> > be wrong though.
> 
> Mmm, do you know who is working on linuxconsole, and what their plan are ?

James also. I think the site is http://linuxconsole.sourceforge.net.

Tony



-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger 
for complex code. Debugging C/C++ programs can leave you feeling lost and 
disoriented. TotalView can help you find your way. Available on major UNIX 
and Linux platforms. Try it free. www.etnus.com

  reply	other threads:[~2003-03-05 15:24 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-05  8:26 Feature Freeze? Antonino Daplas
2003-03-05  9:57 ` Geert Uytterhoeven
2003-03-05 12:46   ` Antonino Daplas
2003-03-05 18:37     ` James Simmons
2003-03-06  1:17       ` Antonino Daplas
2003-03-11 15:55         ` James Simmons
2003-03-05 18:34   ` James Simmons
2003-03-05 18:45     ` Geert Uytterhoeven
2003-03-06  1:18     ` Antonino Daplas
2003-03-06  7:03       ` Carlo E. Prelz
2003-03-06  7:54         ` Antonino Daplas
2003-03-11 15:57       ` James Simmons
2003-03-05 11:05 ` Sven Luther
2003-03-05 12:46   ` Antonino Daplas
2003-03-05 13:43     ` Sven Luther
2003-03-05 14:04       ` Geert Uytterhoeven
2003-03-05 14:21         ` Sven Luther
2003-03-05 14:23           ` Geert Uytterhoeven
2003-03-05 14:26             ` Sven Luther
2003-03-05 14:46       ` Antonino Daplas
2003-03-05 14:49         ` Sven Luther
2003-03-05 15:25           ` Antonino Daplas [this message]
2003-03-05 18:55             ` James Simmons
2003-03-05 18:46         ` James Simmons
2003-03-05 18:52       ` James Simmons
2003-03-05 18:39     ` James Simmons
2003-03-05 18:36   ` James Simmons
2003-03-05 18:29 ` James Simmons
2003-03-06  1:18   ` Antonino Daplas
2003-03-11 16:06     ` James Simmons
     [not found] <20030305211727.GA3839@g-kabel.si>
2003-03-05 23:59 ` 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=1046877877.1291.186.camel@localhost.localdomain \
    --to=adaplas@pol.net \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=luther@dpt-info.u-strasbg.fr \
    /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).