liuxmzc的专栏

MFC中利用树形控件在主对话框当中嵌入子对话框

The TWL5030 is an integrated power-management/audio codec device for use in portable cellular telephone designs that derive their power from batteries based on Li-ion, Li-ion polymer, or manganese-cobalt chemistries. It typically receives commands from either an application processor or a modem and, as shown in Section 1.1.1, Features, and Figure 1-1, provides power conversion/regulation and a complete audio codec section and class-D audio amplifier. In addition to generic support capabilities, the TWL5030 meets the specific power requirements of the TI OMAP3430 and OMAP2430C devices.

第1章 i2c核心数据结构之间的关系 4 第2章 i2c-core.c的初始化 10 i2c_init函数 10 i2cproc_init函数 11 第3章 安装、卸载pxa255的i2c适配器驱动程序 13 pxa_i2c数据结构 13 i2c_adap_pxa_init函数 15 i2c_add_adapter函数 16 i2c_del_adapter函数 18 i2c_adap_pxa_exit函数 20 第4章 安装、卸载ltc3445驱动程序 21 ltc3445_init函数 21 i2c_add_driver函数 22 i2c_probe函数 23 i2c_check_functionality函数 26 i2c_smbus_xfer函数 27 i2c_transfer函数 29 ltc3445_detect_client函数 30 i2c_attach_client函数 31 ltc3445_cleanup函数 32 i2c_del_driver函数 33 ltc3445_detach_client函数 35 i2c_detach_client函数 35 第5章 与pxa255的i2c适配器相关的代码 37 i2c_pxa_reset函数 37 i2c_pxa_abort函数 38 i2c_pxa_xfer函数 38 i2c_pxa_do_xfer函数 39 i2c_pxa_start_message函数 41 i2c_pxa_handler函数 42 i2c_pxa_irq_txempty函数 42 i2c_pxa_irq_rxfull函数 47 第6章 i2c-dev的初始化 49 i2c_dev_init函数 49 i2cdev_attach_adapter函数 50 第7章 i2c框架提供的设备访问方法 52 i2cdev_open函数 52 i2cdev_ioctl函数 53 i2cdev_read函数 54 i2c_master_recv函数 55 对i2cdev_read和i2c_master_recv的修改 56 i2cdev_release函数 59 第8章 编写i2c设备驱动程序模块的方法 61 第9章 用户进程访问i2c设备的步骤 64 讨论和总结 65 i2c操作中的同步问题 65 总结各个模块初始化函数的作用 65 对i2c框架代码的修改 66 有关i2c设备私有数据结构的讨论 68 遗留的问题 68

这份资料，绝对不可多得，下了就知道 Bluetooth, FM, GPS Solution with Shared Transport Table of Contents 2 List of Figures 3 Revision History 4 1. Introduction 5 1.1. Purpose 5 1.2. Out of Scope 5 1.3. File Name 5 1.4. Definitions 5 2. Concept of Shared Transport 7 3. Requirements 9 4. Assumptions 9 5. System Architecture 10 5.1. Shared Transport driver 12 5.2. Initialization Manager 12 5.3. Shared Transport HCILL 13 5.4. Bluetooth driver 13 5.5. FM drivers 13 5.5.1. FM driver via V4L2 sub-system 13 5.5.2. FM driver via character device sub-system 13 5.6. Character device driver for GPS 14 6. Design Approach 15 6.1. Shared Transport driver 15 6.1.1. ST Core 15 6.1.2. ST UIM and ST KIM 17 6.1.3. ST HCILL 18 6.2. Bluetooth driver 18 6.3. FM drivers 19 6.3.1. FM V4L2 driver 20 6.3.2. FM Character Device interface 21 6.4. Character device driver for GPS 21 7. References 24 8. Appendix 1: Shared Transport in Android 25 8.1. Execution of UIM 25 8.2. Bluetooth On/Off 25

Handbook to bring up Shared Transport with Bluetooth and FM Bringing up of connectivity modules like Bluetooth, FM and GPS requires the integration of Shared transport to the customer’s target code-base. Below are the components that should be integrated to the baseline of the customer’s Android code-base.

