mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Adam J. Richter" <adam@ns1.yggdrasil.com>
To: geert@linux-m68k.org
Cc: linux-fbdev-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org, mj@ucw.cz
Subject: Re: [Linux-fbdev-devel] Patch, please TEST: linux-2.4.9 console font modularization
Date: Sun, 19 Aug 2001 03:28:58 -0700	[thread overview]
Message-ID: <200108191028.DAA01752@ns1.yggdrasil.com> (raw)

>What's wrong with the ancient console ioctl()s to change the font at runtine?
>(damned, I can't remember the name of the command)
[...]
>Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

	I don't know enough about fbdev vs. the old PC VGA console 
to know whether those ioctl's are available for fbdev.

	As far as I'm concerned, loading fonts by user level programs
would be even better than by loading modules, although, I think that,
when trying to move a facility from kernel to userland, people are a
lot more willing to try that change if the kernel-based way is still
available, but normally just compiled as modules that people gradually
stop using.

Adam J. Richter     __     ______________   4880 Stevens Creek Blvd, Suite 104
adam@yggdrasil.com     \ /                  San Jose, California 95129-1034
+1 408 261-6630         | g g d r a s i l   United States of America
fax +1 408 261-6631      "Free Software For The Rest Of Us."

             reply	other threads:[~2001-08-19 10:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-19 10:28 Adam J. Richter [this message]
2001-08-19 10:55 ` Geert Uytterhoeven
     [not found] <Pine.LNX.4.05.10108191147400.16179-100000@callisto.of.borg>
2001-08-19 14:08 ` James Simmons
  -- strict thread matches above, loose matches on Subject: below --
2001-08-19  8:56 Adam J. Richter
2001-08-19 14:12 ` [Linux-fbdev-devel] " 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=200108191028.DAA01752@ns1.yggdrasil.com \
    --to=adam@ns1.yggdrasil.com \
    --cc=geert@linux-m68k.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mj@ucw.cz \
    /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

all inboxes | Powered by JetHome®