On Fri, Sep 19, 2014 at 4:41 PM, kilon alios <kilon.al...@gmail.com> wrote:
> I seriously doubt that SqueakNOS uses smalltalk to program the drivers > Actually, it does. The thing is that most drivers can be written in Smalltalk and glued with very very little assembly. 3 years ago, during our MSc thesis we added drivers to support virtual memory management and hard drives, all of them in smalltalk. In the end, the only assembly required was for I/O, for accesing special processor registers like CR0 and CR3 and to bind a function address to a Smalltalk block (callbacks). All of this was abstracted into primitives and managed at image side. Cheers! Javier > > On Fri, Sep 19, 2014 at 10:36 PM, Mayuresh Kathe <mayur...@kathe.in> > wrote: > >> Yes, that's something I would have loved to have, a single language to >> program everything, right from the drivers to user interface and >> applications. >> >> SqueakNOS looks very interesting, but still is way behind a combination >> of Linux kernel + X + Pharo in terms of hardware support and maturity. >> >> Also, in case you didn't know, there was an effort made to run Squeak >> directly on bare metal (Mitsubishi M32R/D) which worked like a charm, but >> has been suppressed for unknown reasons. >> >> ~Mayuresh >> >> >> >> On 2014-09-20 01:00, Torsten Bergmann wrote: >> >>> The idea is to build a minimalist Linux based system which would boot up >>>> straight into a full-screen Pharo environment. >>>> >>> >>> Why use a Linux underneath when you can do it in Smalltalk ;) >>> >>> Look at SqueakNOS - an operating system that was/still is able to >>> boot from disk right into Squeak: >>> >>> http://wiki.squeak.org/squeak/1762 >>> >>> Accessing devices/writing drivers in Smalltalk, etc. >>> >>> Would like to know if it's some how possible to control external >>>> programs from within Pharo, essentially shell scripts for network setup, >>>> etc. >>>> >>> >>> Check out the "OSProcess" package in Pharo. >>> >>> Bye >>> T. >>> >> >> > -- Javier Pimás Ciudad de Buenos Aires
