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 20:46:52 +0800 [thread overview]
Message-ID: <1046868330.1229.59.camel@localhost.localdomain> (raw)
In-Reply-To: <20030305110529.GA2036@iliana>
On Wed, 2003-03-05 at 19:05, Sven Luther wrote:
> On Wed, Mar 05, 2003 at 04:26:04PM +0800, Antonino Daplas wrote:
> >
> > Hi,
> >
> > I believe it's time to finalize what is needed/not needed for the
> > framebuffer framework:
> >
> > 1. Text mode support?
>
> Would this work also on arches which don't traditionnaly do text mode ?
> Like ppc for example.
Yes, pixel-based drawing is still the default. It's only for drivers
(matrox and sbus) where it might be needed.
>
> > 2. console resizing using fbset (besides stty)?
>
> What about dynamic multi-head support ?
>
> > 7. Anything else?
>
> Well, what is the exact status of mult-head and multi-seat ? It is
If you mean one card with multiple heads, that will need driver-specific
support.
> supposed to work, but i did not (yet) experience it myself, mainly
> because non of my graphic cards are yet supported. One point i would
> like to see addressed is the ability to share one framebuffer and have
> both heads be separate viewports into this same framebuffer. This
> means setting a framebuffer with a stride equal to the sum of both's
> head resolution and having each head display a subset of it. This would
> also include having one head be a mirror of the other and other such
> things. This feature and resizing may cause problems though.
>
Because of the massive rewrite, there wasn't really enough time to add
major feature sets to the framework. Most of the effort was spent on
bug fixing, cleaning up, and speeding up the code (to justify the
rewrite).
It does have one benefit though, the newer code should make it easier to
add an infrastructure on top of fbdev, such as xinerama-style support.
But this will be in the future.
> > 8. feature freeze deadline?
>
> This would be for fbdev deature freeze, right, not for the drivers ?
>
Yes, to give people time to port their drivers.
> BTW, i will no more be able to work on pm3fb, since i just recently
> noticed that my nice AGP8 supporting motherboard doesn't accept my
> Appian Jeronimo 2000 board. :(((
>
That's too bad :-(
Tony
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
next prev parent reply other threads:[~2003-03-05 12:45 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 [this message]
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
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=1046868330.1229.59.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).