xudaiyang3的专栏

3A3000硬件参考设计

中航光电GJB2889系列选型手册，中航光电GJB2889系列选型手册

中兴面试指南 中兴面试指南中兴面试指南中兴面试指南中兴面试指南中兴面试指南中兴面试指南中兴面试指南中兴面试指南中兴面试指南中兴面试指南中兴面试指南中兴面试指南

第2章 数据通信基础 第5章 局域网 。。。。。。。。。。。。。

覆盖面不广，这里我将近半年参加的笔试、面试题， 以及一些资料上的经典题目进行汇总，整理为 120 多个。

哈工大数据结构课件 哈工大数据结构课件 D:\TDDOWNLOADD:\TDDOWNLOADD:\TDDOWNLOADD:\TDDOWNLOADD:\TDDOWNLOADD:\TDDOWNLOADD:\TDDOWNLOADD:\TDDOWNLOADD:\TDDOWNLOADD:\TDDOWNLOADD:\TDDOWNLOADD:\TDDOWNLOADD:\TDDOWNLOADD:\TDDOWNLOADD:\TDDOWNLOADD:\TDDOWNLOAD

c++经典书籍 超级宝典 高手必看c++经典书籍 超级宝典 高手必看c++经典书籍 超级宝典 高手必看c++经典书籍 超级宝典 高手必看c++经典书籍 超级宝典 高手必看c++经典书籍 超级宝典 高手必看c++经典书籍 超级宝典 高手必看c++经典书籍 超级宝典 高手必看c++经典书籍 超级宝典 高手必看c++经典书籍 超级宝典 高手必看c++经典书籍 超级宝典 高手必看c++经典书籍 超级宝典 高手必看c++经典书籍 超级宝典 高手必看c++经典书籍 超级宝典 高手必看c++经典书籍 超级宝典 高手必看c++经典书籍 超级宝典 高手必看c++经典书籍 超级宝典 高手必看

vxworks高手也not难vxworks高手也not难

VXWORKS软件开发项目实例完全解析VXWORKS软件开发项目实例完全解析

i Wind River Systems Tornado Training Workshop Wind River Systems, Inc. 500 Wind River Way Alameda, CA 94501 510-749-2141 FAX: 510-749-2378 [email protected] http://www.wrs.com/training Version 5.1 24 May 1999 TM ii Wind River Systems Copyright © Wind River Systems, Inc. 1986 - 1999 Version 5.1, 24 May 1999 ALL RIGHTS RESERVED. No part of this publication may be reproduced in any form, by photocopy, microfilm, retrieval system, or by any other means now known or hereafter invented without the prior written permission of Wind River System, Inc. This document is designed to support the Tornado Training Workshop class. It is not designed as a stand-alone document, nor can it substitute for the Tornado or VxWorks documentation. For information about the Wind River Systems training program, see: http://www.wrs.com/training Training Department . Wind River Systems, Inc. 500 Wind River Way Alameda, CA 94501 510-749-2141 (phone) 510-749-2378 (fax) EMAIL: [email protected] For training in Europe, Asia and Africa, please contact your local sales office. VxWorks® and Wind River Systems® are registered trademarks and Tornado, Tornado II, wind, windX, WindPower, WindNet, WindNet SNMP, WindView, VxGNU, VxGDB, VxSim, VxVMI, VxMP, and MicroWorks are trademarks of Wind River Systems, Inc. All other trademarks cited herein are the properties of their respective owners. iii Wind River Systems Course Prerequisites • General prerequisites: l One year C programming experience: familiarity with basic control structures, pointers, structures, preprocessor commands. l Basic understanding of operating systems and debugging techniques. • Functional knowledge of host platform: l UNIX: user-level knowledge of UNIX file system and csh shell; editing text with vi, emacs, or host-native GUI editor; X window system GUI. l Windows: user-level knowledge of Windows NT/95/ 98 graphical and command-line user interfaces, file systems, and standard Windows editor. iv Wind River Systems Course Objectives • Overview of Tornado / VxWorks facilities. • Boot VxWorks and download object modules to a VxWorks target. • Use Tornado tools to perform cross-development. • Control, and communicate between, tasks executing under VxWorks. • Use WindView to analyze a multitasking application. • Use VxWorks primitives to access resources exclusively, and to synchronize the actions of different tasks. • Use timers for periodic code execution. • Differentiate between the standard I/O library, the formatted I/O library, and the basic I/O system. • Create and use local file systems. • From VxWorks, access file systems on remote machines. • Reconfigure VxWorks, linking in user-defined code. v Wind River Systems Table of Contents Volume 1 Chapter Getting Started ............................................... 1 Components of Tornado Getting Help Hardware/Software Configuration Booting Starting Tornado WDB Agent Projects ............................................................ 2 Projects Overview Bootable Projects and VxWorks Configuration Integrated Simulator Downloadable Projects Build Specifications WindSh and Browser .................................... 3 WindSh Browser CrossWind....................................................... 4 Overview Starting A Debugging Session Basic Debugging System-level Debugging Real-Time Multitasking ............................... 5 Introduction Task Basics Task Control Error Status System Tasks WindView 2.0.................................................. 6 WindView Configuration Events vi Wind River Systems Semaphores..................................................... 7 Overview Binary Semaphores and Synchronization Mutual Exclusion Intertask Communication ............................ 8 Introduction Shared Memory Message Queues Pipes Memory............................................................ 9 Memory Allocation Exceptions, Interrupts and Timers ............. 10 Exception Handling and Signals Interrupt Service Routines Timers I/O and File System ....................................... 11 Introduction Character I/O Block I/O Networking..................................................... 12 Introduction VxWorks Network Configuration Routing Protocols Remote Access Services Reconfiguring VxWorks ............................... 13 Production Issues VxWorks Start-up Optional Products.......................................... 14 Overview Shared Memory Objects (VxMP) Virtual Memory (VxVMI) Appendix Code Examples Index

