From: Joachim Breuer <jmbreuer@gmx.net>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: lkml <linux-kernel@vger.kernel.org>,
Linux Frame Buffer Device Development
<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: Linux 2.4.20-pre6
Date: Wed, 11 Sep 2002 14:49:46 +0200 [thread overview]
Message-ID: <m365xcu1w5.fsf@venus.fo.et.local> (raw)
In-Reply-To: <Pine.GSO.4.21.0209111252340.27524-100000@vervain.sonytel.be> (Geert Uytterhoeven's message of "Wed, 11 Sep 2002 12:55:52 +0200 (MEST)")
Geert Uytterhoeven <geert@linux-m68k.org> writes:
> On Wed, 11 Sep 2002, Adrian Bunk wrote:
>> On Tue, 10 Sep 2002, Marcelo Tosatti wrote:
>>
>> >...
>> > Geert Uytterhoeven <geert@linux-m68k.org>:
>> >...
>> > o Wrong fbcon_mac dependency
>> >...
>>
> [SNIP]
>
> Hmmm... I didn't realize vesafb can use fbcon-mac.
>
> However, it seems to be used if you don't enable any of the fbcon-cfb* modules
> only, since fbcon-cfb* takes precendence.
>
> Do people really use 6x11 fonts with vesafb?
I don't use vesafb (as they (do they still?) tend to interfere with
accelerated X). "But I would if I did."
(Currently typing in an XEmacs on a 1600x1200 21" CRT using 6x13
font. No, I still don't get "enough" on one screen...)
So long,
Joe
--
"I use emacs, which might be thought of as a thermonuclear
word processor."
-- Neal Stephenson, "In the beginning... was the command line"
-------------------------------------------------------
In remembrance
www.osdn.com/911/
next prev parent reply other threads:[~2002-09-11 12:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.NEB.4.44.0209110152380.26432-100000@mimas.fachschaften.tu-muenchen.de>
2002-09-11 10:55 ` Linux 2.4.20-pre6 Geert Uytterhoeven
2002-09-11 12:49 ` Joachim Breuer [this message]
2002-09-11 19:02 ` Thunder from the hill
2002-09-12 13:27 ` Geert Uytterhoeven
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=m365xcu1w5.fsf@venus.fo.et.local \
--to=jmbreuer@gmx.net \
--cc=geert@linux-m68k.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).