SqueakNOS September 2008

squeaknos@lists.squeakfoundation.org

11 participants
19 discussions

Wiki link a SqueakSource
by Karl Ramberg 07 Oct '08

07 Oct '08

Hi, it's really fun this project is moving again. I look forward to using it as default on my XO. The Squeak wiki links at SqueakSource uses the old minnow addresses, could someone with login update ? Karl

4 8

XO for testing
by Juan Vuletich 30 Sep '08

30 Sep '08

Hi folks, Gera, I've heard you're in need of a second XO for testing. I have one! We can meet one of these days, if you like. Write to me off-list to coordinate details. Cheers, Juan Vuletich Ps. I sent this to the list because I had problems trying to write to you directly.

1 0

SqueakNOS on OSNews
by Karl Ramberg 29 Sep '08

29 Sep '08

Osnews runs a brief story about SqueakNOS. http://www.osnews.com/ Most comments are about how useless this project is, I guess they have not used Squeak ;-) Karl

2 1

Re: SqueakNOS OLPC
by Daniel Demski 28 Sep '08

28 Sep '08

I upgraded to firmware q2e18 and squeakOS worked! So something on the OLPC wiki misled me as to whether q2e14 was the latest (that had been my version). First impression, the touchpad isn't as sensitive as it could be! Is there built in Squeak functionality for adjusting that?

1 0

Re: SqeakNOS OLPC
by Gerardo Richarte 27 Sep '08

27 Sep '08

Daniel Demski wrote: > Hi, I don't know if you're the right person to ask (ie > should I be wasting your time) but, I am trying to boot > squeakNOS on my XO. Yes, that's absolutely me, and don't worry about bothering me, I'm interested in feedback, so, thank you for contacting me. I'm also copying the SqueakNOS list, in case anbyody has the same problem, and to keep this archived on the net. > I followed the instructions but had to > rename the files (ge Squeak~1.ima) by hand since I was on > Linux. I think that if you copied the files in order (first .kernel then .image) to a vfat (fat/DOS) formated file system, then the file names should have been ok, even if you see them as full names in Linux, but renaming them manually shoudn't harm. > After that it found the files- it loads the kernel > then loads the image, then it restarts, repeating endlessly. > So I tried the squeakNOS 08 August image and it behaved the > same. > Uhm, let's try something, and if that fixes it, I'll add it to the howto: update your XO's firmware to the latest version as directed by http://wiki.laptop.org/go/Firmware let me know what happened, I guess that's the problem. Also please, before upgrading, check your current version, so we can know (and say) that with that specific version you absolutely need to upgrade before trying SqueakNOS. thanks! gera

1 0

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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

SqueakNOS September 2008