Hello david-b,
I have copied ether.c usbstring.c config.c epautoconf.c rndis.c
omap_udc.c files to 2.4 kernel tree from 2.6 kernel. I compiled these files but
error .Following is the error information .What wrong with me ? How to revise
this error? Thank you .
1.The debug output is as following:
arm_v4t_le-gcc -D__KERNEL__ -I/home/terry/rgb_lcd_linux/include -Wall
-Wstrict-prototypes -Wno-trigraphs -Os -fno-strict-aliasing -fno-common -Uarm
-fno-common -pipe -mapcs -mno-sched-prolog -g -mapcs-32 -D__LINUX_ARM_ARCH__=5
-march=armv5te -mtune=arm9tdmi -mshort-load-bytes -msoft-float -nostdinc
-iwithprefix include -DKBUILD_BASENAME=omap_udc -c -o omap_udc.o omap_udc.c
omap_udc.c:103: error: parse error before "__attribute_used__"
omap_udc.c:103: warning: type defaults to `int' in declaration of
`__attribute_used__'
omap_udc.c:103: warning: initialization makes integer from pointer without a
cast
omap_udc.c:103: warning: excess elements in scalar initializer
omap_udc.c:103: warning: (near initialization for `__attribute_used__')
omap_udc.c:103: warning: excess elements in scalar initializer
omap_udc.c:103: warning: (near initialization for `__attribute_used__')
omap_udc.c:103: warning: excess elements in scalar initializer
omap_udc.c:103: warning: (near initialization for `__attribute_used__')
omap_udc.c:103: warning: excess elements in scalar initializer
omap_udc.c:103: warning: (near initialization for `__attribute_used__')
omap_udc.c:103: warning: data definition has no type or storage class
omap_udc.c:112: error: parse error before "__attribute_used__"
omap_udc.c:112: warning: type defaults to `int' in declaration of
`__attribute_used__'
omap_udc.c:112: error: redefinition of `__attribute_used__'
omap_udc.c:103: error: `__attribute_used__' previously defined here
omap_udc.c:112: warning: initialization makes integer from pointer without a
cast
omap_udc.c:112: warning: excess elements in scalar initializer
omap_udc.c:112: warning: (near initialization for `__attribute_used__')
omap_udc.c:112: warning: excess elements in scalar initializer
omap_udc.c:112: warning: (near initialization for `__attribute_used__')
omap_udc.c:112: warning: excess elements in scalar initializer
omap_udc.c:112: warning: (near initialization for `__attribute_used__')
omap_udc.c:112: warning: excess elements in scalar initializer
omap_udc.c:112: warning: (near initialization for `__attribute_used__')
omap_udc.c:112: warning: data definition has no type or storage class
2.The NO.103 line in omap_udc.c is :
module_param (fifo_mode, uint, 0);
3. The definition of module_param() is defined in moduleparam.h on 2.6
kernel tree.(I have to copy moduleparam.h from 2.6 to 2.4 .)
#define __module_param_call(prefix, name, set, get, arg, perm) \
static char __param_str_##name[] = prefix #name; \
static struct kernel_param const __param_##name \
__attribute_used__ \
__attribute__ ((unused,__section__ ("__param"),aligned(sizeof(void *)))) \
= { __param_str_##name, perm, set, get, arg }
#define module_param_call(name, set, get, arg, perm) \
__module_param_call(MODULE_PARAM_PREFIX, name, set, get, arg, perm)
======= 2005-07-15 22:47:44 =======
>You'll have to do the port yourself. There's no manual, but it should
>be straightforward to make the current code work on 2.4.20 ... the driver
>model stuff can just be removed, the main issue will be the DMA APIs
>which are different on 2.4 kernels.
>
>- Dave
= = = = = = = = = = = = = = = = = = = =
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
[email protected]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
