If you are reading this message, then you have probably heard or read that
ATS
is good for safe systems programming. But you may not have seen low-level
systems
code written in ATS, right? There is a reason for this obvious irony for
writing such code
in ATS is very challenging. It took us a long time to learn the ropes.
Now I want to write a little bit on how ATS can be used effectively to
implement low-level
systems. My focus here is on implementing device drivers for Linux. I will
try to follow the
following book:
If you are reading this message, then you have probably heard or read that
ATS
is good for safe systems programming. But you may not have seen low-level
systems
code written in ATS, right? There is a reason for this obvious irony for
writing such code
in ATS is very challenging. It took us a long time to learn the ropes.
Now I want to write a little bit on how ATS can be used effectively to
implement low-level
systems. My focus here is on implementing device drivers for Linux. I will
try to follow the
following book:
However, please know about qemu sometimes doesn’t kick the kernel’s
interrupt handler.
Yes. I was also told to use Bochs. But Qemu is already very slow on my
machine.On Tuesday, October 21, 2014 2:37:35 PM UTC-4, gmhwxi wrote:
Hi,
If you are reading this message, then you have probably heard or read that
ATS
is good for safe systems programming. But you may not have seen low-level
systems
code written in ATS, right? There is a reason for this obvious irony for
writing such code
in ATS is very challenging. It took us a long time to learn the ropes.
Now I want to write a little bit on how ATS can be used effectively to
implement low-level
systems. My focus here is on implementing device drivers for Linux. I will
try to follow the
following book:
However, please know about qemu sometimes doesn’t kick the kernel’s
interrupt handler.
Yes. I was also told to use Bochs. But Qemu is already very slow on my
machine.
On Tuesday, October 21, 2014 2:37:35 PM UTC-4, gmhwxi wrote:
Hi,
If you are reading this message, then you have probably heard or read
that ATS
is good for safe systems programming. But you may not have seen low-level
systems
code written in ATS, right? There is a reason for this obvious irony for
writing such code
in ATS is very challenging. It took us a long time to learn the ropes.
Now I want to write a little bit on how ATS can be used effectively to
implement low-level
systems. My focus here is on implementing device drivers for Linux. I
will try to follow the
following book:
martinOn Thu, Nov 27, 2014 at 2:13 AM, ‘Yannick Duchêne’ via ats-lang-users ats-lan...@googlegroups.com wrote:
Le mardi 21 octobre 2014 20:37:35 UTC+2, gmhwxi a écrit :
Hi,
If you are reading this message, then you have probably heard or read that
ATS
is good for safe systems programming. But you may not have seen low-level
systems
code written in ATS, right? There is a reason for this obvious irony for
writing such code
in ATS is very challenging. It took us a long time to learn the ropes.
Now I want to write a little bit on how ATS can be used effectively to
implement low-level
systems. My focus here is on implementing device drivers for Linux. I will
try to follow the
following book:
The primary difficulty here lies in setting up the necessary environment
for Linux kernel programming:
I feel that this is like the ultimate test for any language attempting to
support low-level systems programming.
It is actually a lot more difficult than writing an operating system in the
tested language directly because interacting
with Linux kernel code requires a tremendously complex API. Not for
faint-hearted
For the next example, my plan is to implement the SCULL character driver in
the following book: