login
Search
David Mosberger reported in a lkml mesage Linus's current bk tree (http://linux.bkbits.net:8080/linux-2.5) builds and works out of the box for ia64! He adds:
"For maximum performance/stability, I'd still recommend to use the ia64-specific patches, but for someone who needs to build bleeding edge kernels for multiple architectures, being able to use Linus' tree should make it a lot easier to include ia64 in their regular testing."
From: David Mosberger To: linux-ia64 Subject: milstone reached: ia64 linux builds out of Linus' tree Date: 2003-08-04 17:37:39 As of this morning, Linus's current bk tree (http://linux.bkbits.net:8080/linux-2.5) builds and works out of the box for ia64! Thanks to everybody who helped make this happen. In particular, thanks to Andrew Morton and Christoph Hellwig for their efforts, and Andy Grover for a last-minute ACPI patch! For maximum performance/stability, I'd still recommend to use the ia64-specific patches, but for someone who needs to build bleeding edge kernels for multiple architectures, being able to use Linus' tree should make it a lot easier to include ia64 in their regular testing etc. Now that Linus' tree works for ia64, the next question is how we can keep it that way. I think it would be useful to have someone setup a cron job which does daily builds/automated tests off of Linus tree. If something breaks, the person doing this could perhaps come up with a minimal patch which gets Linus' tree to build again (and submit a patch to the appropriate maintainer, with cc to the linux-ia64 list). I plan on continuing to put out roughly monthly ia64-specific patches and during those normal cycles, I'd then integrate the "quick fix up" patches as needed. Does this sound reasonable? Anybody want to volunteer for this "Linus watchdog" role? --david
From: Peter Chubb Subject: milstone reached: ia64 linux builds out of Linus' tree Date: Tue, 5 Aug 2003 09:06:18 +1000 >>>>> "David" == David Mosberger writes: David> Now that Linus' tree works for ia64, the next question is how David> we can keep it that way. I think it would be useful to have David> someone setup a cron job which does daily builds/automated David> tests off of Linus tree. If something breaks, the person doing David> this could perhaps come up with a minimal patch which gets David> Linus' tree to build again (and submit a patch to the David> appropriate maintainer, with cc to the linux-ia64 list). I David> plan on continuing to put out roughly monthly ia64-specific David> patches and during those normal cycles, I'd then integrate the David> "quick fix up" patches as needed. Does this sound reasonable? David> Anybody want to volunteer for this "Linus watchdog" role? We can do this. We're tracking Linus's tree anyway for the work we're doing. We'd probably do daily automated builds to check that the kernel still compiles cleanly for HPSIM, DIG, and ZX1, but test only weekly. If you have anyu specific configuration options you think should be included, let us know. -- Dr Peter Chubb http://www.gelato.unsw.edu.au peterc AT gelato.unsw.edu.au You are lost in a maze of BitKeeper repositories, all slightly different.
From: David Mosberger Subject: Re: milstone reached: ia64 linux builds out of Linus' tree Date: Mon, 4 Aug 2003 16:35:32 -0700 >>>>> On Tue, 5 Aug 2003 09:06:18 +1000, Peter Chubb said: Peter> We can do this. We're tracking Linus's tree anyway for the work we're Peter> doing. Excellent! Peter> We'd probably do daily automated builds to check that the kernel Peter> still compiles cleanly for HPSIM, DIG, and ZX1, but test only weekly. Sounds reasonable. Except doing a boot/halt cycle on the simulator should be easy to automate, no? The simulator can actually catch a surprising number of problems. Peter> If you have anyu specific configuration options you think should be Peter> included, let us know. Nothing in particular, though it would be good to cover UP, MP, 16, and 64KB page sizes (not in all permutations, of course). Thanks, --david
