Re: Linux 2.6.20-rc2: forgot how to make a zImage on powerpc?

Re: Linux 2.6.20-rc2: forgot how to make a zImage on powerpc?

[Mark Glines]

Mark Glines wrote:
> Hmm.  I'm trying to build 2.6.20-rc2 on a little powerpc box with 
> arch/powerpc/configs/linkstation_defconfig, and I get:
...
>   MODPOST vmlinux
> ln: accessing `arch/powerpc/boot/zImage': No such file or directory
> make[1]: *** [arch/powerpc/boot/zImage] Error 1
> make: *** [zImage] Error 2
> 
> So, uh, are we forgetting to go into the right subdirectory to make the 
> actual zImage, or what?  If I'm just doing something wrong, I'd love to 
> know what it is.
> 
> I'll follow up here on lkml if I diagnose this further.  Thanks,


Followup:  Yeah, it looks like it just doesn't know which format of 
zImage to produce for linkstation.

I'm not sure what image should be used by default.  I guess it depends 
on the bootloader.  Maybe default to uImage, as uBoot seems to be fairly 
common on these devices?

Mark

Re: Linux 2.6.20-rc2: forgot how to make a zImage on powerpc?

[Guennadi Liakhovetski]

On Mon, 25 Dec 2006, Mark Glines wrote:

> Mark Glines wrote:
> > Hmm.  I'm trying to build 2.6.20-rc2 on a little powerpc box with
> > arch/powerpc/configs/linkstation_defconfig, and I get:
> ...
> >   MODPOST vmlinux
> > ln: accessing `arch/powerpc/boot/zImage': No such file or directory
> > make[1]: *** [arch/powerpc/boot/zImage] Error 1
> > make: *** [zImage] Error 2
> > 
> > So, uh, are we forgetting to go into the right subdirectory to make the
> > actual zImage, or what?  If I'm just doing something wrong, I'd love to know
> > what it is.
> > 
> > I'll follow up here on lkml if I diagnose this further.  Thanks,
> 
> 
> Followup:  Yeah, it looks like it just doesn't know which format of zImage to
> produce for linkstation.
> 
> I'm not sure what image should be used by default.  I guess it depends on the
> bootloader.  Maybe default to uImage, as uBoot seems to be fairly common on
> these devices?

Yes, uImage is the format used on linkstation. Is there a way to cleanly 
specify this in the kernel sources apart from a comment in Kconfig?

Thanks
Guennadi
---
Guennadi Liakhovetski

[PATCH] powerpc: linkstation uses uimage style zImages

[Mark Glines]

