Simon Wood writes:
>
> Hello all,
> I've been playing again. I have almost finished the console driver (with
> virtual consoles) and have a basic keyboard driver in place. I've tracked
> down the timer interrupt to 0x79 (don't ask...) and this appears to function
> OK.
>
> The 'Code So Far' is on my web page for anyone wanting to try it for
> themselves (http://www.mungewell.ndirect.co.uk/psion/beyond.htm). Please
> note that it still needs a LOT more work, so don't be too judgmental.
I am still trying to dowload the code, but the server seems to be a bit
slow. Have you built some kind of loader, or are you running the kernel as
a binary as you mentioned last week?
>
> I've had a few quirks about fitting a different architecture into the master
> tree (as the overwriting of files in this patch proves). What are people's
> view on how to do this. Personally I feel that the Psion is significantly
> different to justify it's own tree, which could contain variants for the 3,
> 3a, 3c, 3mx and workabout (If people want to write the code :-).
>
Do you mean that we should have a directory under elks/arch, or do you mean
a whole new distribution tree? I think a whole new distribution tree would
be excessive, and would mean that the psion port would not benefit as
easily from bug fixes in the rest of the code. An arch/psion directory is
justified I think though.
Al
