FireWire - Vev

FireWire

Un article de Vev.

Jump to: navigation, search

Modèle:Infobox Computer Hardware Bus

Image:FireWire-46 Diagram.svg
The 6-pin and 4-pin FireWire 400 Connectors
Image:Ethernet plug grey.svg
The alternative ethernet-style cabling used by 1394c

FireWire is Apple Inc.'s brand name for the IEEE 1394 interface (although the 1394 standard also defines a backplane interface). It is also known as i.LINK (Sony's name). It is a personal computer (and digital audio/digital video) serial bus interface standard, for high-speed communications and isochronous real-time data transfer. FireWire has replaced Parallel SCSI in many applications, due to lower implementation costs and a simplified, more adaptable cabling system. IEEE 1394 has been adopted as the High Definition Audio-Video Network Alliance (HANA) standard connection interface for A/V (audio/visual) component communication and control<ref>http://www.hanaalliance.org/docs/whitepaper121405.php</ref>. FireWire is also available in wireless, fiber optic, and coaxial versions using the isochronous protocols. Wireless FireWire is being integrated into the WiMedia Alliance's WiMedia Ultra-Wideband (UWB) standard.

Almost all modern digital camcorders have included this connection since 1995. Many computers intended for home or professional audio/video use have built-in FireWire ports, including all Apple and Sony laptop computers and most Dell and HP models currently produced. It is also widely available on retail motherboards for do-it-yourself PCs, alongside USB. FireWire was used with initial models of Apple's iPod, but later models eliminated FireWire support in favor of USB due to space constraints and for wider compatibility.

Sommaire

History and development

Image:FireWire cables.jpg
4-pin (left) and 6-pin (right) FireWire 400 connectors
Image:FireWire gniazdo.jpg
6-pin FireWire 400 connector on the edge of an expansion card

FireWire is Apple Inc.'s name for the IEEE 1394 High Speed Serial Bus. It was initiated by Apple and developed by the IEEE P1394 Working Group, largely driven by contributions from Apple, although major contributions were also made by engineers from Texas Instruments, Sony, Digital Equipment Corporation, IBM, and INMOS/SGS Thomson (now STMicroelectronics).

Apple intended FireWire to be a serial replacement for the parallel SCSI (Small Computer System Interface) bus while also providing connectivity for digital audio and video equipment. Apple's development was completed in 1995. As of 2007, IEEE 1394 is 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. Work is underway to incorporate all four of those documents into new revision of the 1394 standard.

Sony's implementation of the system is known as i.LINK, and uses only the four signal pins, omitting the two pins which provide power to the device in favor of a separate power connector on Sony's i.LINK products.

