I might misremember. But I thought PCISIG dragged their arse. Intel and Samsung both saw the need for a more sensible form factor for enterprise. Intel developped the ruler. Samsung their edsff. PCISIG ended up endorsing Intels solution. Leaving Samsung out in the cold with their own solution already advanced far.
Here is the thing PCI-SIG pretty much knew what Samsung was up to with their improved hardware and yet they went a head and designed M.2 v1.2 to have conflicts with Samsung's design and are now claiming that Samsung's design is going to cause problems with the upcoming M.2 v1.2 pin out. Here is a thought to PCI-SIG with you fully knowing Samsung's improved design why did you just go ahead and design M.2 v1.2 the way you did I am going to say no it is not Samsung that has the problem but it is you PCI-SIG that has the problem and need to make changes where changes need to be done to your own design.
What? M.2 is their standard. They left out unused pins so THEY THEMSELVES can use later on. Just because someone else took their spec and modified it doesn't meant they have to then follow Samsung's spec.
This is a cute Orwellian spin, but Samsung is really the one at fault for building a proprietary extension atop a standard, rather than going through the PCI SIG.
I'm pretty sure Samsung could've at least negotiated a provisional draft of what they wanted, even if they couldn't get the PCI SIG to ratify their extension in time to suit their market window.
Samsung probably noticed that these standards & naming schemes are headache inducing and very slow in making any progress, so they did there own thing.
We’ve updated our terms. By continuing to use the site and/or by logging into your account, you agree to the Site’s updated Terms of Use and Privacy Policy.
16 Comments
Back to Article
iwod - Friday, November 16, 2018 - link
Any reason why Samsung doesn't adopt the open EDSFF standards other than NIH syndrome?remosito - Friday, November 16, 2018 - link
I might misremember. But I thought PCISIG dragged their arse. Intel and Samsung both saw the need for a more sensible form factor for enterprise. Intel developped the ruler. Samsung their edsff. PCISIG ended up endorsing Intels solution. Leaving Samsung out in the cold with their own solution already advanced far.Billy Tallis - Friday, November 16, 2018 - link
I'm not sure that PCI-SIG has endorsed EDSFF in any official way. The EDSFF standards are published by SFF (now part of SNIA).rocky12345 - Friday, November 16, 2018 - link
Here is the thing PCI-SIG pretty much knew what Samsung was up to with their improved hardware and yet they went a head and designed M.2 v1.2 to have conflicts with Samsung's design and are now claiming that Samsung's design is going to cause problems with the upcoming M.2 v1.2 pin out. Here is a thought to PCI-SIG with you fully knowing Samsung's improved design why did you just go ahead and design M.2 v1.2 the way you did I am going to say no it is not Samsung that has the problem but it is you PCI-SIG that has the problem and need to make changes where changes need to be done to your own design.Gasaraki88 - Friday, November 16, 2018 - link
What? M.2 is their standard. They left out unused pins so THEY THEMSELVES can use later on. Just because someone else took their spec and modified it doesn't meant they have to then follow Samsung's spec.mode_13h - Tuesday, November 20, 2018 - link
This is a cute Orwellian spin, but Samsung is really the one at fault for building a proprietary extension atop a standard, rather than going through the PCI SIG.I'm pretty sure Samsung could've at least negotiated a provisional draft of what they wanted, even if they couldn't get the PCI SIG to ratify their extension in time to suit their market window.
CheapSushi - Tuesday, November 20, 2018 - link
"M.2 revision 1.2"Samsung probably noticed that these standards & naming schemes are headache inducing and very slow in making any progress, so they did there own thing.
nagi603 - Tuesday, November 20, 2018 - link
The best kind of compatibility: whichever you put in the other, smoke _will_ come out...