forked from len0rd/rockbox
Fork of rockbox tailored for ipod classic
038df5cdc9
The following patch makes loadable fonts actually work (finally!). It took me quite a while, but I finally figured out why the sim worked and the target didn't: the SH1 processor won't read longwords from a shortword alignment... I had to rev the .fnt file to version 1.1 (requires remaking *.fnt files) in order to fix this. Please apply the following patch completely. It's diffed against the latest CVS. I've also attached rockbox-fonts-1.1.tar.gz which includes known working *.fnt files, including a courB08 system.fnt, for demonstration. Now the real work can begin... Although the new system.fnt will work fine, if you try going to a really big font (try copying courB14.fnt to system.fnt), then you will find that it comes up and works in tree mode, but will crash the system when going into WPS mode... I'm sure this is because of the low-level lcd_bitmap not clipping properly when given a too-large bitmap, which the characters become. I haven't yet tried to debug the low-level driver. Of course, it all works on the sim... So the apps developers will now have to make sure that all apps screen sizes may vary according to the loaded font. The font height can be gotten through the lcd_getfontsize API. Files patched in fonts-6.patch 1. apps/menu.c - LCD_PROPFONTS error (2nd resubmission on this, please checkin) 2. firmware/font.c - fixes and reformatting. Please check this in as is, my vi editor requires more reformatting changes since I left tabs in the file, these are removed now (2nd resubmission on this, please checkin) 3. firmware/fonts.h - doc change on .fnt file format, .fnt version number incremented. 4. firmware/loadfont.c - fixes to load font properly, typedefs removed. 5. firmware/system.c - lcd_setfont(FONT_SYSFIXED) before issuing error, otherwise font may not exist. 6. tools/bdf2c - fixes for correct output when filename starts with a number, as well as when no DEFAULT_CHAR in .bdf file. (2nd resubmission on this, please checkin) 7. tools/writerbf.c - fixes for bugfixed fontfile format. git-svn-id: svn://svn.rockbox.org/rockbox/trunk@2294 a1c6a512-1295-4272-9138-f99709370657 |
||
|---|---|---|
| apps | ||
| CVSROOT | ||
| docs | ||
| firmware | ||
| gdb | ||
| tools | ||
| uisimulator | ||
| www | ||
__________ __ ___.
Open \______ \ ____ ____ | | _\_ |__ _______ ___
Source | _// _ \_/ ___\| |/ /| __ \ / _ \ \/ /
Jukebox | | ( <_> ) \___| < | \_\ ( <_> > < <
Firmware |____|_ /\____/ \___ >__|_ \|___ /\____/__/\_ \
\/ \/ \/ \/ \/
Build your own archos.mod.
1. Check out 'firmware', 'apps' and 'tools' from CVS (or possibly from a
downloaded archive). You may possibly want 'uisimulator' too (for trying
out things on host before making target tests). If you haven't already
done so, we advise you pull down the 'docs' directory as well.
If you do want to play with the simulator, read UISIMULATOR.
2. Build the tools by running 'make' in the tools/ directory.
3. Create your own build directory, preferably in the same directory as the
firmware/ and apps/ directories. This is where all generated files will be
put.
4. In your build directory, run the 'tools/configure' script and enter what
target you want to build for and if you want a debug version or not. It'll
prompt you. The debug version is for making a gdb version out of it. It is
only useful if you run gdb towards your target Archos.
5. Make sure you have sh-elf-gcc and siblings in the PATH.
6. *ploink*. Now you have got a Makefile generated for you. Run 'make' and
soon the necessary pieces from the firmware and the apps directories have
been compiled and linked.
7. Copy the archos.mod file to your archos, reboot it and *smile*.
Whenever the tools/configure script gets updated, you can make your makefile
updated too by running 'tools/configure update'
If you want to build for more than one target, just create a new build
directory and create a setup for another target combination in there.
Questions anyone? Take them to the mailing list. We'll be happy to help you
out!