FireWire Spec to Boost Data Speeds to 3.2 Gbps
Stony Stevenson writes "A new set of data transfer specs may reach new Firewire speed records. The new transfer version is called S3200 and builds on the earlier specification approved by the IEEE.' The technology will be able to use existing FireWire 800 cables and connectors while delivering a major boost in performance. The new spec also will let users interconnect various home-networking appliances via coax cable, linking HDTVs with set-top boxes, TVs, and computers in various rooms around a home or office. The new release enables the transmission of FireWire data over distances of more than 100 meters. Home entertainment centers are likely to be an early application.'"
will be the earliest application. Remember when this was like e1394, or if you're sony i.Link. Those names never got any momentum, and they didn't push it. Heck, sony isn't too good at pushing standards anyway. Beta? Mini Disk? Memory Stick? Blueray has a chance.
Anyway, when apple calls it firewire2, then it'll get adopted.
Do not meddle in the affairs of sysadmins, for they are subtle, and quick to anger.
what moron tagged a story about fire"wire" "wireless"?
thats right, I rarely use capitals. deal with it. but don't mistake my laziness for stupidity
Maybe it's just me, but I don't see why USB and Firewire need to exist. Maybe I'm naive and don't see where there are ad hoc benefits to both. I would like to see a unified standard. I have both on my machine, so there is no compatibility annoyance. I don't see competition benefiting either one really.
I got a catholic block.
this seems clearly aimed at providing a long reach version of sata at 3Gb/s (Gigabits not GigaBytes per second). Incidentally, too many people call the higher speed sata "SataII" which is somewhat incorrect - sataII means a whole slew of features over and above the first version say Sata IO Org. Note that 3Gbps means 3 x 10^9, not 3 x 1024^3.
I've read a variety of posts about the problems with FireWire (see here and here from what I found on Google), and the big problem is that FireWire didn't become a de facto standard seven or eight years ago when it was really needed. These days, it seems like few computers other than Macs ship with FireWire standard, and I've never seen a laptop in the wild outside of Macs with a six-pin FireWire 400 port, let alone 800.
I've heard this is chiefly due to Apple's initial intransigence regarding licensing; they demanded $1 per computer to use the "FireWire" name, making other device makers really angry. Considering how slim hardware margins are, no one was going to go for it. FireWire 400 is still technically superior to USB 2.0 in many ways, even today, but it's never reached the market penetration it needs, and now USB 2.0 is "good enough" for most purposes.
I use a Mac and so do many family members, and I've long counseled them to get only FireWire drives for backups. When Leopard came out, some were shopping for drives, and I found that I could not find FW400/USB 2 drives for as little as plain USB 2.0 drives. In other words, the FireWire premium for HDs appears to be at least $30. Not a good sign for market penetration.
Now FW 3200 is being discussed when FW 800 already seems dead on arrival in consumer land, and only supported to the limited extent it is by Apple. Not making it backwards compatible with FW400 was an idiotic decision that ensured whatever chance it had in the market was gone. In the meantime, eSATA and the like have come along and perhaps obviated the need for many FireWire applications altogether.
Actually, USB 3.0 will have optical connects (while retaining the metal connectors for USB 2.0 compatibility (the socket, not the cable).
That wasn't the real issue with USB 2.0 anyways. The real issue is that USB 2.0 was suited for burst data transfers (where you got the theoretical speed), but simply can't do streaming at the maximum speed due to the enormous overhead of the protocol.
With that said, CPU utilization will indeed be a HUGE concern since USB 3.0 is so fast. The relatively minor CPU overhead of USB 2.0 will give way to CPU stalling overhead unless USB 3.0 addresses it. There's not enough information to make a statement about this, so we'll have to wait for more information to be released.
Vista's firewire implementation is the pits. I think TI spec controllers basically didn't work at all even though the cards were recognized (maybe it was the other spec). MS recently released a hotfix that remedied some of the problems, but the controllers were then only working up to 100mbps and not 400 even with registry settings set to 400. Getting 12MB/s to an external hard disk instead of 48MB is pretty ghetto.
Also, MS recently released a technote saying that IP over Firewire wasn't an oversight in Vista. It is a feature that will never be re-implemented.
The 800lb gorilla has left the building and I don't think Linux and OSX computers will be enough to keep the market for firewire devices robust except.
Never overestimate the end user. -jeramy b. smith
Finally I can use all the 10 Base 2 crap which I squierelled away. I guess I'll have to disassemble the model Eiffel tower I made out of left over T pieces.
SJW n. One who posts facts.
USB = VHS
USB 2.0 = Super VHS
FireWire = Beta - technically superior but doomed due to lack of marketplace penetration.
Seems to me that the iPod was the first real killer Firewire app for the masses (yeah, video and audio pro's had their own killer apps for Firewire, but they didn't represent enough of the marketplace for that to matter. If Apple had kept the iPod's Firewire only devices (as were the first generations) something would have had to give. Either the iPod would have been DOA (in the PC world at least, since every new Mac has had at least one Firewire port for years), or PC manufacturers would have been forced to start making Firewire the standard due to demand.
Understanding is a three edged sword. - Ambassador Kosh Naranek, Babylon 5
The 1394 spec has included an option for fibre for a while. There used to be a nice graph on the Apple site showing the different lengths you could use (I think you got something like 1000 metres with optical FireWire). As far as I know, no one has implemented the fibre version in consumer devices.
I am TheRaven on Soylent News
Why would I pay $100 for an HDMI cable to connect a Blu-ray/HD-DVD to my HDTV when I could use a $4 coax cable instead! PLUS, you can send the signal over 100 meters... with any hope, there will be splitters so that I can send a movie/broadcast from my cable providers set-top box to EVERY tv in my entire house.
Step away from your PC a moment and consider the possibilities this brings to the Home Entertainment industry!
programming myself into obsolescence
Technically it is 3.0. 400 is 1.0 and 800 is 2.0, if you were to renumber retrospectively.
Geeks get the 400 vs 800 reference, but I think nongeeks get it completely. Sure 400 is not as good as 800, but what does that mean compared to USB?
USB is 1.0 and 2.0. Firewire should be 1.0, 2.0 and 3.0. Why? Because the general masses see version digits as newer = better. USB is only on 2.0? But Firewire is on 3.0? Gee, that must mean Firewire is more advanced!
Geeks know better, but you don't tell only to the geeks, do you? Besides, versioning for the geeks just makes it easier to support.
"All great wisdom is contained in .signature files"
Firewire 400 cards are like $10. which is pretty much what a USB2 card costs although you don't need a USB2 card since every PC has one built-in now, so you can call it $0.
When I said a penny saved is a penny earned I was serious.
Firewire maybe less than a dollar more expensive per port than USB, but it adds up. And the bean counters designing hardware care about the pennies.
Not too mention we couldn't cut over to pure firewire even if wanted to. Firewire versions of low bandwidth devices like keyboards, mice, etc simply don't exist...
This could be interesting because there's already an extension (1394c) that allows for FireWire to be transported over Cat5e cable (and co-exist with Ethernet).
I'm curious to know if the new 3.2 Gbps document allows for Cat5e, or whether you can only use it over the FW800 cables.
This may sound like a stupid question, but why would we see the implementation of the new Firewire spec in HDTVs when we already have HDMI using equivalent or greater bandwidth? Would it not be just as likely to see HDMI ports appearing in PCs for connections to HDTV and AV equipment? Thanks
USB is great for small devices -- thumb drives, mice, webcams and such --
I beg to differ.
I wired my new (2001) house with a couple runs of cat-5E from the comp room to each corner, expecting inexpensive single-chip cameras to become available to be used for security cams.
Well they became available, all right. But all the cheap ones were USB, not Ethernet, and USB has a distance limit suitable for a workstation's desk rather than a house.
If it was just an electrical issue I could have built suitable level-shifters, baluns, etc. to extend the reach. But the limit is apparently timing of the poll/response rather than just signal integrity, so I'm hosed.
In fairness:
- There are ethernet webcams - but they're not cheap.
- There are active USB extenders to bridge USB to cat-5/5e and back for long runs - but they cost more than the cameras and I'd need one for each corner.
- I haven't had the spare round-TUITs to look into whether the timing issue is programmable in the driver or hardwired into the chips...
Bantam Dominique roosters crow a four-note song. Once you've heard it as "Happy BIRTHday" you can't NOT hear it that way
I chained my PCs and external harddrives together using firewire, XP automatically recognised it as a potential network connection and gave me "LAN over firewire". Whichever PC was switched on first "got" the peripherals, and the second one got to share them over the network. No LAN cables involved, and no hubs. I also included a redundant connection to make a complete circuit, so that even if only one PC was powered up, whichever one it was could still access all the peripherals directly with no replugging. You can't do that with USB!
Eric Baird