mirror of
https://github.com/saymrwulf/xous-core.git
synced 2026-11-14 08:03:34 +00:00
9434bb5383
By adding a resolver to a given glyph set, the glyph set is automatically pulled into the image. Glyph set is now co-located in the bao-video process, instead of the loader. The orignial argument for putting the font data in the loader is that it's a large, static blob; by putting it in the loader, updates can be more compact, and fonts don't need to be schlepped over every time you have an application update. This came with consequences. It made verifying the loader more complicated (because its memory space is split between the graphics manager and root keys). It also means we have to fix the partition size for the loader at "fairly large" for fonts, even if we don't need all of them in all of the configs. With baochip, we have swap memory! Off-chip memory is cheap and only the fonts actually used by the host get mapped into main memory. This means we don't have as much of a trade-off in terms of cost for fonts if we put them in off-chip swap storage. Also, the updates are split between swap and main memory, and the roadmap includes an item for swap to be individually loadable programs so that if the video server doesn't need an update, it won't be pulled into the update set. |
||
|---|---|---|
| .. | ||
| bao1x-api | ||
| bao1x-hal | ||
| blitstr2 | ||
| chat | ||
| cos_table | ||
| flatipc | ||
| flatipc-derive | ||
| keystore-api | ||
| mass-storage | ||
| perflib | ||
| precursor-hal | ||
| tls | ||
| userprefs | ||
| ux-api | ||
| xous-bio | ||
| xous-bio-bdma | ||
| xous-pio | ||
| xous-pl230 | ||