Re: 1.5 power management, input events, wakeup events
On Wed, Jun 24, 2009 at 9:56 PM, Daniel Drake wrote: > The end-user interface for those is unlikely to change much (if we do > the ACPI tables right). And we will pay the performance cost of ACPI? It was an oft-repeated thing that ACPI was evil because of complexity and slowness in the critical path to super smooth sleep-resume cycles. Were we overestimating the impact? cheers, m -- martin.langh...@gmail.com mar...@laptop.org -- School Server Architect - 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: 1.5 power management, input events, wakeup events
Hi, > And we will pay the performance cost of ACPI? It was an > oft-repeated thing that ACPI was evil because of complexity and > slowness in the critical path to super smooth sleep-resume > cycles. > Were we overestimating the impact? Yes, I believe so. We may even find that the slowness of some extra indirection before making the same function call we would otherwise make is not actually measurable. We'll find out in a week or two. The complexity of implementation is real, but it turned out that Mitch had to do the work of adding ACPI tables for Windows anyway. Being able to suspend/resume on unmodified distro kernels (and not having to constantly maintain and forward-port "the OLPC suspend/resume patch" every release) will be a big win, worth some hours of our time in setting up ACPI. - Chris. -- Chris Ball ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: 1.5 power management, input events, wakeup events
On Thu, Jun 25, 2009 at 15:49, Chris Ball wrote: > Hi, > > > And we will pay the performance cost of ACPI? It was an > > oft-repeated thing that ACPI was evil because of complexity and > > slowness in the critical path to super smooth sleep-resume > > cycles. > > > Were we overestimating the impact? > > Yes, I believe so. We may even find that the slowness of some extra > indirection before making the same function call we would otherwise > make is not actually measurable. We'll find out in a week or two. > > The complexity of implementation is real, but it turned out that Mitch > had to do the work of adding ACPI tables for Windows anyway. Being > able to suspend/resume on unmodified distro kernels (and not having to > constantly maintain and forward-port "the OLPC suspend/resume patch" > every release) will be a big win, worth some hours of our time in > setting up ACPI. Would that mean that gnome-power-manager and DeviceKit-power would work as-is on the XO-1.5? Regards, Tomeu > - Chris. > -- > Chris Ball > ___ > 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: 1.5 power management, input events, wakeup events
Hi, > Would that mean that gnome-power-manager and DeviceKit-power > would work as-is on the XO-1.5? I don't think we'd want to run gnome-power-manager because it would attempt to do things like manage the backlight, which we want to do ourselves as part of aggressive suspend/resume. But it would probably mean that we could run it and it would be able to figure out what's going on with our hardware, yes. - Chris. -- Chris Ball ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: 1.5 power management, input events, wakeup events
On Jun 25 2009, at 09:49, Chris Ball was caught saying: > The complexity of implementation is real, but it turned out that Mitch > had to do the work of adding ACPI tables for Windows anyway. Being > able to suspend/resume on unmodified distro kernels (and not having to > constantly maintain and forward-port "the OLPC suspend/resume patch" > every release) will be a big win, worth some hours of our time in > setting up ACPI. I'd like to second Chris on the benefits of running something that is already well supported under Linux and allows us to use standard PM tools. One concern I have is whether ACPI provides the granular control over wakeup events that we desire. ~Deepak ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Create and sign Country specific XO image
Hello Cambodia is getting 1000 new XOs very soon. This are the first ones with a Khmer keyboard. To make the installation process easier, I would like to create a country specific image based on build 802, which includes Khmer keyboard support, fonts, the newest language pack with software translations, Activities and some customizations. I found just very few information about creating a country specific image (mainly from Nepal): http://tiezemans.wordpress.com/2008/12/30/customizing-the-xo-image/ http://blog.olenepal.org/index.php/archives/183 http://wiki.laptop.org/go/Customizing_NAND_images How can I get a country specific image file signed? Which other customizations or bugfixes are recommended to be included (e.g. like the ones from paraguay http://lists.laptop.org/pipermail/devel/2009-March/023788.html)? Detailed instructions from other deployments about creating an image are very welcome. Thanks and best regards, Philipp ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Create and sign Country specific XO image
Philip, talk to reuben caron about getting the image signed. Personally, i think you are better off unlocking your XO's and using and unsigned image. If you want to create a custom image, my best recommendation is that you contract Ties Stuij or someone at OLPC to do it for you. Reuben may or may not have the resources to do it himself. Creating a custom image is a fair amount of work and you always have to change it later. On Fri, 2009-06-26 at 11:25 +0700, Philipp Kocher wrote: > Hello > > Cambodia is getting 1000 new XOs very soon. This are the first ones with > a Khmer keyboard. > > To make the installation process easier, I would like to create a > country specific image based on build 802, which includes Khmer keyboard > support, fonts, the newest language pack with software translations, > Activities and some customizations. > > I found just very few information about creating a country specific > image (mainly from Nepal): > http://tiezemans.wordpress.com/2008/12/30/customizing-the-xo-image/ > http://blog.olenepal.org/index.php/archives/183 > http://wiki.laptop.org/go/Customizing_NAND_images > > > How can I get a country specific image file signed? > > Which other customizations or bugfixes are recommended to be included > (e.g. like the ones from paraguay > http://lists.laptop.org/pipermail/devel/2009-March/023788.html)? > > Detailed instructions from other deployments about creating an image are > very welcome. > > Thanks and best regards, > Philipp > ___ > Devel mailing list > Devel@lists.laptop.org > http://lists.laptop.org/listinfo/devel -- Bryan W. Berry Technology Director OLE Nepal, http://www.olenepal.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: #9361 NORM 1.5-F11: drm not working
Hi guys, i'm currently offline and I'm missing an appointment for writing this e-mail, thus no time to log into RT. you have a chrome9 system, please don't try to use it with the old DRM code in the kernel which is for chrome/unichrome. VIA has some out-of-mainlien chrome9 DRM driver, which has been rejected from mainline inclusion so far, because 1) there were some severe security concerns (which I share). I think those have been addressed in later releases (see linux-fbdev-devel) 2) there is still no FOSS code using the DRM interface, and David Airlie seems reluctant to merge something 3) the only FOSS codebase that looks like it might eventually end up having DRM support on chrome9 so far (gallium3d) has modified the kernel/userspace API, and the kernel folks don't want to merge a driver before it provides one API that can be used by closed + open source drivers. -- - Harald Weltehttp://www.hmw-consulting.de/ = Consultant for Linux networking, network security, Linux driver development ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Create and sign Country specific XO image
On Fri, Jun 26, 2009 at 6:47 AM, Bryan Berry wrote: > Personally, i think you are better off unlocking your XO's and using and > unsigned image. Actually, the best option is to get the laptops with their own keys, so they can sign their image themselves. This keeps antitheft tools available. I'm finishing an XS release that supplies the bits that have been missing -- with it you can run the full blown antitheft scheme. cheers, m -- martin.langh...@gmail.com mar...@laptop.org -- School Server Architect - 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