什么叫溶血| 血糖偏高会有什么症状| 995是什么意思| 早上睡不醒是什么原因| 新生儿老是打嗝是什么原因| 治疗白头发挂什么科| 吃什么水果治便秘| 泌乳素高是什么原因引起的| 吃蒜有什么好处| 蝉什么时候叫| 大红袍属于什么茶| 牛仔裤搭配什么衣服好看| 炎字五行属什么| 枕大神经痛吃什么药| 蜂蜜和柠檬一起喝有什么作用| reebok是什么牌子| 蒲公英和什么相克致死| 综合用地是什么性质| 办身份证的地方叫什么| 甲状腺4a类什么意思| 法兰绒是什么面料| 雪里红是什么菜| 今天是什么月| 淋巴滤泡增生用什么药能彻底治愈| 脱发看什么科| 为什么会拉稀| 眼睛干痒滴什么眼药水| 绝非偶然是什么意思| 汗斑是什么| 超声波是什么| 贱人的意思是什么意思| 根管预备是什么意思| 排气是什么意思| 依波手表什么档次| 催乳素高是什么原因| 家里蟑螂多是什么原因| 胃窦肠化是什么意思| 塔利班是什么| 赭石色是什么颜色| 什么情况下需要做心脏造影| 金刚石是由什么构成的| 虚岁31岁属什么生肖| 酸碱度偏高是什么意思| 免疫球蛋白是什么东西| 盆腔炎是什么引起的| 甲鱼什么人不能吃| 2009年是什么年| 肿瘤前期有什么症状| 铁树开花什么意思| 茄子和什么相克| 破伤风什么时候打最好| 高硼硅玻璃是什么材质| 迄今为止什么意思| 谷氨酰基转移酶低是什么原因| 什么是大麦| eos是什么| 人授和试管有什么区别| 灰指甲有什么危害| 心脏由什么组织构成| 枸杞泡水喝有什么作用| 缺钾会有什么症状| 拉肚子适合吃什么食物| 拘谨是什么意思| 什么是手卫生| 胚胎和囊胚有什么区别| 什么粥养胃| 亚米是什么意思| 恚是什么意思| 梦见自己找工作是什么意思| 大修基金什么时候缴纳| 67岁属什么生肖| 韬光养晦下一句是什么| 尿急是什么原因| 效果图是什么意思| 门第什么意思| 蓝本是什么意思| 小肚子胀是什么原因| 辣椒含有什么维生素| 吃菱角有什么好处| mg是什么单位| 黑色素缺失吃什么补充最快| 紫茉莉什么时候开花| 菊花像什么| 唇周发黑是什么原因| 什么是强迫症| 雨渐耳符咒有什么用| 家什是什么意思| 水蛭怕什么| 帛字五行属什么| 胃溃疡吃什么药好| 实性结节什么意思| 什么是幽门螺杆菌| 散仙是什么意思| 八月二十六是什么星座| 2月24日是什么星座| 舌头不舒服挂什么科| 会厌炎吃什么药最有效| 一什么阳光填量词| 杭州市市长什么级别| 阳瘘的最佳治疗方法是什么| 两个夫一个车是什么字| 给孕妇送什么礼物好| 暴饮暴食容易得什么病| 治疗神经痛用什么药最有效| 中国民间为什么要吃腊八粥| 射精什么感觉| 宝宝什么时候开始说话| 绵密是什么意思| 蹭饭吃是什么意思| 红裤子配什么上衣| 越南人说什么语言| 外贸原单是什么意思| 泰坦尼克号什么时候上映的| s是什么m是什么| 角膜炎是什么症状| 盐酸达泊西汀片是什么药| hpm是什么意思| 耳垂后面疼是什么原因| 激光点痣后需要注意什么| 亚麻跌是什么意思| 夏天吃什么水果好| 什么叫文化| 杨柳代表什么生肖| 小孩放屁很臭是什么原因| 开塞露擦脸有什么效果| 什么叫心悸| 梗塞灶是什么意思| 黑枸杞有什么作用| 寒包火感冒吃什么药| 牙疼吃什么药止疼最快| 转隶是什么意思| 簇新是什么意思| 先自度其足的度是什么意思| 网监是干什么的| 蟋蟀吃什么| 蓬头垢面是什么意思| lcr是什么意思| 地包天什么意思| 白介素是什么| 八是什么生肖| 生理盐水是什么东西| 吃什么东西可以除湿气| 腺癌是什么原因引起的| 内热吃什么药清热解毒| 海鲜菇不能和什么一起吃| 生意兴隆是什么生肖| 双相情感障碍是什么| 酵母样真菌是什么意思| 指甲黑线是什么原因| 勿误是什么意思| 一眼万年什么意思| 血管堵塞吃什么好疏通| 凝血酶是什么| 自缢痣是什么意思| 逼格什么意思| 红面是什么面| 条子是什么意思| 放屁臭鸡蛋味什么原因| 梦见刺猬是什么意思| 龙蛇混杂是什么生肖| 胃肠彩超能检查出什么| 爻是什么意思| 儿加一笔是什么字| gloomy是什么意思| 杏干泡水喝有什么功效| 梦见尸体是什么意思| 黑眼圈是什么病| dwi呈高信号什么意思| 大便颜色发黑是什么原因| 市政协主席是什么级别| 三文鱼和什么不能一起吃| 小腿红肿是什么原因引起的| 血压低有什么危险| 阳气最强的树是什么树| 医院去痣挂什么科| 炒面用什么面条最好| 周杰伦是什么星座| 是什么原因| 长期大便不成形是什么原因造成的| 流苏是什么东西| 藤椒是什么| 骨量偏高是什么原因| 农历11月14日是什么星座| 智齿什么时候长| 胳膊疼挂什么科| 糖醇是什么意思| 加特纳菌阳性是什么病| 宝宝为什么老是吐奶| 上挂是什么意思| 急性肠胃炎是什么原因引起的| 平日是什么意思| 拔完智齿可以吃什么| 截石位是什么意思| 绿树成荫是什么季节| 水乳是什么| 夏天防中暑备什么药| 默念是什么意思| 每天吃维生素c有什么好处| 尿蛋白十1是什么意思| 听吧新征程号角吹响是什么歌| hm是什么| 随餐吃是什么意思| 袁崇焕为什么被杀| 梦见摘桑葚是什么意思| 什么是卒中| 九点到十点是什么时辰| 什么时候开始胎教| 等着我为什么停播了| 贝字旁与什么有关| 小孩睡觉张开嘴巴是什么原因| 管型尿是什么意思| 1997年属什么生肖| 肝脏钙化灶是什么意思| 做梦和别人吵架意味着什么| 杀什么吓什么| 梗犬是什么意思| 鸡为什么喜欢吃泡沫| 4月16日是什么星座| 尿痛什么原因引起的| 胜造七级浮屠是什么意思| 贾字五行属什么| 什么人不适合吃海参| 媱字五行属什么| mua是什么意思| 12月8号是什么星座| 酵母是什么| 骑马标志是什么牌子| 豆浆不能和什么一起吃| 为什么医者不自医| 依稀是什么意思| 心阳虚吃什么中成药| 7.28是什么星座| 乳房胀痛挂什么科| 红薯和什么不能一起吃| 海怪是什么海鲜| 智齿是什么| 讽刺是什么意思| 巴基斯坦是什么人种| 四眼狗有什么迷信说法| 光膀子什么意思| 日金念什么| 烫伤用什么药好| 怀孕周期是从什么时候开始算的| 活性炭是什么东西| 爱打哈欠是什么原因| 山楂泡水喝有什么好处| 吃榴莲有什么坏处| 德育是什么| 守岁是什么意思| 囊肿是什么原因造成的| 胃溃疡可以吃什么水果| 哪吒妈妈叫什么名字| 齿痕舌吃什么药| 宝宝肌张力高会有什么影响| 梦见狼是什么预兆| 热退疹出是什么病| 感冒咳嗽吃什么水果好| 为什么吃火龙果会拉肚子| 肾结石炖什么汤喝最好| 颌下淋巴结肿大挂什么科| 什么是双修| 开除党籍有什么后果| 什么补钾最快| 检查甲亢挂什么科| 百度Jump to content

