On Sun, 12 Mar 2000, James Simmons wrote:
>
> > I realised that, however what I am trying to point out is that originally
> > the driver could supply a "no kernel argument default fontname". This seems
> > to be no longer possible, so to get the font you want to be default, you
> > have to specifically deny the user from selecting the other fonts by
> > compiling them out of the kernel.
> >
> > This seems to be a step backwards to me. Could it be arranged that:
> >
> > 1. If the user specified a font, and the font exists, use this.
> > 2. If fb_info.fontname is present, and the font exists, use this.
> > 3. Use the first font available.
>
> No it's not a step backwards. It's a step forward. Its just bloat to have
> a bunch of font sets built into the kernel when you can use a userland app
> to change the fonts. IMO you should only be able to compile in one font
> set and use a userland app to change the font sets otherwise. Userland
> apps are your friend :)
If there is a need for the fonts before userland is "up", then it is a
step backwards. Like modedb, there might be a need to have the fonts
in-kernel, marked with __init[data].
Jeff
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Wed Mar 15 2000 - 21:00:24 EST