Bernie Innocenti wrote:
Hello Mitch Scott,
I have a laptop with a developer key, running an unsigned
image with a few customizations for Turkey.
They want a pretty custom logo and I succeeded in getting it to
work in insecure mode, but it looks ugly because they see the
kernel barfing
C. Scott Ananian wrote:
I am in Brazil at the moment, without good access to email. But since
this seems to be a firmware problem, Mitch Bradley is the right person
to help you, at this stage at least. Please check the batteries as
Mitch suggests (photos might be helpful for us to see what's
Ricardo Carrano wrote:
It is possible that the factory neglected to set the date on some
units,
Isn't if the same that we fixed in some units back in December?
http://wiki.laptop.org/go/Fix_Clock
The problem report stated that they are able to activate the machines,
but that the
I have been told that the Uruguay machines are supposed to have good
battery holders, so my earlier suggestion about coin-cell batteries
popping out of the holder might be incorrect. However, we have also
seen a problem where some of the coin-cell batteries are defective, so
it would be
Some of the machines from the first production run had bad battery
holders. Not the main battery, but rather the small coin cell battery
on the mainboard that powers the time-of-day/calendar clock chip. Those
battery holders have a plastic retention lip that holds the coin cell in
place. On
The right answer to the naming question depends on the meta-question of
what will we be releasing.
Are we going to continue down the path of bundling the OS and the
activities into one giant release wad, or will we split out the separate
components (OS, sugar, core activities) and release them
Perhaps it would be better to use a letter instead of a number for the
generation code (major release). When confronted with a string of
several numbers, the human mind tends to blank out. For some reason,
letter - number - number is easier to remember and say than number -
number - number .
It would have been nice if the criticisms had been delivered directly to
OLPC, instead of broadcast in a public forum, where enemies of OLPC can
cite and expand on them as evidence that OLPC is hopelessly screwed up,
so you should buy our competing product instead. If you get my drift.
I
Bryan Berry wrote:
Other than the fact that the firmware security has to be left disabled
to use these commands, are there any technical drawbacks to using these
commands? I use them extensively and hope I am not causing some kind of
damage to our XO's
save/copy-nand don't preserve user
James Cameron wrote:
On Thu, Mar 27, 2008 at 03:23:59PM -0400, Michael Stone wrote:
A much better strategy is to reflash an XO, boot it off of external
media (like a USB key), make changes to the NAND, then save-nand, thus
avoiding the first-boot configuration junk.
I agree, and
John R. Hogerhuis wrote:
On Sun, Mar 23, 2008 at 9:28 PM, Mitch Bradley [EMAIL PROTECTED] wrote:
snip
In any case, the left and right panels can't sense fingertip pressure -
you would have to use a fingernail, and that would override the signal
from capacitive sensor.
OK
John R.Hogerhuis wrote:
...
Are the left and right panels pressure sensitive? If so, they could be used to
dynamically adjust the brush size/weight depending on how hard she pushes.
You can use either the resistive sensor ( left + middle + right with
stylus-class pressure) or the
Michael Veith wrote:
...
Yes, right. I'd prefer a lot more books than only two. And let me
state some kind of -let's call it- insight. I see some parallels
between the manner one reads religious texts like the Bible or the
Koran and the reading of code (at least in object-oriented
Bennett Todd wrote:
2008-03-11T15:18:57 Jameson Chema Quinn:
Now that there are a significant number of laptops in Peru, high-altitude
testing may be more feasible. What test plan would you want followed in
order to be able to raise the specs?
Surely this has to start with the
Regarding the suggestion of LED bulbs - a smart person on another list
said that many brands of LED bulbs are also prone to failure due to bad
power - so don't treat them as a panacea.
___
Devel mailing list
Devel@lists.laptop.org
JFFS2 does automatic compression so every write invokes zlib
compression. That is a rate-limiting factor on this machine - the raw
NAND write speed is several times faster than the compress speed.
For files with large pieces, that compression results in a 2x space
savings. But JFFS2 can
Richard A. Smith wrote:
C. Scott Ananian wrote:
From my brief triage of *only the blocker bugs*, ones which look
important include:
* trac #1407, 2804: touchpad problems
These 2 will probably not make it. They are long standing issues with
the hardware. Dilinger and I have
Stephen Bannasch wrote:
With regard to build406.16. Can I just replace os656.crc and os656.img
in the boot dir on my USB flash stick with os406.icrc and os406.img
and startup with it?
Will build406.16 work with q2d12?
Q2D12 is compatible with all OS builds that have come out in recent
Kim Quirk wrote:
Ok... I think what we haven't defined at this point that is probably
worthy of discussion is:
If or when we will need formalized testing before release.
If we decide that there is a good reason for formalized testing; then
we can put in place the process that ensures we
Gary Oberbrunner wrote:
subbukk wrote:
sftp and scp both require receiver to share login password with sender. nc
doesn't. It just reads/writes bytestreams from/to network sockets. E.g. You
can transfer sub-directories across machines with :
[EMAIL PROTECTED] $ nc -lp | tar xzvf
Patrick Dubroy wrote:
I've got a beta2 machine, and access to a beta4 machine as well. On
the B2, when I boot into the firmware tests and get to the Pen
Tablet/Glide Sensor test, I get absolutely no response from the Pen
Tablet. The Glide Sensor (touchpad) works fine. I've also tried
running
I can make a q2d12 with the fix for 6291. The fix is extremely low risk
- just a change in one number that tells how far to search for
additional nodes in a partially-written block.
The only reason why I haven't made a q2d12 already is because I can't
get to the build server - the machine
It is Q2D11 plus a fix for http://dev.laptop.org/ticket/6291 . It has
Richard's latest EC improvements (as in D11).
http://wiki.laptop.org/go/OLPC_Firmware_q2d12
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
Arjun Sarwal wrote:
Is there a way to switch Off (and subsequently toggle) the +5V USB
power supply on the XO in software ?
Yes, but it's complicated, because
a) the way you do it depends on whether or not the USB 2.0 host
controller has claimed the port.
b) the USB port that controls the
[EMAIL PROTECTED] wrote:
I'm occasionally seeing an issue with the keyboard in recent builds (no
problem on 682, I've seen problems on everything since). This is a G1G1
laptop
Are you using Q2D09 firmware? There have been reports of strange
keyboard behavior as a result of some EC code
manually revert to q2d08 (see the instructions on the wiki page for
q2d08) and remove the bootfw.zip from /versions/boot/current/boot (to
keep it from autoupdating right back to d09) and the problem might go away.
[EMAIL PROTECTED] wrote:
On Tue, 22 Jan 2008, Mitch Bradley wrote:
[EMAIL
llandre wrote:
Hi all,
I have some questions about openfirmware build environment. I could not
find these information on OLCP wiki.
I successfully cloned the git repository and built ofw on x86-64 host
running CentOS, however I'd like to understand exactly how the build
process works. At
You don't really need the entire olpc.fth - the following lines should
suffice:
ok setenv ramdisk n:\boot\olpcrd.img
ok boot n:\boot\vmlinuz root=mtd0 rootfstype=jffs2
Those lines are short enough to type manually.
The rest of olpc.fth is just automated reflash and support for boot-alt.
Most
Jameson Chema Quinn wrote:
I know that we're supposed to all be developers here, and know how to
change the firmware in our sleep; but it would be great to include a
link to instructions. I searched the wiki -
http://wiki.laptop.org/go/Manual_Firmware_Install is worse than
useless, and
Jameson Chema Quinn wrote:
Simple. Put the manual install instructions in
http://wiki.laptop.org/go/Manual_Firmware_Install and then, in
each relnotes page add {{:Manual_Firmware_Install}}, which will
include the text of that page in the one it is as a template in.
Fixed in Q2D08
http://dev.laptop.org/ticket/5717
David Howard wrote:
Saw a short thread with this subject in December 2007.
I also got the SDHCI: Card didn't power up after 1 second message.
The SD is a Toshiba SDHC 4GB.
Q2D07 and 650/653/656 OS. I tried last two on the SD after
Mr frÿffe9dÿffe9ric pouchal wrote:
Hello
I would like to boot OpenFirmware from an USB key
On a conventional PC or an OLPC XO?
The former is supported; the latter could be made to work but will
probably require some changes.
so I
changed the file
Hal Murray wrote:
When it comes to our radio - we *designed it* to start forward frames
soon after you initialize it and keep doing it regardless of what the
host interface does.
In the context of making the radio safe to use on airplanes...
Does the firmware turn the radio on at
Carl-Daniel Hailfinger wrote:
On 17.01.2008 02:02, Mitch Bradley wrote:
Ricardo Carrano wrote:
Hi Mitch!
Would you recommend using firmware version q2d07 on a B2-1 unit?
Yes.
So Q2D07 has been tested on B2-1? How about B1 and B2-2? IIRC there were
Mr frÿffe9dÿffe9ric pouchal wrote:
Hello
I would like to change the screen resoltuion of my
olpc
I have tried to pass an argument to the kernel
video=gxfb:1024x768-16
but it failed
The screen resolution is fixed; it can't be changed.
I also tried to test the DCON with
Martin Dengler wrote:
Hi,
I'm seeing plenty of suspend/resume problems with my G1G1 C2 laptop
(joyride-1532 with firmware q2d08), and I'd like to try the latest
firmware before I file any proper trac bug reports[1]. I can't seem
to find where to download it on the wiki (though it's been
Robert Millan wrote:
Some comments on things that need polishing. Some are more addressed at one
of the two lists than the others, but feel free to join in either case.
(also, if you feel this is off-topic in olpc-devel, feel free to ki^W let
me know)
btw, Mitch mentioned to me on IRC that
Robert Millan wrote:
We used to run trap insttruction on powerpc. I assume for exitting via
trap
on i386 we need to generate an interrupt; I'm just not sure which is the
right
number for it.
To exit to OFW, call the exit() client service.
I see. Is this one
I was wrong about the mmu thing.
I just checked the patch instructions at
http://openbios.org/Open_Firmware and noticed that the patch comments
out create virtual-mode. So if you build with that patch, you get
physical addressing.
I don't know what is right, because this build configuration
ffm wrote:
Will it be auto-installed when I olpc-update to latest joyride, or
will it have to be manualy installed?
Manual.
-ffm
On Jan 9, 2008 4:33 PM, Mitch Bradley [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
http://wiki.laptop.org/go/OLPC_Firmware_q2d08
At today's bug status meeting, I was asked to investigate SD card resume
timing from OFW.
The range was 24 mS to 187 mS , depending on which SD card is plugged in.
The fixed component of that time is about 5 mS, including re-initing the
host controller and issuing a sequence of card commands
The fact that it is trying to boot from the wireless device means that
it didn't find /boot/olpc.fth on either USB, SD, or NAND.
What happens if you type:
ok dir n:\boot\
[EMAIL PROTECTED] wrote:
Dear all,
I updated build 613 into 650 on B4 Machine. For some time, it worked
well. However,
I would like to debug these problems. Find me on IRC - /server
irc.oftc.net /join #olpc-devel . Instances of devices that exhibit
such problems are valuable for discovering where delays are needed.
If would be nice if devices conformed to the published timing
requirements, but alas, many
:
a) Remove all power - AC and battery - for a few seconds to reset the
wireless really well, then reboot and try the POST diags again.
b) If that doesn't fix it, email me when you get your developer key and
I'll work with you on IRC to see if we can learn more about the failure
details.
Mitch
Ivan Krstić wrote:
On Jan 2, 2008, at 10:13 PM, Ricardo Carrano wrote:
How do I do the opposite of copy-nand - copy the OS image _from_ the
nand into a USB key?
If you don't have OFW access or it isn't convenient to have to reboot,
you can use my 45-second Python hack:
Bernardo Innocenti wrote:
Mr frÿffe9dÿffe9ric pouchal wrote:
I would like to disable the jingle at boot time
you can lower the volume while the jingle is playing. OFW
will store it and remember it for the next boot.
I wish the rest of our software stack was
[EMAIL PROTECTED] wrote:
rant
... the biggest benefits look like they would be in
cleaning up the userspace boot process. there is a _lot_ of stuff started
that may not be needed in the stable hardware environment of the XO laptop
where there is really only one program active at a time
Ricardo Carrano wrote:
I would suggest:
rmmod usb8xxx
That is (or at least used to be) ineffective, as the module would just
get reloaded automatically. The workaround is (was?) to rename
/lib/firmware/usb8388.bin
--
Ricardo Carrano
-- Original Message ---
From:
[16:00] *** now talking in #olpc-meeting
[16:01] Mitch_Bradley Happy New Year, everyone.
[16:02] m_stone hear, hear.
[16:02] cjb You too.
[16:02] jg evening all.
[16:02] jg 'appy new year
[16:03] jg Mitch_Bradley: I gather you don't have to deal with our
intel friends anymore
[16:03] cjb I
John Richard Moser wrote:
Bernardo Innocenti wrote:
Tom Sylla wrote:
http://openbios.org/viewvc/cpu/x86/pc/olpc/lxmsrs.fth?view=markuprevision=739root=OpenFirmware
has:
msr: .1810 fdfff000.fd000111. \ Video (write through), fbsize
which is setting the framebuffer as
Ricardo Carrano wrote:
How do I do the opposite of copy-nand - copy the OS image _from_ the nand
into a USB key?
ok save-nand u:\foo.img
--
Ricardo Carrano
___
Devel mailing list
Devel@lists.laptop.org
At some point, when these fairly obvious loopholes that we have known
about since forever are closed, we plan to change the key so new
machines will only run the more secure OS versions. Old machines will
continue to be vulnerable until they are upgraded to new firmware with
the new key, and
From a security standpoint, there is an advantage to building in
everything. The main kernel is verified with a crypto signature before
it is executed. Loading a module without first verifying a
similarly-strong signature weakens the security.
Modules are a good idea for kernels that are
Edward Cherlin wrote:
Does anybody know of a documentation tool for Open Firmware, or for
FORTH more generally? Exploring using 'words' and 'see'
is fun up to a point if you're learning FORTH, but really doesn't cut
it for supporting documentation.
I presume that you have seen
David W Hogg wrote:
On a somewhat related note, is there any way to attach an external
monitor to the XO? I would love to give my astronomy research
seminars in the spring from my G1G1 XO; but this would also be useful
for those with impaired sight (some of my colleagues need to immensely
Richard noticed that on the community-development list there are at
least two reports of the EC going terminal, meaning that on boot
they get the error message: EC problem. Remove all power and
restart. We need to get those machines to Cambridge to investigate
further.
It is unlikely
Jaya Kumar wrote:
On Dec 31, 2007 3:23 AM, Mitch Bradley [EMAIL PROTECTED] wrote:
resetting without the EC's knowledge. There is a 2-line patch in the
ticket; it makes the kernel reboot using the approved EC interaction.
Looking at your trac entry, I see:
The change is in arch
Richard A. Smith wrote:
Mitch Bradley wrote:
Richard noticed that on the community-development list there are at
least two reports of the EC going terminal, meaning that on boot
they get the error message: EC problem. Remove all power and
restart. We need to get those machines to Cambridge
I would hate to fill up my 1GB and use all my flash write cycles...
The probability of wearing out NAND FLASH is much less than people seem
to think.
The part is rated for 100,000 *erase* cycles per block. There are 64
independently-writable 2K pages per block. Writing doesn't count
M. Edward (Ed) Borasky wrote:
Chris Ball wrote:
Hi,
I signed up for a developer key, so I have one now. But what can I
do with it?
You can do anything that you'd expect to do with a standard laptop;
install any operating system, and flash a new BIOS.
How can I be sure
This reminds me of a situation I ran into about a zillion years ago,
using V6 Unix: The filesystem and the swapper disagreed about the
boundary between the FS and swap areas, so parts of the FS were getting
swapped onto.
I suppose something like that might be possible with certain
OFW's card prober.
Mitch Bradley
James Lee wrote:
I hope this isn't a bad place to post this.
I have a Kingston 4GB Class 4 SDHC card which I'd like to use with my XO
(flashing, alternate distros, etc), but it does not seem to work in OFW.
Factory formatted, I get the following:
ok dir sd
I think we will need to debug this problem interactively on IRC. The
card detection is fairly complicated, depending on v1 vs. v2 SD physical
layer, MMC vs SD, SD vs SDHC, and on the set of operating voltages that
the card supports. There are too many code paths for me to guess which
one is
John Gilmore wrote:
Please note that there are users like me who have the exact problem
described by http://dev.laptop.org/ticket/5558. I have been
totally __unable__ to gain access to the Open Firmware ok prompt.
Please read the top section of
The main reason you have gotten no feedback is because we are ultra-busy
right now with mass-production and other issues.
I have been looking into partitioning schemes for some time now. We
need to have a discussion about this, but now is not the time.
Artem Bityutskiy wrote:
Hello Mitch,
Jake B wrote:
Are XO developers planning to implement support for
suspend-to-RAM/resume on the XO?
Please let me know. Thanks.
That feature is already implemented. Press the power button and it
suspends; press again to resume. Lid closures do it too.
Jake
You may be amused to know that the firmware has an Easter Egg of the
Conway's Life. If you press the rocker pad (left side of screen) to the
right after powering on, you will get a randomly-select amusement, one
of which is Life. It uses the traditional life-death rule with a
wrap-around
Michael Stone wrote:
Emiliano,
First things first - caveat emptor.
Direct access to the firmware makes it very easy to brick your machine.
Do not attempt to use these instructions unless you are prepared to deal
with the possible consequences of mistakes and/or failure. Consult OFW
experts
is set
correctly (if your machine is working now, the RTC is okay), it won't go
bad unless you remove the RTC battery or the RTC battery fails (unlikely
for several years) or you go out of your way to invalidate the RTC value.
My apologies for this egregious bug.
Mitch Bradley
Asheesh Laroia wrote:
On Thu, 6 Dec 2007, Rafael Enrique Ortiz Guerrero wrote:
Hi all
i've put some notes in here..
http://wiki.laptop.org/go/Stable_Upgrade
Thanks for writing it up!
I just tried it with a USB memory key (an SD card in a multi-card
reader), and my XO said
ffm wrote:
I am not completely sure how to set it for the XO-1. I have followed
instructions for other implementations of OpenFirmware, but without
success.
Password security is not enabled in the XO version of OFW. Most of the
deployed systems will be in secure mode, in which you can't
I wonder how the WP tag got set?
Alexander M. Latham wrote:
--- [EMAIL PROTECTED] wrote:
At powerup it says S/N Unknown, then
could not activate this XO
Serial number: SHF
When I try the activative procedure, I instead get:
No serial number in mfg data
No serial number
[EMAIL PROTECTED] wrote:
Scott,
Um, I don't like those instructions at all. Why not just set the
serial number in SPI flash, and set the 'ak' tag while you're at it?
Mitch suggested that first, and it didn't work. Setting a SN tag plus
a U# tag did work,
According to my recall, it
Mike C. Fletcher wrote:
It's not About the Hardware:
In principle, that is true.
In practice, it is the hardware that has been responsible for all the
attention.
If the project had been just a software framework to support
constructivist education, the worldwide response would have been ho
This is a Color of the Bikeshed issue.
Give it a rest.
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
Eben Eliason wrote:
Is there a reason you haven't made the clock and the stopwatch different
functions for a single activity?
I second that. I think these could be integrated
While you're at it, how about integrating the camera activity with it,
so it could be like Dick Tracy's
Eben Eliason wrote:
On Nov 14, 2007 4:07 PM, Michael Stone [EMAIL PROTECTED] wrote:
On Wed, Nov 14, 2007 at 02:36:08PM -0500, Eben Eliason wrote:
We still intend to incorporate that - the overhead of launching an
activity is silly.
More precision would make this particular
Ivo Emanuel Gonçalves wrote:
I've noticed that mesh activity appears to be ALWAYS on. Even when
the laptop is not doing anything, as in not conected to a school/local
mesh and not sharing any activity. Sometimes even on Suspend mode I
see the Wireless activity light flashing. I'm sure this
Arjun Sarwal wrote:
Hi,
I need to do some testing (need sine waves of 50hz, 1khz, 10khz) and I
am unable to get hold of a function generator. I was thinking of using
my computer (PC) sound card to generate these tones. I am wondering if
anybody has done this - so that I may know how clean
The Give One, Get One program will put many XO laptops in situations
unlike the design target. In particular, North American G1G1 purchasers
won't be in clear school/village/community clusters.
For the target country deployments, we have been assuming that printing
will be done rarely (as
Seth Woodworth wrote:
Slightly off of the conversational thread here but: Information on the
specific output spectrum capabilities might improve transcoding of
audio files into smaller file sizes. If there is no, or poor quality,
auditory response below or above a given threshold, it might
, DCON) going to suspend
- Close as fixed
2401 Update.2 rsmith Wakeup event is repeated continuously (EC and kernel)
- The recipe given by MitchCharity has been reproduced by Mitch Bradley
- Not a show-stopper because the system recovers if you press the
button again
- We don't want spin
http://wiki.laptop.org/go/OLPC_Firmware_q2d03
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
Quote of the Day: Did Apple design this?
- The first words uttered by Noura, a woman in her twenties, when she
saw the xo laptop for the first time on a recent plane flight.
Fractured song lyric of the day:
Jobs didn't make the little green laptops, and it don't rain in
Indianapolis in
So far the new keyboard descriptions in the manufacturing data are a
paper spec only.
By that I mean that, as far as I know, the new tags are not present in
the pre-build machines, and the OS doesn't look for them.
(That is not quite true for OFW; it will use the new KA tag if it exists).
One
Ian Daniher wrote:
Samir,
IIRC, there *is* a serial port, but due to constraints I have not been
made aware of, It isn't exposed, instead it is buried inside the case.
One primary constraint is that there is absolutely no room left for
other connectors to come out.
Yes, I know there are
Ceramic resonators are less expensive than crystals. Their stability
and accuracy is not as good as crystals, but is much better than RC
oscillators.
The waveform that comes from most oscillators is nominally a square
wave, but when the frequency gets into the tens of megahertz range, it
At the current rate of XO software churn, any printed book will be
obsolete/inaccurate before the ink is dry.
Todd Kelsey wrote:
I have been struggling with my literary agent and trying to knock
someone over the head with a wet noodle into realizing that there
*will* be a market for a book,
http://wiki.laptop.org/go/OLPC_Firmware_q2d01
This is the release for the mass production build.
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
Todd Kelsey wrote:
Hello - trying to get b2-7 working for demo of mesh between b2-7 and
b4 running 542-
wondering what the best firmware/build combination would be. I believe
it has build 542 and q2c28 -- wasn't sure if it should have q2c26.
notes indicate 542 and firmware tested for
This sounds a lot like a problem that I was working on yesterday.
Can you go on IRC (freenode, #olpc) ? If so, I would like to work with
you to see if my latest firmware works around your problem.
Yoshiki Ohshima wrote:
Hello,
My B4 with 616 build went into some interesting state. I
Bert Freudenberg wrote:
On Oct 9, 2007, at 8:15 , Albert Cahalan wrote:
I notice that some keyboards lack the multiplication
and division symbols. Providing them for all kids
would be good, even if they need to move elsewhere.
Why those? They are not used universally.
And even in
svn://openbios.org/openfirmware
Build by make in cpu/x86/pc/olpc/build
Kein Yuan wrote:
Dear list,
Can anybody here kindly let me know where I can download OFW
source code for OLPC? Under _ _http://dev.laptop.org/git there is
comments says No commits.
Thanks a lot,
Kein
The proposal for the ASCII keyboard map is detailed in:
http://wiki.laptop.org/go/Manufacturing_Data#Keyboard_ASCII_Map
In the process, I extended the tag format in an upward-compatible
fashion to allow value strings longer than 127 bytes:
/07, *Mitch Bradley* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
wrote:
The proposal for the ASCII keyboard map is detailed in:
http://wiki.laptop.org/go/Manufacturing_Data#Keyboard_ASCII_Map
In the process, I extended the tag format in an upward-compatible
fashion to allow
Jim's proposal solves the X problem, and I think we should adopt it.
We also have the problem of letting OFW and the Linux kernel know enough
about the keyboard so developers can type US ASCII , which is the common
subset that is sufficient for managing diagnostics, booting, and
installation
Bernardo Innocenti wrote:
Mitch Bradley wrote:
One solution would be to include a lot of keymaps in OFW and select one
based on the new KL tag. However, I'm not keen on having to carry
around a lot of keymaps in the ROM, and extend that list from time to time.
There's also
Carl-Daniel Hailfinger wrote:
On 27.09.2007 01:44, Jim Gettys wrote:
As we run up to mass production of systems, the team at OLPC must
focus its efforts on testing and bug fixing on the mass-production
hardware.
To date, we've been careful to ensure that our firmware and software
works
Mitch Bradley wrote:
B3 and later machines are essentially identical as far as the firmware
is concerned. OFW senses the board revision and reports it in the
device tree, but does behave differently as a result of board revision
difference.
I meant does
OLPC does not support VGA/EGA/CGA graphics, so the display code for all
those old programs will not work.
big one wrote:
Booting to console mode / svgalib possible
Can someone put a wiki / HOWTO about booting OLPC to console mode, setting up
svgalib, SDL, xinit command and xinitrc?
201 - 300 of 332 matches
Mail list logo
