Embedded Linux Conference Europe - registration open
OK, sorry in advance... I know this is a technical list, but I think this conference has a large amount of kernel-related topics (and no-one makes any money off the event). I won't post these very often, but here goes this one... CELF is happy to announce that the program for Embedded Linux Conference Europe 2008 is finalized, and registration is now open!! This year's conference will be held in conjunction with NLUUG Autumn Conference November 6-7 in Ede, The Netherlands at "de Reehorst". Please see: http://www.embeddedlinuxconference.com/elc_europe08/ for details. Click on the "Registration" tab and follow the instructions to register for the event. CELF is happy to announce our keynote speakers: * Harald Welte - Open Source liaison for VIA, and * David Woodhouse - official 'embedded' maintainer for the Linux kernel Another highlight of the event is our social event, where you can have dinner with penguins! Our conference program is particularly strong this year, including talks from numerous individuals and companies on a variety of useful topics. Here are just a few highlights: * Thomas Gleixner - maintainer of the x86 kernel architecture will report on this year's kernel summit * Bas Engel - of Philips will describe Linux use in digital televisions * Tim Bird - of Sony will give tips for fast-booting the Linux kernel * Vitaly Wool - of Embedded Alley will discuss embedded display technology and flash memory optimization and tuning * Stefan Seyfried - of SUSE will describe suspend modes and Linux power management Topics range from power management, to licensing, to wireless networking, to security, graphics, mobile applications, payment systems, and many more. Please see the conference web site for the full program. If you want to improve how you use Linux in embedded products, you owe it to yourself to attend this event! Note that the first 50 ELC Europe registrations will receive a free Early Bird gift! Note: The Embedded Linux Conference Europe is part of a broad range of technical events sponsored by the CE Linux forum to advance its mission of improving and enhancing Linux for use in consumer electronics products. For more information about the CE Linux Forum and our activities, see http://www.celinuxforum.org/ = Tim Bird Architecture Group Chair, CE Linux Forum Senior Staff Engineer, Sony Corporation of America = -- To unsubscribe from this list: send the line "unsubscribe linux-embedded" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
RFC - size tool for kernel build system
I've been thinking about a tool that might be useful to track kernel size changes. I'm posting this Request For Comments to get feedback, and determine if this is something that would be worthwhile to pursue. What I envision is some new kernel build targets, specifically related to gathering size information and generating a size comparison report. Some small helper scripts would be written to gather the necessary information, and generate the report. A kernel developer would type: 1) make size-baseline And kernel size information would be recorded for the current kernel (after a build, if needed). I envision this saving off the .config and System.map, the result of 'size vmlinux' and several of the 'size */builtin.o' results. Additionally (and optionally), a program could be run to acquire some size information from a running system (e.g. a newly booted system, or a system under a particular load), to include in the baseline report. All of the gathered information would be stored as the "size baseline". --- After making some modifications, either to the source or the configuration, the developer could type: 2) make size-report The kernel size information would be recorded again, and compared with the size-baseline results. A report of differences (e.g. from bloat-o-meter and other comparison tools) would be produced. Any differences exceeding some threshhold (specified in a size-watch config file?) could be highlighted. The git commit IDs would be recorded, as well as differences between the configs used (e.g. diffconfig output). If some designated size difference exceeds a threshold (specified in the size-watch configuration) then the make could return an error, while still producing the report. This would mean that this could be used for git bisection to find a size regression. Another way to look at this, would be that a developer could pick a specific size value to monitor (for example, the static size of the network sub-system, or the size of a particular slab in the dynamic memory of a newly booted kernel). They would specify that in the size-watch config, and could monitor that size over time and under various configurations. I envision a couple of usages: 1) A developer could use this to be able to see a report about the total size increases caused by a patch they are about to submit 2) A developer could compare kernel versions for overall size changes 3) A maintainer could examine the affect of a patch on the size of their subsystem. 4) A developer could compare different kernel configs to see the impact of configuration option choices. 5) An automated tool could generate size values to associate with different config option choices (at least, starting from a consistent config set). 6) An automated tool could generate size values for each kernel version (this is what Bloatwatch does now). Bloatwatch generates information on the static size information for various kernel versions. This would have a similar purpose, but the intent would be to integrate it into the kernel build system, to allow any developer to measure the size information, and highlight and track the information of their choice. Any comments? -- Tim = Tim Bird Architecture Group Chair, CE Linux Forum Senior Staff Engineer, Sony Corporation of America = -- To unsubscribe from this list: send the line "unsubscribe linux-embedded" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: PRAMFS with XIP support
On Tue, Oct 7, 2008 at 05:14, Marco Stornelli wrote: > I enjoyed to make a porting of pramfs to the kernel 2.6.26.5. In > addition, I made a patch to add execute-in-place support. You can > download the patches from the project site under "tracker/patches". If > you have comments and/or suggestions you can write to me an email :). why not submit it for inclusion to lkml ? -mike -- To unsubscribe from this list: send the line "unsubscribe linux-embedded" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
PRAMFS with XIP support
Hi all, I enjoyed to make a porting of pramfs to the kernel 2.6.26.5. In addition, I made a patch to add execute-in-place support. You can download the patches from the project site under "tracker/patches". If you have comments and/or suggestions you can write to me an email :). Thanks. Regards, -- Marco Stornelli Embedded Software Engineer CoRiTeL - Consorzio di Ricerca sulle Telecomunicazioni http://www.coritel.it [EMAIL PROTECTED] +39 06 72582838 -- To unsubscribe from this list: send the line "unsubscribe linux-embedded" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
