rvinterf/etmsync/fsnew.c: cast 0 to (char *) for execl sentinel I generally don't use NULL and use plain 0 instead, based on a "NULL considered harmful" discussion on the classiccmp mailing list many aeons ago (I couldn't find it, and I reason that it must have been 2005 or earlier), but a recent complaint by a packager sent me searching, and I found this: https://ewontfix.com/11/ While I don't give a @#$% about "modern" systems and code-nazi tools, I realized that passing a plain 0 as a pointer sentinel in execl is wrong because it will break on systems where pointers are longer than the plain int type. Again, I don't give a @#$% about the abomination of x86_64 and the like, but if anyone ever manages to port my code to something like a PDP-11 (16-bit int, 32-bit long and pointers), then passing a plain 0 as a function argument where a pointer is expected most definitely won't work: if the most natural stack slot and SP alignment unit is 16 bits, fitting an int, with longs and pointers taking up two such slots, then the call stack will be totally wrong with a plain 0 passed for a pointer. Casting the 0 to (char *) ought to be the most kosher solution for the most retro systems possible.

# Set WS=3 for both nCS0 and nCS1, same as the more basic Compal phones

w16 fffffb00 00A3
w16 fffffb02 00A3

# We need to switch the CS4/ADD22 pin from its default function of CS4
# to the needed ADD22, to access the 8 MiB of flash.  Compal's C155/156
# in-flash boot code does this setting, but let's do it ourselves too.

w16 fffef006 0008

# We don't mess with the FFFF:FB10 register on C155/156, i.e., we
# leave the "enable boot ROM" setting established by compalstage.
# Unlike C139, C155 and C156 phones do have working flash mapping
# at 0x03000000, so we use that.