[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: What became of SLIP for Contiki?
Oliver Schmidt wrote:
>
> Why, there are plenty of Apple2 emulators and the cc65 docs even come
> with a step-by-step tutorial on running own code with them.
I just haven't seen too many for Linux. I'm also kind of crippled to
either awful X11 performance (DRI is being very naughty. Still in the
process of spanking it), or svgalib for emulation.
> - A hardware independent driver kernel linked statically with the
> application.
> - A hardware specific driver loaded dynamically from disk by the
> driver kernel or the application.
Everything suddenly makes a lot more sense.
>
> The driver kernel API is declared in serial.h. I'd propose to get the
> cc65 source and use the API implementation as documentation.
Been using it :)
>
> The loadable drivers for the Apple2 are called a2[e].ssc.ser.
I've tried some simple cc65 projects using serial.h, under c64 and
apple2.
I just keep getting extern errors whenever I try to use any of the
functions.
Even the struct in serial.h doesn't exist according to cc65. I'll get
to the bottom of this eventually.
>
> Contiki for the Apple2 comes in two variants. The "high end" variant
> now supports the mouse and therefore has general interrupt support
> built-in. The mouse driver is just the same kind of loadable driver as
> the rs232 driver so check out the CVS source for the mouse driver
> handling to get an idea on how to load the driver from the application
> instead of the driver kernel (to save sapce).
Already started on trying to get the serial lib to work. I think I need
to downgrade my version of cc65 though. I'm using the 666 snapshot now.
There seems to be something not quite right about its linker, or at
least something else causing the curent version of it to misbehave
sometimes.
> Check out the README.TXT in CVS.
Would you believe I didn't see 'readme.txt' because I was looking for
'README'?
Thanks again. I am enlightened.
> The latest Contiki "high end" variant is that tight on memory anymore
> (because of AUX RAM usage ;-) so there you can allocate an additional
> 1024 buffer without loosing significant functionality.
I'm going to be gutting it for my own purposes anyway. A nice high-end
version with mouse, 80 cols etc would be good. Well, 80 cols is nice as
it is. But I'm just going to try my best to get SLIP happening on the
apple2 version, and use the VNC driver.
My Apple's intended use, at least for a while is as a server for a MUD
or something like that. It just depends on what I can shoehorn into
RAM.
Thankyou very much for your help.