I know most are suppliers on the component end, but the one that got my attention is Hon Hai Precision, which is a major end-product manufacturer.Most of those are parts suppliers not peripheral vendors. Namely mostly optical transceiver vendors. Frankly the laser needed for 10G ethernet or infinband isn't all that different than light peak. electrical 1's and 0's come in and light goes out or light comes in and 1's and 0's go out. That is not a protocol controller. Where are the multiple implementors of the protocol controller ? ( this was a dust up with USB 3.0 also where Intel wanted to ship before anyone else had a chance to implement the standard)
Specifically the volume of OEM/ODM work they do for other major vendors (Apple and HP for example). The Foxconn label they produce as on their own, will only get Intel so far. I see the ability to use the OEM/ODM supplier as a means of persuading other vendors to take the plunge, whether installed on the main board products they sell to these vendors, or as an add-on card they'd supply as an optional product for those systems.
I figured this aspect was covered before in a previous post. At any rate, there are potential problems (that I do think will surface, but not sure to the degree yet, as there's still voids in the available information). Namely the supporting semiconductors necessary to make anything work with it becoming available, save connecting 2x LP equipped systems together, as was done in the demo.Likewise vendors who are actually going to put parts in their devices that end users will buy. Unless end users buy complete devices to plug in it is not going anywhere. If end users are going to buy dongles that's going to limit adoption. I know Apple likes selling dongles but mini-display isn't exactly taking the market by storm.
USB 3.0 does have the advantage here, as it's already backwards compatible with devices users already own. For the newer standard, the necessary parts already exist, so it's not a situation of Part A is there, but B is vapor = useless for most, if not all practical purposes.
There's definitely a difference between a standard that began as an open standard (or became that shortly after it was created), and one that has it's IP held by a company or group of companies.Flash is a standard by that criteria. A real open standard is where there are multiple implementors. As long as there is just one implementor of the controller it isn't very standard. One of the short term limitations on USB 3.0 was that only NEC managed to get something working at first. There are other implementors coming online now.
LP's not based on an open standard, so the companies involved would have to agree to do so before any other parts suppliers could get involved without a licensing fee. Unlike NEC, where it was, and they were just the first out with a working part. Others are following, but no license fees are involved.
No, but they were pushing it hard, and are what most consumers associate with it (I was trying to keep the example simple, as the posts are getting long). Few may actually realize that others such as Panasonic were ever involved with it from the beginning.Sony isn't the only implementor of BR. Nor is there just one controller for the whole market.
Money indeed. It was a good move, as there's fewer separate assemblies between the SP and DP systems. Shortens the parts bin requirements for easier production, and more importantly, saves costs.Second, with Apple's decoupling the PCI planes from the CPU package sockets and high speed PCI controller means they can change PCB with zero impact on the sockets. Still will save money to run for two years with minor tweaks. However, money not socket implementation is driving that.
Typing too fast. Not much different than typing MB/s instead of Mb/s mistake.Eh? Tock is the "shrink with same socket" phase.
Other standards are entrenched, and won't be easily moved. I actually see LP making the largest impact on laptop systems as a means of simplification combined with a cost reduction.To me it makes more sense to build into the motherboard a tech that has the more widespread set of devices. The number of USB 3.0 devices is going to greatly outnumber the number of LP ones. The exception would be two boxes need to snap together ( laptop with docking station). Unless there is going to be some lego block change to the MP, just don't see it as pressing.
For desktop systems, not as much. There would need to be some other reason, namely inexpensive speed, to cause them to go get the necessary pieces to make it all work (assuming they actually show up, as this late in the game, as none of the peripheral components have been announced that I've seen).
Workstations I hope will benefit by being able to exceed 1G E for example, for at most, similar funds. It would assist in the creation of small lower cost clusters IMO if this proves itself out (i.e makes clusters more available to independents or SMB markets that could utilize that much performance).
I actually agree here, and do suspect it's that simple, as they've been silent on those details.I don't buy that. There has to be a protocol. It may be a simple one just oriented to transport data packets from one machine to another with some simple QoS/isochronous abilities, but there has to be something.
What I expect, is that they differentiate this from other standards (much more complex).
I know that they make NIC's, and they'd have labs with the necessary equipment for validation testing.I meant Intel makes actual Ethernet NICs ("Ethernet connectors"). I wasn't talking about making RJ-45 jacks or PHY implementations. They should have labs with lasers , fiber cabling , etc. to test those devices since part of the products.
But that can be bought. I think of it this way. Why build a scope, frequency generator, .... when companies like Tektronix, Agilent and Lecroy already product it?
Lasers, fibre optics, ... are areas their partners specialize in. IIRC, there's a significant amount of work put into the lasers,..., namely to get the materials and manufacturing in at a low cost.
I previously mentioned that the ability to bond is a hoped for speculation that could allow it be used for more than just a way to simplify laptop connectors.So now the "so lightweight you can't notice it" protocol supports bonded ports. I'm not holding my breath.
Assuming Intel and their partners are willing to license them the technology.I think there is amble opportunity for Ethernet and Infiniband to adopt the laser transceivers and wider fiber cable to lower adapter costs. Optical connectors don't have to be crazy high in price.
But they are slow at it, as it's expensive (time consuming as it's almost certainly a major re-write). Those that haven't done it seem to be waiting for someone else to do most of the work for them (i.e. waiting for tools, OS support,...). Basically just adding new features to the same old, tired base code that's been recycled for years (finding ways of milking the product with as little development time as possible).But it is increasing an old, tired excuse at this point. The Mac Pro in 2006 had 4 cores. Any app that can't go 4-way in some sections now are slackers in the Pro space. It has been 4 fraking years. That's going to include a major upgrade cycle for all but most glacially slow development. Some iMacs can go 4-way. A decent chance all iMacs could be 4-way by end of this Fall ( unless Apple sticks 2core/IGP into the lower end.)
It sucks, but I don't see anything motivating most software developers that've been sitting on the fence, to get off and go to work.
It was just to illustrate a point in general. Yes, multiple instances of the same application or simultaneous use of multiple applications can make better use of a system. But that won't change the fact if it can't benefit from SMP, which is what the MP and XServe are really meant for (where the performance will really become apparent).It is relatively easy to start more than one program at a time. Even more so where there are ones that "do something" and don't require user interaction. For Apps that primarily sit and wait for the user actively do something .... often don't really need a MP. That isn't the MP's problem, nor should it particularly be a constraint on MP's design criteria.