>
>
>
> > (using UART for io using --serial stdio option in qemu). The drivers/rest
> > of the kernel infrastructure could then be crowd sourced :)
>
> Will you give it a try?
>
I think that I am close to doing it with miniPicoLisp :)
> You mean Pil64 and Pil
right?
You mean Pil64 and PilOS? (Beause pil21 has no assembly sources)
The sources of Pil64 and PilOS *are* Lisp files. They are evaluated via 'load'
in "src64/mkAsm.l". That's why I said in the last mail that a running PicoLisp
is nneded to bootstrap the build.
☺/ A!ex
700, C K Kashyap wrote:
> > Any chance that we could expect a pil21 based pilos?
>
> This would indeed be fascinating. Perhaps there is some LLVM backend to
> Verilog?
> But PilOS is a huge task, and needs lots of drivers etc. for some target
> hardware. I have no hope for the n
On Thu, Oct 05, 2023 at 07:32:26AM -0700, C K Kashyap wrote:
> Any chance that we could expect a pil21 based pilos?
This would indeed be fascinating. Perhaps there is some LLVM backend to Verilog?
But PilOS is a huge task, and needs lots of drivers etc. for some target
hardware. I have no h
Thanks Alex,
Any chance that we could expect a pil21 based pilos?
I had not been watching pil21 for a while - I looked at it now and I really
liked "lib.c" :) If I understood right, then all the platform
dependencies are in there (atleast as far as the picolisp executable)
On Thu, O
Hi Kashyap,
> It looks like pilos build may be broken :( I think it has dependency on
> pil64.
This may well be. PilOS is built by PicoLisp, and is a modified and partially
scaled down version of Pil64.
☺/ A!ex
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Hey Alex,
It looks like pilos build may be broken :( I think it has dependency on
pil64.
I will take a look more later but it would be great if you could share the
updated instructions :)
Regards,
Kashyap
On Mon, Sep 04, 2017 at 06:02:49PM +0200, Alexander Burger wrote:
> Hi all,
>
> this change was sent to be by Alexander Shendi. It should fix one of the
> problems with some BIOSes when using PilOS.
>
> If anybody who observed "READ ERROR 09" in the past, pl
Hi all,
this change was sent to be by Alexander Shendi. It should fix one of the
problems with some BIOSes when using PilOS.
If anybody who observed "READ ERROR 09" in the past, please test this new
version! :)
♪♫ Alex
- Forwarded message from Alexander Shendi -
Date: Mon,
On Sat, Apr 23, 2016 at 02:55:47AM +0200, Danilo Kordic wrote:
> 0.0 It is alive! Acer AOD270 (Intel Atom N2600).
> `` PilOS 15.11.0
So Acer again! I wonder if any other BIOS (in addition to qemu's) will
work.
♪♫ Alex
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
0.0 It is alive! Acer AOD270 (Intel Atom N2600).
`` PilOS 15.11.0
Heap: 1010MiB
:
''
I downloaded pios.tgz a few minutes ago, or so it feels ;) . Just `dd'ed
x86-64.img.
have much access to Windows), but trying to compile the sources
for that version, and all surrounding versions, was met with linker errors
only *after* 99% of the object files were generated.
Compilation issues aside, the Windows exe does in fact run inside Wine and
PilOS does in fact run inside th
On Fri, Apr 15, 2016 at 03:46:06PM -0400, cat stevens wrote:
> > This is an error from the BIOS (Was this also Qemu?).
>
> Yes, that was Qemu. Here's a screenshot <http://imgur.com/5bCRrVF.png>.
>
> It comes after the "Loading PilOS" text, and I found the s
;
> It comes after the "Loading PilOS" text, and I found the string constant
> "READ ERROR 00" in the image binary (at 0xBF), so I thought that was PilOS.
>
> I also recompiled using the provided source / instructions on the Wiki, and
> tried booting the res
> This is an error from the BIOS (Was this also Qemu?).
Yes, that was Qemu. Here's a screenshot <http://imgur.com/5bCRrVF.png>.
It comes after the "Loading PilOS" text, and I found the string constant
"READ ERROR 00" in the image binary (at 0xBF), so I thought
On Fri, Apr 15, 2016 at 12:08:56PM -0400, cat stevens wrote:
> Hi! I am very interested in the idea and look of PilOS; however, I'm having
> some issues trying to get started with it. Can I ask about those here?
Sure! :)
> First, the command on the Wiki seems to have an issue,
Hi! I am very interested in the idea and look of PilOS; however, I'm having
some issues trying to get started with it. Can I ask about those here?
First, the command on the Wiki seems to have an issue, which I asked about
here
<http://unix.stackexchange.com/questions/276480/booting-a-
015 at 04:48:19PM -0400, me wrote:
> > Hello list. I've been following the pilOS progress and very interested
> in
> > running picolisp on bare metal.
> >
> > After following the instructions my exploration was halted shortly after
> > booting. "Welcome
Hi me,
On Sat, Oct 31, 2015 at 04:48:19PM -0400, me wrote:
> Hello list. I've been following the pilOS progress and very interested in
> running picolisp on bare metal.
>
> After following the instructions my exploration was halted shortly after
> booting. "Welcome to
Hello list. I've been following the pilOS progress and very interested in
running picolisp on bare metal.
After following the instructions my exploration was halted shortly after
booting. "Welcome to pilOS!" line followed by "Error 9" whatever that is.
This was on
to turn the work on
> PilOS into a 32-bit PicoLisp running on specifically an ARM Cortex-A9 dual
> core with a Mali400 GPU?
PilOS is strictly 64-bit. It won't run on a 32-bit architecture.
I would take miniPicoLisp. It can also be built as a stand-alone
embedded system, see
h
I have a few TV sticks laying around running Android, but they have a
microSD slot, which you can boot a Linux image from. I am thinking on
learning ARM programming, since so many IOT devices, small netbooks and
tablets use these processors. How hard would it be to turn the work on
PilOS into a 32
Hi Geo,
> Oh! indeed that would be nice! so what's the hindrance for this goal?
1. I have no hardware to test (and on qemu Debian doesn't install yet on
ARMv8).
2. It is a lot of work.
> also, is there a port for MIPS64?
No. Only x86-64 and Ppc64 so far.
> ^^And yes i know its German for
Hi Rob,
> How about the Qualcomm DragonBoard? It's a 4 core 64 bit beast.
You mean e.g. DragonBoard 410? Looks very good!
♪♫ Alex
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
I will hope and look for a 64bit home for PilOS in the hardware world!
How about the Qualcomm DragonBoard? It's a 4 core 64 bit beast.
Rob
On Tue, Aug 4, 2015 at 6:07 PM, Alexander Burger
wrote:
> On Tue, Aug 04, 2015 at 09:40:18AM +, George Orais wrote:
> > >
AM +, George Orais wrote:
> > Not just "prefer" ... There is no way to run PilOS on 32-bits.
> Besides> the fact that there is no ARM port yet.
> Ah yes coz PilOS is fully based on pil64. Ah you mean there is no ARM
> port of the pil32 yet right? i thought someone
On Tue, Aug 04, 2015 at 09:40:18AM +, George Orais wrote:
> > Not just "prefer" ... There is no way to run PilOS on 32-bits.
> Besides> the fact that there is no ARM port yet.
> Ah yes coz PilOS is fully based on pil64. Ah you mean there is no ARM
> port of th
Hi Alex,
> Not just "prefer" ... There is no way to run PilOS on 32-bits. Besides> the
> fact that there is no ARM port yet.
Ah yes coz PilOS is fully based on pil64. Ah you mean there is no ARM port of
the pil32 yet right? i thought someone here has successfuly install
Hi Robert, Geo,
indeed, an interesting piece of hardware!
> But its an ARM Cortex M4 and from what i remember Alex would prefer to
> have it on a 64bit machine as much as possible?
Not just "prefer" ... There is no way to run PilOS on 32-bits. Besides
the fact that there is
an change
the firmware. Do you think it would be possible to get PilOS running on this?
It is ARM, and has a lot of convenience to it: USB A, LEDs, button, 22 GPIO,
and best of all it's named Pico!
http://www.espruino.com/Pico
Rob
I was checking out Espruino. It has a jumper to 'Boot to' where you can
change the firmware. Do you think it would be possible to get PilOS running
on this? It is ARM, and has a lot of convenience to it: USB A, LEDs,
button, 22 GPIO, and best of all it's named Pico!
http://www.es
Hi Rob,
> I posted it on HN: https://news.ycombinator.com/item?id=9954773
Great! Thanks! :)
♪♫ Alex
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Yes, thank you very much, Alex!
I posted it on HN: https://news.ycombinator.com/item?id=9954773
I am amazed at what you have done and are doing with your creation!
Rob
On Mon, Jul 27, 2015 at 6:17 PM, wrote:
> Great! Thanks Alex!
>
> - Original Message -
> From: Alexander Burger [mail
Great! Thanks Alex!
- Original Message -
From: Alexander Burger [mailto:a...@software-lab.de]
To: picolisp@software-lab.de
Sent: Mon, 27 Jul 2015 11:24:07 +0200
Subject:
On Sat, Jul 25, 2015 at 11:13:55AM +0200, Alexander Burger wrote:
> There should really be an article about that in pic
On Sat, Jul 25, 2015 at 11:13:55AM +0200, Alexander Burger wrote:
> There should really be an article about that in picolisp.com :(
Done! :)
http://picolisp.com/wiki/?rcsim
♪♫ Alex
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Hi Rob,
> How would you even start to write a VGA driver/device in PicoLisp
> or pil-assembly?
Ha! I just found an old version of RcSim, from 1991, running on DOS,
using 16-color VGA graphics (and also one using B/W CGA ;). I didn't
remember at all that I had already implemented all that stuff ba
By 'above' I was referring to the thread above, where I was asking about
pil-assembly, and you replied 'Lisp'. I was just clarifying for myself that
it was PicoLisp you were referring to, and not Common Lisp, SBCL or
otherwise.
I would love to help with RC-Sim on PilOS if I ha
logistics that entails. Would you stick with z3d.l or create something
> wholly new? Sounds exciting.
Yes, "lib/z3d.l" would have to be rewritten.
But that's by far not the problem. Rather trivial. The REAL problem is
to get a decent Video mode (SVGA?, VESA?,
me from a
> > learning perspective.
>
> Good :)
>
> And you brought me to the idea of porting RcSim :) I think I'll
> investigate that more. This should be the first real "application"
> in PilOS.
>
>
> > When you say "@lib/z3d.l" is in
Hi Rob,
> I'll keep hacking away at it, since the payoffs are big for me from a
> learning perspective.
Good :)
And you brought me to the idea of porting RcSim :) I think I'll
investigate that more. This should be the first real "application"
in PilOS.
> When you
I'm starting to understand what PilOS really is, thanks to your patient
explanations.
I'll keep hacking away at it, since the payoffs are big for me from a
learning perspective.
I don't need a typical system - gcc, clibs, or a gui. I was trying to
follow some of the rosetta cod
On Fri, Jul 24, 2015 at 04:30:53PM +0200, Alexander Burger wrote:
> So you must first port X11 and OpenGL to PilOS. A surely interesting
> task ;)
.. especially as there is no C compiler yet (and probably also not in
the future). So it must be done in Lisp and/or pil-assembly.
Of course
Hi Robert,
> I tried saving a file (3dtext.l) to the misc directory in PilOS, but I
> could not see it when using the (dir "misc"). I am suspecting I need to
> write it and save it from within PilOS?
You can put a file into a directory while building the PilOS image:
Enter
I tried saving a file (3dtext.l) to the misc directory in PilOS, but I
could not see it when using the (dir "misc"). I am suspecting I need to
write it and save it from within PilOS?
How to add a library to PilOS such as the OpenGL one that is native to the
64bit PicoLisp distribution? D
bit hole though, since I have learned heaps
> about DMA and qemu, and I have even started to look into Alex's code. Now,
> back to PilOS!!!
>
> Rob
>
> On Tue, Jul 21, 2015 at 7:18 PM, Joe Bogner wrote:
>>
>> Hi Rob,
>>
>> I'm using qemu-2.0.9.1 on
code. Now,
back to PilOS!!!
Rob
On Tue, Jul 21, 2015 at 7:18 PM, Joe Bogner wrote:
> Hi Rob,
>
> I'm using qemu-2.0.9.1 on win64 with pilos and it works fine
>
> I downloaded it from here:
>
> http://qemu.weilnetz.de/w64/qemu-w64-setup-20140715.exe
>
> Later versio
Hi Rob,
I'm using qemu-2.0.9.1 on win64 with pilos and it works fine
I downloaded it from here:
http://qemu.weilnetz.de/w64/qemu-w64-setup-20140715.exe
Later versions, including qemu-w64-setup-20150503.exe did not run for me
Hope that helps
On Mon, Jul 20, 2015 at 6:10 AM, Robert H
On Tue, Jul 21, 2015 at 03:26:03PM +0800, Robert Herman wrote:
> Thanks for the boost, Alex. I'll do some work on my own now, and get back
> to you. I am going to try more qemu versions, then I am going to try
> modifying or rewriting the bios file in qemu to see if I can bypass this
> limit.
Yes,
Thanks for the boost, Alex. I'll do some work on my own now, and get back
to you. I am going to try more qemu versions, then I am going to try
modifying or rewriting the bios file in qemu to see if I can bypass this
limit. I guess it is trying to emulate the x86-64 architecture to the bit,
so maybe
On Mon, Jul 20, 2015 at 08:30:01PM +0800, Robert Herman wrote:
> Is there a way to change a qemu bios file config?
The man page of qemu-system says "QEMU uses the PC BIOS from the Seabios
project and the Plex86/Bochs LGPL VGA BIOS". But there is also a
-bios file
option. I haven't tried.
>
look in the source to
> > troubleshoot this myself? Exciting fun anyhow, so no complaints here!
>
> The place where this happens is "pilos/x86-64/beg.l", line 26 ff
>
>mov $DAP, %si # Disk Address Packet
>mov $0x42, %ah# Extend
And interesting: This seems to be the first time that error
number 09 appears.
> How can I fix it or keep moving on? Where do I look in the source to
> troubleshoot this myself? Exciting fun anyhow, so no complaints here!
The place where this happens is "pilos/x86-64/beg
do I look in the source to
troubleshoot this myself? Exciting fun anyhow, so no complaints here!
Rob
On Mon, Jul 20, 2015 at 1:32 PM, Alexander Burger
wrote:
> Hi Robert,
>
> > First, I would like to donate some money anyway, seeing how much fun I
> have
> > had with PicoLis
Hi Robert,
> First, I would like to donate some money anyway, seeing how much fun I have
> had with PicoLisp and PilOS.
Thanks, that's very nice! But don't worry, that's not what I'm looking
for. I need some stable, long-term project(s) ;)
> Second, I get a &
Alex,
First, I would like to donate some money anyway, seeing how much fun I have
had with PicoLisp and PilOS.
Second, I get a 'Guest has not initialized the display (yet).' when trying
to run PilOS in qemu on my i5 Windows 8.1 64bit machine. Any steps I am
missing? I am a qemu newbie,
On Wed, Jul 15, 2015 at 11:05:42AM -0400, Rick Lyman wrote:
> Which board would you like to start with?
Suggestions? As I said, this is in the far future. And - as nobody is
going to pay for it - this will not be too soon, I'm afraid.
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubs
Which board would you like to start with?
On Wed, Jul 15, 2015 at 10:55 AM, Alexander Burger
wrote:
> Hi Rick,
>
> > >In the future, we might think of utilizing it in embedded systems
> >
> > Meaning ARM boards?
>
> Yes, this too. But first pil64 must be ported to ARMv8. This is on my
> todo lis
Hi Rick,
> >In the future, we might think of utilizing it in embedded systems
>
> Meaning ARM boards?
Yes, this too. But first pil64 must be ported to ARMv8. This is on my
todo list since a long time, but I don't have the necessary hardware.
♪♫ Alex
--
UNSUBSCRIBE: mailto:picolisp@software-lab
Alex,
>The PicoLisp Operating System
>on standard PC hardware
>In the future, we might think of utilizing it in embedded systems
Meaning ARM boards?
Thanks,
-rl
On Fri, Jul 10, 2015 at 07:03:28PM +0200, Alexander Burger wrote:
> > What could PilOS be used for?
> ...
And of course it represents the essence of PicoLisp: Being totally in
control, and knowing every single machine instruction in your machine
personally.
This thrill alone was worth t
Hi Rick,
> > PilOS is complete so far
Well, to be honest, not completely complete. The most interesting part
is still missing, but that's not an OS-issue, but a matter of PicoLisp
internals: Parallelize parts of the interpreter to employ multiple CPU
cores. First will be the garbag
Alex,
> PilOS is complete so far
What could PilOS be used for?
Does it have any way of communicating with the outside world?
(http://lwip.wikia.com/wiki/Porting_For_Bare_Metal)
Any thoughts re: IOT: eg:
http://www.adafruit.com/products/2112?gc
14-21-Porting%20and%20testing%20a%20TCPIP%20stack%20without%20an%20ethernet%20driver.pdf
> https://news.ycombinator.com/item?id=8537645
> http://www.embedded.com/design/prototyping-and-development/4237636/Bare-metal-embedded-software-development-with---without-an-RTOS
Thanks for the links!
Howe
Hi Rick,
> Do we need to re-invent the wheel here? maybe we could leverage:
>
> https://en.wikipedia.org/wiki/BareMetal
> https://github.com/ReturnInfinity/BareMetal-OS
> http://www.returninfinity.com/baremetal.html
> http://www.osnews.com/story/27566/BareMetal_OS_gets_TCP_IP
Yes, I've seen it.
t;
> > I think i got some leads why some of us got stuck with "Checking long
> mode"
> > What i noticed is the that if i insert some message printing on most
> > parts of the code between "Loading PilOS" and "Checking long mode", i
> > will
, Alexander Burger
wrote:
> Hi Geo,
>
> thanks for the investigations!
>
> > I think i got some leads why some of us got stuck with "Checking long
> mode"
> > What i noticed is the that if i insert some message printing on most
> > parts of the code between
Hi Geo,
thanks for the investigations!
> I think i got some leads why some of us got stuck with "Checking long mode"
> What i noticed is the that if i insert some message printing on most
> parts of the code between "Loading PilOS" and "Checking long mode&q
Hi Alex,
I think i got some leads why some of us got stuck with "Checking long mode"
What i noticed is the that if i insert some message printing on most parts of
the code between "Loading PilOS" and "Checking long mode", i will arrive on the
real error which is &qu
Hi Geo,
> Indeed! ok so time to install qemu.. but hmm if the current pilOS
> works on your qemu then it would not help right? Or does qemu also
> depends on its host hardware that its running?
I think it doesn't. After all, qemu can emulate various systems.
> Hmmm might be
Hi Alex,
> The problem is that this is a bit tedious (unless using e.g. qemu)> because
> you have to put the test onto the USB-stick each time and reboot> the test
> machine with it.
Indeed! ok so time to install qemu.. but hmm if the current pilOS works on your
qemu then it
I believe that the 'cpuid' instruction cannot loop or crash. Rather, I
suspect that for some reason the following messages are not printed
because the CPU got into an unknown state.
> it possible to have a debug mode for PilOS that it will not overwrite
> the messages?
Yes. What
Hi Mattias + Geo,
> Alex, you already got the following results, I'm just reposting them to the
> list
> as well.
Yes, thanks!
> I have tried PilOS on the following machines:
> ...
> *Lenovo Thinkpad x201i, i3 cpu
> Fails with the message "READ ERROR 08"
e btw?
> The checks are done in "pilos/x86-64/beg.l" starting from line 32. If> the
> checks were successful, it should next print "Initializing memory".>
> Otherwise, we should see "ERROR: CPU does not support long mode" or> "ERROR:
> CPU h
room and feedback to you how it goes... this is great!!
I ran into the same message when trying to boot PilOS on an Asus UL30A,
this machine has a core2duo cpu.
Alex, you already got the following results, I'm just reposting them to the list
as well.
I have tried PilOS on the following mac
Hi Geo,
> Another feedback is i try to boot it on my VirtualBox and I'm seeing
> "Loading PilOS" but its already a while, is this expected?
No, it all goes in a tiny fraction of a second. Normally, you don't see
any of the messages.
I think other people also tri
Hi Alex,
Another feedback is i try to boot it on my VirtualBox and I'm seeing "Loading
PilOS" but its already a while, is this expected?
BR,Geo
On Wednesday, July 8, 2015 4:41 PM, George Orais wrote:
Hi Alex,
> Oops, sorry. My fault! "init/.pil/history&quo
the check for long
mode doesn't work? I would at least expect an error message.
The checks are done in "pilos/x86-64/beg.l" starting from line 32. If
the checks were successful, it should next print "Initializing memory".
Otherwise, we should see "ERROR: CPU does not suppo
Hi Alex,
> Oops, sorry. My fault! "init/.pil/history" was added recently, and I> forgot
> to include it into the release script.>> Please download once more
> "pilos.tgz".
Yes! i was able build the image and immediately tried it using my USB stick,
it's working!!! but I'm stuck at "Checking lon
Hi Geo,
thanks for the feedback! :)
> I tried building them and here is what i get:
> * First release: make will generate x86-64.bin* Latest release: make:
> *** No rule to make target `init/.pil/history', needed by `db.bin'.
Oops, sorry. My fault! "init/.pil/history" was added recently, and I
Hi Geo,
> Actually i did try to boot this since from your first release but
> until now i still cant make it boot, it pauses for a while then proceed
> to the default OS stored on the hard drive..
I see. So it isn't even recognized as a bootable USB disk.
> Next plan is to build it
> within the
matter on this?
BR,Geo
On Sunday, July 5, 2015 5:19 PM, Alexander Burger
wrote:
Hi all,
today I got the *first* positive feedback of booting PilOS on a physical
machine (i.e. not qemu etc.), from Mattias Sundblad. Thanks again!
Strange that nobody else seems to succeed (or has
?
BR,Geo
On Sunday, July 5, 2015 5:19 PM, Alexander Burger
wrote:
Hi all,
today I got the *first* positive feedback of booting PilOS on a physical
machine (i.e. not qemu etc.), from Mattias Sundblad. Thanks again!
Strange that nobody else seems to succeed (or has ever tried
Hi all,
today I got the *first* positive feedback of booting PilOS on a physical
machine (i.e. not qemu etc.), from Mattias Sundblad. Thanks again!
Strange that nobody else seems to succeed (or has ever tried?)!
.. after quite some hype here about PilMCU and later PilOS.
I'd like to fin
On Mon, Jun 29, 2015 at 08:02:06PM +0200, Alexander Burger wrote:
> It seems that virtualbox doesn't support BIOS 0x13 interrupts for
> "Extended Read Sectors" calls.
>
>
> > It still freezes on the black screen Loading PilOS
>
> We guessed that from the
Hi Joe,
> The new version boots fine on qemu under windows 7 x64. Under
> virtualbox on the same platform, get stuck with a black screen that
> says Loading PilOS with nothing else displayed
For the mailing list: We discussed this in IRC just now.
It seems that virtualbox doesn'
Hi Alex,
The new version boots fine on qemu under windows 7 x64. Under
virtualbox on the same platform, get stuck with a black screen that
says Loading PilOS with nothing else displayed
This is how I converted the image
"c:\Program Files\qemu\qemu-img.exe" convert -O vmdk x86-64.i
Hi all,
it seems that there are still problems with booting PilOS.
While it works for me (on Qemu and on my Acer notebook), it hear that on
other emulators or hardware people just see a black screen. So I would
be glad to find out the reason(s).
One reason might be that the image is not
Exciting! Thank you very much, Alex!
On 19.06.2015 22:16, Alexander Burger wrote:
Hi all,
I'm happy to announce PilOS - The PicoLisp Operating System!
Hi Kuba,
Thanks! Will check it out and PM you how it goes.. cheers!
-geo
On Monday, June 22, 2015 10:00 AM, Kuba Tyszko wrote:
Hi Geo,
How about ready-made code to support sdram on altera?:
https://github.com/stffrdhrn/sdram-controller
This was written by my buddy Stafford Horne
Hi Geo,
How about ready-made code to support sdram on altera?:
https://github.com/stffrdhrn/sdram-controller
This was written by my buddy Stafford Horne
Give it a try and let me know how it goes...
Cheers
Sent from my iPhone
> On Jun 21, 2015, at 20:36, George Orais wrote:
>
> Hi Alex,
>
Hi Alex,
I see! That's indeed great, thanks! This is really good stuff Alex.
Hi Kuba,
Sorry the progress was so slow because crazy schedule at work.. for pilMCU I'm
stuck with mobile DDR SDRAM interface, it's not as straight forward as SRAM so
tentatively i'm planning to fabricate a FPGA board w
Great stuff,
I was just going to ask Geo whether this means to end of Picolisp on fpga...
I just tried PilOS - works on my qemu, will try on my actual PC later and
report back.
Cheers
> On Jun 21, 2015, at 12:15 AM, George Orais wrote:
>
> This is great! Will try it soon, thanks!
Hi Geo,
> btw, if ever pilMCU is implemented, will PilOS work immediately over it?
Yes, the PicoLisp VM asm sources are the same. Just the low-level
interfaces, boot procedure etc. are different. I don't want to maintain
the pilMCU source tree separately, so we can backport to pilMCU
This is great! Will try it soon, thanks!
I'm really sorry about pilMCU, actually I'm still pursuing to build it but as
of the moment time is not on my side... but still hoping someday soon... btw,
if ever pilMCU is implemented, will PilOS work immediately over it?
On Saturda
Thank you!
On 19/06/15 22:16, Alexander Burger wrote:
> Hi all,
>
> I'm happy to announce PilOS - The PicoLisp Operating System!
>
> It is a modification of the infamous PilMCU, which unfortunately doesn't
> seem to get off the ground. So in order not to have
. Are you considering adding networking support in the
future? I imagine that would be quite difficult.
On Fri, Jun 19, 2015 at 4:16 PM, Alexander Burger
wrote:
> Hi all,
>
> I'm happy to announce PilOS - The PicoLisp Operating System!
>
> It is a modification of the in
to play with. Are you considering adding networking support in the
> future? I imagine that would be quite difficult.
>
> On Fri, Jun 19, 2015 at 4:16 PM, Alexander Burger
> wrote:
>>
>> Hi all,
>>
>> I'm happy to announce PilOS - The PicoLisp Operating Sy
py to announce PilOS - The PicoLisp Operating System!
>
> It is a modification of the infamous PilMCU, which unfortunately doesn't
> seem to get off the ground. So in order not to have wasted all that
> effort, I decided to let it run on standard PC hardware, basically
> directly o
Hi all,
I'm happy to announce PilOS - The PicoLisp Operating System!
It is a modification of the infamous PilMCU, which unfortunately doesn't
seem to get off the ground. So in order not to have wasted all that
effort, I decided to let it run on standard PC hardware, basically
direct
99 matches
Mail list logo
