-----------------------------------------------------------------------------
1) This file is a supplement to arcnet.txt. Please read that for general
driver configuration help.
-----------------------------------------------------------------------------
2) This file is no longer Linux-specific. It should probably be moved out of
the kernel sources. Ideas?
-----------------------------------------------------------------------------
Because so many people (myself included) seem to have obtained ARCnet cards
without manuals, this file contains a quick introduction to ARCnet hardware,
some cabling tips, and a listing of all jumper settings I can find. Please
e-mail apenwarr@worldvisions.ca with any settings for your particular card,
or any other information you have!
INTRODUCTION TO ARCNET
----------------------
ARCnet is a network type which works in a way similar to popular Ethernet
networks but which is also different in some very important ways.
First of all, you can get ARCnet cards in at least two speeds: 2.5 Mbps
(slower than Ethernet) and 100 Mbps (faster than normal Ethernet). In fact,
there are others as well, but these are less common. The different hardware
types, as far as I'm aware, are not compatible and so you cannot wire a
100 Mbps card to a 2.5 Mbps card, and so on. From what I hear, my driver does
work with 100 Mbps cards, but I haven't been able to verify this myself,
since I only have the 2.5 Mbps variety. It is probably not going to saturate
your 100 Mbps card. Stop complaining. :)
You also cannot connect an ARCnet card to any kind of Ethernet card and
expect it to work.
There are two "types" of ARCnet - STAR topology and BUS topology. This
refers to how the cards are meant to be wired together. According to most
available documentation, you can only connect STAR cards to STAR cards and
BUS cards to BUS cards. That makes sense, right? Well, it's not quite
true; see below under "Cabling."
Once you get past these little stumbling blocks, ARCnet is actually quite a
well-designed standard. It uses something called "modified token passing"
which makes it completely incompatible with so-called "Token Ring" cards,
but which makes transfers much more reliable than Ethernet does. In fact,
ARCnet will guarantee that a packet arrives safely at the destination, and
even if it can't possibly be delivered properly (ie. because of a cable
break, or because the destination computer does not exist) it will at least
tell the sender about it.
Because of the carefully defined action of the "token", it will always make
a pass around the "ring" within a maximum length of time. This makes it
useful for realtime networks.
In addition, all known ARCnet cards have an (almost) identical programming
interface. This means that with one ARCnet driver you can support any
card, whereas with Ethernet each manufacturer uses what is sometimes a
completely different programming interface, leading to a lot of different,
sometimes very similar, Ethernet drivers. Of course, always using the same
programming interface also means that when high-performance hardware
facilities like PCI bus mastering DMA appear, it's hard to take advantage of
them. Let's not go into that.
One thing that makes ARCnet cards difficult to program for, however, is the
limit on their packet sizes; standard ARCnet can only send packets that are
up to 508 bytes in length. This is smaller than the Internet "bare minimum"
of 576 bytes, let alone the Ethernet MTU of 1500. To compensate, an extra
level of encapsulation is defined by RFC1201, which I call "packet
splitting," that allows "virtual packets" to grow as large as 64K each,
although they are generally kept down to the Ethernet-style 1500 bytes.
For more information on the advantages and disadvantages (mostly the
advantages) of ARCnet networks, you might try the "ARCnet Trade Association"
WWW page:
http://www.arcnet.com
CABLING ARCNET NETWORKS
-----------------------
This section was rewritten by
Vojtech Pavlik <vojtech@suse.cz>
using information from several people, including:
Avery Pennraun <apenwarr@worldvisions.ca>
Stephen A. Wood <saw@hallc1.cebaf.gov>
John Paul Morrison <jmorriso@bogomips.ee.ubc.ca>
Joachim Koenig <jojo@repas.de>
and Avery touched it up a bit, at Vojtech's request.
ARCnet (the classic 2.5 Mbps version) can be connected by two different
types of cabling: coax and twisted pair. The other ARCnet-type networks
(100 Mbps TCNS and 320 kbps - 32 Mbps ARCnet Plus) use different types of
cabling (Type1, Fiber, C1, C4, C5).
For a coax network, you "should" use 93 Ohm RG-62 cable. But other cables
also work fine, because ARCnet is a very stable network. I personally use 75
Ohm TV antenna cable.
Cards for coax cabling are shipped in two different variants: for BUS and
STAR network topologies. They are mostly the same. The only difference
lies in the hybrid chip installed. BUS cards use high impedance output,
while STAR use low impedance. Low impedance card (STAR) is electrically
equal to a high impedance one with a terminator installed.
Usually, the ARCnet networks are built up from STAR cards and hubs. There
are two types of hubs - active and passive. Passive hubs are small boxes
with four BNC connectors containing four 47 Ohm resistors:
| | wires
R + junction
-R-+-R- R 47 Ohm resistors
R
|
The shielding is connected together. Active hubs are much more complicated;
they are powered and contain electronics to amplify the signal and send it
to other segments of the net. They usually have eight connectors. Active
hubs come in two variants - dumb and smart. The dumb variant just
amplifies, but the smart one decodes to digital and encodes back all packets
coming through. This is much better if you have several hubs in the net,
since many dumb active hubs may worsen the signal quality.
And now to the cabling. What you can connect together:
1. A card to a card. This is the simplest way of creating a 2-computer
network.
2. A card to a passive hub. Remember that all unused connectors on the hub
must be properly terminated with 93 Ohm (or something else if you don't
have the right ones) terminators.
(Avery's note: oops, I didn't know that. Mine (TV cable) works
anyway, though.)
3. A card to an active hub. Here is no need to terminate the unused
connectors except some kind of aesthetic feeling. But, there may not be
more than eleven active hubs between any two computers. That of course
doesn't limit the number of active hubs on the network.
4. An active hub to another.
5. An active hub to passive hub.
Remember, that you can not connect two passive hubs together. The power loss
implied by such a connection is too high for the net to operate reliably.
An example of a typical ARCnet network:
R S - STAR type card
S------H--------A-------S R - Terminator
| | H - Hub
| | A - Active hub
| S----H----S
S |
|
S
The BUS topology is very similar to the one used by Ethernet. The only
difference is in cable and terminators: they should be 93 Ohm. Ethernet
uses 50 Ohm impedance. You use T connectors to put the computers on a single
line of cable, the bus. You have to put terminators at both ends of the
cable. A typical BUS ARCnet network looks like:
RT----T------T------T------T------TR
B B B B B B
B - BUS type card
R - Terminator
T - T connector
But that is not all! The two ty
没有合适的资源?快使用搜索试试~ 我知道了~
linux-2.4.0内核源代码
共8181个文件
h:3496个
c:3240个
s:400个
5星 · 超过95%的资源 需积分: 10 205 下载量 103 浏览量
2011-07-06
15:58:10
上传
评论 3
收藏 26.71MB ZIP 举报
温馨提示
在内核代码 2.6.15.5中/kernel/fork.c第1255-1261中有如下代码: 1. p = copy_process(clone_flags, stack_start, regs, stack_size, parent_tidptr, child_tidptr, pid); 2. if (!IS_ERR(p)) { 3. struct completion vfork; 4 . if (clone_flags & CLONE_VFORK) { 5. p->vfork_done = &vfork; 6. init_completion(&vfork); 7. } 为了方便描述我在这段代码上加了行号。 第一行首先通过copy_process()函数完成具体的进程创建工作,返回值类型为task_t类型。 第2行用函数 IS_ERR()分析copy_process()的返回值是否正确。如果正确则执行第3-7行代码。 这里分析一下接下来这几行代码: struct completion vfork; //定义struct completion 类型的变量 vfork; 关于struct completion的定义如下: struct completion { unsigned int done; wait_queue_head_t wait;
资源推荐
资源详情
资源评论
收起资源包目录
linux-2.4.0内核源代码 (8181个子文件)
00-INDEX 6KB
00-INDEX 3KB
00-INDEX 1KB
00-INDEX 1KB
00-INDEX 941B
00-INDEX 694B
00-INDEX 539B
00-INDEX 305B
00-INDEX 195B
00-INDEX 146B
dasdfmt.8 2KB
a5k 11KB
README.act2000 3KB
AD1816 3KB
README.aha152x 6KB
README.aic7xxx 24KB
ALS 4KB
README.AM53C974 9KB
apus_defconfig 12KB
md5sums.asc 1KB
md5sums.asc 642B
assabet 12KB
Assabet 1KB
README.audio 6KB
AudioExcelDSP16 4KB
README.avmb1 6KB
README.awe 8KB
ChangeLog.awe 6KB
INSTALL.awe 4KB
AWE32 4KB
compile.awk 2KB
print_offsets.awk 1KB
compile.awk 1KB
actionnm.awk 444B
aztcd 42KB
balance 5KB
ld.script.balo 3KB
ld.script.big 3KB
boot-options 2KB
brutus 6KB
Brutus 2KB
bseip_defconfig 8KB
README.buddha 8KB
BUG-HUNTING 4KB
BUGS 1KB
BUGS-parport 204B
README.BusLogic 28KB
README.buz 8KB
nls_cp949.c 854KB
nls_cp936.c 677KB
advansys.c 671KB
nls_cp950.c 579KB
qlogicfc_asm.c 494KB
nls_cp932.c 478KB
aic7xxx.c 400KB
sym53c8xx.c 378KB
dgrs_firmware.c 351KB
FlashPoint.c 308KB
pcibr.c 274KB
ixj.c 259KB
DAC960.c 237KB
ncr53c8xx.c 230KB
ips.c 223KB
qla1280.c 217KB
synclink.c 212KB
ide-tape.c 204KB
53c7,8xx.c 201KB
cpqfcTSworker.c 198KB
smctr.c 193KB
skgepnmi.c 190KB
53c7xx.c 190KB
cyclades.c 186KB
aironet4500_rid.c 183KB
font_sun12x22.c 182KB
BusLogic.c 179KB
de4x5.c 174KB
zlib.c 174KB
softfloat.c 164KB
sbpcd.c 162KB
serial.c 158KB
osst.c 158KB
awe_wave.c 154KB
iph5526.c 148KB
istallion.c 141KB
stallion.c 137KB
wavelan_cs.c 135KB
atyfb.c 134KB
qlogicisp_asm.c 128KB
gdth.c 128KB
esp.c 120KB
cs46xx.c 119KB
sys_ia32.c 118KB
wavelan.c 117KB
audio.c 116KB
ppc-opc.c 115KB
ioctl32.c 115KB
epca.c 114KB
floppy.c 113KB
iphase.c 111KB
ip2main.c 109KB
共 8181 条
- 1
- 2
- 3
- 4
- 5
- 6
- 82
huangyongru
- 粉丝: 1
- 资源: 6
上传资源 快速赚钱
- 我的内容管理 展开
- 我的资源 快来上传第一个资源
- 我的收益 登录查看自己的收益
- 我的积分 登录查看自己的积分
- 我的C币 登录后查看C币余额
- 我的收藏
- 我的下载
- 下载帮助
安全验证
文档复制为VIP权益,开通VIP直接复制
信息提交成功
- 1
- 2
- 3
- 4
- 5
- 6
前往页