中国石油去年净利润增近两倍

From Wikipedia, the free encyclopedia
(Redirected from FireWire)
百度 《危机公关道与术》中说危机是:危中藏机,机中含危,负阴抱阳,对立统一,周而复始,运行不息。

IEEE 1394 Interface
Type Serial
Production history
Designer Apple (1394a/b), IEEE P1394 Working Group, Sony, Panasonic, etc.
Designed 1986; 39 years ago (1986)[1]
Standardized January 1995; 30 years ago (1995-01)
Manufacturer Various
Produced 1994–current
Superseded by Thunderbolt (and USB 3.0 for consumer use)
General specifications
Length 4.5 m (15 ft) maximum
Width 1
Hot pluggable Yes
Daisy chain Yes, up to 63 devices
Audio signal No
Video signal No
Pins 4, 6, 9
Electrical
Max. voltage 30 V
Max. current 1.5 A
Data
Data signal Yes
Bitrate
  • 1394a, half-duplex 100–400 Mbit/s (12.5–50 MB/s)
  • 1394b and later, full-duplex 800–3200 Mbit/s (100–400 MB/s)

IEEE 1394 is an interface standard for a serial bus for high-speed communications and isochronous real-time data transfer. It was developed in the late 1980s and early 1990s by Apple in cooperation with a number of companies, primarily Sony and Panasonic. It is most commonly known by the name FireWire (Apple), though other brand names exist such as i.LINK (Sony), and Lynx (Texas Instruments). Most consumer electronics manufacturers phased out IEEE 1394 from their product lines in the 2010s.

The copper cable used in its most common implementation can be up to 4.5 m (15 ft) long. Power and data is carried over this cable, allowing devices with moderate power requirements to operate without a separate power supply. FireWire is also available in Cat 5 and optical fiber versions.

The 1394 interface is comparable to USB. USB was developed subsequently and gained much greater market share. USB requires a host controller whereas IEEE 1394 is cooperatively managed by the connected devices.[2]

History and development

[edit]
The 6-conductor and 4-conductor alpha FireWire 400 socket
A 9-pin FireWire 800 connector
The alternative Ethernet-style cabling used by 1394c
4-conductor (left) and 6-conductor (right) FireWire 400 alpha connectors
A PCI expansion card that contains four FireWire 400 connectors.
A FireWire 800 ExpressCard

FireWire is Apple's name for the IEEE 1394 High Speed Serial Bus. Its development was initiated by Apple[1] in 1986,[3] and developed by the IEEE P1394 Working Group, largely driven by contributions from Sony (102 patents), Apple (58 patents), Panasonic (46 patents), and Philips (43 patents), in addition to contributions made by engineers from LG Electronics, Toshiba, Hitachi, Canon,[4] INMOS/SGS Thomson (now STMicroelectronics),[5] and Texas Instruments.

IEEE 1394 is a serial bus architecture for high-speed data transfer, serial meaning that information is transferred one bit at a time. Parallel buses utilize a number of different physical connections, and as such are usually more costly and typically heavier.[6] IEEE 1394 fully supports both isochronous and asynchronous applications.

Apple intended FireWire to be a serial replacement for the parallel SCSI bus, while providing connectivity for digital audio and video equipment. Apple's development began in the late 1980s, later presented to the IEEE,[7] and was completed in January 1995. In 2007, IEEE 1394 was a composite of four documents: the original IEEE Std. 1394–1995, the IEEE Std. 1394a-2000 amendment, the IEEE Std. 1394b-2002 amendment, and the IEEE Std. 1394c-2006 amendment. On June 12, 2008, all these amendments as well as errata and some technical updates were incorporated into a superseding standard, IEEE Std. 1394–2008.[8]

