Language Selection

English French German Italian Portuguese Spanish

Nvidia starts working on SLI 2

Filed under
Hardware

WE DON'T NEED to be in Taiwan to know what's going on in the industry but as you know it was not our choice to skip humid Computex show.

However, we learned that even if Crossfire defeats SLI, Nvidia has some secret horses for a new race. It is working on something that we know as SLI 2.

As you know SLI, has been around for a few quarters now and Nvidia is working to improve this marchitecture. One of the teams was working to get some better silicon at the same time and that’s what we believe is going to be called SLI2.

We learned that Nvidia is working on a motherboard that will have more PCIe lanes and might actually get close to two times 16 PCIe lanes, the ultimate for PCIe graphic cards in SLI mode.

We are not sure how much two times PCIe 16 times lanes will change the actual SLI score but this is something that we need to see before making our own mind . It could be good thing you never know.

Nvidia will also improve number things on its new silicon once it polishes it enough as it learned from its first born SLI chipset. We don’t have any idea about timing of final specification and features of such SLI 2 chipsets and boards but we will work on it. µ

theinquirer.

More in Tux Machines

Android Leftovers

Leftovers: OSS

Ubuntu 16.04 Review: What’s New for Desktop Users

Ubuntu is a tricky distribution. As much as I love it on my home server, my desktop is a different ballgame. In my experience, releases between LTS versions have many new technologies that may or may not survive in the next LTS. There were many technologies or features that Canonical thought were ambitious -- HUD, experimenting with menus, online dash search, Ubuntu Software Center, etc. -- but they were abandoned. So, if I were to use Ubuntu on my desktop, I would still choose LTS. Read more

Workflow and efficiency geek talks Drush and Drupal

I started using Drupal because I needed an open source content management system (CMS) to use in several community projects. One of the projects I was involved with was just getting started and had narrowed its CMS selection down to either Drupal or Joomla. At the time I was using a different framework, but I had considered Drupal in the past and knew that I liked it a lot better than Joomla. I convinced them to go with the new Drupal 6 release and converted all of my other projects for consistency. I started working with Drush because I wanted a unified mechanism to work with local and remote sites. My first major contribution to Drush was site aliases and sql-sync in Drush 3. Read more