Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror
×
Upgrades Input Devices Hardware

USB 3.0's New Jacks and Sockets 390

The Register has a brief look posted (with photos and diagrams) of "USB 3.0, the upcoming version of the universal add-on standard re-engineered for the HD era, made a small appearance at the Consumer Electronics Show (CES)." The posting explains that USB 3.0 "wasn't demonstrated in operation, but we did get to see what the new connectors look like." How does it handle backward compatibility? The extra pins needed for USB 3.0 "are placed behind the USB 1.1/2.0 ones. USB 3.0 connectors and receptacles will be deeper than the current ones."
This discussion has been archived. No new comments can be posted.

USB 3.0's New Jacks and Sockets

Comments Filter:
  • Is it burst speed? (Score:5, Interesting)

    by danomac ( 1032160 ) * on Wednesday January 09, 2008 @06:51PM (#21976072)
    I wonder about the new speed specification... in my experience even with no other devices on the USB bus getting 480mbit was impossible. I always had to resort to firewire for my drive caddy because I got consistent results with it.

    I sure hope they've addressed this issue. The OS caching helped, unless you wanted to unplug the damn thing right away - then you had to wait 5 minutes for the cache to flush out.
  • by Marcion ( 876801 ) on Wednesday January 09, 2008 @06:54PM (#21976132) Homepage Journal
    Is the software side of USB an open specification or some members only, pass the royalty thing that the open source world will have to take the next ten years reverse engineering?
  • by Kickboy12 ( 913888 ) on Wednesday January 09, 2008 @07:01PM (#21976226) Homepage
    Funny how I just upgraded to a new computer that uses SATA 3.0Gb/s. If USB3 is faster than SATAII, then why not just use that for drives? Not that anyone ever really maxes out SATAII to begin with. So it's all kind of useless in the end.
  • by johnrpenner ( 40054 ) on Wednesday January 09, 2008 @07:08PM (#21976356) Homepage

    the more things change, the more they stay the same -- now
    they're back to using 9 pins to implement the spec -- other than
    making the connectors physically different so people don't end up
    plugging in old RS-422 cables into it -- from the number of actual
    pins needed to implement a spec -- we're physically back to using
    9 pins that were available in the DB9 form factor, only this connector
    is considerably more difficult to manufacture. :-^

  • A serious question (Score:5, Interesting)

    by moosesocks ( 264553 ) on Wednesday January 09, 2008 @07:17PM (#21976468) Homepage
    What happened to firewire? All signs point to it going extinct in the very near future....

    Wasn't it vastly superior to USB? It had a higher maximum throughput that could almost be realistically achieved, delivered useful amounts of power over the bus, and allowed devices to talk to each other. The audio/video features are pretty nice as well....

    Both firewire and usb were well-supported on all platforms, so *that*'s not the issue. It's also robust, to the point of being found in many modern aircraft designs and the space shuttle.

    IEEE1394c is even cooler, and uses CAT5e/RJ45 for wiring, allowing for automatic negotiation between other 1394 devices, and normal ethernet devices. Max speed is 800mbps, and it very nicely bridges the gap between "traditional" peripherals, and network-attached devices.

    So what happened? Did I miss something? Who killed Firewire?
  • And it doesn't work (Score:5, Interesting)

    by SuperKendall ( 25149 ) on Wednesday January 09, 2008 @07:24PM (#21976600)
    I bought a USB OTG external hard drive that is supposed to be able to copy files off a slave device, and a box that is supposed to support two master devices and initiate copies between them - neither work at all with any USB storage I have tried.

    USB OTG is a farce.
  • by Lumpy ( 12016 ) on Wednesday January 09, 2008 @07:36PM (#21976776) Homepage
    Going extinct? huh?? I dont see any pro cameras ditching firewire for usb.

    I see sata taking over for external hard drives. I converted all my firewire 800 external drives on my powermac tower to SATA 3 drives last year and gained a crapload of performance at 1/3rd the price. but every HD camcorder that is more than a toy for the masses has firewire on it and will be there forever. Even the hard drive based cameras from panasonic that cost more than most guys' houses still have firewire on them.

    Problem is SATA has a failure point. I can have 20 foot firewire cables.. good luck making sata work over 3 feet.

  • Patents killed it (Score:3, Interesting)

    by lennier ( 44736 ) on Wednesday January 09, 2008 @08:28PM (#21977502) Homepage
    "So what happened? Did I miss something? Who killed Firewire?"

    Patent royalties, I believe, or at least that's the popular impression: this guy [teener.com] seems to be saying that Steve Jobs attempted to hike the royalty price and though he wasn't ultimately successful, perhaps the mere suggestion that he could was enough to sour third party implementors and move them to USB.

    Like with Token Ring vs Ethernet and Objective-C vs C++, the answer seems to be that if there's a nearly-almost-good-enough open technology and a way-cool but closed/expensive technology fighting for the same market with no network effects yet in place, the open (at least in terms of free-to-implement) one wins.

  • by vectra14 ( 470008 ) on Wednesday January 09, 2008 @08:41PM (#21977668)
    Too bad they're adding the 5 new pins (given, 1 of them is in theory good old GND but still). As an EE, the one thing I liked about USB over Firewire is its physical simplicity... power, ground, and a differential bus. With 1394c heading towards RJ45 it's like USB and 1394 have traded places in terms of physical convenience (I'm sure a number of people have had the pleasure of dealing with ultra-over-engineered (and consequently overpriced) 1394a/b cables and repeaters.. oh the repeaters).

    ..Not like the host-heavy USB stack made it a much-liked protocol for me in the first place.

  • by Jeffrey Baker ( 6191 ) on Wednesday January 09, 2008 @08:53PM (#21977806)
    This is the stupidest and most-wrong, and also the most commonly believed, reason for FireWire's relative obscurity. Sure, there was a royalty for the FireWire name, but that hardly mattered in the great scheme of things. Early FireWire ASICs cost $50. Even today, a FireWire interface will set you back $20. USB interfaces are in the vicinity of $1. On top of that, your device must implement a complicated peer-to-peer software protocol. This costs even more. So the $1 royalty was only a tiny part of FireWire's overall higher cost.

    If you want to find out exactly how complicated the FireWire protocol is, just look in the Linux kernel. The 1394 subsystem is a huge piece of code, and it's also by far the lowest quality of all the major subsystems. Compare to the USB subsystem, which works perfectly.
  • by MMC Monster ( 602931 ) on Wednesday January 09, 2008 @09:37PM (#21978292)
    Seriously annoying. Is it that difficult to have (name your distribution here) Linux do an automatic sync every couple seconds when a USB drive is connected.

    Waiting 2 minutes to unmount without any progress meter is just broken UI design.
  • But... (Score:4, Interesting)

    by Junta ( 36770 ) on Wednesday January 09, 2008 @10:09PM (#21978640)
    syncing every few seconds isn't the good 'fix'. Using mount -o sync on obviously transient mounts would be the 'fix' to the problem described. If you sync ever so often, there *still* is no good way to track it/indicate it, while the fs being mounted with sync means the file write operation itself can be tracked more accurately.

    Of course, the line to draw at what is 'obviously' transient may be hard, but I think 4GB and under and USB connected is a good rule of thumb today of transient sticks vs. persistantly attached usb storage. When you get into the realm of 'guessing' the intent of the user implicitly, things get hairy.
  • by vectra14 ( 470008 ) on Thursday January 10, 2008 @12:49AM (#21980006)
    I haven't seen the 3.0 spec but from the diagrams in TFA it seems that the 5 new pins do the following:

    1 pin (middle) - ground (I suspect that with the higher bandwidth they're adding a signal ground separate from the already existing shared signal/power ground. this may be completely false).
    2 pins (probably differential twisted pair) - "USB3_TX" - is USB3 departing from the shared-differential-bus setup?
    2 pins (also probably a diff. TP) - "USB3_RX"

    USB1/2 was somewhat special in contrast to Ethernet or IEEE1394 in that it used a single bus and everyone connected to it had to figure out how to share it (each device in turn takes control of the data lines when it needs to transmit). It looks like USB3 is changing this a bit (makes sense for higher bandwidth - the taking control of/releasing the data lines wasted precious data line cycles and makes the interface hardware/firmware/software do extra work). From the RX/TX markings it would seem that for two devices sharing a cable, one TP will always be driven by one device and the other by the other device. However from the little I know about the USB1/2 spec this doesn't make too much sense (currently the USB host has to poll a peripheral for it to transmit any data back the the host), so I'll be looking forward to hearing the details.

    If the above guess is right then I'd expect to see a much more advanced family of USB controllers than the current (quite straight-forward) iteration. Maybe USB3 will be significantly changing the USB topology and becoming more like Firewire.. it seems somewhat logical.. who knows.
  • by zobier ( 585066 ) <.zobier. .at. .zobier.net.> on Thursday January 10, 2008 @01:13AM (#21980204)

    Really the only way of dealing with this perfectly is making the media impossible to disconnect until the filesystem is dismounted orderly. This can be done with CD and tape drives, but isn't going to work with anything connected to an USB port.
    It could do if you wanted it to, there's these two little holes on the USB connector that a latch could engage during transfer.

All the simple programs have been written.

Working...