SqueakNOS

squeaknos@lists.squeakfoundation.org

87 discussions

OFWDeviceNode findDevice: '/memory'
by Gerardo Richarte 24 Sep '08

24 Sep '08

As part of interfacing with OpenFirmware we need to access the device tree, nodes and instances. This is the main interface into OFW's support for most things. With help from Mitch Bradley again, the document Luke sent and some time, I managed to implement a base for OFWDeviceNode. mem := OFWDeviceNode findDevice: '/memory' may be working, it answers an instace of OFWDeviceNode with the phandle set however, if I then try mem getPropLen: 'size' to get the size of the property named 'size', SqueakNOS freezes (crashes probably). So I think we may actually be running on the memory problem we (Luke) described in an earlier mail. Or otherwise, some problem derived from the primitive implementation... uhm, this gives me an idea to test what's going on... let's see. richie

1 0

ColaNOS
by Luke Gorrie 22 Sep '08

22 Sep '08

.. moving an offline discussion between me and Gerardo Richarte onto the SqueakNOS mailing list in case others are interested too. We're talking about bringing up SqueakNOS (and NOSen in general) on top of the OLPC XO's Openfirmware (a small Forth OS). 2008/9/21 Gerardo Richarte <gera(a)corest.com>: > My ugly > (http://lists.squeakfoundation.org/pipermail/squeak-dev/2008-September/13160…) > implementation of the callout mechanism is working! > > I can do "interpret"("nand:\") for example, and it works :) Cool :-) > now, I ran into another problem, and I think this is a real problem: > I have two (actually three) different memory managers at this point: Is there an easy way that when starting Squeak you can allocate all the memory you will ever need (e.g. 95% of system memory) for the Squeak heap and runtime system -- and then keep all your own memory allocations inside that and make OFW happy with the leftover 5% that it can keep for itself? (Just an idea.) I've been reading over the C "client interface" towards Openfirmware. The Firmworks manuals are not freely available (and I'm having some trouble buying them) but it turns out to be documented in the IEEE Openfirmware specification -- I didn't think IEEE docs would be on the 'net but happily this one is: http://www.complang.tuwien.ac.at/forth/1275.ps.gz The client interface offers a well-defined interface for opening devices and making calls into their drivers' methods. That's probably just a bit neater than calling into INTERPRET with fragments of Forth source code (and if you want to use custom Forth code you can always load some new methods on the devices presumably). More later :-) > Squeak's (Garbage collection, for which I "allocate" all available > memory starting at 1MB) > SqueakNOS' native memory mamanger (nothing really, just a static > pointer that's incremented on avery alloc() and never decremented) > > and now, Forth's (OFW's) allocator, which I think, interferes and > clashes with the Garbage collector (it returns objects inside the Object > Memory, but this objects are not allocated from Squeak, so the memory is > actually used independently by both at the same time). This will very > easily crash the system (and does as soon as I want to open a file). > > So, this is a problem I have. Not sure if you'll have it (for > example, you could directly relay EVERY memory allocation to OFW, and > let it manage the memory for you... at least to start with). > > richie >

2 1

Grub changes
by John Thornborrow 22 Sep '08

22 Sep '08

Hi all, Where can I get my hands on the changes made to grub (namely for setvbe?) I'm trying to get together a compilation package (ebuild) on gentoo, and will need these sources :) Many thanks, John. ****************************************************************************************************************************************** This email is from Pinesoft Limited. Its contents are confidential to the intended recipient(s) at the email address(es) to which it has been addressed. It may not be disclosed to or used by anyone other than the addressee(s), nor may it be copied in anyway. If received in error, please contact the sender, then delete it from your system. Although this email and attachments are believed to be free of virus, or any other defect which might affect any computer or IT system into which they are received and opened, it is the responsibility of the recipient to ensure that they are virus free and no responsibility is accepted by Pinesoft for any loss or damage arising in any way from receipt or use thereof. ******************************************************************************************************************************************* Pinesoft Limited are registered in England, Registered number: 2914825. Registered office: 266-268 High Street, Waltham Cross, Herts, EN8 7EA

2 3

Monticello update: OpenFirmware "Hello World" primitive
by Gerardo Richarte 19 Sep '08

19 Sep '08

Name: SqueakNOS-gera.48 Author: gera Time: 19 September 2008, 8:39:36 am UUID: 9c80063b-ef62-4ade-bf00-ee8882844db4 Ancestors: SqueakNOS-gera.47 "Hello World" primitive for testing OpenFirmware callout mechanism. This is a hardcoded callout, next step (tomorrow maybe) will be to make it generic, accepting an array. That's enough to use any service provided by OpenFirmware (OFW).

2 1

Monticello update: USB first version sort of coming alive :)
by Gerardo Richarte 14 Sep '08

14 Sep '08

Name: SqueakNOS-gera.47 Author: gera Time: 14 September 2008, 3:30 pm UUID: 37560d3f-2be9-447d-aa75-2fb7ba966a1c Ancestors: SqueakNOS-gera.46 Commented out mouse scrolling, because although it works very nicely in VMWare, it hung the keyboard when booted for real on my Laptop. USB is kind of working, sort of, maybe :) The scheduling for talking to USB devices is somehow complex, right now what we have is more than very basic, and the only thing that works is USBUHCIController >> #testGetDeviceDescriptor In a VMWare, I booted, connected a USB device (only one, from the VMWare menu), and did: Computer current usbUHCIController testGetDeviceDescriptor Inspecting this brings back a 2 elements array, the second is the buffer, if in the inspector you do: (self second stringAt: 1 size: 1000) asByteArray That's going to be the answer from the device. you can compare the bytes from the device, 4 of the first few are the device ID. You can compare that to what lsusb returns (in linux), or something similar on windows (don't really remember right now how to get the USB device IDs on windows). When booting for real, this works much better than previous versions, but I had not finished testing it, as my laptop has 4 UHCI controllers, and I've always been testing in the first (and apparently, that's not where I'm plugging my devices). Good luck! I'll keep working a little bit more :)

