Bug#550584: Initial triggers patch and tracking of highest kernel

2011-03-10 Thread Vagrant Cascadian
On Thu, Mar 10, 2011 at 01:10:41PM +, Hector Oron wrote: > 2011/3/10 Hector Oron : > > 2011/3/10 Loïc Minier : > > >>>  1. Chainload boot, at first boot load the usual kernel then call the > >>> new one with kexec, if everything is fine then the user can replace > >>> old kernel with new kerne

Bug#550584: Initial triggers patch and tracking of highest kernel

2011-03-10 Thread Loïc Minier
On Thu, Mar 10, 2011, Hector Oron wrote: > I meant that initramfs-tools do not support cross initrd generation, > but sure that should be provided by the hooks in the package. Ah I see what you mean; this might be something we need to raise to the initramfs-tools / kernel teams; I see the kernel

Bug#550584: Initial triggers patch and tracking of highest kernel

2011-03-10 Thread Hector Oron
Hi, 2011/3/10 Loïc Minier : >  Not sure what you mean; I understand that cross-compiled kernel .debs >  should follow the same interface (/etc/kernel*) as described in the >  kernel packaging handbook.  Maybe the tool you use doesn't generate the >  proper postinsts and needs to be fixed? I mean

Bug#550584: Initial triggers patch and tracking of highest kernel

2011-03-10 Thread Loïc Minier
On Thu, Mar 10, 2011, Hector Oron wrote: > We got this running in a board of ours, it is provided by a script in > the initrd, it loads a kernel from NOR then chain loads into kernel > provided by rootfs. I guess that would be a separated bug report. Yeah; I'm not even sure this should be handled

Bug#550584: Initial triggers patch and tracking of highest kernel

2011-03-10 Thread Hector Oron
Hi, 2011/3/10 Hector Oron : > 2011/3/10 Loïc Minier : >>>  1. Chainload boot, at first boot load the usual kernel then call the >>> new one with kexec, if everything is fine then the user can replace >>> old kernel with new kernel, else the kexec call fails and leaves you >>> with old kernel. >

Bug#550584: Initial triggers patch and tracking of highest kernel

2011-03-10 Thread Hector Oron
Hi, 2011/3/10 Loïc Minier : >  Ah thanks; sorry that it's not working, do you have the log of running >  flash-kernel/kernel updates etc.? Sorry I do not keep any logs, I'll do next time. >>  1. Chainload boot, at first boot load the usual kernel then call the >> new one with kexec, if everythi

Bug#550584: Initial triggers patch and tracking of highest kernel

2011-03-10 Thread Loïc Minier
On Thu, Mar 10, 2011, Hector Oron wrote: > Last night I tested this patch, but maybe I was doing something wrong > as it did not seem to work. Then I manually generated uImage and > uInitrd and now kernel stalls at: Ah thanks; sorry that it's not working, do you have the log of running flash-ker

Bug#550584: Initial triggers patch and tracking of highest kernel

2011-03-10 Thread Hector Oron
Hi, 2011/3/9 Loïc Minier : >  I had forgotten the actual flash-kernel call.  I've also added >  a --supported test at the top in this v2. Last night I tested this patch, but maybe I was doing something wrong as it did not seem to work. Then I manually generated uImage and uInitrd and now kernel

Bug#550584: Initial triggers patch and tracking of highest kernel

2011-03-10 Thread Steve McIntyre
On Wed, Mar 09, 2011 at 08:18:44PM +0100, Loïc Minier wrote: >On Wed, Mar 09, 2011, Steve McIntyre wrote: >> Neither do I *for definite*, but I know that other tools that rely on >> kernel ABI have been thrown by the sort order of "trunk" vs "1", "2", >> etc. so I'm raising it early in case it matt

Bug#550584: Initial triggers patch and tracking of highest kernel

2011-03-09 Thread Loïc Minier
On Wed, Mar 09, 2011, Steve McIntyre wrote: > Neither do I *for definite*, but I know that other tools that rely on > kernel ABI have been thrown by the sort order of "trunk" vs "1", "2", > etc. so I'm raising it early in case it matters. My first reaction was that it was basically the problem of

Bug#550584: Initial triggers patch and tracking of highest kernel

2011-03-09 Thread Steve McIntyre
On Wed, Mar 09, 2011 at 07:54:00PM +0100, Loïc Minier wrote: >On Wed, Mar 09, 2011, Steve McIntyre wrote: >> Can we work it out by looking at any kernels that are currently >> installed, or checking in u-boot setup (or similar) which kernel it's >> currently going to use? It bothers me a little tha

Bug#550584: Initial triggers patch and tracking of highest kernel

2011-03-09 Thread Loïc Minier
On Wed, Mar 09, 2011, Steve McIntyre wrote: > Can we work it out by looking at any kernels that are currently > installed, or checking in u-boot setup (or similar) which kernel it's > currently going to use? It bothers me a little that we need to keep > state somewhere, but I don't see a better way

Bug#550584: Initial triggers patch and tracking of highest kernel

2011-03-09 Thread Steve McIntyre
On Wed, Mar 09, 2011 at 04:10:03AM +0100, Loïc Minier wrote: >Hey > > I've read through the bug, but still didn't setup a test environment, > but "triggered" by Hector and Clint's activity on the bug I thought I'd > rather share patches and proposals early. > > First, quick problem statemen

Bug#550584: Initial triggers patch and tracking of highest kernel

2011-03-08 Thread Loïc Minier
On Wed, Mar 09, 2011, Loïc Minier wrote: > I'm attaching a naive implementation which doesn't deal with removals > and only keeps track of the latest initrd ABI (not of the kernel one). I had forgotten the actual flash-kernel call. I've also added a --supported test at the top in this v2. --

Bug#550584: Initial triggers patch and tracking of highest kernel

2011-03-08 Thread Loïc Minier
Hey I've read through the bug, but still didn't setup a test environment, but "triggered" by Hector and Clint's activity on the bug I thought I'd rather share patches and proposals early. First, quick problem statement: a) flash-kernel isn't called when installing a new kernel ABI b