11.2.0 feature plan
We're now in our feature development milestone of 11.2.0. Here is the summarized outcome of our discussion on features that OLPC will be working on during this cycle: http://wiki.laptop.org/go/11.2.0/Release_plan#Feature_plan The release is time-based, not feature-based, items may be dropped if they do not make the deadline of April 18th (or the date might shift slightly to accomodate a select few). Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: 10.1.3 image and Firmware q2e42
On Wed, Feb 16, 2011 at 5:06 PM, James Cameron wrote: > If you based your image on OLPC OS 10.1.3 then after installation the > firmware will be automatically upgraded to Q2E45, so you should test > with Q2E45. Daniel - James is right here. Just include /boot/bootfw.zip in your image (os-builder will do the right thing if you provide the "unsigned" bootfw rpm and follow the signing procedures). Right after install, each boot will check if there is battery+external power, and if those 2 conditions are met, will upgrade OFW. About your keyboard issues -- things have changed a bit from 8.2.x to 10.1.x in how we manage the keyboard. Can you tell us what you're trying to do (perhaps in a separate email thread), and we'll find a good way to do it. cheers, m -- martin.langh...@gmail.com mar...@laptop.org -- Software Architect - OLPC - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: 10.1.3 image and Firmware q2e42
G'day, I'm puzzled. If you based your image on OLPC OS 10.1.3 then after installation the firmware will be automatically upgraded to Q2E45, so you should test with Q2E45. If you based your image on Dextrose os439dx, the same thing should occur, since it contains Q2E45 firmware. If it does not occur because of not being signed, you can sign the firmware, during image build, with your deployment keys. (This is assuming you have deployment keys in your secured laptop population). Are you intending to prevent the firmware update that Dextrose normally performs? For OLPC OS 10.1.3, it was tested with Q2E45, and so we don't really know how it will go wrong with Q2E41. For Dextrose, I imagine the same testing limitation was imposed. I think you've found at least one way it goes wrong; the keyboard mapping. You should review the full list of changes since Q2E41 to fully evaluate them. Paul didn't mention some that concern me: Q2E42 - key delegation, (you can ignore this if you do not use key delegation), - SMBIOS setup, (effect unknown, there was no test case), - nbclone to secure XO, (you can ignore this if you do not use nbclone), - many problems with ext2 filesystem access, (you can ignore this if you do not plan to deploy operating system images using ext2 filesystems), - many problems with USB access, (you can ignore this if you do not plan to deploy operating system images on USB drives), Q2E43 - free cluster tracking in FAT filesystem driver, (you can ignore this if you do not plan to capture data using firmware scripts that will write to USB or SD with FAT filesystems), - compatibility with USB keyboards, (you can ignore this if USB keyboards won't be connected at the time the laptop is turned from off to on). #9100 you may not be able to reproduce with your test laptops, but may reproduce on your deployed laptops. We don't have a firm idea of the probability distribution, but my estimate is somewhere between 5% and 20% of a population may be affected, depending on manufacturing variations. You might control for this risk by monitoring failures and applying firmware updates only to affected laptops. (The problem is caused by the new kernel relying on the contents of memory which is not initialised by the BIOS). On Wed, Feb 16, 2011 at 04:15:37PM -0200, Daniel Castelo wrote: > My question is, the use of setolpckeys in our F11 build could be > dangerous or incompatible with the keyboard mapping based on HAL? I'm not sure. I think you should test it. Paul may have a response. -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Planning to package our 'audited' libtommath and libtomcrypt
And now bios-crypto is also cleaned up and packaged. Use and abuse Specs and patches in fedpkg-style: http://dev.laptop.org/git/packages/bios-crypto http://dev.laptop.org/git/packages/tomsfastmath-audited/ http://dev.laptop.org/git/packages/libtomcrypt-audited/ And the resulting rpms at: http://dev.laptop.org/~martin/public_rpms/f14/ This should simplify things for os-builder users, bitfrost packaging, XS management and deployments' work with local keys. I will probably fork off some of the scripts from bios-crypto -- stuff we use mainly for the XS and deployments work. cheers, m -- martin.langh...@gmail.com mar...@laptop.org -- Software Architect - OLPC - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: bios-crypto: do we use cli_tool or libtfm_cli.a / libtomcrypto_cli.a?
On Wed, Feb 16, 2011 at 2:19 PM, Mitch Bradley wrote: > I don't thing that cli_tool is needed. I don't use it. Thanks! I cleared it out. Made some changes in the bios-crypto repo, mainly makefiles. I tried hard to now affect your workflow; you should be able to build as you are used to, and at the same time the utilities are buildable against libtfm.a and libtomcrypto from rpms. That means we now have a much more presentable rpm for bios-crypto itself. m -- martin.langh...@gmail.com mar...@laptop.org -- Software Architect - OLPC - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: bios-crypto: do we use cli_tool or libtfm_cli.a / libtomcrypto_cli.a?
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 background at: > http://lists.laptop.org/pipermail/devel/2011-February/031163.html ] > > There are several bits in there that seem stale -- for example > cli_tool and the special _cli.a files > > If they are used, I'll be more than happy to include them in the > relevant rpms. If not, I'll prune them. > > cheers, > > > m ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
bios-crypto: do we use cli_tool or libtfm_cli.a / libtomcrypto_cli.a?
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 background at: http://lists.laptop.org/pipermail/devel/2011-February/031163.html ] There are several bits in there that seem stale -- for example cli_tool and the special _cli.a files If they are used, I'll be more than happy to include them in the relevant rpms. If not, I'll prune them. cheers, m -- martin.langh...@gmail.com mar...@laptop.org -- Software Architect - OLPC - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: 10.1.3 image and Firmware q2e42
Our idea is that just our technical stuff (and maybe volunteers with certain knowledge) could update the firmware. But this process will take us at least two or three months. So, we want to release our new software version trying to make it compatible with both firmware version Q2E41 and Q2E45. You have mentioned some bugs that could affect us: * #9100 (machines hanging during boot) * EC firmware which fixes issues with resuming from suspend from the touchpad * bugs in selftest diagnostics * others that could affect OFW's ability to install new releases We couldn't reproduce the bug #9100, and maybe we could accept the price of the other bugs that you have mentioned. However we have another problem in the keyboard mapping: the user couldn't use certain special keys, for example the "frame" key. I know that in the past the keyboard mapping configuration has changed from setolpckeys utility to HAL. The workaround that we found is the use of "setolpckeys" in our F11 image. If we copy /etc/udev/rules.d/96-olpc-keyboard.rules and /usr/sbin/setolpckeys all the key combination work. My question is, the use of setolpckeys in our F11 build could be dangerous or incompatible with the keyboard mapping based on HAL? Regards, Daniel. On Tue, Feb 1, 2011 at 6:02 PM, Paul Fox wrote: > daniel wrote: > > Hi! We are using a software image based on dextrose, I know that the > > official OLPC software image is different, but for this question I think > > that is the same. > > We want to install dextrose (suppose 10.1.3 image) with the firmware > q2e42. > > What do you think? This is possible or we will have problems with this > > combination of firmware and software image? > > you can read the release notes for the firmware releases between > q2e42 and q2e45 here: >http://wiki.laptop.org/go/OLPC_Firmware_q2e45 >http://wiki.laptop.org/go/OLPC_Firmware_q2e44 >http://wiki.laptop.org/go/OLPC_Firmware_q2e43 > > i'm sure the release will run. but q2e45 in particular contains > a fix for machines hanging during boot (d.l.o #9100) as well > as EC firmware which fixes issues with resuming from suspend from > the touchpad. you can also see that q2e43 fixed very many bugs -- > many of them are related to the selftest diagnostics, but others > could affect OFW's ability to install new releases. > > we don't issue new firmware lightly, and of course we recommend > that deployments always use the latest firmware. > > paul > > > > > Regards, Daniel. > > > > -- Forwarded message -- > > From: Daniel Castelo > > Date: Tue, Feb 1, 2011 at 4:25 PM > > Subject: Dextrose and Firmware q2e42 > > To: dextr...@lists.sugarlabs.org > > > > > > We have delivered dextrose 1.0 for our XO 1.5 machines, we want to > release > > this version to XO 1.0 one's, but based on some bad experiences that we > had > > in the past we aren't allowed to update the firmware (problems with some > > machines that remained broken after the process). The question is, if we > > have the firmware q2e42 installed, will dextrose (version 1) run > properly in > > this machines? > > After a first test ( ten minutes one) seem that works, but I suppose > that we > > could have some problems if we don't update the firmware to the last > > version. > > > > > > Thanks > > Daniel > > > > -- > > Ing. Daniel Castelo > > Plan Ceibal - Área Técnica > > Avda. Italia 6201 > > Montevideo - Uruguay. > > Tel.: 2 601 57 73 Interno 2228 > > E-mail : dcast...@plan.ceibal.edu.uy > > part 2 text/plain 129 > > ___ > > Devel mailing list > > Devel@lists.laptop.org > > http://lists.laptop.org/listinfo/devel > > =- > paul fox, p...@laptop.org > -- Ing. Daniel Castelo Plan Ceibal - Área Técnica Avda. Italia 6201 Montevideo - Uruguay. Tel.: 2 601 57 73 Interno 2228 E-mail : dcast...@plan.ceibal.edu.uy ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: 11.2.0 development build 9 released
On 16 February 2011 14:41, Gonzalo Odiard wrote: > Read 88 is not here? Read was dropped when we dropped all activities that weren't compatible with 0.90. Wasn't aware you'd finished fixing that now. Queued for next build. Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: 11.2.0 development build 9 released
Read 88 is not here? http://activities.sugarlabs.org/es-ES/sugar/addon/4028 Gonzalo On Wed, Feb 16, 2011 at 11:21 AM, Daniel Drake wrote: > http://wiki.laptop.org/go/11.2.0 > > http://build.laptop.org/11.2.0/os9 > > The bug where keyboard sometimes stops working after resume (#10650) > is hopefully fixed by this release. > > Notable updates: > Maze updated to v7 > Scratch updated to v17 > TamTamMini updated to v56 > Write updated to v73 > > Fixed bugs: > #10684 Browse has no "busy" indication > #10690 Cannot play music in TamTamMini using the keyboard > ___ > 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
11.2.0 development build 9 released
http://wiki.laptop.org/go/11.2.0 http://build.laptop.org/11.2.0/os9 The bug where keyboard sometimes stops working after resume (#10650) is hopefully fixed by this release. Notable updates: Maze updated to v7 Scratch updated to v17 TamTamMini updated to v56 Write updated to v73 Fixed bugs: #10684 Browse has no "busy" indication #10690 Cannot play music in TamTamMini using the keyboard ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [BULK] XO 1.5 blackscreen
2011/2/15 James Cameron : > On Tue, Feb 15, 2011 at 08:42:15PM +, Ahmed MANSOUR wrote: >> I have a XO 1.5 that no longer boot, and display doesn't turn on at >> all with no booting sound. > > What serial number? > > Please review http://dev.laptop.org/ticket/10314 to see if the evidence > you have matches the other instances described there. > know there's a > chance it might prevent booting once power is up. My serial number is SHC 9370109E I confirm that this is the same problem than the one stated in the ticket. -- Ahmed Mansour ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