Apple first included onboard FireWire in some of its 1999 Macintosh models (though it had been a build-to-order option on some models since 1997), and most Apple Macintosh computers manufactured from 2000 through 2011 included FireWire ports. However, in February 2011, Apple introduced its first Mac with Thunderbolt, which superseded FireWire. Apple released its last computers with FireWire in 2012. By 2014, Thunderbolt had become a standard feature across Apple's entire line of computers (later with the exception of the 12-inch MacBook introduced in 2015, which featured only a sole USB-C port), effectively becoming the spiritual successor to FireWire in the Apple ecosystem. Apple's last Mac products with FireWire, the Thunderbolt Display and 2012 13-inch MacBook Pro, were discontinued in 2016. Apple sold a Thunderbolt to FireWire adapter, with a single FireWire 800 port, until 2023.[9] A separate adapter was required to use it with Thunderbolt 3.

Sony's implementation of the system, i.LINK, used a smaller connector with only four signal conductors, omitting the two conductors that provide power for devices in favor of a separate power connector. This style was later added into the 1394a amendment.[7] This port is sometimes labeled S100 or S400 to indicate speed in Mbit/s.

The system was commonly used to connect data storage devices and DV (digital video) cameras, but was also popular in industrial systems for machine vision and professional audio systems. Many users preferred it over the more common USB 2.0 for its then greater effective speed and power distribution capabilities. Benchmarks show that the sustained data transfer rates are higher for FireWire than for USB 2.0, but lower than USB 3.0. Results are marked on Apple Mac OS X but more varied on Microsoft Windows.[10][11]

Patent considerations

[edit]

Implementation of IEEE 1394[12] is said to require use of 261 issued international patents[4] held by ten[5] corporations. Use of these patents requires licensing; use without license generally constitutes patent infringement.[13] Companies holding IEEE 1394 IP formed a patent pool with MPEG LA, LLC as the license administrator, to whom they licensed patents. MPEG LA sublicenses these patents to providers of equipment implementing IEEE 1394. Under the typical patent pool license, a royalty of US$0.25 per unit is payable by the manufacturer upon the manufacture of each 1394 finished product;[13] no royalties are payable by users.

The last of the patents, MY 120654 by Sony, expired on November 30, 2020. As of November 30, 2020, the following are patent holders of the IEEE 1394 standard, as listed in the patent pool managed by MPEG LA.[4]

Company Total patents
Sony 102
Apple 58
Panasonic 46
Philips 43
LG 11
Toshiba 10
Hitachi 4
Canon 1
Compaq 1
Samsung 1

A person or company may review the actual 1394 Patent Portfolio License upon request to MPEG LA.[14] MPEG LA does not provide assurance of protection to licensees beyond its own patents. At least one formerly licensed patent is known to have been removed from the pool,[4] and other hardware patents exist that reference IEEE 1394.[15]

The 1394 High Performance Serial Bus Trade Association (the 1394 TA) was formed to aid the marketing of IEEE 1394. Its bylaws prohibit dealing with intellectual property issues.[16] The 1394 Trade Association operates on an individual no cost membership basis to further enhancements to 1394 standards. The Trade Association also is the library source for all 1394 documentation and standards available.

Technical specifications

[edit]

