hi android, i tried ur suggestion, also i put the ioctl.h file in application dir(earlier this was getting reffered from kernel dir). Now i passed through this problem.
but still i face some problems wrt to drivers. there is an enum(from a header file say a.h) in driver A and driver B, but the values for the same enum in both the drivers is different, how is it possible?? also i'm not able to build the kernel along with android code. i do the following steps for building android: $ source build/envsetup.sh $ lunch 1 $ export ARCH= arm & CROSS_COMPILE=arm-eabi- $ make with these steps, the whole android gets built but not the kernel. how do i build the kernel along with android? On Jan 6, 8:36 pm, "David Turner" <[email protected]> wrote: > try compiling your user code with -fno-short-enums to see if it solves the > problems. > > On Tue, Jan 6, 2009 at 4:04 PM, getandroid <[email protected]> wrote: > > > I've a driver for audio accelerator on my hardware. when the test app > > on top of this driver does some ioctl calls to driver and it says: > > "unknown ioctl no: xxxx" > > > the ioctl number passed from application is an enum defined in one > > header file which is included in test app and also the driver. So the > > driver & test app should see the same enum value which is not > > happening. The 'cmd' parameter (which is an enum from *.h) which is > > passed from application and the value of the enum in driver included > > from the same *.h is different. > > > Has anybody faced the same issue? This problem is not faced when the > > test app is built with -static option. > > --~--~---------~--~----~------------~-------~--~----~ unsubscribe: [email protected] website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
