Re: compiling CVS kernel-2.6 for h5500

On St, 2007-06-20 at 15:05 +0200, Hinko Kocevar wrote:
> Hi,

  Hello,

>
> I'm new to the list.
> I have Ipaq h5500 lying around for some time now. I've also tested few
> 2.4 kernels several months ago, but wanted to try 2.6 at that time.
> Now that several people did some quite good work by porting 2.4 driver
> to 2.6 I would like to boot 2.6, too.
>
> I did CVS checkout for linux-2.6 kernel as stated on hh webpage but I
> stumbled accross this problem:
>
> moee_at_dellboi ~/work/handhelds.org/linux-2.6.x-hh $ make ipaqpxa_defconfig

  Please try make h5000_defconfig (or h5000_static_defconfig, whichever
suits better your needs). It should compile fine then.

> moee_at_dellboi ~/work/handhelds.org/linux-2.6.x-hh $ make mrproper
> scripts/Makefile.clean:17:
> /work/handhelds.org/linux-2.6.x-hh/arch/arm/fastfpe/Makefile: No such
> file or directory
> make[1]: *** No rule to make target
> `/work/handhelds.org/linux-2.6.x-hh/arch/arm/fastfpe/Makefile'. Stop.
> make: *** [_clean_arch/arm/fastfpe] Error 2
>
> My dirty fix (since the directory is empty dummy Makefile is harmless?):
> moee_at_dellboi ~/work/handhelds.org/linux-2.6.x-hh $ touch
> arch/arm/fastfpe/Makefile
>
> moee_at_dellboi ~/work/handhelds.org/linux-2.6.x-hh $ make mrproper
> CLEAN arch/arm/kernel
> CLEAN init
> CLEAN usr
> CLEAN .tmp_versions
> CLEAN include/asm-arm/mach-types.h include/asm-arm/arch
> include/asm-arm/.arch
> CLEAN scripts/basic
> CLEAN scripts/kconfig
> CLEAN scripts/mod
> CLEAN scripts
> CLEAN include/config
> CLEAN .config .config.old include/asm .version
> include/linux/autoconf.h include/linux/version.h
> include/linux/utsrelease.h
>
>
> Also compile fails with:
> ..
> AS arch/arm/mm/proc-xscale.o
> LD arch/arm/mm/built-in.o
> CC arch/arm/common/rtctime.o
> CC arch/arm/common/dmabounce.o
> LD arch/arm/common/built-in.o
> CC arch/arm/mach-pxa/clock.o
> CC arch/arm/mach-pxa/generic.o
> CC arch/arm/mach-pxa/irq.o
> CC arch/arm/mach-pxa/dma.o
> CC arch/arm/mach-pxa/time.o
> CC arch/arm/mach-pxa/pxa25x.o
> LD arch/arm/mach-pxa/aximx3/built-in.o
> LD arch/arm/mach-pxa/aximx30/built-in.o
> LD arch/arm/mach-pxa/aximx5/built-in.o
> CC arch/arm/mach-pxa/h5400/h5400.o
> LD arch/arm/mach-pxa/h5400/built-in.o
> CC [M] arch/arm/mach-pxa/h5400/h5400_lcd.o
> CC arch/arm/mach-pxa/rover/roverp1.o
> In file included from arch/arm/mach-pxa/rover/roverp1.c:32:
> include/asm/arch/udc.h: In function `udc_gpio_to_irq':
> include/asm/arch/udc.h:14: error: `GPIO_MD_MASK_NR' undeclared (first
> use in this function)
> include/asm/arch/udc.h:14: error: (Each undeclared identifier is
> reported only once
> include/asm/arch/udc.h:14: error: for each function it appears in.)
> include/asm/arch/udc.h: In function `udc_gpio_init_vbus':
> include/asm/arch/udc.h:19: error: `GPIO_MD_MASK_NR' undeclared (first
> use in this function)
> include/asm/arch/udc.h:19: error: `GPIO_IN' undeclared (first use in
> this function)
> include/asm/arch/udc.h: In function `udc_gpio_init_pullup':
> include/asm/arch/udc.h:24: error: `GPIO_MD_MASK_NR' undeclared (first
> use in this function)
> include/asm/arch/udc.h:24: error: `GPIO_OUT' undeclared (first use in
> this function)
> include/asm/arch/udc.h:24: error: `GPIO_DFLT_LOW' undeclared (first
> use in this function)
> include/asm/arch/udc.h: In function `udc_gpio_get':
> include/asm/arch/udc.h:29: warning: implicit declaration of function `GPLR'
> include/asm/arch/udc.h:29: warning: implicit declaration of function `GPIO_bit'
> include/asm/arch/udc.h: In function `udc_gpio_set':
> include/asm/arch/udc.h:37: warning: implicit declaration of function `GPSR'
> include/asm/arch/udc.h:37: error: invalid lvalue in assignment
> include/asm/arch/udc.h:39: warning: implicit declaration of function `GPCR'
> include/asm/arch/udc.h:39: error: invalid lvalue in assignment
> make[2]: *** [arch/arm/mach-pxa/rover/roverp1.o] Error 1
> make[1]: *** [arch/arm/mach-pxa/rover] Error 2
> make: *** [arch/arm/mach-pxa] Error 2
>
> This kind of errors drove me away from trying out 2.6, as I'm quite
> familiar with ipaq5500 architecture and hardware in the past. Now,
> hopefully I will find more time to study that h5500 HW pdfs more, and
> understand the underlying HW!

  I think these errors could be caused by using the wrong defconfig; try
compiling again with one of the suggested. If you will have any
questions about the hardware, feel free to ask, someone will likely know
to answer:)

>
> Is this 'rover' stuff need for h5500 or is it compiling by mistake?
>
> Best regards,
> hinko
> --
> HK

        Milan

> _______________________________________________
> H5400-port mailing list
> H5400-port_at_handhelds.org
> https://www.handhelds.org/mailman/listinfo/h5400-port
Received on Wed Jun 20 2007 - 10:58:41 EDT