1 1

Re: [SqNOS] NOSifying any Squeak image
by Gerardo Richarte 04 Sep '08

04 Sep '08

Mathieu Suen wrote: > > When I load the second package it complain about the missing > SmartSyntaxInterpreterPlugin class. > Is it normal? Oh yes, that's normal too. That's because you don't have VMMaker installed, but that's ok. You only need that if you are going to change any of the primitives and recompile the kernel, but I don't think you'll need to do it. richie PS: I couldn't change the default reply-to for the list yet. I'm formwarding this to the list in case anybody else wants to see it.

1 0

NOSifying any Squeak image
by Gerardo Richarte 04 Sep '08

04 Sep '08

You'll need FFI installed in the image (Universes -> System -> FFI) Then open a Monticello browser, add an HTTP repository as: MCHttpRepository location: 'http://www.squeaksource.com/SqueakNOS' user: '' password: '' Then add another: MCHttpRepository location: 'http://www.squeaksource.com/Net' user: '' password: '' >From the first one load the last version, it'll complain about some missing things, like an SDCommand class. Ignore this, it's a missing poolDictionary, we'll fix it in the near future. Then from the 2nd repository load the latest version, this is TCP/IP by Luciano Notarfrancesco, it'll fix the other missing thing. Open a Transcript, save the image, and reboot. We've tested this with a good number of recent images, and it worked. We also tested it with etoys.image from the OLPC, and it didn't work for some reason, quite probably some uninteligence in how we installed FFI. enjoy! richie

1 0

Re: [SqNOS] Compiling SqueakNOS on Macos
by Gerardo Richarte 04 Sep '08

04 Sep '08

Some news from Methieu Suen, who could rebuild the ISO image without recompiling, just in case somebody else wants to try it: Mathieu Suen wrote: > Cool it work perfectly. I have copy the SqueakNOS.kernel and the > image into the iso.template and run: > mkisofs -J -hide-rr-moved -joliet-long -l -r -b > boot/grub/stage2_eltorito -no-emul-boot -boot-load-size 4 > -boot-info-table -o SqueakNOS.iso iso.template > > in ./boot > > Now I am trying to get the mouse scrolling to work. :) Good look there!!! I think there's a mode for the PS/2 mouse that will just tell it to send the scroller values. You would need to change the initialization code and then the IRQ handling and mouse event generation to handle the extra info. richie

2 3

Re: [SqNOS] Compiling SqueakNOS on Macos
by Mathieu Suen 03 Sep '08

03 Sep '08

oops! yes thanks On Sep 3, 2008, at 6:57 PM, Gerardo Richarte wrote: > don't you want to resend the email to squeaknos(a)lists.squeakfoundation.org > ? > I see if I can change the default reply-to to point to the list. > > thanks, > richie > > Mathieu Suen wrote: >> >> On Sep 3, 2008, at 4:16 PM, Gerardo Richarte wrote: >> >>> Some news from Methieu Suen, who could rebuild the ISO image without >>> recompiling, just in case somebody else wants to try it: >>> >>> Mathieu Suen wrote: >>>> Cool it work perfectly. I have copy the SqueakNOS.kernel and the >>>> image into the iso.template and run: >>>> mkisofs -J -hide-rr-moved -joliet-long -l -r -b >>>> boot/grub/stage2_eltorito -no-emul-boot -boot-load-size 4 >>>> -boot-info-table -o SqueakNOS.iso iso.template >>>> >>>> in ./boot >>>> >>>> Now I am trying to get the mouse scrolling to work. :) >>> Good look there!!! I think there's a mode for the PS/2 mouse that >>> will just tell it to send the scroller values. You would need to >>> change >>> the initialization code and then the IRQ handling and mouse event >>> generation to handle the extra info. >> >> Yeap now I need the scancode of the up and down arrow key. It seems that the scroll generate the ctrl+arrow key event in squeak. Btw should I send the newKeyboardUpEvent: and newKeyboardDownEvent: ? >> >>> >>> >>> richie >>> _______________________________________________ >>> SqueakNOS mailing list >>> SqueakNOS(a)lists.squeakfoundation.org >>> http://lists.squeakfoundation.org/mailman/listinfo/squeaknos >> >> Mth >> >> >> >> >> >> >> >> >> >> ___________________________________________________________________________Yahoo >> ! >> Mail réinvente le mail ! Découvrez le nouveau Yahoo! Mail et son >> interface révolutionnaire. >> http://fr.mail.yahoo.com >> > Mth ___________________________________________________________________________ Yahoo! Mail réinvente le mail ! Découvrez le nouveau Yahoo! Mail et son interface révolutionnaire. http://fr.mail.yahoo.com

1 0

Re: [SqNOS] VMWare appliacen released
by Gerardo Richarte 03 Sep '08

03 Sep '08

Pablo Iaria wrote: > Hola Gerardo, > > Where can I get the vmware appliance? > ups, sorry about that, stupid me. Get it from: https://sourceforge.net/project/showfiles.php?group_id=3891&package_id=3865… I just updated my diary entry with that info... http://people.squeakfoundation.org/person/gera/ thanks for asking. richie

1 0

← Newer
1
2
3
4
5
6
7
8
9
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

SqueakNOS