Linux TCP-IP协议栈笔记（二）路由缓存 - Linux内核探索 - SecPower - Powered by Discuz!.filesLinux TCP-IP协议栈笔记（二）路由缓存 - Linux内核探索 - SecPower - Powered by Discuz!.filesLinux TCP-IP协议栈笔记（二）路由缓存 - Linux内核探索 - SecPower - Powered by Discuz!.files

网络协议分析 网络协议分析网络协议分析网络协议分析网络协议分析网络协议分析网络协议分析网络协议分析网络协议分析网络协议分析网络协议分析网络协议分析网络协议分析网络协议分析网络协议分析网络协议分析网络协议分析网络协议分析

s3c2410 s3c2410s3c2410s3c2410s3c2410s3c2410s3c2410s3c2410s3c2410s3c2410s3c2410s3c2410s3c2410s3c2410s3c2410s3c2410s3c2410s3c2410s3c2410s3c2410s3c2410s3c2410s3c2410s3c2410s3c2410s3c2410s3c2410s3c2410s3c2410s3c2410s3c2410s3c2410s3c2410s3c2410s3c2410s3c2410s3c2410s3c2410s3c2410s3c2410s3c2410s3c2410s3c2410s3c2410s3c2410s3c2410s3c2410s3c2410

I've been working with Windows CE for almost as long as it's been in existence. A Windows programmer for many years, I'm amazed by the number of different, typically quite small, systems to which I can apply my Windows programming experience. These Windows CE systems run the gamut from PC-like mini-laptops to embedded devices buried deep in some large piece of industrial equipment. The use of the Win32 API in Windows CE enables tens of thousands of Windows programmers to write applications for an entirely new class of systems. The subtle differences, however, make writing Windows CE code somewhat different from writing for the desktop versions of Windows. It's those differences that I'll address in this book.

QW2410开发套件wince使用说明书 网址:www.arm380.com Email: [email protected] 一,bootloader的烧录 1,在板子已经有程序的前提下,如果想更新自己的nboot和eboot,可以采用光盘里<烧写程序工程>>目录里的 AXDflash烧写工程进行烧写.这个方法比较快. 对于wince来说:nboot要烧写在第0块,eboot要烧写在第二块.对 于linux来说,vivi要烧写在第0块.具体请参照<<AXDflash烧写工程>>里的说明文件. 2,在板子无程序的情况下,可以参照光盘里<烧写程序工程>>目录里的sjf2410里PDF文档介绍的方法烧写,这个 方法比较慢,烧一个nboot估计需要5分钟左右.

I've been working with Windows CE for almost as long as it's been in existence. A Windows programmer for many years, I'm amazed by the number of different, typically quite small, systems to which I can apply my Windows programming experience. These Windows CE systems run the gamut from PC-like mini-laptops to embedded devices buried deep in some large piece of industrial equipment. The use of the Win32 API in Windows CE enables tens of thousands of Windows programmers to write applications for an entirely new class of systems. The subtle differences, however, make writing Windows CE code somewhat different from writing for the desktop versions of Windows. It's those differences that I'll address in this book.

