Re: [Techteam] New F14-arm build os36 - Sugar in sync, device-tree!
Hi Peter, With this image installed (and yum update executed) the following activities does not work yet: TamTam* Write: no abiword module Jukebox, started but did not played a ogg file Read: no module webkit There are other problems, but I am working with the maintainers. Are these known issues? If you have rpms and want do tests, tell me Gonzalo On Sat, Aug 6, 2011 at 9:12 AM, Peter Robinson pbrobin...@gmail.com wrote: On Fri, Aug 5, 2011 at 11:52 PM, Martin Langhoff mar...@laptop.org wrote: The Sugar in sync! device-tree build. Download from: http://build.laptop.org/F14-arm/os32/ Use with OFW Q4B07 - http://wiki.laptop.org/go/OLPC_Firmware_q4b07 Changes and notes: - sugar and sugar-toolkit rpms are at 0.92.4! - abiword and libabiword are in, but may have been built without asio (the network/collaboration side) -- please test collaboration! This is now fixed and built. I think the actual NVRs are less so its likely it won't be pulled in. I'll fix that soon so I would wait. - In kernel land... = We have device-tree! So what used to be in /ofw now appears in /proc/device-tree . Time to port bitfrost, dracut-modules-olpc, sugar control panel, olpc-utils. Thanks Andres, Mitch and Saadia! = There is a new schedulear/timer patch from Lennert -- mystery minutes-long hangs should be gone for real now. - Some packages have been downgraded - need to work with Peter on these -dracut-006-3.fc14.noarch -dracut-modules-olpc-0.5.3-1.fc14.1.armv5tel +dracut-006-2.fc14.noarch +dracut-modules-olpc-0.5.3-1.fc14.armv5tel -linux-firmware-20100806-4.fc14.noarch +linux-firmware-20100106-4.fc14.noarch -olpc-update-2.23-1.fc14.noarch +olpc-update-2.22-1.fc14.noarch All of those should be now fixed. Also I'm in the process of importing 4500 packages that are noarch so they don't need to be rebuilt. So there's going to be a lot of churn very soon but it should get us a lot closer. I'll look at doing the same for updates soon too, just need to check what the deps and other possible issues would be in doing that. I've also untagged all packages that have a newer NVR. I'll let you know when it all settles as at that point its likely worth while cutting another release and comparing the change in packages. Peter ___ 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: [Techteam] New F14-arm build os36 - Sugar in sync, device-tree!
On Tue, Aug 9, 2011 at 2:26 PM, Gonzalo Odiard gonz...@laptop.org wrote: Hi Peter, With this image installed (and yum update executed) the following activities does not work yet: TamTam* Write: no abiword module Jukebox, started but did not played a ogg file Read: no module webkit There are other problems, but I am working with the maintainers. Are these known issues? Mostly. The Write and Read issues are known. Write will be fixed in the next OS build, webkit is a known issue. Jukebox might be fixed in the next one too as there's some newer gstreamer packages. We're in the middle of some mass churn since the weekend, its starting to settle out now. Once its settled I plan to do another OS build. That will likely be in the Thurs time frame. Peter If you have rpms and want do tests, tell me Gonzalo On Sat, Aug 6, 2011 at 9:12 AM, Peter Robinson pbrobin...@gmail.com wrote: On Fri, Aug 5, 2011 at 11:52 PM, Martin Langhoff mar...@laptop.org wrote: The Sugar in sync! device-tree build. Download from: http://build.laptop.org/F14-arm/os32/ Use with OFW Q4B07 - http://wiki.laptop.org/go/OLPC_Firmware_q4b07 Changes and notes: - sugar and sugar-toolkit rpms are at 0.92.4! - abiword and libabiword are in, but may have been built without asio (the network/collaboration side) -- please test collaboration! This is now fixed and built. I think the actual NVRs are less so its likely it won't be pulled in. I'll fix that soon so I would wait. - In kernel land... = We have device-tree! So what used to be in /ofw now appears in /proc/device-tree . Time to port bitfrost, dracut-modules-olpc, sugar control panel, olpc-utils. Thanks Andres, Mitch and Saadia! = There is a new schedulear/timer patch from Lennert -- mystery minutes-long hangs should be gone for real now. - Some packages have been downgraded - need to work with Peter on these -dracut-006-3.fc14.noarch -dracut-modules-olpc-0.5.3-1.fc14.1.armv5tel +dracut-006-2.fc14.noarch +dracut-modules-olpc-0.5.3-1.fc14.armv5tel -linux-firmware-20100806-4.fc14.noarch +linux-firmware-20100106-4.fc14.noarch -olpc-update-2.23-1.fc14.noarch +olpc-update-2.22-1.fc14.noarch All of those should be now fixed. Also I'm in the process of importing 4500 packages that are noarch so they don't need to be rebuilt. So there's going to be a lot of churn very soon but it should get us a lot closer. I'll look at doing the same for updates soon too, just need to check what the deps and other possible issues would be in doing that. I've also untagged all packages that have a newer NVR. I'll let you know when it all settles as at that point its likely worth while cutting another release and comparing the change in packages. Peter ___ 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 F14-arm build os36 - Sugar in sync, device-tree!
On Sun, Aug 07, 2011 at 12:40:33PM -0400, Chris Ball wrote: On Sat, Aug 06 2011, Niels de Vos wrote: = We have device-tree! So what used to be in /ofw now appears in /proc/device-tree . Time to port bitfrost, dracut-modules-olpc, sugar control panel, olpc-utils. Thanks Andres, Mitch and Saadia! Wow, this is quite impressive! You must be one of the first that have this in a real distribution for ARM :) I think ChromiumOS is using flattened trees, but we're also running Open Firmware and have it stay resident to be called into. Ah, didn't know ChromiumOS used it too. It may be that OpenFirmware makes it easier (as PPC gathered some initial experience with FDT), it's very cool never the less! = There is a new schedulear/timer patch from Lennert -- mystery minutes-long hangs should be gone for real now. Do you have any references like a git-commit or discussion on a mailinglist for this? I'd like to match this with some other ARM hardware (non/OLPC) issues I have seen. There's a description of our problem at: http://dev.laptop.org/git/olpc-kernel/commit/?h=arm-3.0id=b8923ed0809f29e53bd246153ca3a9e9367b4c56 Nice description! As it's mach-mmp dependent, it's unlikely that I can apply this for mx51 based systems. The information in the git-commit is clear and I'll try to investigate if 'sporadic hangs' could be caused due to missing events. (Which sounds sane, as it might happen when the system is under high load.) Many thanks for your reply, Niels ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [OLPC Engineering] [Techteam] New F14-arm build os36 - Sugar in sync, device-tree!
On Mon, Aug 8, 2011 at 11:22 AM, Lennert Buytenhek buyt...@wantstofly.org wrote: On Sat, Aug 06, 2011 at 03:44:09PM +0100, Niels de Vos wrote: = There is a new schedulear/timer patch from Lennert -- mystery minutes-long hangs should be gone for real now. Do you have any references like a git-commit or discussion on a mailinglist for this? I'd like to match this with some other ARM hardware (non/OLPC) issues I have seen. I submitted it upstream here: http://marc.info/?l=linux-arm-kernelm=131223859020216w=2 http://marc.info/?l=linux-arm-kernelm=131223860820224w=2 http://marc.info/?l=linux-arm-kernelm=131223862820251w=2 http://marc.info/?l=linux-arm-kernelm=131223864920268w=2 Cool, many thanks for pointing to the exact patches! Niels ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: New F14-arm build os36 - Sugar in sync, device-tree!
On Tue, Aug 09, 2011 at 02:49:42PM +0100, Niels de Vos wrote: = There is a new schedulear/timer patch from Lennert -- mystery minutes-long hangs should be gone for real now. Do you have any references like a git-commit or discussion on a mailinglist for this? I'd like to match this with some other ARM hardware (non/OLPC) issues I have seen. There's a description of our problem at: http://dev.laptop.org/git/olpc-kernel/commit/?h=arm-3.0id=b8923ed0809f29e53bd246153ca3a9e9367b4c56 Nice description! As it's mach-mmp dependent, it's unlikely that I can apply this for mx51 based systems. The information in the git-commit is clear and I'll try to investigate if 'sporadic hangs' could be caused due to missing events. (Which sounds sane, as it might happen when the system is under high load.) Looking at arch/arm/plat-mxc/time.c and its *_set_next_event() functions, it appears to correctly handle the case where the timeout has already expired, so it's not likely that mx51 is suffering from the same problem. thanks, Lennert ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: New F14-arm build os36 - Sugar in sync, device-tree!
On Tue, Aug 9, 2011 at 2:59 PM, Lennert Buytenhek buyt...@wantstofly.org wrote: On Tue, Aug 09, 2011 at 02:49:42PM +0100, Niels de Vos wrote: = There is a new schedulear/timer patch from Lennert -- mystery minutes-long hangs should be gone for real now. Do you have any references like a git-commit or discussion on a mailinglist for this? I'd like to match this with some other ARM hardware (non/OLPC) issues I have seen. There's a description of our problem at: http://dev.laptop.org/git/olpc-kernel/commit/?h=arm-3.0id=b8923ed0809f29e53bd246153ca3a9e9367b4c56 Nice description! As it's mach-mmp dependent, it's unlikely that I can apply this for mx51 based systems. The information in the git-commit is clear and I'll try to investigate if 'sporadic hangs' could be caused due to missing events. (Which sounds sane, as it might happen when the system is under high load.) Looking at arch/arm/plat-mxc/time.c and its *_set_next_event() functions, it appears to correctly handle the case where the timeout has already expired, so it's not likely that mx51 is suffering from the same problem. Wow, thats a swift reply! Thanks for checking :) Niels ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
ARM summit at Plumbers 2011
Hi folks, Following on from the founding of the cross-distro ARM mailing list, I'd like to propose an ARM summit at this year's Linux Plumbers conference [1]. I'm hoping for a slot on Thursday evening, but this remains to be confirmed at this point. We had some lively discussion about the state of ARM Linux distros at the Linaro Connect [2] event in Cambridge last week. It rapidly became clear that some of the topics we discussed deserve a wider audience, so we're suggesting a meetup at Plumbers for that bigger discussion. The initial proposed agenda is: * ARM hard-float + What is it and why does it matter? + How can distributions keep compatible (i.e. gcc triplet to describe the port)? * Adding support for ARM as an architecture to the Linux Standard Base (LSB) + Does it matter? + What's needed? * FHS - multi-arch coming soon, how do we proceed? * 3D support on ARM platforms + Open GL vs. GLES - which is appropriate? but I'm sure that other people will think of more issues they'd like to discuss. :-) If you wish to attend, please reply to the cross-distro list and let us know to expect you. Make sure you're registered to attend Plumbers Conf, and get your travel and accommodation organised ASAP. [1] http://www.linuxplumbersconf.org/2011/ [2] http://connect.linaro.org/ Cheers, -- Steve McIntyresteve.mcint...@linaro.org http://www.linaro.org/ Linaro.org | Open source software for ARM SoCs ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: ARM summit at Plumbers 2011
On Tue, Aug 9, 2011 at 11:15 AM, Steve McIntyre steve.mcint...@linaro.org wrote: Hi folks, Following on from the founding of the cross-distro ARM mailing list, I'd like to propose an ARM summit at this year's Linux Plumbers conference [1]. I'm hoping for a slot on Thursday evening, but this remains to be confirmed at this point. We had some lively discussion about the state of ARM Linux distros at the Linaro Connect [2] event in Cambridge last week. It rapidly became clear that some of the topics we discussed deserve a wider audience, so we're suggesting a meetup at Plumbers for that bigger discussion. The initial proposed agenda is: * ARM hard-float + What is it and why does it matter? + How can distributions keep compatible (i.e. gcc triplet to describe the port)? * Adding support for ARM as an architecture to the Linux Standard Base (LSB) + Does it matter? + What's needed? * FHS - multi-arch coming soon, how do we proceed? * 3D support on ARM platforms + Open GL vs. GLES - which is appropriate? but I'm sure that other people will think of more issues they'd like to discuss. :-) If you wish to attend, please reply to the cross-distro list and let us know to expect you. Make sure you're registered to attend Plumbers Conf, and get your travel and accommodation organised ASAP. [1] http://www.linuxplumbersconf.org/2011/ [2] http://connect.linaro.org/ Cheers, -- Steve McIntyre steve.mcint...@linaro.org http://www.linaro.org/ Linaro.org | Open source software for ARM SoCs ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel I should also point out that we will be hosting the OLPC SF Community Summit 2011 October 21 thru 23, which is right before the ARM TechCon 2011 in Santa Clara, CA (45 miles south of San Francisco) http://e.ubmelectronics.com/armtechcon/index.html The ARM conference dates were one consideration in picking our summit dates. Wrap up on Sunday, sightseeing on Monday, ARM conf on Tuesday :-) cheers, Sameer -- Dr. Sameer Verma, Ph.D. Professor, Information Systems San Francisco State University http://verma.sfsu.edu/ http://opensource.sfsu.edu/ http://is.sfsu.edu/ http://olpcsf.org/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
identifying a 1.75
on XO-1 and XO-1.5, we were able to discover the model of the laptop from the information under /sys/class/dmi/id. the DMI schema comes from the PC world, and we can't expect it to exist on ARM. there was also information to be found in /ofw on those machines, like serial number, and uuid. the hex model designator found there was used as a fallback if the dmi tree wasn't there (on older XO-1 firmware). on 1.75, there's no dmi tree, and /ofw has moved to /proc/device-tree, so we need to modify a lot of places that try and dig up platform info. (see #6) so i'm floating the attached script, tentatively named olpc-hwinfo, as a strawman. i think it gives access to the most often needed info, and can obviously be expanded if needed. it would go in olpc-utils, which would put it in /usr/sbin (since some clients live in /usr/sbin). thoughts/comments? better approaches? obvious additions? paul =- paul fox, p...@laptop.org olpc-hwinfo Description: - ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: identifying a 1.75
On Tue, Aug 9, 2011 at 16:31, Paul Fox p...@laptop.org wrote: on XO-1 and XO-1.5, we were able to discover the model of the laptop from the information under /sys/class/dmi/id. the DMI schema comes from the PC world, and we can't expect it to exist on ARM. there was also information to be found in /ofw on those machines, like serial number, and uuid. the hex model designator found there was used as a fallback if the dmi tree wasn't there (on older XO-1 firmware). on 1.75, there's no dmi tree, and /ofw has moved to /proc/device-tree, so we need to modify a lot of places that try and dig up platform info. (see #6) so i'm floating the attached script, tentatively named olpc-hwinfo, as a strawman. i think it gives access to the most often needed info, and can obviously be expanded if needed. it would go in olpc-utils, which would put it in /usr/sbin (since some clients live in /usr/sbin). thoughts/comments? better approaches? obvious additions? Check the CPU? Shouldn't /proc/cpuinfo tell you what you have since the major change is cpu? -- Stephen J Smoogen. The core skill of innovators is error recovery, not failure avoidance. Randy Nelson, President of Pixar University. Let us be kind, one to another, for most of us are fighting a hard battle. -- Ian MacLaren ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: identifying a 1.75
stephen john smoogen wrote: On Tue, Aug 9, 2011 at 16:31, Paul Fox p...@laptop.org wrote: on XO-1 and XO-1.5, we were able to discover the model of the laptop from the information under /sys/class/dmi/id. the DMI schema comes from the PC world, and we can't expect it to exist on ARM. there was also information to be found in /ofw on those machines, like serial number, and uuid. the hex model designator found there was used as a fallback if the dmi tree wasn't there (on older XO-1 firmware). on 1.75, there's no dmi tree, and /ofw has moved to /proc/device-tree, so we need to modify a lot of places that try and dig up platform info. (see #6) so i'm floating the attached script, tentatively named olpc-hwinfo, as a strawman. i think it gives access to the most often needed info, and can obviously be expanded if needed. it would go in olpc-utils, which would put it in /usr/sbin (since some clients live in /usr/sbin). thoughts/comments? better approaches? obvious additions? Check the CPU? Shouldn't /proc/cpuinfo tell you what you have since the major change is cpu? yeah, i thought of that. it's likely the next OLPC product will use the same processor, so we'll need something else in the future anyway. it happens that /proc/cpuinfo even says: Hardware: OLPC XO-1.75 (since ARM kernels provide slightly different info than x86 kernels), which makes it very tempting to use that. but if we're lucky, the next product might share the same kernel (so that string may change). in any case, i think i'd prefer using info that sourced from the hardware or firmware rather than a compiled in string. (but maybe i'm missing something here, and that line in /proc/cpuinfo is exactly what we should be using. anyone?) paul =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: identifying a 1.75
On Tue, Aug 9, 2011 at 6:31 PM, Paul Fox p...@laptop.org wrote: thoughts/comments? better approaches? obvious additions? Hi Paul timely - I was just hacking on olpc-utils, bitfrost and sugar on exactly the same thing (while on the plane, no internet). Something along the lines of what you have is needed, I'll probably merge it into my hacking. And we need it as part of a mini bash function library as well, machine identification and other tasks reading from ofw are spread across olpc-utils at random. So I'll prolly hack olpc-hwinfo into a shell of what you posted (oh! the pun!) -- calling into shared function calls. And will refactor other scripts to match. 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: identifying a 1.75
martin wrote: On Tue, Aug 9, 2011 at 6:31 PM, Paul Fox p...@laptop.org wrote: thoughts/comments? better approaches? obvious additions? Hi Paul timely - I was just hacking on olpc-utils, bitfrost and sugar on exactly the same thing (while on the plane, no internet). Something along the lines of what you have is needed, I'll probably merge it into my hacking. And we need it as part of a mini bash function library as well, machine identification and other tasks reading from ofw are spread across olpc-utils at random. So I'll prolly hack olpc-hwinfo into a shell of what you posted (oh! the pun!) -- calling into shared function calls. And will refactor other scripts to match. okay. most clients don't need hw info at high rates, so i figured a self-contained script would be sufficient (and necessary, for some clients). but certainly refactoring into sourceable chunks is a fine idea. (and more to the point, i won't commit anything -- ball's in your court. :-) paul =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