Table of Contents Table of Contents 2 List of Figures 3 Revision History 4 1. Introduction 5 1.1. Purpose 5 1.2. Out of Scope 5 1.3. File Name 5 1.4. Definitions 5 2. Concept of Shared Transport 7 3. Requirements 9 4. Assumptions 9 5. System Architecture 10 5.1. Shared Transport driver 12 5.2. Initialization Manager 12 5.3. Shared Transport HCILL 13 5.4. Bluetooth driver 13 5.5. FM drivers 13 5.5.1. FM driver via V4L2 sub-system 13 5.5.2. FM driver via character device sub-system 13 5.6. Character device driver for GPS 14 6. Design Approach 15 6.1. Shared Transport driver 15 6.1.1. ST Core 15 6.1.2. ST UIM and ST KIM 17 6.1.3. ST HCILL 18 6.2. Bluetooth driver 18 6.3. FM drivers 19 6.3.1. FM V4L2 driver 20 6.3.2. FM Character Device interface 21 6.4. Character device driver for GPS 21 7. References 24 8. Appendix 1: Shared Transport in Android 25 8.1. Execution of UIM 25 8.2. Bluetooth On/Off 25

cmake-3.10.2-win64-x64，最新版本，外网下载非常慢，特此保存。

########################BT FM ########################## Download the image using command: 1 # Flash Image Put the board in Flashing mode. Refer below Appendix - 1 cd <your path>/Nvidia_Demo/android_gb_cardhu_os_image sudo ./nvflash --bct flash.bct --setbct --odmdata 0x40080105 --configfile flash.cfg --create --bl bootloader.bin --go #################################################################################################################################################################################################### Appendix - 1 Nvidia Board in Flashing Mode #################################################################################################################################################################################################### 1. Connect the Debug board to Cardhu board. 2. Connect the power supply and Micro USB to Cardhu 3. On the Debug Board Press S12 (FRC RCV), Keeping this pressed Press and release S7 (RESET), Now Release S12. 4. Now Device is in Flashing mode, We can start nvflash command now. #################################################################################################################################################################################################### Appendix - 2 Nvidia Board Keys (On Debug Board) #################################################################################################################################################################################################### 1. S7 (RESET) --&gt; is the RESET button. 2. S5 (ROW1) --&gt; is the BACK button. 2. S10 (ROW2) --&gt; is the Home button. 4. S6 (ON KEY) --&gt; is Wake up button. #################################################################################################################################################################################################### Appendix - 3 Nvidia Board unavailable Keys workaround #################################################################################################################################################################################################### 1.To execute teh specific keys, provide the key inputs from adb shell. Provide the keyevent for the desired key.Refer teh key list below. Eg: for MENU key run adb shell #input keyevent 82 { "STAR", 17 }, { "POUND", 18 }, { "DPAD_UP", 19 }, { "DPAD_DOWN", 20 }, { "DPAD_LEFT", 21 }, { "DPAD_RIGHT", 22 }, { "DPAD_CENTER", 23 }, { "VOLUME_UP", 24 }, { "VOLUME_DOWN", 25 }, { "POWER", 26 }, { "CAMERA", 27 }, { "CLEAR", 28 }, { "HEADSETHOOK", 79 }, { "FOCUS", 80 }, { "PLUS", 81 }, { "MENU", 82 }, { "NOTIFICATION", 83 }, { "SEARCH", 84 }, { "MEDIA_PLAY_PAUSE", 85 }, { "MEDIA_STOP", 86 }, { "MEDIA_NEXT", 87 },

Win8 I2C驱动程序，很好的参考例子

