See below
Simon Wood
Hardware Engineer
Pace Micro Technology plc
Victoria Road, Saltaire, Shipley
West Yorkshire, BD18 3LF
Tel : +44(0)1274 532000 Fax: +44(0)1274 532029
This E-Mail and any attachments hereto are strictly confidential and
intended solely for the addressee. If you are not the intended addressee
please notify the sender by return and delete the message. You must not
disclose, forward or copy this E-mail or attachments to any third party
without the prior consent of the sender.
> -----Original Message-----
> From: Alan Cox [SMTP:[EMAIL PROTECTED]]
> Sent: Monday, August 16, 1999 11:18 AM
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
> Subject: Re: SIBO/Psion Elks
>
> > 1). Reduced character size to 8x8 to increase screen size and save
> memory
> > (the font is held in Data segment)
>
> Can you not find the Psion font in rom ? Also you could push the font into
> its own segment and 'borrow' ES momentarily with a cli around a single
> char
> render.
[<Simon Wood>]
I haven't looked and have no idea where and what format it might be. I'm
under the opinion that we should work completely separated from Psion ROM,
that way the code written could be ported to other systems (which might not
have similar steal-able features from ROM).
Yes it could be placed in a separate segment - I need to check how this
might be loaded from a Psion '.img' format executable as that's how the
system is 'booted' at present
> > 1). The current version of Init (in elkscmd) seems to need /var/utcp to
> be
> > exist, what does this do and should this file be writable (which won't
> be
> > possible with a read only file system!)?
>
> Eventually you are going to need a ram disk.
[<Simon Wood>]
Why ???
I agree that in a 'PC' type environment you will need disk storage, but
there are many applications for ELKS that will not...
In this specific case 'init' would need to create a RAM disk for /var before
it continued booting - seems a suspect way of doing it to me.
> > 2). PS requires '/proc', but I can't see any code where this 'created'.
>
> The mainstream Linux has a /proc we don't. The intention is to make /proc
> dig around in /dev/kmem
[<Simon Wood>]
So why is this PS in elkscmd if it can't possible work??
And on this line in whinging 'clock' talks directly to hardware (which in my
case doesn't exist!) - it should be through a clock driver!
> > 1). I still can't get Config #DEF's to link through to .S files for
> parsing.
> > Is this working on other people's machines? (this is making life kind of
> > difficult).
>
> .S files should go via the C pre processor. .s files dont
[<Simon Wood>]
Yep I get the concept, but I can't get it to work :-(, how are the config
#DEF's passed through Makefile to gcc?? (they certainly don't appear if you
do 'gcc -dD').
