Android Deep Exploration

The Development Board is the main hardware device for developing and learning embedded technologies, because when Linux drives require access to hardware, they are difficult to emulate on a PC, so they need to be debugged and tested on boards with these hardware. Through the introduction of the s3c6410 Development Board, the Development Board of the internal structure and functional characteristics of the further understanding of the Development Board to achieve a successful installation of the Android system and the successful connection of the limited network.

Understanding and exploring Linux drivers is critical to driving development programmers, and Linux systems map each driver to a device file, stored in the/dev directory. This design concept makes interacting with Linux driver files as easy as interacting with normal files, so exchanging data with Linux drives becomes a data exchange with the device files. In this section I read the steps to write a Linux driver, from writing Word_count-driven business logic: In the example of counting the number of words, let me understand the Linux driver steps more specific and detailed.

Because kernel-space programs do not have direct access to user-space data, you need to use copy _to_user and Copy_from_user in the Word_count_read and Word_count_write functions respectively function to copy data from kernel space to user space or copy from user space to kernel space.

Finally, the Word_count driver is successfully tested by writing the build.sh script file.

Android Deep Exploration