MPC860的SCC的演示代码

mobile phone nokia1110solutions-mobile phone nokia1110solutions-----------------

This the contents of a computer network experiment!-This is the contents of a computer network experiment!

Tuxedo快速入门-Tuxedo Quick Start

代码阅读有自身的一套技能，重要的是能够确定什么时候使用哪项技术。本书中，作者使用600多个现实的例子，向读者展示如何区分好的（和坏的）代码，如何阅读，应该注意什么，以及如何使用这些知识改进自己的代码。养成阅读高品质代码的习惯，可以提高编写代码的能力。-code readers have their own set of skills, it is important to determine when to use which technology. The book, the authors use more than 600 practical examples to show readers how to distinguish good (and bad) code, how to read, it should be noted that, and how to use this knowledge to improve their own code. Develop high-quality code reading habits, and improve the ability to write code.

这些算法是在Vc++环境下编写的一些常用数学算法，希望对大家能有用。-These algorithms in Vc++ environment to prepare a number of commonly used mathematical algorithms, in the hope that we can be useful.

2812的液晶显示源程序，是基于c语言的程序-2812 source of liquid crystal display is based on c language program

jtag program 的说明,对初学者可能会有帮助,请查看-jtag program description may be helpful for beginners, please see

张贤达一本很经典的信号处理的书，强烈推荐，大家可以看一看-a good bood

linux嵌入式开发全过程介绍，bootloader,kernel,rootfs等。很好的入门或加强材料。-linux embedded introduce the whole process of development, bootloader, kernel, rootfs and so on. Very good entry or strengthening materials.

　这本书拥有一大堆“看点”。譬如说，它的作者Rod Johnson拥有10年编写Java程序的经验，目前是Servlet和JDO 2.0两个JSR专家组的成员；再譬如说，书中着力介绍的Spring、Hibernate、WebWork等都是时下流行的开源框架，IoC、AOP之类都是时下流行的概念词汇。而最大的看点就赫然摆在这本书的封面上：“without EJB”。我们曾经在无数的书籍和文章中看到，EJB是J2EE的核心技术之一；而Rod Johnson的这本书竟然宣称，绝大多数的J2EE应用根本不需要EJB。这种近乎挑衅的姿态令任何一个负责的J2EE架构师很难不萌生一探究竟的念头――不论你是打算赞同他还是打算驳斥他。 　　 但所有这些尽皆不是本书最大的价值所在。选择一种架构、一种技术的依据是什么？Rod Johnson认为，应该是基于实践的证据、来自历史项目或亲自试验的经验，而不是任何形式的偶像崇拜或者门户之见。书中谈到了企业应用方方面面的问题和解决办法，而这些方案无一不是这种“循证方法”的产物。除了把这些方案交给读者，Rod Johnson通过这本书希望传达的、更为重要的信息正是“循证”的工作方式――那原本就应该是程序员的工作方式。　　 -The results of using J2EE in practice are often disappointing: applications are often slow, unduly complex, and take too long to develop. Rod Johnson believes that the problem lies not in J2EE itself, but in that it is often used badly. Many J2EE publications advocate approaches that, while fine in theory, often fail in reality, or deliver no real business value.