Re: X50v testing files with fat32 SD card

Fisherss,

Please forgive the verbosity of this email, just wanted to describe the
process accurately ;)

I am using a pre-built GCC 4.0 tool chain, my environment and build
process appears to work as whatever kernels I make at the moment attempt
to boot and appear on screen. However I can't get the touchscreen driver
"h4000_ts_x50.ko" to build. I cannot use JeDi's existing modules because
they were built with GCC 3.4 and are incompatible, so I have to rebuild
all the modules too.

I grabbed the kernel source kernel26_x50_beta1.tar.gz from your site,
extracted it and ran the build as per your instructions.

$ make ARCH=arm CROSS_COMPILE=/usr/bin/arm-linux- aximx30_defconfig
$ make ARCH=arm CROSS_COMPILE=/usr/bin/arm-linux- modules

> lots of warnings

because of a "extern volatile void" in include/asm/cpu-single.h:44
"warning: type qualifiers ignored on function return type"

> then fails with

drivers/scsi/scsi_sysfs.c:154: error: static declaration of
'scsi_device_dev_release' follows non-static declaration
drivers/scsi/scsi_priv.h:139: error: previous declaration of
'scsi_device_dev_release' was here
drivers/scsi/scsi_sysfs.c:188: error: static declaration of 'sdev_class'
follows non-static declaration
drivers/scsi/scsi_priv.h:148: error: previous declaration of
'sdev_class' was here
make[2]: *** [drivers/scsi/scsi_sysfs.o] Error 1
make[1]: *** [drivers/scsi] Error 2

> i amended the config in arch/arm/configs/aximx30_defconfig

CONFIG_BLK_DEV_IDESCSI=n
CONFIG_SCSI=n
CONFIG_SCSI_PROC_FS=n
CONFIG_BLK_DEV_SD=n
CONFIG_BLK_DEV_SR=n
CONFIG_CHR_DEV_SG=n

> make clean, reconfigure, rebuild 'modules' and it completes successfully

$ make ARCH=arm CROSS_COMPILE=/usr/bin/arm-linux- zImage

> fails

   CC drivers/serial/serial_core.o
   CC drivers/serial/pxa.o
drivers/serial/pxa.c:762: error: static declaration of
'serial_pxa_ports' follows non-static declaration
drivers/serial/pxa.c:612: error: previous declaration of
'serial_pxa_ports' was here
drivers/serial/pxa.c:770: error: initializer element is not constant
drivers/serial/pxa.c:770: error: (near initialization for
'serial_pxa_ports[0].port.mapbase')
drivers/serial/pxa.c:784: error: initializer element is not constant
drivers/serial/pxa.c:784: error: (near initialization for
'serial_pxa_ports[1].port.mapbase')
drivers/serial/pxa.c:798: error: initializer element is not constant
drivers/serial/pxa.c:798: error: (near initialization for
'serial_pxa_ports[2].port.mapbase')
drivers/serial/pxa.c:812: error: initializer element is not constant
drivers/serial/pxa.c:812: error: (near initialization for
'serial_pxa_ports[3].port.mapbase')
drivers/serial/pxa.c:822: error: static declaration of 'serial_pxa_reg'
follows non-static declaration
drivers/serial/pxa.c:613: error: previous declaration of
'serial_pxa_reg' was here
make[2]: *** [drivers/serial/pxa.o] Error 1

> i worked around this with

CONFIG_SERIAL_PXA=n
CONFIG_SERIAL_PXA_CONSOLE=n

however I am unsure if this is 'correct' or if its in fact disabling the
serial-port on the Axim.

> make clean, reconfigure, rebuild modules, rebuild zImage and it
completes successfully

So far, this process builds everything I need apart from
"h4000_ts_x50.ko" so I guess I am missing some of the steps JeDi went
though...

Any thoughts???

Cheers,

Michael Cutler

Fisherss wrote:
> What's your problem ?
>
>
> Michael Cutler wrote:
>
>> Hi,
>>
>> I have a working build environment and can build my own kernels which
>> at least appear on-screen before exploding spectacularly. I have also
>> scripted my build process to copy the modules into all the right
>> places (initrd & x50v-rootfs) but my only problem is how to get
>> "h4000_ts_x50.ko" to build.
>>
>> Did you have to hack Fisherss source any to get this to work?
>>
>> Cheers,
>>
>> Michael
>>
Received on Thu Jan 12 2006 - 06:48:45 EST