Le dimanche 23 juillet 2017 à 16:21 +0300, Paul Kocialkowski a écrit :
> Le lundi 17 juillet 2017 à 22:11 +0200, Patrick Georgi via coreboot a
> écrit :
> > I wouldn't scale at compile time (as said, storage constrained
> > payloads might not be happy about that).
> >
> > I wouldn't scale each
Le lundi 17 juillet 2017 à 22:11 +0200, Patrick Georgi via coreboot a
écrit :
> I wouldn't scale at compile time (as said, storage constrained
> payloads might not be happy about that).
>
> I wouldn't scale each character up on each access though (we won't
> hardware accelerate the scaling, and
Paul Kocialkowski wrote:
> I am wondering what the best way to solve this would be.
..
> * Having larger fonts for hi-dpi displays
This should be the top priority, because it provides the best user
experience. (Ie. it looks the best.)
> * Scaling the font to reach a particular DPI (e.g. based
I wouldn't scale at compile time (as said, storage constrained payloads
might not be happy about that).
I wouldn't scale each character up on each access though (we won't hardware
accelerate the scaling, and yes, that does get slow - framebuffers aren't
always the fastest type of memory and that
I agree with most of what Patrick said, I think dynamic scaling to integer
multiples may be best. Scaling the font up at compile-time seems like
unnecessary bloat to the binary (although I'm not sure, how big are these
fonts?). If you do want to include them at compile time, you may as well
Le lundi 17 juillet 2017 à 10:55 +0200, Patrick Georgi a écrit :
> 2017-07-16 11:32 GMT+02:00 Paul Kocialkowski :
> > So I am wondering what the best way to solve this would be. I see a
> > few
> > options:
> > * Having larger fonts for hi-dpi displays
>
> I'd go with that.
2017-07-16 11:32 GMT+02:00 Paul Kocialkowski :
> So I am wondering what the best way to solve this would be. I see a few
> options:
> * Having larger fonts for hi-dpi displays
>
I'd go with that. Plus, maybe, a function to select the right font given a
few constraints (display
I am using upstream coreboot with top-of-tree depthcharge and vboot on
kevin (Chromebook Plus from Samsung) and I've patched depthcharge[0] to
display text messages instead of looking up bitmaps in the GBB/cbfs.
I noticed that corebootfb is using[1] a fixed 8x16 font for showing text
there. In
8 matches
Mail list logo