Draft Copyright © 1996, Intel Corporation, Microsoft Corporation, Toshiba Corp. All rights reserved. INTELLECTUAL PROPERTY DISCLAIMER THIS SPECIFICATION IS PROVIDED “AS IS” WITH NO WARRANTIES WHATSOEVER INCLUDING ANY WARRANTY OF MERCHANTABILITY, FITNESS FOR ANY PARTICULAR PURPOSE, OR ANY WARRANTY OTHERWISE ARISING OUT OF ANY PROPOSAL, SPECIFICATION, OR SAMPLE. NO LICENSE, EXPRESS OR IMPLIED, BY ESTOPPEL OR OTHERWISE, TO ANY INTELLECTUAL PROPERTY RIGHTS IS GRANTED OR INTENDED HEREBY. INTEL, MICROSOFT, AND TOSHIBA, DISCLAIM ALL LIABILITY, INCLUDING LIABILITY FOR INFRINGEMENT OF PROPRIETARY RIGHTS, RELATING TO IMPLEMENTATION OF INFORMATION IN THIS SPECIFICATION. INTEL, MICROSOFT, AND TOSHIBA, DO NOT WARRANT OR REPRESENT THAT SUCH IMPLEMENTATION(S) WILL NOT INFRINGE SUCH RIGHTS. THIS DOCUMENT IS A DRAFT FOR COMMENT ONLY AND IS SUBJECT TO CHANGE WITHOUT NOTICE. READERS SHOULD NOT DESIGN PRODUCTS BASED ON THIS DOCUMENT.

堆栈帧，函数调用，堆栈切换 函数调用过程种种细节分析

最新 Git-2.16.1-64-bit，外面下载很慢，在此保存。。

The OMAP36xx high-performance, multimedia application device is based on the enhanced OMAP™ 3 architecture and is integrated on TI advanced 45-nm process technology. The architecture is designed to provide best-in-class video, image, and graphics processing sufficient to support the following: • Streaming video • 2-dimension/3-dimension (2D/3D) mobile gaming • Video conferencing • High-resolution still image • Video capture in 2.5G wireless terminals, 3G wireless terminals, rich multimedia-featured handsets, and high-performance personal digital assistants (PDAs) The device supports high-level operating systems (OSs) such as: • Android™ OS • Linux® • Symbian OS™ • Windows® CE This OMAP device includes state-of-the-art power-management techniques required for high-performance mobile products. The following subsystems are part of the device: • Microprocessor unit (MPU) subsystem based on the ARM Cortex™-A8 microprocessor • Imaging video and audio (IVA2.2) subsystem with a TMS320C64x™ digital signal processor (DSP) core • POWERVR® SGX530 subsystem for 2D and 3D graphics acceleration to support display and gaming effects • Camera image signal processor (ISP2P) that supports multiple formats and interfacing options to a wide variety of image sensors • Display subsystem with a wide variety of features for multiple concurrent image manipulation, and a programmable interface supporting a wide variety of displays. The display subsystem also supports NTSC/PAL video out. • Level 3 (L3) and level 4 (L4) interconnects that provide high-bandwidth data transfers for multiple initiators to the internal and external memory controllers and to on-chip peripherals The device also offers: • A comprehensive power and clock-management scheme that enables high-performance, low-power operation, and ultralow-power standby features. The device also supports SmartReflex™ adaptative voltage control. This power-management technique for automatic control of the operating voltage of a module reduces the active power consumption. • Connectivity to various cellular modem chipset • Memory stacking feature using the package-on-package (POP) implementation (see Section 1.4, Package-on-Package Concept)

Handbook to bring up Shared Transport with Bluetooth and FM Bringing up of connectivity modules like Bluetooth, FM and GPS requires the integration of Shared transport to the code-base. Below are the components that should be integrated to the baseline of the customer’s Android code-base.

Host MCP software BT, FM and NaviLink WLAN support Mobile Connectivity Package Framework OS abstraction Platform abstraction NaviLink features Assisted mode SUPL Autonomous mode GPS Components NAVC – navigation controller NAVL – navigation library RRC / RRLP enc & decode NL-IF – navilink interface (command adapter)

做个测试机玩玩，也可供大家下载

windows 设备管理 设备控制

比较新，这里下载方便

很不错啊，送人温软！