/* ARP packet tracing routines */ #include <stdio.h> #include "global.h" #include "mbuf.h" #include "arp.h" #include "netuser.h" #include "trace.h" void arp_dump(fp,bpp) FILE *fp; struct mbuf **bpp; { struct arp arp; struct arp_type *at; int is_ip = 0; char tmp[25]; if(bpp == NULL || *bpp == NULL) return; fprintf(fp,"ARP: len %d",len_p(*bpp)); if(ntoharp(&arp,bpp) == -1){ fprintf(fp," bad packet\n"); return; } if(arp.hardware < NHWTYPES) at = &Arp_type[arp.hardware]; else at = NULL; /* Print hardware type in Ascii if known, numerically if not */ fprintf(fp," hwtype %s",smsg(Arptypes,NHWTYPES,arp.hardware)); /* Print hardware length only if unknown type, or if it doesn't match * the length in the known types table */ if(at == NULL || arp.hwalen != at->hwalen) fprintf(fp," hwlen %u",arp.hwalen); /* Check for most common case -- upper level protocol is IP */ if(at != NULL && arp.protocol == at->iptype){ fprintf(fp," prot IP"); is_ip = 1; } else { fprintf(fp," prot 0x%x prlen %u",arp.protocol,arp.pralen); } switch(arp.opcode){ case ARP_REQUEST: fprintf(fp," op REQUEST"); break; case ARP_REPLY: fprintf(fp," op REPLY"); break; case REVARP_REQUEST: fprintf(fp," op REVERSE REQUEST"); break; case REVARP_REPLY: fprintf(fp," op REVERSE REPLY"); break; default: fprintf(fp," op %u",arp.opcode); break; } fprintf(fp,"\n"); fprintf(fp,"sender"); if(is_ip) fprintf(fp," IPaddr %s",inet_ntoa(arp.sprotaddr)); fprintf(fp," hwaddr %s\n",at->format(tmp,arp.shwaddr)); fprintf(fp,"target"); if(is_ip) fprintf(fp," IPaddr %s",inet_ntoa(arp.tprotaddr)); fprintf(fp," hwaddr %s\n",at->format(tmp,arp.thwaddr)); }

络协议是网络上所有设备（网络服务器、计算机及交换机、路由器、防火墙等）之间通信规则的集合，它定义了通信时信息必须采用的格式和这些格式的意义。大多数网络都采用分层的体系结构，每一层都建立在它的下层之上，向它的上一层提供一定的服务，而把如何实现这一服务的细节对上一层加以屏蔽。一台设备上的第n层与另一台设备上的第n层进行通信的规则就是第n层协议。在网络的各层中存在着许多协议，接收方和发送方同层的协议必须一致，否则一方将无法识别另一方发出的信息。网络协议使网络上各种设备能够相互交换信息。

用“mkdir”命令建立目录 用“du”命令检查文件及目录占用空间 使用“ls”命令浏览目录内容 用“groupdel”命令删除组 用“uname”命令获得系统信息 用“userdel”命令删除用户 用“top”命令显示系统进程 用“df”命令查看磁盘分区 用 cal 命令显示月历和年历 用“clear”命令清理终端 用命令创建用户 用“CD”命令定向到目录 “rpm”包和“rpm”命令 使用源代码安装 mplayer 播放器 用“mount”命令安装分区 用“mount”命令安装分区一 用“mount”命令安装分区二 用“mount”命令安装分区三 用“mount”命令安装分区四 用命令复制、移动和删除文件 用命令复制、移动和删除文件一 用命令复制、移动和删除文件二 用命令复制、移动和删除文件三 使用源代码安装kaffeine播放器 使用源代码安装 kaffeine 播放器一 使用源代码安装 kaffeine 播放器二 使用源代码安装 kaffeine 播放器三 用“groupadd”命令创建组 用“kill”命令杀死进程 用“file”命令验明文件正身

，我给进程设定了自己的语法，输入一般 的字符cpu 调用时只是正常输出，假如碰到' 表示该进程要调用系统资源后面必 须跟一个数字表示占有的时间，假如资源闲置则占有资源否则阻塞，等资源释放 在占有资源。进程的调用算法我采用的是时间片轮转算法并有所改进，当某个进 程从阻塞队列释放后，他将把以前因为等待资源而被浪费的时间补回来。 希望大家多提意见

进程XXX 占用了多少内存？这是个经常被问到，也经常被答错的问 题。Linux 进程的内存分配是个比较复杂的话题，而Linux 上的工具 往往把这个问题过分简单化，因此引出不少误解和困惑。

腾讯技术类校园招聘笔试试题(A8卷)一. 单选题(每题4分,15题,共60分) 1.考虑函数原型void hello(int a,int b=7,char* pszC="*"),下面的函数调用钟,属于不合法调用的是:C A hello(5) B.hello(5,8) C.hello(6,"#") D.hello(0,0,"#") 2.下面有关重载函数的说法中正确的是:C A.重载函数必须具有不同的返回值类型 B.重载函数形参个数必须不同 C.重载函数必须有不同的形参列表 D.重载函数名可以不同 重载：必须同名函数；必须参数表不同（包含参数个数不同；参数类型不同；或参数个数与类型都不同）

在本系列序中作者概述了 linux 进程间通信的几种主要手段。其中管道和有名管道是最早的进程间通信机制之一，管道可用于具有亲缘关系进程间的通信，有名管道克服了管道没有名字的限制，因此，除具有管道所具有的功能外，它还允许无亲缘关系进程间的通信。 认清管道和有名管道的读写规则是在程序中应用它们的关键，本文在详细讨论了管道和有名管道的通信机制的基础上，用实例对其读写规则进行了程序验证，这样做有利于增强读者对读写规则的感性认识，同时也提供了应用范例。