Talk:IEEE 1394

Possible original research
"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"

This is unsupported by a reference and the rest of the paragraph implies that the standard is used for aircraft controls by linking the ability for isochronous communications in IEEE 1394 with the general use of isochronous communications in aircraft systems.

Now, I have no idea whether aircraft use 1394 to perform these types of communications, but the article does not cite a suitable reference to support this.

194.74.130.171 (talk) 12:55, 24 July 2017 (UTC)

Superceding SCSI - NOT
The article claims that IEEE 1394 is the successor to Parallel SCSI. It is not. SAS and SATA are the successors, especially in the largest-volume markets for storage devices: those of desktop PCs and servers (which also use FC). The claim might be true in the Apple universe, where Apple just had to make it the successor. It will be difficult to find market share (of actual satellite devices) in numbers and currency after such a long time. The numbers for computers with IEEE 1394 ports cannot reflect actual usage, so numbers for devices with only IEEE 1394 will be most useful. For now, I have only inserted notes on missing sources. I also have to provide some for my claims. ;-) --92.211.192.188 (talk) 01:41, 1 September 2017 (UTC)

External links modified
Hello fellow Wikipedians,

I have just modified 6 external links on IEEE 1394. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
 * Added archive https://web.archive.org/web/20120415064551/http://bio.research.ucsc.edu/people/feldheim/MouseEyeTracker/NI-IMAQ%203.1.3/patents.txt to http://bio.research.ucsc.edu/people/feldheim/MouseEyeTracker/NI-IMAQ%203.1.3/patents.txt
 * Added archive https://web.archive.org/web/20111104134827/http://www.1394ta.org/about/Bylaws.html to http://www.1394ta.org/about/Bylaws.html
 * Added archive https://web.archive.org/web/20080517132445/http://technet2.microsoft.com/WindowsVista/en/library/005f921e-f706-401e-abb5-eec42ea0a03e1033.mspx to http://technet2.microsoft.com/WindowsVista/en/library/005f921e-f706-401e-abb5-eec42ea0a03e1033.mspx
 * Added archive https://web.archive.org/web/20080430041438/http://technet2.microsoft.com/WindowsVista/en/library/37f23bde-283a-4341-9a8a-ca6eb86ac8a41033.mspx to http://technet2.microsoft.com/WindowsVista/en/library/37f23bde-283a-4341-9a8a-ca6eb86ac8a41033.mspx
 * Added archive https://web.archive.org/web/20080511195551/http://technet2.microsoft.com/WindowsVista/en/library/20184cb6-7038-4e82-a32c-4bc10ffe56ab1033.mspx to http://technet2.microsoft.com/WindowsVista/en/library/20184cb6-7038-4e82-a32c-4bc10ffe56ab1033.mspx
 * Added archive https://web.archive.org/web/20100129032343/http://www.hanaalliance.org/docs/whitepaper121405.php to http://www.hanaalliance.org/docs/whitepaper121405.php

When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.

Cheers.— InternetArchiveBot  (Report bug) 03:27, 10 November 2017 (UTC)

9-pin cable
I've got a picture of a 1394b cable with 9 pins. I don't see a good place for it in the document, should I include it somewhere? If so, where? McKay (talk) 21:19, 26 February 2019 (UTC)
 * It looks a lot like the picture on the right FireWire800 Stecker.jpeg, except there's 9 holes in the center block.McKay (talk) 21:22, 26 February 2019 (UTC)


 * That's the same connector. The holes are just exposed contact spring holes, the contacts themselves are on top of and below the center block. --Zac67 (talk) 21:38, 26 February 2019 (UTC)

Requested move 24 March 2022

 * The following is a closed discussion of a requested move. Please do not modify it. Subsequent comments should be made in a new section on the talk page. Editors desiring to contest the closing decision should consider a move review after discussing it on the closer's talk page. No further edits should be made to this discussion. 

The result of the move request was: not moved   Calidum  16:13, 28 April 2022 (UTC)

IEEE 1394 → FireWire – Is the name Firewire not commonly used outside of Apple spheres? Is the numerical identifier that much more widespread in common use? —151.132.206.250 (talk) 18:53, 14 December 2021 (UTC)  (move proposed 15:37, 24 March 2022 (UTC))  — Relisting. 🐶 EpicPupper (he/him &#124; talk) 07:06, 9 April 2022 (UTC)


 * FWIW here's the ngram. ~Kvng (talk) 15:22, 18 December 2021 (UTC)
 * Afraid the linked Ngram search only covers lowercase. Here's a corrected link. FireWire appears approximately four times more frequently than the IEEE designation throughout the corpus, and i.LINK barely at all. —151.132.206.250 (talk) 00:10, 25 January 2022 (UTC)

PAGE ]]) 19:06, 3 April 2022 (UTC) PAGE ]]) 20:19, 5 April 2022 (UTC)
 * Support FireWire was the WP:COMMONNAME while it was in use, although I believe it is pretty much dead now. ᴢxᴄᴠʙɴᴍ (ᴛ) 07:57, 25 March 2022 (UTC)
 * Oppose Apple developed it but the name Firewire was only used for Apple products. Just like the i.Link was only used by Sony and Lynx was only used by Texas Instruments.  Stepho  talk 11:57, 25 March 2022 (UTC)
 * What was it called when found on, say, Dell computers? FWIW a quick Google search seems to imply that FireWire was still used five times more often than IEEE-1394. —151.132.206.250 (talk) 16:49, 28 March 2022 (UTC)
 * Based on this archived page from 2010, or this one from 2008, IEEE 1394 or 1394a. --Ahecht ([[User talk:Ahecht|TALK
 * I meant more along the lines of what users or the media called it when referring to off-brand use. Seems dubious to treat technical specs as common use. Like, did Dell support forums have talk of FireWire devices, or did HP laptop reviewers tout its i.LINK support? Or did they avoid brand names when not discussing those brands? —151.132.206.250 (talk) 17:59, 5 April 2022 (UTC) (edited 20:04, 5 April 2022 (UTC))
 * In that case, yes, some reviews did refer to it as FireWire. See https://www.cnet.com/reviews/dell-studio-15-review/ or https://www.laptopmag.com/reviews/laptops/dell-studio-15-1558 for examples. --Ahecht ([[User talk:Ahecht|TALK
 * Oppose - The article is about more than the Apple implementation so the IEEE 1394 title is a better fit. Though IEEE 1394 was used less often and is less snappy, it is sufficiently recognizable so as not to WP:ASTONISH readers. ~Kvng (talk) 19:13, 25 March 2022 (UTC)
 * Note: WikiProject Computing has been notified of this discussion. 🐶 EpicPupper (he/him &#124; talk) 07:07, 9 April 2022 (UTC)


 * Weak oppose. IEEE 1394 is a clearer term when discussing the standard as a whole, as "FireWire" is indeed Apple's name for the product and generally only is used to refer to the 400/800 implementations of it and not more recent specs. In its heyday, many manufacturers seemingly avoided use of the FireWire name if they could avoid it. That all being said, the term remains the common name of the standard as originally implemented. I think I prefer the present state -- that FireWire redirects to this page, and the terms "FireWire," "i.Link," and "Lynx" are all in bold in the leading paragraph. - - mathmitch7 (talk/contribs) 18:59, 14 April 2022 (UTC)
 * Comment Worth noting that this article apparently was previously called "FireWire" and a 2006 RM proposal to move it away from that name was roundly rejected on commonname grounds. It was subsequently boldly moved in 2008. Colin M (talk) 19:11, 16 April 2022 (UTC)