2015-10-28 14:59 GMT+08:00 Sascha Hauer <s.hauer@xxxxxxxxxxxxxx>: > Hi, > > On Tue, Oct 27, 2015 at 04:40:56AM +0800, Kevin Du Huanpeng wrote: >> On Mon, Oct 26, 2015 at 08:18:36AM +0100, Sascha Hauer wrote: >> > >> > This patch has several hunks without changes which makes it hard to look >> > at. >> > >> > Somehow this looks like beginning unicode support. Wouldn't it be better >> > to pick the relevant parts we need from unicode and support them? >> >> >> How about store the font data externally, for reasons >> 1. the font data maybe hurge, it take time to burn it to flash make barebox fat. >> 2. the part of font data namally don't change durning the devolopment. >> 3. 'custom' means usless for other application. >> 4. the fontdata maybe stored in a external spi flash and share with OS. >> just pass the base address of index and fontdata or tell barebox how to get the >> font data. > > Do you know the pf2 font format? That may be the right candidate for a > font format. See: http://grub.gibibit.com/New_font_format > If we could read this font format we could throw arbitrary unicode fonts > into barebox. > Nice font! it designed for bootloader! but it needs more learning, if being a bootloader user, for supportting several dozens of chars. the barebox user have to get font data from some .ttf or other format font, or hardware font(hardware font chip). and convert it to pf2 format. need more work. but maybe some people use barebox as a bare-metal application, not a bootloader, it will be useful. I guess. How about simply support the 'bitmap' font, simple and friendly to barebox user. next step, support pf2. ---- Du Huanpeng +86.13719074147 _______________________________________________ barebox mailing list barebox@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/barebox
