Going to write an I2C Driver, need to know the relationship between the core driver of bus and board setup file. I am using OMAP2 based ARM board. Just want to know about basic relationship.

Thanks

Manoj Arora

Is rules.d in udev is the only way for a Linux Kernel to know about the connectivity of the External H/w Device or something else is also there as an alternate to it..??

Problem is solved, got 3rd way to remove the padding from a structure. i.e. Declare a structure like this..

struct abc

{

……..char a;

……..int b;

}__attribute__ ((packed));

main()

{

……. struct abc obj;

………printf(size);

}

Output is : 5

where as in normal 32 bit machine it comes 8 when we directly use a variable.

yups…:-)…C makes me happy

Thank you

-lgcc has been solved by changing the version of glibc. but another error occured , i.e. -lc not found… on the execution of a file.

Also facing error in configuring glibc-2.13.

It is exiting with the following error.

.

.

The compiler must support c cleanup handling.

The actual error is in it … that my libgomp directory inside the target’s lib/ is empty…I think, I am not giving the exact required path… for that,  I shall need your help.

Thank you

Is there any way available to convert an .obj (object file) file to a .c file…?

and error is gone…

but after that..

the error is:.

checking for working strncmp… no….(Previous Error was at this line)
configure: updating cache ./config.cache
configure: creating ./config.status
config.status: creating Makefile
config.status: creating testsuite/Makefile
config.status: creating config.h
config.status: executing default commands
make[1]: Leaving directory `/home/manoj_board/Control-project/build-tools/build-gcc’
make: *** [all] Error 2

Help me out in solving this.

Error occurs at make -j 2 .

Error is : Link tests are not allowed after GCC_NO_EXECUTABLES

The operating systems that we come across today, generally have many features which are not the necessary features to make a system work. But these features are required to make the interaction with the system easier. Such features include graphical interface, file management, process management, shell, etc. These features rely on the core part of the OS (called as kernel) to run and provide interface to the user or other application programs. It is to be realized that these features are inevitable, and only a kernel alone is of no use to the user.