Re: [Linux-fbdev-users] Switching to my chosen console font when the framebuffer console starts.

[cga2000 <cg...@op...>]

On Mon, Oct 22, 2007 at 03:20:54PM EDT, thu...@xs... wrote:
> From: cga2000 <cg...@op...>
> Date: Sun, Oct 21, 2007 at 08:44:29PM -0400
> > It looks like I need to:
> > 
> > 1. convert the .psf font to a text format (fontforge?)
> 
> This is, IMHO, the most difficult step. 

I remember peeking into font files that looked exactly like the stuff in
those font*.c files but I can't remember where.

Surely this particular encoding must correspond to a specific dot
something format?

That's why I mentioned "fontforge" hoping there had to be some tool that
lets you convert from the .psf format to this other format painlessly.

If not, then it _is_ going to be difficult ..

:-(

> > 2. wrap it up in a .c file -- same as the other font*.c's
> 
> that is a task awk, or perl, or python (etc) should be handy for.

For just this one font I'm not sure a tool that automates the process
is worth the effort. 

Or I am missing something?

> > 3. signal this new font to "make menuconfig" so it gets compiled in
> > 4. make it the default startup font
> 
> if you select it as the 'only' font in step 3, it's automatically the
> default font.

I should have written "make kernel configuration tools aware of this new
font so I can select it at make-menuconfig time"

I would imagine there's some kernel .config boolean that needs to be
created and initialized somehow?

Naturally as Geert also indicated the easiest way to enable the font is
definitely to make it the "only" font .. which is not really such a big
sacrifice .. It has just about all the glyphs I need , so I will not
need to switch to any other font on the fly.

> I did get some adapted fonts into the kernel (which remains my only
> claim to fame), and it really isn't that hard.

Thanks. 

Another good reason I should do it as soon as time allows, hopefully
within the next month or so.

cga.