The system is commonly used for connection of data storage devices and DV (digital video) cameras, but is also popular in industrial systems for machine vision and professional audio systems. It is preferred over the more common USB for its greater effective speed and power distribution capabilities, and because it does not need a computer host. Perhaps more importantly, FireWire makes full use of all SCSI capabilities and, compared to USB 2.0 Hi-Speed, has higher sustained data transfer rates, especially on Apple Mac OS X (with more varied results on Windows, presumably since USB2 is Intel's answer to FireWire on Windows machines)<ref>http://www.usb-ware.com/firewire-vs-usb.htm</ref><ref>http://www.tomshardware.com/2004/04/02/go_external/</ref>, a feature especially important for audio and video editors.

However, the royalty which Apple Inc. and other patent holders have initially demanded from users of FireWire (US$0.25 per end-user system) and the more expensive hardware needed to implement it (US$1–$2) has prevented FireWire from displacing USB in low-end mass-market computer peripherals, where cost of product is a major constraint.<ref> a feature especially important for audio and video editors.

However, the royalty which Apple Inc. and other patent holders have initially demanded from users of FireWire (US$0.25 per end-user system) and the more expensive hardware needed to implement it (US$1–$2) has prevented FireWire from displacing USB in low-end mass-market computer peripherals, where cost of product is a major constraint.<ref>http://www.teener.com/</ref>

Technical specifications

FireWire can connect up to 63 peripherals in a tree topology (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 hosts per bus. It is designed to support Plug-and-play and hot swapping. Its six-wire cable is more flexible than most Parallel SCSI cables and can supply up to 45 watts of power per port at up to 30 volts, allowing moderate-consumption devices to operate without a separate power supply. (As noted earlier, the Sony-branded i.LINK usually omits the power wiring of the cables and uses a 4-pin connector. Devices have to get their power by other means.)

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 (an extension of the 48-bit Ethernet MAC address format) in addition to well-known codes indicating the type of device and the protocols it supports.

Operating system support

Full support for IEEE 1394a and 1394b is available for FreeBSD, Linux, Apple Mac OS 8.6 through to Mac OS 9, and Mac OS X<ref>http://docs.info.apple.com/article.html?artnum=86020</ref> as well as NetBSD and Haiku. Microsoft Windows XP supports both, but as of Service Pack 2, each FireWire device will run at S100 (100 Mbit/second) speed. A download is available from Microsoft which enables devices rated at S400 or S800 speeds to operate at their rated speed.<ref>http://support.microsoft.com/kb/885222</ref> Some FireWire hardware manufacturers also provide custom device drivers which replace the Microsoft OHCI host adapter driver stack, enabling S800-capable devices to run at full 800 Mbit/s transfer rates. Microsoft Windows Vista currently supports only 1394a, with 1394b support coming later in a service pack. (Vista SP1 RC1 is available from mid December 2007, with full release expected during Q1 200Image:Cool.gif<ref>http://www.eetimes.com/news/latest/showArticle.jhtml?articleID=187002039</ref>

Cable system support

Cable TV providers (in the US, with digital systems) must, upon request of a customer, provide a high-definition capable cable box with a functional FireWire interface. This applies only to customers leasing high-definition capable cable boxes from said cable provider after April 1, 2004. The relevant law is CFR 76.640 Section 4 Subsections i and ii.<ref>http://www.fcc.gov/mb/engineering/part76.pdf page 145 </ref> The interface can be used to display or record Cable TV, including HDTV programming.<ref>http://www.avsforum.com/avs-vb/printthread.php?t=386740</ref>

Node hierarchy

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 reset. The order in which the self-ids are assigned is equivalent to traversing the tree in a depth-first, post-order manner.

Standards and versions

FireWire 400 (IEEE 1394)

Image:Firewire6-pin.jpg
A 6-Pin FireWire 400 connector

FireWire 400 can transfer data between devices at 100, 200, or 400 Mbit/s 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 MBytes per second respectively). These different transfer modes are commonly referred to as S100, S200, and S400.

Cable length is limited to Modèle:Formatnum:4.5 metres ({{formatnum:{{rnd/+|4.5*1/0.3048|1|Modèle:Rnd/01}}}} ft), although up to 16 cables can be daisy chained using active repeaters, external hubs, or internal hubs often present in FireWire equipment. The S400 standard limits any configuration's maximum cable length to 72 meters. The 6-pin connector is commonly found on desktop computers, and can supply the connected device with power.

The 6-pin powered 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.<ref>http://developer.apple.com/documentation/HardwareDrivers/Conceptual/HWTech_FireWire/Articles/FireW_implementation.html#//apple_ref/doc/uid/TP40003892-SW1</ref> 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 9V and more likely about 12V.

Enhancements (IEEE 1394a)

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

1394a also standardized the 4 pin connector already widely in use. The 4-pin version is used on many consumer devices such as camcorders, some laptops and other small FireWire devices. Though fully data compatible with 6-pin interfaces, it lacks power connectors.

FireWire 800 (IEEE 1394b)

Image:Firewire800plug.jpg
A 9-pin FireWire 800/3200 (IEEE 1394b) connector.

FireWire 800 (Apple's name for the 9-pin "S800 bilingual" version of the IEEE 1394b standard) was introduced commercially by Apple in 2003. This newer 1394 specification (1394b) and corresponding products allow a transfer rate of 786.432 Mbit/s via a new encoding scheme termed beta mode. It is backwards compatibility to the slower rates and 6-pin connectors of FireWire 400. However, while the IEEE 1394a and IEEE 1394b standards are compatible, FireWire 800's connector is different from FireWire 400's connector, making the legacy cables incompatible. A bilingual cable allows the connection of older devices to the newer port.

The full IEEE 1394b specification supports data rates up to 3200 Mbit/s over beta-mode or optical connections up to 100 metres in length. Standard Category 5e unshielded twisted pair supports 100 metres at S100. The original 1394 and 1394a standards used data/strobe (D/S) encoding (called legacy mode) on the signal wires, while 1394b adds a data encoding scheme called 8B10B (also referred to as beta mode).

FireWire S3200

In December 2007, the 1394 Trade Association announced the products will soon be available using S3200 mode which was already (mostly) defined in 1394b. They will use the same 9-pin connectors as the existing FireWire 800 and will be fully compatible with existing S400 and S800 devices. The future products are intended to compete with the forthcoming USB 3.0.<ref name=S3200-pr> 1394 Trade Association Announces 3.2 Gigabit per Second Speed for FireWire

. 1394 Trade Association
 (2007-12-12)
   

. Retrieved on 2007-12-17. </ref>

FireWire S800T (IEEE 1394c)

Image:Cat5.jpg
FireWire is enhanced to share gigabit Category 5e cable

IEEE 1394c-2006 was published on June 8 2007.

It provides the following improvements

Though the potential for a combined Ethernet and FireWire RJ45 port is intriguing, as of December 2007, there are no products or chipsets which include this capability.

Future enhancements

Besides the short term shoring up of S3200 over the beta connector already discussed, future iterations of FireWire should bring a bump in speed to 6.4 Gb/s, use of single-mode fiber, and additional connectors such as the small multimedia interface.<ref> Baxter , Les



     (2007-11-01)
   
.    New developments in IEEE 1394 (a.k.a. FireWire) 
. Lightwave 
   

. Retrieved on 2007-12-19. </ref>

Comparison to USB

Although high-speed USB 2.0 runs at a higher signaling rate (480 Mbit/s) than FireWire 400, typical PC-hosts rarely exceed sustained transfers of 35 MB/s, with 30 MB/s being more typical (the theoretical limit for a USB 2 high-speed bulk transfer is 53.125 MB/s). This is likely due to USB's reliance on the host-processor to manage low-level USB protocol, whereas FireWire automates the same tasks in the interface hardware. For example, the FireWire host interface supports memory-mapped devices, which allows high-level protocols to run without loading the host CPU with interrupts and buffer-copy operations.<ref>http://www.usb-ware.com/firewire-vs-usb.htm</ref>

FireWire 800 is substantially faster than Hi-Speed USB.<ref> Heron, Robert




.    USB 2.0 Versus FireWire 
. TechTV 
   

. Retrieved on 2006-12-04. </ref>

Alternative Uses for IEEE 1394

Aircraft

IEEE 1394b is used in military aircraft, where weight savings are desired; even four pairs of wires, to permit multiple redundancy, are far lighter than hundreds of discrete wires. Developed for use as the data bus on the F-22 Raptor, it is also used on the F-35 Lightning II.<ref name="avweek_20070205">"The Electric Jet." Philips, E. H. Aviation Week & Space Technology. February 5, 2007.</ref> NASA's Space Shuttle also uses IEEE 1394b to monitor debris (foam, ice) which may hit the vehicle during launch.<ref name="avweek_20070205" /> This standard should not be confused with the unrelated MIL-STD-1394B.

Automobiles

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

Networking over FireWire

FireWire can be used for ad-hoc (terminals only, no routers) 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, FreeBSD, and Windows XP include support for networking over FireWire. 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, wire length, and the fact that standard FireWire cables can be used for point-to-point communication.

Note that this feature is not supported in Windows Vista.<ref>http://www.microsoft.com/whdc/system/bus/1394/IP_1394.mspx</ref>

The PlayStation 2 console had an i.LINK-branded 1394 connector. This was used for networking until the release of an Ethernet adapter late in the console's lifespan, but was poorly supported by software.

IIDC

IIDC (Instrumentation & Industrial Digital Camera) is the FireWire data format standard for live video, and what Apple's iSight A/V camera uses. The system was designed for machine vision systems,<ref>http://damien.douxchamps.net/ieee1394/libdc1394/iidc_specifications.php</ref> 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 ordinary DV (Digital Video) camcorder protocol.

DV

Main article: DV

Digital Video (DV) is a standard protocol used by nearly all digital camcorders. Nearly all DV cameras have a FireWire interface (usually a 4-pin). Labeling of the port varies by manufacturer, with Sony always using its i.LINK trademark. Many digital video recorders have a "DV-input" FireWire connector (usually a 6-pin connector) which can be used to record video from a directly-connected DV camcorder ("computer-free").

The protocol also allows remote control (play, rewind, etc.) of connected devices.

Security issues

Devices on a FireWire bus can communicate by direct memory access, 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.

On many implementations, particularly those like PCs and Macintoshes 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 risk if untrustworthy devices are attached to the bus. For this reason, high-security installations will typically either purchase newer machines which map a virtual memory space to the FireWire "Physical Memory Space" (such as a Power Macintosh G5, or any Sun workstation), disable the OHCI hardware mapping between FireWire and device memory, physically disable the entire FireWire interface, or do not have FireWire at all.

This feature can also be used to debug a machine whose operating system has crashed, and in some systems for remote-console operations. On FreeBSD, the dcons driver provides both, using gdb as debugger. Under Linux, firescope<ref>http://lkml.org/lkml/2006/4/3/301</ref> and fireproxy<ref>http://www.suse.de/~bk/firewire</ref> exist.

See also

References

<references />

Other Sources

</div>

External links

Modèle:FOLDOCbs:FireWire ca:FireWire cs:FireWire da:FireWire de:FireWire el:Firewire es:IEEE 1394 eo:IEEE 1394 eu:IEEE 1394 fr:FireWire gl:Firewire ko:IEEE 1394 hr:FireWire id:IEEE-1394 it:IEEE 1394 he:FireWire lb:Fire Wire lt:FireWire hu:FireWire nl:FireWire ja:IEEE 1394 no:FireWire pl:FireWire pt:FireWire ru:IEEE 1394 sq:FireWire simple:FireWire sk:FireWire fi:FireWire sv:Firewire th:ไฟร์ไวร์ tr:FireWire zh:IEEE 1394