On Wed, Apr 06, 2011 at 01:44:16PM +0800, Shawn Guo wrote:
Hi Paul,
On Tue, Apr 05, 2011 at 12:59:27PM -0700, Paul E. McKenney wrote:
On Tue, Apr 05, 2011 at 01:11:43PM -0600, Grant Likely wrote:
Hey Paul,
As promised, here is my list of topics, tasks and priorities for the 11.11 cycle. It's a bit of a rough list, but I'll refine it as we get closer to UDS
Thank you, Grant! I have summarized this in the table that I am building:
https://wiki.linaro.org/Cycles/1111/TechnicalTopics/Kernel
I have made rough guesses at priorities, please let me know what priorities would be better.
Boot Architecture
I have this as K3. I put the boot-architecture paper as "high", kexec boot loader as "low", and all else as "medium".
- Refine UEFI position paper (draft of position paper will be prepared
before UDS)
- Refine boot architecture technical recommendations paper (draft will
be prepared before UDS)
- must include reference implementation (based on existing u-boot;
not talking about writing something new here)
- Upgrade procedure for OS
- Upgrade procedure for Firmware
- Security concerns?
- Must guarantee reliability (no bricked boards).
- Discuss kexec bootloader, possibly implement for 11.11 cycle
- Implement appending of device tree and initrd to zImage
- To support minimal bootloader and kexec bootloaders.
- Simplify the process of installing a boot image.
- Implement device tree bindings to describing boot method
- So that Linux knows how to upgrade the kernel and possibly the bootloader.
- SDcard? NAND? NOR? Which partition? etc.
I've got a lot of topics on boot architecture. Most of the needed technology is in place, but I think it is needed to document best practices and methods that should be used when designing a system. What technologies, why, how to put them together, and how to maintain/support them. It's important to get the guidelines out onto paper instead of as 'tribal knowledge'
Device Tree
I have this as K3. The virq work marked "essential", the others marked "high".
You probably meant K2 here.
Indeed I did! I had both device tree and boot architecture as K3, which I have now fixed.
Thanx, Paul