Calling all small keyboards
Texas Instruments, "Speak and Spell", I bought one in about 1980. Very small keyboard lay out. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Evil code-sharing hacks?
Here is a fun and amusing "easy weekend project" for an enterprising activity author: Implement a "code sharing" demo as follows: 1. stub out a collaborative "RemoteControl" activity (perhaps based on Chat, Xavier, or Distribute)... 2. which, when started fresh, asks you to select an activity compatible with RemoteControl to be launched in the container of the RemoteControl instance under the control of said instance, 3. which, when shared, causes both the RemoteControl instance and the controlled activity instance to be shared, and 4. which, when joined, transfers the code of the controlled activity to the joining RemoteControl instance which promptly instantiates its own controlled instance and directs that instance to join the shared controlled instance. (Some questionable modifications to activities may be needed in order to make them conform to this control flow. Follow the plan described above at your own risk and be prepared for rotten tomatoes. :) Regards, Michael ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Cannot boot joyride-2200 from USB stick
Deepak Saxena wrote: > Sigh++ Bought a 1G microSD with a usb adapter and it happens to be one > that OpenFirmware cannot talk to so I can't boot off it. Just wanted > to give you an update that this is still on my plate, just seems to be > hitting every roadblock in the way of solving it. :O > > ~Deepak > One more data point. After some initial peeking in the ramdisk, I copied the 2212 ext3 image to a SD card, inserted it in the XO and tried to boot from it. That works !!! Of course, no activities since /home/olpc is also on the SD card and the jffs does not get mounted. So it seems USB is the problem. There is one warning message early in the boot at approximately 2 seconds about using an obsolete function in the sd driver, to use bus-methods instead. I am writing from memory, so this is not exact. Could this have something to do with it, since the sd driver is needed for USB? Regards Ton van Overbeek ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: electricity table (Google Docs)
On Tue, Jul 22, 2008 at 3:49 PM, Richard A. Smith <[EMAIL PROTECTED]> wrote: > [EMAIL PROTECTED] wrote: > >> I was also wondering if you could give me feedback on this table. The >> table shows how much kWh is needed a year to power a xo based on >> different scenarios. If you think I should add or change anything > > As I often state in my discussions on laptop power, calculations like > this are actually pretty complex and the simplistic approach while good > for ballpark estimations can have a large amount of error. > > First as others pointed out you units are wrong. You need to substitute > Watts every where you have kW. > > The next issue is that you are assuming a perfect conversion on the > recharge half of your cycle. Which is not correct. The avg power draw > of 5-7 watts for the XO is measured internally either via the battery > sensor or by our instrumented XO. It does not take into account the > efficiency of the DC/DC converter when recharging the XO from external > power. > It also does not take into consideration the charge efficiency of the > battery. It takes more power charge a battery than just the usable > capacity of the battery. > > The DC/DC converter's efficiency is affected by the difference between > the input voltage and the output voltage. We don't really have any > numbers on the exact range of efficiency for the XO @ 12V but typically > your average DC/DC converter is around 85%. The 88% number pops into > mind from when I was last looking at such things. > > Then there is the charge efficiency. Which is more complex because its > actually 2 numbers. One for constant current (CC) charge mode and then > another for constant voltage (CV) charge. The batteries start off in CC > mode and then switch to CV mode after certain criteria are reached the > criteria happens around the same time but is a bit different for each > battery and much more different between the 2 types of batteries. > > I don't have numbers for these efficiencies. The EC code has comments > with magical constants that suggest certain numbers for these values but > I've learned that a lot of those comments may be wrong or apply to > earlier versions of the batteries. The range suggested is 80 - 90%. would (somehow) updating these magical constants for current batteries (depending on LiFe or NiCad chemistries) improve anything? bobby > The only way to know exactly what a good average for charge efficiency > is would be to measure and compare the power in with power out across > several batteries of each type (remember we have 2 chemistries). > > Thats possible in the case where the XO is powered up and you can read > the battery sensor, but when the XO is off its not so easy. Guess what? > Your %'s will be different in the 2 cases because the charge rate is > much faster when the XO is off. > > Buts lets just say for a quick ball park that DC/DC is 88% and average > battery CE is 85%. Now your recharge numbers are off by about 25%. > > Listing things in "cranking hours" may also be problematic. If you > really were cranking some human power device your output would be so > variable that the only way to get meaningful data is to measure it and > develop some sort of profile for what the average person can really do. > > -- > Richard Smith <[EMAIL PROTECTED]> > One Laptop Per Child > ___ > Devel mailing list > Devel@lists.laptop.org > http://lists.laptop.org/listinfo/devel > ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: New joyride build 2216
if packages are included or updated from people using their public_rpms directory on dev.laptop.org, they have to update a changelog file references the new rpm. it is _recommended_ they list the changes, but not mandatory. that is my understanding anyway. I don't think updates pulled in from F9 have changelog information available for buildannouncer. bobby On Sat, Jul 26, 2008 at 2:54 PM, <[EMAIL PROTECTED]> wrote: > i think i saw the reason for this at some point, but why do > some joyride announcements have changelog messages included, > and some (like this one) do not? > > paul > > build announcer v2 wrote: > > http://xs-dev.laptop.org/~cscott/olpc/streams/joyride/build2216 > > > > Changes in build 2216 from build: 2214 > > > > Size delta: 0.00M > > > > -xkeyboard-config 1.3-1.olpc3 > > +xkeyboard-config 1.3-2.olpc3 > > > > -- > > This mail was automatically generated > > See http://dev.laptop.org/~rwh/announcer/joyride-pkgs.html for aggregate > logs > > See http://dev.laptop.org/~rwh/announcer/joyride_vs_update1.html for a > > comparison > > ___ > > Devel mailing list > > Devel@lists.laptop.org > > http://lists.laptop.org/listinfo/devel > > =- > paul fox, [EMAIL PROTECTED] > ___ > Devel mailing list > Devel@lists.laptop.org > http://lists.laptop.org/listinfo/devel > ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Calling all small keyboards
> We are looking for examples of keyboards for small children > present before 1993. > > Specifically, we are looking for keyboards whose key-key spacing > is between 10.8 and 16.4 mm horizontally, and 10.8 to 18.0 mm > vertically, and with a stroke distance of 0.9 to 6mm. This article offers several candidates: http://www.pcworld.com/article/139100/the_10_worst_pc_keyboards_of_all_time.html One I remember here in Australia was the Tandy (Radio Shack) TRS-80 Color Computer 1 with the rubber "chiclet" keyboard. From memory the key spacing was closer than normal, though the small keytops may have been deceptive; the stroke is definitely in the right ballpark (later CoCo 2 keyboards were "full travel".) Good luck with your quest. -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Paul Taylor Veni, vidi, tici - [EMAIL PROTECTED]I came, I saw, I ticked. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: calling all small keyboards
The classic is the Texas Instruments Speak & Spell, introduced in 1978. http://en.wikipedia.org/wiki/Speak_&_Spell_(game) ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Calling all small keyboards
Hi The UK's Sinclair Spectrum may well be what you are looking for - it was tiny ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
devel@lists.laptop.org
You might find what you are looking for here: http://en.wikipedia.org/wiki/Chiclet_keyboard ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Calling all small keyboards
Hi. I found some toys on the internet, I do not own any of those. http://www.datamath.org/Speech/MouseComputer.htm http://www.datamath.org/Speech/ComputerFun.htm http://www.datamath.org/Speech/ComputerFun_UK.htm http://www.datamath.org/Speech/ComputerFunD.htm SALUDOS ALVARO ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: New joyride build 2216
i think i saw the reason for this at some point, but why do some joyride announcements have changelog messages included, and some (like this one) do not? paul build announcer v2 wrote: > http://xs-dev.laptop.org/~cscott/olpc/streams/joyride/build2216 > > Changes in build 2216 from build: 2214 > > Size delta: 0.00M > > -xkeyboard-config 1.3-1.olpc3 > +xkeyboard-config 1.3-2.olpc3 > > -- > This mail was automatically generated > See http://dev.laptop.org/~rwh/announcer/joyride-pkgs.html for aggregate logs > See http://dev.laptop.org/~rwh/announcer/joyride_vs_update1.html for a > comparison > ___ > Devel mailing list > Devel@lists.laptop.org > http://lists.laptop.org/listinfo/devel =- paul fox, [EMAIL PROTECTED] ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
New joyride build 2216
http://xs-dev.laptop.org/~cscott/olpc/streams/joyride/build2216 Changes in build 2216 from build: 2214 Size delta: 0.00M -xkeyboard-config 1.3-1.olpc3 +xkeyboard-config 1.3-2.olpc3 -- This mail was automatically generated See http://dev.laptop.org/~rwh/announcer/joyride-pkgs.html for aggregate logs See http://dev.laptop.org/~rwh/announcer/joyride_vs_update1.html for a comparison ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Calling all small keyboards
> We are looking for examples of keyboards for small children > present before 1993. A request for clarification here. Are you looking for keyboards designed for small children, or for keyboards and devices with keyboards that meet your size specs? > Specifically, we are looking for keyboards whose key-key spacing > is between 10.8 and 16.4 mm horizontally, and 10.8 to 18.0 mm > vertically, and with a stroke distance of 0.9 to 6mm. One I remember from c. 1981 was the Panasonic HHC. Here's a link 'http://www.old-computers.com/museum/computer.asp?st=1&c=644'. Search 'Panasonic HHC' or '1400' and you'll find several. The machine was 95 x 227 mm. As there were five rows of keys taking up most of the height, I'd guess about 12mm pitch. Bob ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Calling all small keyboards
as i mentioned to wad the other day, the fujitsu Poqet PC may also qualify as prior art. (a full IBM PC, and 100 hours on 2 AA batteries. what more could you ask for?) =- paul fox, [EMAIL PROTECTED] ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Calling all small keyboards
And, as has been mentioned on Groklaw http://www.groklaw.net/comment.php? mode=display&sid=20080725152355696&title=OLPC+%3A+++Calling+For+Small +Keyboards+Prior+Art%2C++pre +1993&type=article&order=&hideanonymous=0&pid=714454#c714472 http://www.groklaw.net/comment.php? mode=display&sid=20080725152355696&title=Here+it +is&type=article&order=&hideanonymous=0&pid=714474#c714475 references this Wikipedia article: http://en.wikipedia.org/wiki/TRS-80_MC-10 Looking around for a diagram for the thing, I get this page on chiclet keyboards, with a moderate list of potential suspects (wikipedia again): http://en.wikipedia.org/wiki/Chiclet_keyboard (I cannot help shaking my head in disgust at those patents. Shades of children calling "DIBS!" And let's make it all legal-like and bring back the old patronage system, while we're at it, but I'm being redundant, I know.) Joel Rees (waiting for a 3+GHz ARM processor to come out, to test Steve's willingness to switch again.) ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Calling all small keyboards
It was not specifically designed for children, but the Atari Portfilio had a small keyboard, probably about 12 mm spacing. It was designed in the UK by DIP and marketed by Atari beginning in 1989. I bought mine in 1990. It was 200 mm x 100 mm x 28 mm, about the same size as a VHS videocassette. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Submitting errors in the mfg data
Hello, How do I submit errors in the Manufacturing data (mostly typos in the keyboard layout related section) ? Thanks, Sayamindu -- Sayamindu Dasgupta [http://sayamindu.randomink.org/ramblings] ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: New joyride build 2213
On Friday 25 July 2008, Daniel Drake wrote: > Bert Freudenberg wrote: > > Am 25.07.2008 um 17:29 schrieb Build Announcer v2: > >> http://xs-dev.laptop.org/~cscott/olpc/streams/joyride/build2213 > >> > >> -gnome-python2-gnomevfs 2.22.1-5.olpc3 > >> +gnome-python2-gnomevfs 2.22.1-3.olpc3 > > > > Was this intentional? > > Yes, it's the same package, I just moved it from public_rpms into Fedora > proper. At the same time I resynced the version numbers to follow on > directly from F9 (which is currently at 2). Its too late now. but you should have added a .1 so it would have been gnome-python2-gnomevfs 2.22.1-2.olpc3.1 this way you konw exactly what fedora build its based on -- Dennis Gilmore signature.asc Description: This is a digitally signed message part. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Calling all small keyboards
This is probably not what your looking for but have you taken into account the ZX81 spectrum computer , tiny keyboard , see here , http://www.gondolin.org.uk/hchof/machines/spectrum.html -- Andrew Crosbie F24 CDO FSE ASM Services & Support Ireland Ltd TEL: 353(0)160 66619 E-mail: [EMAIL PROTECTED] E-mail: [EMAIL PROTECTED] -- Disclaimer: This e-mail may contain privileged or confidential information for the sole use of the intended recipients. If you are not the intended recipient, you are hereby notified that you may not derive any rights from the information contained herein and any use, dissemination, or reproduction is strictly prohibited and may be unlawful. P Please consider the environment before printing this e-mail - Intel Ireland Limited (Branch) Collinstown Industrial Park, Leixlip, County Kildare, Ireland Registered Number: E902934 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Techteam] NAND full issue
On Fri, Jul 25, 2008 at 9:27 PM, Deepak Saxena <[EMAIL PROTECTED]> wrote: > On Jul 25 2008, at 20:00, Daniel Drake was caught saying: >> So unionfs is the "formal bug fix for 8.2 going forward", or is it a >> Uruguay-specific thing? >> >> unionfs will involve a kernel change. Are we planning to shift them from >> 2.6.22 to 2.6.25 where unionfs has been included, or are we going to >> backport unionfs to 2.6.22? >> >> Also, I am a little wary of unionfs, I have used it in the past and >> found it to be buggy and unreliable. It may be better now, but we should >> be cautious. > > I've done an analysis of the UFS code and it may be possible to > have a standalone unionfs module w/o changes to core kernel. See [1] > for my email sent to UFS maintainers and list. My concern is that > by forking the code this way, we're introducing another variable. > > However... Erik has been using AUFS[2] as UFS was crashing badly and > not allowing sugar to boot. AUFS is completely standalone and requires > no changes to the deployed kernel. This is also non-upstream so we should > run it through some form of stress test in our desired configuration. > > ~Deepak > > [1] http://www.fsl.cs.sunysb.edu/pipermail/unionfs/2008-July/005895.html > [2] http://aufs.sourceforge.net/ > This might be old news, but Knoppix (the original linux live CD) changed from unionfs to aufs some years ago with good results. I suppose you could ask Klaus Knopper about his experiences with the reliability of aufs. See www.knopper.net (in German) or www.knoppix.com (in English). HTH Ton van Overbeek ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
