Submitting a review for consideration is easy; please first read Slashdot's book review guidelines. Updated: 2008114 by samzenpus
All trademarks and copyrights on this page are owned by their respective owners. Comments are owned by the Poster. The Rest © 1997-2009 Geeknet, Inc.
I think Apple.... (Score:4, Insightful)
Anyway, when apple calls it firewire2, then it'll get adopted.
Re: (Score:2)
I haven't found too much use for my FW800 port... I just hope that I can find a sweet external drive for the FW3200
Re:I think Apple.... (Score:5, Informative)
I've got a drive with USB 2.0, FW400, FW800, and eSATA connectors. (It's a LaCie "quadra," if anyone is interested.)
In terms of performance, that's pretty much the order, there -- USB is slow, despite it's claims of 480mbits/sec. FW800 and eSATA get me about 85MBytes/sec reading from the raw device; writing appears to be a bit slower, but that was going through the filesystem, so I'll do another test on a drive I don't mind wiping out :).
As with SCSI, the big advantage the faster FW speeds have is that you can have multiple devices chained. So you can have six or seven disks on the chain, and not worry about running out of bandwidth. eSATA doesn't give me that advantage.
Parent
Re: (Score:3, Interesting)
I have two older LaCie disks on a FW800 chain. They are the triple-interface version with FW400, USB2 and two FW800 ports. With FW800, I can plug both disks into a laptop at the same time with a single cable (there's another FW800 cable strung between the two) and get 30MB/s copying from one disk to the other (like I said, these disks are a few years old now). The lack of FW800 on the old MacBook Pros was the reason I delayed upgrading my PowerBook for so long.
FireWire is also a good way of adding an
Re: (Score:3, Informative)
Re: (Score:3, Informative)
Re: (Score:3, Informative)
Not only that but also USB networking requires special software. Linux/WinXP/2K/98 all do FW networking out of the box. Vista does NOT, however, so keep that in mind if you need it.
Re: (Score:3, Funny)
Re: (Score:3, Informative)
Re: (Score:3, Informative)
You're thinking of IEEE1394, which it still is. And Sony's iLink implementation was the unpowered 4-pin version of it.
Re: (Score:2)
Re: (Score:3, Funny)
Re: (Score:3, Insightful)
Betamax has also been the basis for ED Beta, the prosumer format nearly every TV crew uses and has used over the last two decades. Trying to create a black and while picture by dialing up t
Better yet.... 3.0 (Score:3, Interesting)
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
Re: (Score:3, Informative)
stupid tags (Score:5, Funny)
Re: (Score:2, Funny)
I would just like a single standard... (Score:4, Interesting)
Re: (Score:2)
Re:I would just like a single standard... (Score:5, Informative)
Parent
Re: (Score:2)
Re: (Score:2)
Re:I would just like a single standard... (Score:5, Interesting)
I've seen the same thing on my MacBook Pro with my external drive. FireWire 400 is maybe 25% faster, FireWire 800 is 50% faster (same drive). The big thing is CPU utilization though. Maxing out the disk on FireWire 800 is no problem. Very little CPU usage (maybe under 10%, this is based on a little graph, I've never looked at hard numbers). Running it over USB has a very noticeable CPU impact.
FireWire is great at what it was made for. USB is very good at what it was designed for (mice, keyboards) and weak at things it was forced to do (hard drives).
It's all Intel's fault. They put USB on everything, but didn't put FireWire on anything until very recently, if they even have by now. So USB "won".
Parent
Re: (Score:3, Informative)
If you really wanted to blame someone, you can at least partially blame Steve Jobs. Wikipedia [wikipedia.org] mentions that one of the reason Firewire wasn't as popular as USB was the high licensing and manufacturing costs compared to USB. (One of the IP owners is Apple). This gentleman [teener.com] mentions that just when Apple was going to give away licenses for a fairly cheap price (199
Re:I would just like a single standard... (Score:5, Informative)
The highest copy speed I have ever reached on FW400 is 32MB/s - limited by the ATA33-FW400 bridge chip (Oxford 911) while the highest speed I have ever seen with any combination of my USB2/480 external HDD boxes and PCs is 24MB/s with 18MB/s being more typical. Under the best circumstances, USB barely matches the SLOWEST speeds I take for granted on FW400. If I string two of my FireWire drives together and move data between the two boxes, I still get the same 24-30MB/s I am used to but if I try to do the same with USB2 and a hub, USB2 crawls at 8-10MB/s. In this scenario, FireWire is as much as 3X as fast as USB2.
With eSATA for external storage, USB3 (late 2008) for all sorts of high-bandwidth (4.8Gbps) devices and GbE for mainstream networking, FW3200 will become irrelevant soon enough: USB3 is supposed to be 4.8Gbps double-simplex fiber, blowing away FW3200 on raw speed and finally getting rid of USB1/2's half-duplex overhead.
Parent
Re: (Score:3, Informative)
I wouldn't assume that USB3 will do much at all. If it doesn't require a more intelligent bus controller to offload the work, it will be torture on the CPU at those speeds, and if it does, a lot of manufacturers will reject it because it costs too much more to build cards for it, and a lot of users will reject it because of the substantial extra expense of the cards compared with other technologies. Similarly, for external devices, cost will probably play a more important role in driving adoption than any
Re:I would just like a single standard... (Score:5, Informative)
Whereas 1394 is device-centric - designed for tranferring video, audio, data, etc. between "dumb" devices.
The PC world "snubbed" 1394 (not completely) because of the $.25(or something equally absurd) royalty to Apple; Intel pushed USB.
1394 is more expensive to implement in hardware (which should be obvious - it's for dumb devices!), while USB is cheap - the CPU does most of the work.
Parent
Re: (Score:2)
Re:I would just like a single standard... (Score:5, Informative)
Here are the technical specs for Firewire from Wiki:
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.
From the USB wiki:
USB was originally seen as a complement to FireWire (IEEE 1394), which was designed as a high-speed serial bus which could efficiently interconnect peripherals such as hard disks, audio interfaces, and video equipment. USB originally operated at a far lower data rate and used much simpler hardware, and was suitable for small peripherals such as keyboards and mice.
The most significant technical differences between FireWire and USB include the following:
* USB networks use a tiered-star topology, while FireWire networks use a repeater-based topology.
* USB uses a "speak-when-spoken-to" protocol; peripherals cannot communicate with the host unless the host specifically requests communication. A FireWire device can communicate with any other node at any time, subject to network conditions.
* A USB network relies on a single host at the top of the tree to control the network. In a FireWire network, any capable node can control the network.
These and other differences reflect the differing design goals of the two buses: USB was designed for simplicity and low cost, while FireWire was designed for high performance, particularly in time-sensitive applications such as audio and video. Although similar in theoretical maximum transfer rate, in real-world use, especially for high-bandwidth use such as external hard-drives, FireWire 400 generally has a significantly higher throughput than USB 2.0 Hi-Speed.[13][14][15][16] The newer FireWire 800 standard is twice as fast as FireWire 400 and outperforms USB 2.0 Hi-Speed both theoretically and practically.[17]
There are technical reasons why USB 2.0 devices cannot efficiently utilize all the available bandwidth. USB communication is based on polling the devices; there is no pipelining of commands. After sending a command to a device, the USB host must wait for a reply to the command before a new command can be sent to the same device. The bandwidth of a USB bus is divided by all devices connected to the bus. The USB host cannot send commands to one device while waiting for reply from another device. Since all communication is initiated by a USB host, the host must periodically poll all those USB devices that can provide data at unexpected intervals, such as network cards and keyboards. This consumes unnecessary resources when the devices are idle. These issues are being addressed by the forthcoming USB 3.0 specification, although it is not clear whether USB 3.0 is going to match FireWire in bandwidth efficiency.
Parent
Re:I would just like a single standard... (Score:5, Informative)
One of the big advantages FW has over USB is that a device can request, and get, a specific bandwidth. So, for example, a video camera can say, "I need to have 19mbits/sec." And if it can, then it'll get that -- and nothing on the bus will be able to take it away until it releases it.
When doing real-time applications such as video, this is pretty important.
Parent
Re: (Score:3, Informative)
Each device on a USB bus have to get equal bandwidth slices.
Re:I would just like a single standard... (Score:5, Interesting)
Firewire is fast and cost more.
So they both existed. One was good for mice and keyboards, one was good for digital video and external hard drives.
Then USB2 came out which is almost as fast as firewire, and the lines got blurry.
Firewire was still considerably better as a technology. It does a lot of its own processing while usb2 offloads a lot of processing to the host system... so firewire drives don't tie up the CPU the way a USB2 one does. Firewire supports more simultaneous devices, and seems to have fewer issues with power as well. It also doesn't have stupid rectangular connectors that users will try upside down 50% of the time.
Then Firewire 3200 was announced and santify was restored.
USB2 is slow and cheap.
"Firewire-3200" is fast and costs more.
Do we 'need' usb? no. We could get by on just firewire. But usb is cheaper and a penny saved is a penny earned.
Parent
Re: (Score:3, Insightful)
Yeah, but when you spread that across a million machines, you're talking real money.
Re: (Score:3, Insightful)
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, mi
Re: (Score:2)
Second, USB uses CPU. Firewire uses its own chip. (Which is why Apple removed the chip from the iPods, it wasn't going to fit with that and the video decoder in the same form factor).
USB is good because... there's no reason my mouse needs that much speed.
They're for completely d
Why still no optical link? (Score:2)
(I know, it's because that's not profitable enough for the manufacturers. They wouldn't be able to sell us new cables every 5 years)
Re: (Score:2, Informative)
Re: (Score:3, Informative)
compared to sata 3Gbps (Score:3, Informative)
Yeah -- so what? (Score:4, Interesting)
I've read a variety of posts about the problems with FireWire (see here [pcstats.com] and here [theappleblog.com] 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 [eetimes.com]. 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.
Re: (Score:3, Informative)
I've seen the mini firewire port on many notebooks. I think the problem with puting the six pin port in it is that it would allow the device to consume power and that's not necessarily desirable when everything has to be so small and allowing more power to power a high-draw FW device can be a problem.
I think eSATA is the replacement for Firewire in many of its previous niches other than video decks and camcorders. It
Does it matter? (Score:5, Interesting)
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.
Firewire chaining and networking (Score:3, Interesting)
Co-ax (Score:4, Funny)
Its like a VCR... (Score:4, Interesting)
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.
Re: (Score:3, Funny)
That analogy sucks even more than the sucky VHS/Beta analogy. Wait a minute, why are people trying to make analogies in this case, when there is no analogy needed?
Oh right, this is slashdot. I forgot that you need to reach your daily analogy quota. BMW vs. Chevy FTW!
Re: (Score:2)
Re: (Score:3, Interesting)
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 ab
Re: (Score:2)
I have two shells for some laptop drives. The older Firewire shell, with an ATA drive, is very reliable, feels as fast as the internal drive, and requires only one cord to run. My newer one is a USB sata shell -- two wires, the drive seems to get bogged down during large transfers, and it can be finicky about mounting. Sadly, when I went looking for a shell to put that sata drive in, I
USB is NOT good for webcams unless they're close. (Score:3, Interesting)
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-s