linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Petr Vandrovec <vandrove@vc.cvut.cz>
To: James Simmons <jsimmons@infradead.org>
Cc: Antonino Daplas <adaplas@pol.net>,
	Linux Fbdev development list
	<linux-fbdev-devel@lists.sourceforge.net>,
	Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: [Linux-fbdev-devel] [PATCH][FBDEV]: fb_putcs() and fb_setfont() methods
Date: Sun, 5 Jan 2003 00:30:08 +0100	[thread overview]
Message-ID: <20030104233008.GB1188@ppc.vc.cvut.cz> (raw)
In-Reply-To: <Pine.LNX.4.44.0301042058240.24903-100000@phoenix.infradead.org>

On Sat, Jan 04, 2003 at 09:07:29PM +0000, James Simmons wrote:
> 
> Rejected. I have put thought into it and the whole point was to not allow 
> the fbdev layer to touch console data. I stand firm on this!!! The reason 
> being is the core console layer is going to change the next development 
> cycle. We have to change to deal with things like the PC9800 type hardware 
> that support more than 512 fonts. Do we realy want to break every fbdev 
> driver again. This way the breakage is once and for all. Its is also a 

Why? (a) only those which will use putcs, and (b) I see no 512 chars limit
anywhere in new code. And in old code it is there only because of passed
data are only 16bit, not 32bit wide... With simple search&replace you can
extend it to any size you want, as long as you'll not use sparse font
bitmap.

> pandoras box. If we place these hooks in we end up with the same crappy 
> driver problem we had before. I never heard anyone every say the old api 
> we clean. 

I believe that I repeatedly said that I see no problem with old API which
cannot be solved by incremental updates and without removing functionality.

It is like with modules - some believe in evolution, and some in revolution...
Fortunately modules situation finally settled down and it is enough just install
new app to handle module loading/unloading. With current fbdev even trivial
console resizing does not do anything useful (thanks, Antonio).
						Best regards,
							Petr Vandrovec
							vandrove@vc.cvut.cz

  parent reply	other threads:[~2003-01-04 23:30 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-04  9:25 [PATCH][FBDEV]: fb_putcs() and fb_setfont() methods Antonino Daplas
2003-01-04 14:00 ` Jurriaan
2003-01-04 21:08   ` James Simmons
2003-01-04 20:41 ` Petr Vandrovec
2003-01-04 21:12   ` James Simmons
2003-01-04 23:17     ` Petr Vandrovec
2003-01-07 21:46       ` [Linux-fbdev-devel] " James Simmons
2003-01-04 21:07 ` James Simmons
2003-01-04 22:06   ` [Linux-fbdev-devel] " Antonino Daplas
2003-01-07 21:43     ` James Simmons
2003-01-04 23:30   ` Petr Vandrovec [this message]
2003-01-07 21:51     ` [Linux-fbdev-devel] " James Simmons
2003-01-08 10:47       ` Geert Uytterhoeven
2003-01-08 18:19         ` Antonino Daplas
2003-01-09 18:09           ` [Linux-fbdev-devel] " James Simmons
2003-01-09 20:54             ` Geert Uytterhoeven
2003-01-09 21:25               ` [Linux-fbdev-devel] " James Simmons
2003-01-10 14:36             ` Antonino 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=20030104233008.GB1188@ppc.vc.cvut.cz \
    --to=vandrove@vc.cvut.cz \
    --cc=adaplas@pol.net \
    --cc=jsimmons@infradead.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).