FireWire can connect up to 63 peripherals in a tree or daisy-chain topology[17] (as opposed to Parallel SCSI's electrical bus topology). It allows peer-to-peer device communication — such as communication between a scanner and a printer — to take place without using system memory or the CPU. FireWire also supports multiple host controllers per bus. It is designed to support plug and play and hot swapping. The copper cable it uses in its most common implementation can be up to 4.5 m (15 ft) long and is more flexible than most parallel SCSI cables. In its six-conductor or nine-conductor variations, it can supply up to 45 watts of power per port at up to 30 volts,[18] allowing moderate-consumption devices to operate without a separate power supply.

FireWire devices implement the ISO/IEC 13213 configuration ROM model for device configuration and identification, to provide plug-and-play capability. All FireWire devices are identified by an IEEE EUI-64 unique identifier in addition to well-known codes indicating the type of device and the protocols it supports.

FireWire devices are organized at the bus in a tree topology. Each device has a unique self-ID. One of the nodes is elected root node and always has the highest ID. The self-IDs are assigned during the self-ID process, which happens after each bus resets. The order in which the self-IDs are assigned is equivalent to traversing the tree depth-first, post-order.

FireWire is capable of safely operating critical systems due to the way multiple devices interact with the bus and how the bus allocates bandwidth to the devices. FireWire is capable of both asynchronous and isochronous transfer methods at once. Isochronous data transfers are transfers for devices that require continuous, guaranteed bandwidth.[6] In an aircraft, for instance, isochronous devices include control of the rudder, mouse operations and data from pressure sensors outside the aircraft. All these elements require constant, uninterrupted bandwidth. To support both elements, FireWire dedicates a certain percentage to isochronous data and the rest to asynchronous data. In IEEE 1394, 80% of the bus is reserved for isochronous cycles, leaving asynchronous data with a minimum of 20% of the bus.[19]

Encoding scheme

[edit]

FireWire uses Data/Strobe encoding (D/S encoding).[20] In D/S encoding, two non-return-to-zero (NRZ) signals are used to transmit the data with high reliability. The NRZ signal sent is fed with the clock signal through an XOR gate, creating a strobe signal.[20] This strobe is then put through another XOR gate along with the data signal to reconstruct the clock.[20] This in turn acts as the bus's phase-locked loop for synchronization purposes.[20]

Arbitration

[edit]

The process of the bus deciding which node gets to transmit data at what time is known as arbitration.[21] Each arbitration round lasts about 125 microseconds.[21] During the round, the root node (device nearest the processor) sends a cycle start packet.[21] All nodes requiring data transfer respond, with the closest node winning.[21] After the node is finished, the remaining nodes take turns in order. This repeats until all the devices have used their portion of the 125 microseconds, with isochronous transfers having priority.[21]

Standards and versions

[edit]

The previous standards and its three published amendments are now incorporated into a superseding standard, IEEE 1394-2008.[8] The features individually added give a good history on the development path.

FireWire 400 (IEEE 1394-1995)

[edit]
4-pin connector to 6-pin FireWire 400 Adapter

The original release of IEEE 1394-1995[22] specified what is now known as FireWire 400. It can transfer data between devices at 100, 200, or 400 Mbit/s half-duplex[23] data rates (the actual transfer rates are 98.304, 196.608, and 393.216 Mbit/s, i.e., 12.288, 24.576 and 49.152 MB/s respectively).[7] These different transfer modes are commonly referred to as S100, S200, and S400.

Cable length is limited to 4.5 m (15 ft), although up to 16 cables can be daisy chained using active repeaters, e.g. external hubs or the internal hubs that are often present in FireWire equipment. The S400 standard limits any configuration's maximum cable length to 72 m (236 ft). The 6-conductor connector is commonly found on desktop computers and can supply the connected device with power.

The 6-conductor powered connector, now referred to as an alpha connector, adds power output to support external devices. Typically a device can pull about 7 to 8 watts from the port; however, the voltage varies significantly from different devices.[24] Voltage is specified as unregulated and should nominally be about 25 volts (range 24 to 30). Apple's implementation on laptops is typically related to battery power and can be as low as 9 V.[24]

Improvements (IEEE 1394a-2000)

[edit]

An amendment, IEEE 1394a, was released in 2000,[25] which clarified and improved the original specification. It added support for asynchronous streaming, quicker bus reconfiguration, packet concatenation, and a power-saving suspend mode.

IEEE 1394a offers a couple of advantages over the original IEEE 1394–1995. 1394a is capable of arbitration accelerations, allowing the bus to accelerate arbitration cycles to improve efficiency. It also allows for arbitrated short bus reset, in which a node can be added or dropped without causing a big drop in isochronous transmission.[19]

1394a also standardized the 4-conductor alpha connector developed by Sony and trademarked as i.LINK, already widely in use on consumer devices such as camcorders, most PC laptops, a number of PC desktops, and other small FireWire devices. The 4-conductor connector is fully data-compatible with 6-conductor alpha interfaces but lacks power connectors.

FireWire 800 port (center)

FireWire 800 (IEEE 1394b-2002)

[edit]
A 9-conductor bilingual connector

IEEE 1394b-2002[26] introduced FireWire 800 (Apple's name for the 9-conductor S800 bilingual version of the IEEE 1394b standard). This specification added a new encoding scheme termed beta mode which allowed compliant devices to operate at 786.432 Mbit/s full-duplex. It is backwards compatible with the slower rates and 6-conductor alpha connectors of FireWire 400. However, while the IEEE 1394a and IEEE 1394b standards are compatible, FireWire 800's connector, referred to as a beta connector, is different from FireWire 400's alpha connectors, making legacy cables incompatible. A bilingual cable allows the connection of older devices to the newer port. In 2003, Apple was the first to introduce commercial products with the new connector, including a new model of the Power Mac G4 and a 17" PowerBook G4.

The full IEEE 1394b specification supports data rates up to 3200 Mbit/s (i.e., 400 MB/s) over beta-mode or optical connections up to 100 m (330 ft) in length. Standard category 5e cable supports 100 m (330 ft) at S100. The original 1394 and 1394a standards used data/strobe (D/S) encoding, now known as alpha mode, with the cables, while 1394b added a data encoding scheme called 8b/10b referred to as beta mode.

Beta mode is based on 8b/10b (from Gigabit Ethernet, also used for many other protocols). 8b/10b encoding involves expanding an 8-bit data word into 10 bits, with the extra bits after the 5th and 8th data bits.[27] The partitioned data is sent through a Running Disparity calculator function.[27] The Running Disparity calculator attempts to keep the number of 1s transmitted equal to 0s,[28] thereby assuring a DC-balanced signal. Then, the different partitions are sent through a 5b/6b encoder for the 5-bit partition and a 3b/4b encoder for the 3-bit partition. This gives the packet the ability to have at least two 1s, ensuring synchronization of the PLL at the receiving end to the correct bit boundaries for reliable transfer.[28] An additional function of the coding scheme is to support the arbitration for bus access and general bus control. This is possible due to the surplus symbols afforded by the 8b/10b expansion. (While 8-bit symbols can encode a maximum of 256 values, 10-bit symbols permit the encoding of up to 1024.) Symbols invalid for the current state of the receiving PHY indicate data errors.

FireWire S800T (IEEE 1394c-2006)

[edit]

IEEE 1394c-2006 was published on June 8, 2007.[29] It provided a major technical improvement, namely new port specification that provides 800 Mbit/s over the same 8P8C (Ethernet) connectors with Category 5e cable, which is specified in IEEE 802.3 clause 40 (gigabit Ethernet over copper twisted pair) along with a corresponding automatic negotiation that allows the same port to connect to either IEEE Std 1394 or IEEE 802.3 (Ethernet) devices.

FireWire S1600 and S3200

[edit]

In December 2007, the 1394 Trade Association announced that products would be available before the end of 2008 using the S1600 and S3200 modes that, for the most part, had already been defined in 1394b and were further clarified in IEEE Std. 1394–2008.[8] The 1.572864 Gbit/s and 3.145728 Gbit/s devices use the same 9-conductor beta connectors as the existing FireWire 800 and are fully compatible with existing S400 and S800 devices. It competes with USB 3.0.[30]

S1600 (Symwave[31]) and S3200 (Dap Technology[32]) development units have been made, however because of FPGA technology DapTechnology targeted S1600 implementations first with S3200 not becoming commercially available until 2012.

Steve Jobs declared FireWire dead in 2008.[33] As of 2012, there were few S1600 devices released, with a Sony camera being the only notable user.[34]

Cancelled enhancements (including P1394d)

[edit]

A project named IEEE P1394d was formed by the IEEE on March 9, 2009 to add single-mode fiber as an additional transport medium to FireWire.[35] The project was withdrawn in 2013.[36]

Other future iterations of FireWire were expected to increase speed to 6.4 Gbit/s and additional connectors such as the small multimedia interface.[37][citation needed]

Operating system support

[edit]

Full support for IEEE 1394a and 1394b was implemented in Microsoft Windows, FreeBSD,[38] Linux,[39][40] macOS and NetBSD.

In Windows XP, a degradation in performance of 1394 devices may have occurred with installation of Service Pack 2. This was resolved in Hotfix 885222[41] and in SP3. Some FireWire hardware manufacturers also provide custom device drivers that replace the Microsoft OHCI host adapter driver stack, enabling S800-capable devices to run at full 800 Mbit/s transfer rates on older versions of Windows (XP SP2 w/o Hotfix 885222) and Windows Vista. At the time of its release, Microsoft Windows Vista supported only 1394a, with assurances that 1394b support would come in the next service pack.[42] Service Pack 1 for Microsoft Windows Vista has since been released, however the addition of 1394b support is not mentioned anywhere in the release documentation.[43][44][45] The 1394 bus driver was rewritten for Windows 7 to provide support for higher speeds and alternative media.[46]

In Linux, support was originally provided by libraw1394 making direct communication between user space and IEEE 1394 buses.[47] Subsequently, a new kernel driver stack, nicknamed JuJu, has been implemented.[48]

IEEE 1394 drivers are no longer included in Windows by default since Windows 10.[49] FireWire support was removed from macOS in macOS Tahoe 26.[50] Support for FireWire in Linux is planned to be deprecated after 2029.[51]

Cable TV system support

[edit]

Under FCC Code 47 CFR 76.640 section 4, subsections 1 and 2, Cable TV providers (in the US, with digital systems) must, upon request of a customer, have provided a high-definition capable cable box with a functional FireWire interface. This applied only to customers leasing high-definition capable cable boxes from their cable provider after April 1, 2004.[52] The interface can be used to display or record Cable TV, including HDTV programming.[53] In June 2010, the FCC issued an order that permitted set-top boxes to include IP-based interfaces in place of FireWire.[54][55]

Comparison with USB

[edit]

While both technologies provide similar end results, there are fundamental differences between USB and FireWire. USB requires the presence of a host controller, typically a PC, which connects point to point with the USB device. This allows for simpler (and lower-cost) peripherals, at the cost of lowered functionality of the bus. Intelligent hubs are required to connect multiple USB devices to a single USB host controller. By contrast, FireWire is essentially a peer-to-peer network (where any device may serve as the host or client), allowing multiple devices to be connected on one bus.[56]

The FireWire host interface supports DMA and memory-mapped devices, allowing data transfers to happen without loading the host CPU with interrupts and buffer-copy operations.[10][57] Additionally, FireWire features two data buses for each segment of the bus network, whereas, until USB 3.0, USB featured only one. This means that FireWire can have communication in both directions at the same time (full-duplex), whereas USB communication prior to 3.0 can only occur in one direction at any one time (half-duplex).[citation needed]

While USB 2.0 expanded into the fully backwards-compatible USB 3.0 and 3.1 (using the same main connector type), FireWire used a different connector between 400 and 800 implementations.

Common applications

[edit]

Consumer automobiles

[edit]

IDB-1394 Customer Convenience Port (CCP) was the automotive version of the 1394 standard.[58]

Consumer audio and video

[edit]

IEEE 1394 was the High-Definition Audio-Video Network Alliance (HANA) standard connection interface for A/V (audio/visual) component communication and control.[59] HANA was dissolved in September 2009 and the 1394 Trade Association assumed control of all HANA-generated intellectual property.

Military and aerospace vehicles

[edit]

SAE Aerospace standard AS5643 originally released in 2004 and reaffirmed in 2013 establishes IEEE-1394 standards as a military and aerospace databus network in those vehicles. AS5643 is utilized by several large programs, including the F-35 Lightning II, the X-47B UCAV aircraft, AGM-154 weapon and JPSS-1 polar satellite for NOAA. AS5643 combines existing 1394-2008 features like looped topology with additional features like transformer isolation and time synchronization, to create deterministic double and triple fault-tolerant data bus networks.[60][61][62]

General networking

[edit]

FireWire can be used for ad hoc (terminals only, no routers except where a FireWire hub is used) computer networks. Specifically, RFC 2734 specifies how to run IPv4 over the FireWire interface, and RFC 3146 specifies how to run IPv6.

Mac OS X, Linux, and FreeBSD include support for networking over FireWire.[63] Windows 95, Windows 98, Windows Me,[64] Windows XP and Windows Server 2003 include native support for IEEE 1394 networking.[65] Windows 2000 does not have native support but may work with third party drivers. A network can be set up between two computers using a single standard FireWire cable, or by multiple computers through use of a hub. This is similar to Ethernet networks with the major differences being transfer speed, conductor length, and the fact that standard FireWire cables can be used for point-to-point communication.

On December 4, 2004, Microsoft announced that it would discontinue support for IP networking over the FireWire interface in all future versions of Microsoft Windows.[66] Consequently, support for this feature is absent from Windows Vista and later Windows releases.[67][68] Microsoft rewrote their 1394 driver in Windows 7[69] but networking support for FireWire is not present. Unibrain offers free FireWire networking drivers for Windows called ubCore,[70] which support Windows Vista and later versions.

Earlier models of the PlayStation 2 console (SCPH 1000x to 3900x series) had an i.LINK-branded 1394 connector. This was used for networking until the release of an Ethernet adapter later in the console's lifespan, but very few software titles supported the feature. The connector was removed from the SCPH 5000x[71] series onward.

IIDC

[edit]

IIDC (Instrumentation & Industrial Digital Camera) is the FireWire data format standard for live video, and is used by Apple's iSight A/V camera. The system was designed for machine vision systems[72] but is also used for other computer vision applications and for some webcams. Although they are easily confused since they both run over FireWire, IIDC is different from, and incompatible with, the ubiquitous AV/C (Audio Video Control) used to control camcorders and other consumer video devices.[73]

DV

[edit]

Digital Video (DV) is a standard protocol used by some digital camcorders. All DV cameras that recorded to tape media had a FireWire interface (usually a 4-conductor). All DV ports on camcorders only operate at the slower 100 Mbit/s speed of FireWire. This presents operational issues if the camcorder is daisy chained from a faster S400 device or via a common hub because any segment of a FireWire network cannot support multiple speed communication.[74]

Labeling of the port varied by manufacturer, with Sony using either its i.LINK trademark or the letters DV. Many digital video recorders have a DV-input FireWire connector (usually an alpha connector) that can be used to record video directly from a DV camcorder (computer-free). The protocol also accommodates remote control (play, rewind, etc.) of connected devices, and can stream time code from a camera.

USB is unsuitable for the transfer of the video data from tape because tape by its very nature does not support variable data rates. USB relies heavily on processor support and this was not guaranteed to service the USB port in time. The later move away from tape towards solid-state memory or disc media (e.g., SD Cards, optical disks or hard drives) has facilitated moving to USB transfer because file-based data can be moved in segments as required.

Frame grabbers

[edit]

IEEE 1394 interface is commonly found in frame grabbers, devices that capture and digitize an analog video signal; however, IEEE 1394 is facing competition from the Gigabit Ethernet interface (citing speed and availability issues).[75]

iPod and iPhone synchronization and charging

[edit]

iPods released prior to the iPod with Dock Connector used IEEE 1394a ports for transferring music files and charging, but in 2003, the FireWire port in iPods was succeeded by Apple's dock connector and IEEE 1394 to 30-pin connector cables were made. Apple began removing backwards compatibility with FireWire cables starting with the first generation iPod nano and fifth generation iPod, both of which could only sync via USB but retained the ability to charge through FireWire. This was also carried over to the second and third generation nanos as well as the iPod Classic. Backwards compatibility was removed completely beginning with the iPhone 3G, second generation iPod touch, and the fourth generation iPod nano,[76] all of which could only charge and sync via USB.

Security issues

[edit]

Devices on a FireWire bus can communicate by direct memory access (DMA), where a device can use hardware to map internal memory to FireWire's physical memory space. The SBP-2 (Serial Bus Protocol 2) used by FireWire disk drives uses this capability to minimize interrupts and buffer copies. In SBP-2, the initiator (controlling device) sends a request by remotely writing a command into a specified area of the target's FireWire address space. This command usually includes buffer addresses in the initiator's FireWire Physical Address Space, which the target is supposed to use for moving I/O data to and from the initiator.[77]

On many implementations, particularly those like PCs and Macs using the popular OHCI, the mapping between the FireWire physical memory space and device physical memory is done in hardware, without operating system intervention. While this enables high-speed and low-latency communication between data sources and sinks without unnecessary copying (such as between a video camera and a software video recording application, or between a disk drive and the application buffers), this can also be a security or media rights-restriction risk if untrustworthy devices are attached to the bus and initiate a DMA attack. One of the applications known to exploit this to gain unauthorized access to running Windows, Mac OS and Linux computers is the spyware FinFireWire. For this reason, high-security installations typically either use newer machines that map a virtual memory space to the FireWire physical memory space (such as a Power Mac G5, or any Sun workstation), disable relevant drivers at operating system level,[78] disable the OHCI hardware mapping between FireWire and device memory, physically disable the entire FireWire interface, or opt to not use FireWire or other hardware like PCMCIA, PC Card, ExpressCard or Thunderbolt, which expose DMA to external components.

An unsecured FireWire interface can be used to debug a machine whose operating system has crashed, and in some systems for remote-console operations. Windows natively supports this scenario of kernel debugging,[79] although newer Windows Insider Preview builds no longer include the ability out of the box.[80] On FreeBSD, the dcons driver provides both, using gdb as debugger. Under Linux, firescope[81] and fireproxy[82] exist.

See also

[edit]

References

[edit]
  1. ^ a b "1394ta.org". 1394ta.org. Archived from the original on 2025-08-14. Retrieved 2025-08-14. The 1394 digital link standard was conceived in 1986 by technologists at Apple Computer
  2. ^ Yaghmour, Karim; Masters, Jon; Ben-Yossef, Gilad; Gerum, Philippe (2025-08-14). Building embedded Linux systems. O'Reilly Media, Inc. p. 70. ISBN 978-0-596-52968-0. Retrieved 2025-08-14.
  3. ^ "What Is FireWire?". 1394 Trade Association. Archived from the original on 2025-08-14.
  4. ^ a b c d "Attachment 1 List of Patents in the 1394 Patent Portfolio" (PDF). Archived from the original (PDF) on 2025-08-14. Retrieved 2025-08-14.
  5. ^ a b "MPEG LA - 1394 Licensors". Archived from the original on 2025-08-14. Retrieved 2025-08-14.
  6. ^ a b "IEEE Standard 1394a - Thunderbolt". Thunderbolt. Retrieved 2025-08-14.
  7. ^ a b c Teener, Michael J. "What is Firewire?". Retrieved 2025-08-14.[self-published source?]
  8. ^ a b c "IEEE Standard for a High-Performance Serial Bus". IEEE STD. 1394-2008. 2025-08-14. doi:10.1109/IEEESTD.2008.4659233. ISBN 978-0-7381-5771-9.
  9. ^ "Apple Thunderbolt to FireWire Adapter". Retrieved 2025-08-14.
  10. ^ a b "FireWire — USB Comparison". Usb-ware.com. Archived from the original on 2025-08-14. Retrieved 2025-08-14.
  11. ^ Schmid, Patrick (2025-08-14). "Go External: FireWire 800". Tom's Hardware. Retrieved 2025-08-14.
  12. ^ "MPEG LA - 1394 License Agreement". Archived from the original on 2025-08-14. Retrieved 2025-08-14.
  13. ^ a b "MPEG LA - 1394 FAQ". Archived from the original on March 14, 2010.
  14. ^ "MPEG LA - 1394 License Agreement Express (hardcopy)". Archived from the original on October 8, 2009.
  15. ^ "Google Patent search "IEEE 1394"".
  16. ^ "BYLAWS OF THE 1394 TRADE ASSOCIATION". Archived from the original on 2025-08-14.
  17. ^ "IEEE 1394 - The Multimedia Bus of The Future". cablelabs.com. Archived from the original on 2025-08-14.
  18. ^ "IEEE 1394 Tutorial". Retrieved 2025-08-14.
  19. ^ a b "IEEE 1394 Architecture" (PDF). I/ONE. Archived from the original on 2025-08-14.
  20. ^ a b c d "IEEE 1394 (AKA 'FireWire' & 'iLink')" (PDF). Retrieved 2025-08-14.
  21. ^ a b c d e "IEEE 1394 and Linux". Tindel.net. Archived from the original on 2025-08-14. Retrieved 2025-08-14.
  22. ^ IEEE p1394 Working Group (2025-08-14). IEEE Standard for a High Performance Serial Bus (PDF). IEEE. doi:10.1109/IEEESTD.1996.81049. ISBN 1-55937-583-3. Archived from the original (PDF) on 2025-08-14. Retrieved 2025-08-14.{{cite book}}: CS1 maint: numeric names: authors list (link)
  23. ^ Davis, Larry. "Firewire Bus". interfacebus.com. Retrieved 2025-08-14.
  24. ^ a b "FireWire Developer Note". Developer.apple.com. 2025-08-14. Archived from the original on May 18, 2009. Retrieved 2025-08-14.
  25. ^ IEEE p1394a Working Group (2025-08-14). IEEE Standard for a High Performance Serial Bus (Amendment). IEEE. doi:10.1109/IEEESTD.2000.91614. ISBN 0-7381-1958-X.{{cite book}}: CS1 maint: numeric names: authors list (link) P1394a Draft 5.0[dead link] available.
  26. ^ IEEE p1394b Working Group (2025-08-14). IEEE Std 1394b-2002 High Performance Serial Bus — Amendment 2. IEEE. ISBN 0-7381-3253-5.{{cite book}}: CS1 maint: numeric names: authors list (link)[dead link]
  27. ^ a b "Encoder/Decoder". Iram.cs.berkeley.edu. 2025-08-14. Retrieved 2025-08-14.
  28. ^ a b Haden, Rhys (2025-08-14). "CP3070 Principles of Data Communications". Rhyshaden.com. Retrieved 2025-08-14.
  29. ^ "IEEE Standard for a High-Performance Serial Bus - Amendment 3". IEEE STD 1394c-2006. 2025-08-14. doi:10.1109/IEEESTD.2006.371044. ISBN 978-0-7381-5237-0.
  30. ^ "1394 Trade Association Announces 3.2 Gigabit per Second Speed for FireWire". 1394 Trade Association. 2025-08-14. Retrieved 2025-08-14.
  31. ^ "Archived copy" (PDF). symwave.com. Archived from the original (PDF) on 6 March 2016. Retrieved 14 January 2022.{{cite web}}: CS1 maint: archived copy as title (link)
  32. ^ "Fires Up World's First 3.2 Gigabit IEEE 1394b FireWire SOC Solution". DapTechnology. 2025-08-14. Archived from the original on 2025-08-14. Retrieved 2025-08-14.
  33. ^ Arthur, Charles (2025-08-14). "Steve Jobs explains why FireWire is dead". TheGuardian.com. Retrieved 2025-08-14.
  34. ^ Henehan, Burke (2025-08-14). "FireWire at 4Gbps-Impact on industrial apps". EE Times. Retrieved 2025-08-14.
  35. ^ "P1394d - IEEE Standard for a High-Performance Serial Bus - Amendment: IEEE 1394 Single-mode Fiber Fiber Physical Medium (PMD) Specification". IEEE Standards. IEEE. Archived from the original on January 8, 2013. Retrieved 8 October 2012.
  36. ^ "IEEE-SA - Standards Board Approvals - March 2013". Retrieved 2025-08-14.
  37. ^ Baxter, Les (2025-08-14). "New developments in IEEE 1394 (a.k.a. FireWire)". Lightwave. Retrieved 2025-08-14.
  38. ^ "FreeBSD firewire(4) man page". Freebsd.org. 2025-08-14. Retrieved 2025-08-14.
  39. ^ "Linux FireWire wiki". Ieee1394.wiki.kernel.org. 2025-08-14. Retrieved 2025-08-14.
  40. ^ "Linux Unified Target wiki". linux-iscsi.org. 2025-08-14. Archived from the original on 2025-08-14. Retrieved 2025-08-14.
  41. ^ "Performance of 1394 devices may decrease after you install Windows XP Service Pack 2". Support.microsoft.com. 2025-08-14. Retrieved 2025-08-14.
  42. ^ "Microsoft to support 1394b standard". EETimes.com. Retrieved 2025-08-14.
  43. ^ "Notable Changes in Windows Vista Service Pack 1". Technet2.microsoft.com. Archived from the original on 2025-08-14. Retrieved 2025-08-14.
  44. ^ "Release Notes for Windows Vista Service Pack 1". Technet2.microsoft.com. Archived from the original on 2025-08-14. Retrieved 2025-08-14.
  45. ^ "Hotfixes and Security Updates included in Windows Vista Service Pack 1". Technet2.microsoft.com. Archived from the original on 2025-08-14. Retrieved 2025-08-14.
  46. ^ "1394 Bus Driver in Windows 7". Microsoft.com. 2025-08-14. Retrieved 2025-08-14.
  47. ^ "Package: libraw1394-8 (1.3.0-4)". Retrieved 2025-08-14.
  48. ^ "Juju Migration". Retrieved 2025-08-14.
  49. ^ Tyson, Mark (2025-08-14). "Firewire refuses to die, but needs help — as hardware becomes rarer, maintainer seeks volunteers for device testing". Tom's Hardware. Retrieved 2025-08-14.
  50. ^ "macOS Tahoe Beta Drops FireWire Support". MacRumors. 2025-08-14. Retrieved 2025-08-14.
  51. ^ Klotz, Aaron (2025-08-14). "Linux to Support Firewire Until 2029". Tom's Hardware. Retrieved 2025-08-14.
  52. ^ "page 145" (PDF). Archived from the original (PDF) on 2025-08-14. Retrieved 2025-08-14.
  53. ^ rcliff. "How-To: Mac OS X Firewire HDTV recording". AVS Forum. Retrieved 2025-08-14.
  54. ^ Requests for Waiver of Section 76.640(b)(4)(ii) of the Commission's Rules (PDF), Federal Communications Commission, 2025-08-14, retrieved 2025-08-14
  55. ^ "FCC Douses FireWire Requirement For Set-Tops With IP". Multichannel News. Retrieved 2025-08-14.
  56. ^ FireWire vs. USB 2.0 (PDF), Qimaging, archived from the original (PDF) on 2025-08-14, retrieved 2025-08-14
  57. ^ "firewirevsusb". Directron.com. Archived from the original on 2025-08-14. Retrieved 2025-08-14.
  58. ^ "IDB Forum Homepage". 2025-08-14. Archived from the original on 2025-08-14. Retrieved 2025-08-14.
  59. ^ "About HANA". Hanaalliance.org. Archived from the original on 2025-08-14. Retrieved 2025-08-14.
  60. ^ Mourn, Richard (2025-08-14). "IEEE-1394 and AS5643 bring deterministic networking to high reliability Mil-Aero designs". Retrieved 2025-08-14.
  61. ^ "AS5643: IEEE-1394b Interface Requirements for Military and Aerospace Vehicle Applications - SAE International". Retrieved 2025-08-14.
  62. ^ Mourn, Richard (2025-08-14). "UAVs leverage IEEE-1394b data buses for success". EE Times. Retrieved 2025-08-14.
  63. ^ "FreeBSD 7.1 fwip(4) man page". Freebsd.org. 2025-08-14. Retrieved 2025-08-14.
  64. ^ "Windows Millennium Edition (Me) Support for IP over IEEE 1394 Bus". Support.microsoft.com. 2025-08-14. Retrieved 2025-08-14.
  65. ^ "Using IEEE 1394 (FireWire) Devices with Windows XP". Support.microsoft.com. 2025-08-14. Retrieved 2025-08-14.
  66. ^ "Discontinued Support for IP over 1394". Microsoft.com. 2025-08-14. Retrieved 2025-08-14.
  67. ^ "IP networking over the IEEE 1394 bus is not supported in Windows Vista and in all later versions of Windows". Support.microsoft.com. 2025-08-14. Retrieved 2025-08-14.
  68. ^ "New Networking Features in Windows Server 2008, Windows Vista, and Windows 7". Technet.microsoft.com. Retrieved 2025-08-14.
  69. ^ "1394 Bus Driver in Windows 7". Microsoft.com. 2025-08-14. Retrieved 2025-08-14.
  70. ^ "ubCore 1394 Firewire drivers". Unibrain.com. Retrieved 2025-08-14.
  71. ^ "PS2 Model Differences". ConsoleMods Wiki.
  72. ^ "libdc1394: IIDC/DCAM specifications". Damien.douxchamps.net. Retrieved 2025-08-14.
  73. ^ "AV/C Overview". Microsoft Developer Network. Archived from the original on 2025-08-14. Retrieved 2025-08-14.
  74. ^ IEEE 1394a specification.
  75. ^ "How to Establish VGA to Firewire Connection". Epiphan.com. Retrieved 2025-08-14.
  76. ^ "iPod nano: Charging the battery". Retrieved 2025-08-14.
  77. ^ "Tool Physically Hacks Windows — Security/Vulnerabilities — DarkReading". DarkReading. Retrieved 2025-08-14.[permanent dead link]
  78. ^ "Blocking the SBP-2 Driver to Reduce 1394 DMA Threats to BitLocker". Microsoft. 2025-08-14. Retrieved 2025-08-14.
  79. ^ "Setting Up Kernel-Mode Debugging over a 1394 Cable Manually". docs.microsoft.com. 2025-08-14. Retrieved 2025-08-14.
  80. ^ "KD 1394 Work-Around". blogs.msdn.microsoft.com. 2025-08-14. Retrieved 2025-08-14.
  81. ^ "Andi Kleen: [ANNOUNCE] firescope for i386/x86-64 released". LKML. 2025-08-14. Retrieved 2025-08-14.
  82. ^ "Bernhard Kaindl's fireproxy forwards the gdb remote protocol to FireWire. It allows reading and writing remote memory by gdb". Ieee1394.wiki.kernel.org. 2025-08-14. Retrieved 2025-08-14.

Further reading

[edit]
  • INCITS T10 Project 1467D (2004). Information technology—Serial Bus Protocol 3 (SBP-3). ANSI INCITS. ANSI INCITS 375-2004.{{cite book}}: CS1 maint: numeric names: authors list (link)
  • Anderson, Don (1999). FireWire System Architecture. MindShare, Inc. ISBN 0-201-48535-4.
  • "IEEE Standard for a High-Performance Serial Bus". IEEE STD. 1394-2008. 2025-08-14. doi:10.1109/IEEESTD.2008.4659233. ISBN 978-0-7381-5771-9.
[edit]
什么叫银屑病 fy是什么意思 国窖1573是什么香型 什么的街道 痣是什么
吃太烫的东西有什么坏处 脸上长斑是因为什么原因引起的 四维是什么 肋间神经痛挂什么科 飘了是什么意思
每晚做梦是什么原因 有什么不能说 世界上最难写的字是什么 刺史相当于现在的什么官 不将就是什么意思
疤痕增生是什么引起的 吃什么能壮阳 去脂体重什么意思 黑色素通过什么排出来 闰月给父母买什么
金鱼可以和什么鱼混养0735v.com cro是什么意思hcv8jop7ns5r.cn 生意兴隆是什么生肖hcv9jop0ns3r.cn 失眠吃什么药最有效hcv9jop2ns7r.cn 什么病需要透析onlinewuye.com
杨柳是什么生肖hcv9jop6ns4r.cn 紫萱名字的含义是什么cj623037.com igg抗体阳性是什么意思hcv8jop2ns2r.cn 人情是什么意思hcv9jop7ns1r.cn 家用制氧机什么牌子好hcv8jop4ns7r.cn
爱吃酸的人是什么体质hcv9jop4ns3r.cn 打酱油是什么意思hcv8jop1ns9r.cn 割包皮属于什么科室hcv9jop1ns0r.cn 多梦是什么原因造成的hcv9jop2ns6r.cn 乙木的根是什么hcv8jop2ns3r.cn
茄子和什么相克cj623037.com 为什么放屁多hcv7jop6ns9r.cn 结婚12年是什么婚hcv9jop6ns5r.cn 薄谷开来为什么杀人hcv9jop3ns5r.cn 手脚发热是什么原因hcv9jop1ns9r.cn
百度