[-- Attachment #1: Type: text/plain, Size: 1395 bytes --]

Guennadi Liakhovetski wrote:
> On Mon, 25 Dec 2006, Mark Glines wrote:
>> Followup:  Yeah, it looks like it just doesn't know which format of zImage to
>> produce for linkstation.
>>
>> I'm not sure what image should be used by default.  I guess it depends on the
>> bootloader.  Maybe default to uImage, as uBoot seems to be fairly common on
>> these devices?
> 
> Yes, uImage is the format used on linkstation. Is there a way to cleanly 
> specify this in the kernel sources apart from a comment in Kconfig?

Yep.  Kconfig just needs to select DEFAULT_UIMAGE, and then the system 
tries to build a uImage.

Once I tracked down and installed a "mkimage" command (dependency needed 
by the WRAP line), my "make zImage" succeeded.  So, I hope you guys 
apply this.

...

   GEN     .version
   LD      .tmp_vmlinux1
   KSYM    .tmp_kallsyms1.S
   AS      .tmp_kallsyms1.o
   LD      .tmp_vmlinux2
   KSYM    .tmp_kallsyms2.S
   AS      .tmp_kallsyms2.o
   LD      vmlinux
   SYSMAP  System.map
   SYSMAP  .tmp_System.map
   MODPOST vmlinux
   WRAP    arch/powerpc/boot/uImage
Image Name:   Linux-2.6.20-rc2-kuroboxHG
Created:      Sun Dec 24 19:24:12 2006
Image Type:   PowerPC Linux Kernel Image (gzip compressed)
Data Size:    1673973 Bytes = 1634.74 kB = 1.60 MB
Load Address: 0x00000000
Entry Point:  0x00000000
paranoid@kuro-2 /usr/src/linux $


Signed-off-by: Mark Glines <mark@glines.org>

[-- Attachment #2: linkstation-uses-uimage.diff --]
[-- Type: text/plain, Size: 447 bytes --]

--- linux-2.6.20-rc2/arch/powerpc/platforms/embedded6xx/Kconfig.orig	2006-12-24 19:13:49.000000000 -0800
+++ linux-2.6.20-rc2/arch/powerpc/platforms/embedded6xx/Kconfig	2006-12-24 19:14:02.000000000 -0800
@@ -79,6 +79,7 @@
 	select MPIC
 	select FSL_SOC
 	select PPC_UDBG_16550 if SERIAL_8250
+	select DEFAULT_UIMAGE
 	help
 	  Select LINKSTATION if configuring for one of PPC- (MPC8241)
 	  based NAS systems from Buffalo Technology. So far only

Re: [PATCH] powerpc: linkstation uses uimage style zImages

[Guennadi Liakhovetski]

Mark

Thanks for the patch. Are you actually going to test this kernel on a real 
hardware or just testing builds? If it is going to be a real life test, 
I'd be interested to know what exactly hardware, U-boot version, dts, and 
what results.

BTW, ack-ing your patch would be a bit easier if you sent it inline.

On Mon, 25 Dec 2006, Mark Glines wrote:

> Once I tracked down and installed a "mkimage" command (dependency needed by
> the WRAP line), my "make zImage" succeeded.  So, I hope you guys apply this.

...

> Signed-off-by: Mark Glines <mark@glines.org>
Acked-by: Guennadi Liakhovetski <g.liakhovetski@gmx.de>

> --- linux-2.6.20-rc2/arch/powerpc/platforms/embedded6xx/Kconfig.orig	2006-12-24 19:13:49.000000000 -0800
> +++ linux-2.6.20-rc2/arch/powerpc/platforms/embedded6xx/Kconfig	2006-12-24 19:14:02.000000000 -0800
> @@ -79,6 +79,7 @@
>  	select MPIC
>  	select FSL_SOC
>  	select PPC_UDBG_16550 if SERIAL_8250
> +	select DEFAULT_UIMAGE
>  	help
>  	  Select LINKSTATION if configuring for one of PPC- (MPC8241)
>  	  based NAS systems from Buffalo Technology. So far only

Re: [PATCH] powerpc: linkstation uses uimage style zImages

[Mark Glines]

Guennadi Liakhovetski wrote:
> Mark
> 
> Thanks for the patch. Are you actually going to test this kernel on a real 
> hardware or just testing builds? If it is going to be a real life test, 
> I'd be interested to know what exactly hardware, U-boot version, dts, and 
> what results.

Yes, I do very much intend to test it on real hardware.  I have a couple 
of Kurobox HGs which desperately need a 21st century kernel.  I still 
need to install U-boot on it, but first I'm just going to test the 
vmlinux with the loader.o kernel module.  (And my rs232 voltage 
converters haven't gotten here yet, so I'm being a little conservative 
about all of this.)


> BTW, ack-ing your patch would be a bit easier if you sent it inline.

Yeah, thunderbird sucks for this stuff.  Keep nagging me and I'll set up 
mutt again. :)  Thanks!

Mark

Re: [PATCH] powerpc: linkstation uses uimage style zImages

[Guennadi Liakhovetski]

On Mon, 25 Dec 2006, Mark Glines wrote:

> Guennadi Liakhovetski wrote:
> 
> Yes, I do very much intend to test it on real hardware.  I have a couple of
> Kurobox HGs which desperately need a 21st century kernel.  I still need to

Ah, what a pity:-) I mean, it is good, but it's exactly the same hardware 
I developed this port for and tested on. So, it should be easy. If you 
have any problems with your setup, look in linkstation / kurobox mailing 
list archives, I posted some instructions there for setting up a suitable 
u-boot version. Or just ask me. Or I could even just send you binaries to 
start with. Do you have JTag?...

Thanks
Guennadi
---
Guennadi Liakhovetski

Re: Linux 2.6.20-rc2: forgot how to make a zImage on powerpc?

[Mark Glines]

Linus Torvalds wrote:
> (much of the latter syntactic cleanups). And arm and powerpc updates.

Hmm.  I'm trying to build 2.6.20-rc2 on a little powerpc box with 
arch/powerpc/configs/linkstation_defconfig, and I get:

paranoid@kuro-2 /usr/src/linux $ make zImage
   HOSTCC  scripts/basic/fixdep
   HOSTCC  scripts/basic/docproc
   HOSTCC  scripts/kconfig/conf.o
   HOSTCC  scripts/kconfig/kxgettext.o
[snip lots of buildspam]
   LD      lib/zlib_deflate/built-in.o
   LD      lib/zlib_inflate/built-in.o
   GEN     .version
   LD      .tmp_vmlinux1
   KSYM    .tmp_kallsyms1.S
   AS      .tmp_kallsyms1.o
   LD      .tmp_vmlinux2
   KSYM    .tmp_kallsyms2.S
   AS      .tmp_kallsyms2.o
   LD      vmlinux
   SYSMAP  System.map
   SYSMAP  .tmp_System.map
   MODPOST vmlinux
ln: accessing `arch/powerpc/boot/zImage': No such file or directory
make[1]: *** [arch/powerpc/boot/zImage] Error 1
make: *** [zImage] Error 2

So, uh, are we forgetting to go into the right subdirectory to make the 
actual zImage, or what?  If I'm just doing something wrong, I'd love to 
know what it is.

I'll follow up here on lkml if I diagnose this further.  Thanks,

Mark