It seems okay to me on first reading.
On 6/13/2013 7:53 AM, Daniel Drake wrote:
> Hi Mitch,
>
> As mentioned, upstream now has APBC/APMU clock drivers, and I think there
> are a couple of things in way that clock-dt.c interacts with the common
> clock framework that upstream wouldn't approve of.
On 6/11/2013 4:21 AM, Daniel Drake wrote:
> Hi,
>
> I am looking at upstreaming these patches:
>
> http://dev.laptop.org/~dsd/20130611/0003-ARM-mmp-Fix-MMP2-interrupt-controller-DT-nodes.patch
>
> http://dev.laptop.org/~dsd/20130611/0004-ARM-mmp-irq-Use-of_get_address-instead-of-of_address.pat
OLPC stopped making x86 machines some time ago. XO-1 machines have
reached or exceeded their design lifetime. I expect that, if there are
any active users of GRUB on OLPC machines, upgrading to new versions of
GRUB-booted OSs is becoming less and less attractive due to resource
constraints and ha
On 12/18/2012 5:48 AM, Paul Fox wrote:
> manuel wrote:
> > On Sun, Dec 16, 2012 at 1:40 PM, Daniel Drake wrote:
> > > XO-4 now has HDMI support in Linux (#12350). Other kernel fixes:
> >
> > Is there some "user guide" about this?
> >
> > I mean, what I need to know to make this work? I h
The space required by the serial terminal thing is insignificant.
On 3/28/2012 4:44 PM, John Watlington wrote:
On Mar 27, 2012, at 5:52 AM, James Cameron wrote:
This is a serial terminal implementation for an XO-1.75 using Open Firmware.
Useful --- the computer science equivalent of the voltm
New OFW can boot older Linux if you say:
ok false to use-fdt?
ok boot
On 3/26/2012 8:08 AM, Sascha Silbe wrote:
Excerpts from James Cameron's message of 2012-03-21 06:11:57 +0100:
- enable flattened device tree export to Linux, requires recent
kernels, ticket #11568,
Does this just mean t
http://wiki.laptop.org/go/OLPC_Firmware_q4c10
It fixes a regression in the LED selftest that would have affected the
XO-1.75 ramp build.
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
http://wiki.laptop.org/go/OLPC_Firmware_q4c09
Q4C09 fixes longstanding bugs in WEP and WPA WiFi authentication; it
works with at least the following authentication schemes:
WEP {Open,Shared Key} x {40/64,128} bit x {hex, ascii} key
{WPA, WPA2-Personal} x {TKIP,AES}
It does not support WPA2-E
have the same behaviour in both laptops.
For each boot, the laptop repeats steps b and c, then, laptop powers
off. If XO have "rt" tag will never boot.
2011/10/14 Mitch Bradley mailto:w...@laptop.org>>
The most likely explanation is that OFW had to power off in order
to
The most likely explanation is that OFW had to power off in order to
re-enable writing to the SPI FLASH. That can happen if the last reboot
was from Linux. See http://dev.laptop.org/ticket/4397
Unless that bug is fixed, the process will be:
a) Linux reboots
b) OFW runs rtc-rollback? and trie
On 9/22/2011 10:07 PM, James Cameron wrote:
http://wiki.laptop.org/go/OLPC_Firmware_q4b10
* new EC version,
* working suspend and resume (OpenFirmware only),
* improved audio,
* fix pingd,
* hold EC in reset during reflash of OpenFirmware,
* thermal sensor watchdog reset,
* enforce SPI FLASH w
Yeah, what James said.
That said, in most cases the mount/unmount penalty is not bad, because
in cases where it was, I did some caching to make it less onerous.
Cases in point include JFFS2, where mount is inherently horrible, so I
cache the result of scanning the whole NAND surface, and the
http://wiki.laptop.org/go/Forth_Lesson_23
Contains some random recipes. Please add your favorites.
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
On 5/7/2011 12:15 PM, Daniel Drake wrote:
> On 5 May 2011 22:25, Mitch Bradley wrote:
>> It would be necessary to erase the entire device, rather than just the
>> number of blocks specified by the zblocks: line, because that number is not
>> known until very late in the p
On 5/5/2011 9:08 AM, Daniel Drake wrote:
> On 5 May 2011 08:57, James Cameron wrote:
>> Q3A65 removed this blanking, because it interfered with NANDblaster,
>> which stores the received blocks of the .zd file in the SD card before
>> fs-update begins. On extending the blanking to the whole devi
On 3/20/2011 6:58 AM, Chris Ball wrote:
> Hi,
>
> On Sun, Mar 20 2011, Daniel Drake wrote:>
>> 1. Is this approach a good idea?
>
> Sounds great to me.
>
>> 2. Are we bothered by a misleading WARNING message appearing at the
>> end of the flashing process for those running on old/current firmware
On 3/20/2011 6:58 AM, Chris Ball wrote:
> Hi,
>
> On Sun, Mar 20 2011, Daniel Drake wrote:>
>> 1. Is this approach a good idea?
>
> Sounds great to me.
>
>> 2. Are we bothered by a misleading WARNING message appearing at the
>> end of the flashing process for those running on old/current firmware
On 3/13/2011 8:09 AM, Richard A. Smith wrote:
> On 03/13/2011 01:15 AM, Sridhar Dhanapalan wrote:
>> With firmware Q2E45 on an XO-1 (yes, I finally got it unlocked!), I
>> type 'menu' at the ok prompt.
>>
>> On an XO-1.5, I get a very useful list of icons that run different
>> hardware tests. On
Patch applied to svn head.
Note that it might be prudent to do the patch in olpc.fth instead of
going through a release/test cycle for XO-1 OFW.
On 2/28/2011 7:09 AM, Daniel Drake wrote:
> In Linux we plan to use the device tree for probing the DCON, battery, and
> XO-1 RTC drivers.
>
> Add the
I don't thing that cli_tool is needed. I don't use it.
On 2/16/2011 9:18 AM, Martin Langhoff wrote:
> Mitch, list,
>
> Context -- I am in the midst of reworking a bit bios-crypto, while
> trying hard to avoid breaking things for Mitch and others that are
> likely working from src.
>
> [ more back
You already know more about this than I do, so I can't be of any help here.
On 1/13/2011 3:47 AM, Daniel Drake wrote:
> Hi,
>
> Low priortity query...
>
> I'm investigating the possibility of implementing _SWS (system wakeup
> source) support in the XO-1.5 DSDT, along with _SWS support in Linux.
>
I released Q4A10, but you should not use it unless your name is Quanta.
It is for the A2 board build. It will not work on any boards
currently in existence.
I am sending this message in case someone happens to find it and somehow
misses all the "Do Not Use" warnings on the web page.
http://wiki.laptop.org/go/OLPC_Firmware_q3a62
svn 2054 - SDHCI - keep track of last 8 commands and display them when
an error occurs.
svn 2065 - Increase external SD card power-up off time for a 32 G class
10 SD card being tested.
svn 2068 - Changed the check for NTLDR to be less language-sensit
ec 2010 14:56:15 -1000
> Mitch Bradley wrote:
>
>> There is some battery info in the _BIF (battery info) method in the
>> BATT node of the ACPI DSDT. I don't remember if it is correct or
>> not. The numbers below match the DSDT numbers.
>
> Wait, so where did *
There is some battery info in the _BIF (battery info) method in the BATT
node of the ACPI DSDT. I don't remember if it is correct or not. The
numbers below match the DSDT numbers.
On 12/10/2010 2:38 PM, Andres Salomon wrote:
> On Fri, 10 Dec 2010 22:15:10 +
> David Woodhouse wrote:
>
>> O
I know very little about how ebook detection works on Windows. There is
a magic Windows driver that does that stuff, and we don't have much
insight into its inner workings.
The only thing I can suggest is to test it.
On 12/4/2010 5:20 AM, Daniel Drake wrote:
> Hi Mitch,
>
> With this DSDT cha
Does the ACPI spec say anything about an ebook switch? Lid switch,
power button and sleep button are standard ACPI thingys, but I'm not
sure there is an ACPI standard for other kinds of buttons. A search of
the ACPI spec for "button" didn't find anything other than power and sleep.
ACPI, in g
The DCON does not "see" video memory directly - it works with the
real-time display data that is driven onto the wires that would normally
go to an LCD panel.
I wonder if, in the VT case, the driver is stopping the display
controller soon after clearing the DCONLOAD pin? In that case, I can
i
On 9/21/2010 7:24 AM, Andres Salomon wrote:
> On Tue, 21 Sep 2010 06:35:48 -1000
> Mitch Bradley wrote:
>
> ...
>> You could get all the information from the device tree, after having
>> first checked for the presence of the device tree by looking for the
>
On 9/21/2010 6:15 AM, Daniel Drake wrote:
> I'm working on XO-1.5 support upstream and would appreciate comments
> on the following:
>
>
>
> The very core "am I an XO?" check that runs during boot is this:
>
> http://lxr.free-electrons.com/source/arch/x86/kernel/olpc.c#L212
>
> It runs ioremap() o
http://wiki.laptop.org/go/OLPC_Firmware_q3a58 is a new OFW release for
XO-1.5. It fixes problems with the audio CODEC
protection settings and includes new EC firmware.
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/d
On 9/16/2010 1:28 PM, Martin Langhoff wrote:
> On Thu, Sep 16, 2010 at 7:01 PM, James Cameron wrote:
>> No, certainly not. There's no justification for either mke2fs or
>> resize2fs to write to blocks that do not form part of the filesystem
>> metadata. Why would you want to zero-out blocks an
Submitted for your consideration and amusement:
http://wiki.laptop.org/go/Forth_Lesson_20
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
http://wiki.laptop.org/go/OLPC_Firmware_q3a48
* Fixes a SD card timeout problem with ADATA 4GB and 8GB SD cards
* User interface improvements in "test /keyboard" to help catch a "stuck
key" problem seen in the factory
* Resume-from-S3 now works with Windows XP
___
We just found and fixed a bug in q3a44 that breaks fs-update in secure
mode. q3a45 will be issued within a few hours, so you can just forget
about q3a44 and wait for q3a45 .
Mitch Bradley wrote:
> http://wiki.laptop.org/go/OLPC_Firmware_q3a44 is the latest firmware
> release. It su
http://wiki.laptop.org/go/OLPC_Firmware_q3a44 is the latest firmware
release. It supports secure XO-1.5 NANDblasting and the new mechanical
keyboards.
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
Martin Langhoff wrote:
> On Thu, May 13, 2010 at 6:10 PM, Mitch Bradley wrote:
>
>> http://wiki.laptop.org/go/OLPC_Firmware_q2e43 is a candidate for a
>> general-availability firmware release for XO-1. It fixes problems found
>> during testing of q2e42, which was
http://wiki.laptop.org/go/OLPC_Firmware_q2e43 is a candidate for a
general-availability firmware release for XO-1. It fixes problems found
during testing of q2e42, which was not intended for general availability
(because we suspected it would have problems due to the long interval
from q2e41 t
Well, actually, there is one other option - it is possible to use one
XO-1.5 to reprogram the SPI FLASH inside another. It requires that you
solder header connectors to both machines and connect them with a ribbon
cable. I don't think that there is a writeup for how to do it.
Mitch Br
Your only option at this point is to replace the SPI FLASH part.
Gonzalo Odiard wrote:
> One of the XOs 1.5 here in La Rioja have the serial number with lower
> case letters "SHC00500ad0", this machine can't be activated.
> We tried to change the tag, but made a mistake and used "delete-tag"
> a
The "4" is 406 is for 400 Mhz. The normal value is "a06", where "a" is
decimal 10 for 1000 Mhz.
The "6" is the voltage selection code; this processor only supports the
value "6".
Mitch Bradley wrote:
> ok 406. 199 msr!
>
> The perio
ok 406. 199 msr!
The period after 406 is mandatory - it forces the number to be 64-bits,
suitable as the data operand to msr!.
John Watlington wrote:
> Mitch,
>Is there a simple way from OFW (or ACPI) to restrict
> the operating frequency of the processor in the XO-1.5
> to be the lowest po
The various alpha suffix revisions fix the problems that have been
reported. Systematic testing has not happened yet. Is there a plan yet
for engaging deployment teams to do testing?
Martin Langhoff wrote:
> On Sun, Feb 14, 2010 at 4:31 PM, James Cameron wrote:
>
>
>> Reproduced #10024 (fa
http://wiki.laptop.org/go/OLPC_Firmware_q2e42
This release is for testing a number of security enhancements for XO-1.0
and many other changes that have been added to the source tree during
the development of XO-1.5. Since it has been a long time since the last
XO-1.0 firmware release, it would
I regret that I must once again unsubscribe from devel, as the noise
level has gotten out of control.
I need to get some actual OLPC-related work done, instead of listening
to people giving free advice and telling others what they ought to be doing.
If something that requires my attention shoul
Tabitha Roder wrote:
>
> Updated 5 XO 1.5 machines and 4 XO 1.0 machines.
> On XO 1.5s the open firmware help is unhelpful. The new fs-update
> command for reflashing the XO is not described in the help and the old
> flash-nand command which no longer works is listed.
>
Thanks, I entered this
http://dev.laptop.org/report/44 collects the tickets that q3a18 fixed.
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
http://wiki.laptop.org/go/OLPC_Firmware_q3a18
Please test
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
atlington wrote:
>
>> I suggest that we dedicate the unused
>> memory ID 0 jumper (GPIO9) to indicate that
>> this DRAM is present.
>>
>> Thanks for reminding me, as Richard and I
>> wanted to add another jumper since we've used
>> them all up.
BTW, after removing the power resistor, you must be careful to clean off
excess solder, because the crucial gap is small and "embedded" in the
large pads. I had to use ChipQuick to get the resistor off, then I had
to add regular solder back to the pad to alloy with the ChipQuik, as
ChipQuik do
This is just a success report on the new serial auto-enable feature on
B3. I removed the mistakenly-stuffed power resistor (pr148) on the
serial_en signal and modified a USB serial dongle (cut the trace that
goes from 3.3V to pin 1 of the header, soldered a jumper from pin 1 to
pin 4).
With t
Paul Fox wrote:
> mitch wrote:
> > http://wiki.laptop.org/go/Nandblaster_for_XO-1.5 records my current
> > thoughts about NANDblaster for XO-1.5. Please comment.
> >
>
> i'm a little confused by the concerns re: partitioning. most of
> what you're designing is a fast block mirroring proto
http://wiki.laptop.org/go/OLPC_Firmware_q3a16
It fixes several issues that affect the display, and is especially
appropriate for use with os40.
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
Richard Smith wrote:
> Is it possible to turn the .zd scheme into the same FEC scheme so that
> fs-update and nandblaster use the same source stream? I know that adds
> a lot of additional overhead in the non-lossy channel case but even if
> it results in a slowdown in the fs-update case it mig
http://wiki.laptop.org/go/Nandblaster_for_XO-1.5 records my current
thoughts about NANDblaster for XO-1.5. Please comment.
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
In the secure case, initramfs discovers the root device by looking in
the /chosen node of the /ofw device tree.
Daniel Drake wrote:
> 2009/11/5 Esteban Bordon :
>
>> I saw the OFW code and I did not understand :-/
>>
>> I created a ticket (http://dev.laptop.org/ticket/9558) with the issue and
Emiliano Pastorino wrote:
>
> There is a way to check the temperature under Linux. It involves
> the "lmsensors" package, but I don't know the exact details.
>
>
> Yes, that's what I've been using. The package is lm_sensors, if
> installed, you just have to type "sensors" and you get th
Emiliano Pastorino wrote:
> Mitch,
>
> Does q3a15 automatically throttle the processor in case of overheating?
Yes
>
> If so, is there a way to check if it is working? cat /proc/cpuinfo maybe?
>
>
Here is a test you can do with Open Firmware:
ok show-temperature (cr many
That command runs th
> Computer are supposed to be a Science ...
>
Regardless of what anyone thinks computing is "supposed" to be, in
reality what it really is is business.
Things happen because or money or the hope of money. OLPC tries to buck
that trend to some extent, but all of the components that we buy,
"Remove all power and wait" is by far the easiest way to reset a
keyboard, but ...
If one really could not get the keyboard to work, but wanted to upgrade
the firmware anyway, here is a recipe:
a) Get a USB stick, ideally factory-formatted with a FAT filesystem, but
ext2 will work too.
b) Put
http://wiki.laptop.org/go/OLPC_Firmware_q3a15
Lots of good stuff. Please help me test it!
My trac tickets are at http://dev.laptop.org/report/41 . If you click
on the "Action Needed" column, the "test in release" tickets will
collate together. Those tickets are ostensibly fixed in q3a15. It
st and i
> can wikify them if you want.
>
> my $1 cent.
>
> cheers!.
> Rafael Ortiz
>
>
>
> 2009/10/28 Mitch Bradley :
>
>>> Q3a14 release notes are missing in the wiki.
>>>
>>> is this intended to be so ?
>>>
>>>
>
> Q3a14 release notes are missing in the wiki.
>
> is this intended to be so ?
>
I did q3a14 in a hurry one night, so Chris would have something to test
over the weekend. I was too tired to write the release notes.
Maybe I will write them soon. Maybe not. It is very late here and I am
t
I don't like the idea of a second copy - "A man with 2 watches never
knows what time it is".
Martin Langhoff wrote:
> On Wed, Oct 21, 2009 at 8:37 AM, Daniel Drake wrote:
>
>> Maybe you don't have /boot mounted, or maybe there is a bug in the
>> build system now that we moved to a separate bo
/boot/olpc_version usually contains the right number.
Martin Langhoff wrote:
> On Wed, Oct 21, 2009 at 7:55 AM, Tabitha Roder wrote:
>
>> OLPC release 11 Leonidas
>> Sugar 0.84.2
>> Firmware Q3A11
>>
>
> Yeah, those OSs don't report themselves correctly. The XOs probably
> were sent with
http://dev.laptop.org/~wmb/q3a13c.rom
This is a "brown bag" release whose main purpose is to test the
effectiveness of Richard's EC fixes for the "keyboard stops working"
problem.
It also has a fun feature for your amusement:
ok screen-ih iselect
ok 40 30 set-scaled-resolution
(It also works
The Linux-booting problem that Raul Gutierrez Segales found with Q3A12
was serious enough to warrant a quick-turn release. Please use Q3A13
instead of Q3A12 .
http://wiki.laptop.org/go/OLPC_Firmware_q3a13
___
Devel mailing list
Devel@lists.laptop.or
http://wiki.laptop.org/go/OLPC_Firmware_q3a12
This is a stabilization release for B2 machines, fixing numerous issues
with the q3a11 firmware that was installed on them during manufacturing.
It works on XO-1.5 A1, A2, B1, and B2 systems, but does not work on any
XO-1 machines.
The change list
You can get the erase block size from SD cards - it's in the Card
Specific Data structure - but I don't know of any standard way to get it
for USB mass storage devices.
Sascha Silbe wrote:
> On Sat, Oct 10, 2009 at 02:46:17AM +0100, Martin Dengler wrote:
>
>> Nope (SoaS) - that'll waste your par
> Working on an OLPC package (olpc-bios-crypto, which has a reasonable
> chance of being upstreamable when it stabilizes)... we keep appending
> -L lines to make it build in different releases / distros.
>
> Is there an rpm macro that points to the location of libgcc.a? Or an
> elegant way to get
I hope we can find some better way to distinguish between the different
board flavors in early startup code. The current technique, involving
an EC command (whose response latency cannot be guaranteed) with the
answer cached in CMOS RAM (which cannot be accessed quickly due to the
power-glitch
> I am using NANDBlaster to update all of our SFSU Lending Library XOs
> (a total of 12). All machines update via nb-secure to 8.2.1 except one
> XO, which repeatedly (five tries so far) fails to find the NANDBlaster
> info, cycles through all other options and says "Boot failed". It
> does updat
Martin Langhoff wrote:
> On Tue, Oct 6, 2009 at 11:27 AM, Mitch Bradley wrote:
>
>> To solve a hard problem to the level where you can ship the result
>> requires money
>>
>
> Not particularly controversial with me at least. The community is made
> of m
Tiago Marques wrote:
> Trying to find datasheets of the flash chips to know what their erase
> block size and page size(and number of erase cycles) has been a
> nightmare for me, the manufacturer just doesn't care if your
> partitioning choice ends up sending the SSD/SD/MMC sooner than the
> warran
Martin Langhoff wrote:
> On Tue, Oct 6, 2009 at 12:07 AM, Mitch Bradley wrote:
>
>> time, I expect the situation to get better and better as the firmware
>> that "gets it right" supplants the earlier tries.
>>
>
> It's reassuring to hear
David might be right in principle, but when component price matters, you
have to buy the hardware that the mass market offers. Right now the
sweet spot is "smart" devices with embedded Flash Translation Layer
firmware. I'd place my bet on that trend continuing.
Linux does not "drive" the mass
http://dev.laptop.org/ticket/9476 narrows it down to a specific model of
15W adapter. The 17W adapters that I tried worked.
John Watlington wrote:
>
> Mitch,
>Regarding your note on IRC about power adapters:
> no, I hadn't noticed any problems with using XO-1
> adapters with XO-1.5 laptops.
scp dev.laptop.org:~wmb/q3a11c.rom
Consider this a pre-release of q3a12 ...
Highlights:
a) The Via Thermal Monitor is on. That prevents overheating.
b) fs-update has several improvements:
1) Now handles large chunk sizes correctly
2) "dir int:\" immediately after fs-update now works
3) Better
ute force,
but empirically it seems to work quite well in the OLPC context.
Martin Dengler wrote:
> On Wed, Sep 16, 2009 at 11:18:17AM +0800, Mitch Bradley wrote:
>
>> It is gratifying that so many people like the idea of being able to zap
>> back into OFW from Linux - especially
Martin Dengler wrote:
> On Wed, Sep 16, 2009 at 11:18:17AM +0800, Mitch Bradley wrote:
>
>> It is gratifying that so many people like the idea of being able to zap
>> back into OFW from Linux - especially since I got such intense pushback
>> when I first proposed
It is gratifying that so many people like the idea of being able to zap
back into OFW from Linux - especially since I got such intense pushback
when I first proposed leaving OFW resident on OLPC.
___
Devel mailing list
Devel@lists.laptop.org
http://lis
d it was. :)
>
>
>
>
> Rafael Ortiz
>
>
>
> On Wed, Aug 26, 2009 at 3:29 PM, Mitch Bradley wrote:
>
>> Which version of Open Firmware are you using?
>>
>> Rafael Enrique Ortiz Guerrero wrote:
>>
>>> Thanks for your reply Mitch.
e screen only after all of the text messages have
> finished, you can add "echo 0 >/sys/devices/platform/dcon/freeze" to a
> late initscript.
>
> or what can i do to workaround this issue ?.
>
> Rafael Ortiz
>
>
>
> On Wed, Aug 26, 2009 at 3:06 PM, Mi
It's probably the same thing as the first item in
http://wiki.laptop.org/go/Rawhide-XO#Known_issues
We made "pretty boot" the default in later versions of Open Firmware,
but many alternative operating systems don't know how to "unfreeze" the
screen.
Rafael Enrique Ortiz Guerrero wrote:
> Hello
> Wish I knew how to create drivers for OFW so it could boot from UBIFS.
>
>
Normally I would encourage adding such drivers to OFW, but in this case
I think it's wasted effort that could be much better spent in other ways.
a) XO OFW already has well-elaborated partition support. It's
inter
lilo is nearly worst of breed in terms of putting magic stuff in the
Master Boot Record.
da...@lang.hm wrote:
> On Tue, 28 Jul 2009, Mitch Bradley wrote:
>
>> da...@lang.hm wrote:
>>> On Tue, 28 Jul 2009, Mitch Bradley wrote:
>>>
>>>> Another imp
da...@lang.hm wrote:
> On Tue, 28 Jul 2009, Mitch Bradley wrote:
>
>> Another important advantage to partitions is that the existence of a
>> boot partition isolates the firmware from changes in the filesystem
>> used for the root.
>
> can you explain this a
Another important advantage to partitions is that the existence of a
boot partition isolates the firmware from changes in the filesystem used
for the root.
Advantage #2 that you cite below is also quite valuable - it makes it
easy to preserve user data while replacing/recovering/updating the
s
The filesystem is no longer internally compressed. The current size for
the XO-1.5 system is 1.1 GB. 2 GB gives some headroom for growth and
for temporary overages during updates.
Walter Bender wrote:
> Why such a large system partition?
>
> -walter
>
> On Mon, Jul 27, 2009 at
This is a request for comments on a proposed disk layout for XO-1.5.
XO-1.5 will have "managed NAND" instead of raw NAND, so we can use
conventional filesystems instead of e.g. JFFS2.
Proposal:
The internal NAND storage will be partitioned with an FDISK partition
map, into three partitions:
/
I spent the week bringing the XO1.5 firmware up to scratch, updating the
OFW trac tickets, enabling features that had been omitted for early
testing and merging submissions from Paul, Luke, and Lilian. Chris and
I worked to get suspend/resume working when Linux is booted from OFW.
On Thursday
> The images come with olpc-update and the initramfs is ready to boot
> our special "versioned layout" filesystem (like 8.2 and previous).
> However the code to generate the images as the versioned layout is
> currently disabled because it exposed a bug in OFWs ext2 code.
That bug is fixed in q
>
> Even the OLPC wiki contains links [1] to misleading reports [2] about
> Windows on the XO without any further, clarifying comment.
> OLPCNews' quote of NN didn't make it clear [3] as well:
>
> """
> For this reason, Sugar needs a wider basis, to run on more Linux
> platforms and to run under
>
> Now AFAIK, there's little to no Windows work being done in-house by
> the OLPC team, and it's all or mostly at Microsoft's side that the
> work's being done.
>
At the moment, OLPC is doing approximately zero work on Windows. That
wasn't true last year. I spent several months last year ma
Deepak Saxena wrote:
> simply grabbing that irq via request_irq() causes USB
> device insertion (and other things?) to break.
I had a related problem in OFW - enabling the SMBALRT# pin (for DCON
use) caused immediate wakeups from suspends (in OFW-based testing).
OFW's solution is to enab
John Gilmore wrote:
>> Basically, for each configuration (external microphone plugged in, and
>> external microphone not plugged in), I'd like to know the following:
>> - which of the 8 microphones is the one to use
>> - which ports we can turn off
>>
>
> In reading the generic Intel HDA c
> As for speedups, I see 2 different ways :
> a) using a SD with a fat partition + ext2 filesystem
> b) using the nand with a fat partition + ubifs - this requires 2.6.29
> which is not ready yet.
>
A FAT partition will not work well on the raw NAND of XO-1, because of
blocksize, erase bloc
Martin Langhoff wrote:
>
>> Easily? Yeah, right.
>>
>
> Well, he can show us how it's done. I'll definitely be impressed :-)
>
>
>
My point is that, while each individual step is rather straightforward,
requiring no new technology, putting together all the pieces to
accomplish the goa
Guylhem Aznar wrote:
> Approx timings from pressing on the power button on my test machine
> using an old 2.6.22 on a jffs2 partition
> 2 seconds with the screen turned off
>
There is very little that can be done to reduce that 2 seconds, which is
dominated by the time it takes to read the f
> From what I've read on the
> wiki, JFFS2 is here only because OFW doesn't know how to use UBIFS.
>
Don't believe everything you read on a wiki.
As Peter Robinson says, JFFS is used because it was the only viable
alternative at the time we were doing the initial development. UBIFS
did not
1 - 100 of 414 matches
Mail list logo
