On Fri, Jan 28, 2000 at 01:01:29AM -0500, Shadow Daemon wrote:
> > I'm in Perth, Western Australia and would be happy to loan them to someone
> > in this region if that helps.
>
> The offer is appreciated :)
>
> I am in Atlanta, Georgia, USA (on the east side in a crummy little
> town called Clarkston, right next to the railroad tracks)...not exactly
> walking distance from Perth. Perhaps there is another ELKS developer in
> Perth who would be interested? Or perhaps someone with a flatbed scanner
> and a lot of time on their hands?
>
> Right now I am simply copying the necessary .c and .h files for MCA and
> ESDI support from the linux 2.2.14 source directly into the elks source
> directory. We shall see what happens at compile time. I've created a
> directory called "drivers" and in that, a directory called "block" for
> block device drivers such as ps2esdi.c, coming straight out of the linux
> 2.2.14 source.
They will probably need some work simply because they are too big, and
rely on kernel subsystems which work differently in ELKS. The directory
hierarchy is slightly different in ELKS. Block device drivers are kept in
arch/i86/drivers/block, rather than in drivers/block. Please put the files
in there.
>
> Is there a way to run bcc on a file or set of files to see where the
> problems will lie with regards to moving from 32-bit instructions to
> 16-bit instructions? Having only been learning C for 3 weeks now, I'm
> still not quite able to pick out problems with changes in system
> architecture :)
The easiest way is the add the files to the arch/i86/drivers/block directory,
and thenn add them to the list of objects in the Makefile and see how they
build.
Al
