Fudzilla
April 25, 2014, 07:25:46 AM *
Welcome, Guest. Please login or register.

Login with username, password and session length
News: Fudzilla Forum is open
 
   Home   Help Search Login Register  
Pages: [1]   Go Down
  Print  
Author Topic: The Intel® Core™ processor family lives... kind-of... well... sorta  (Read 3254 times)
y eye
Sr. Member
****
Posts: 282



View Profile
« on: January 17, 2011, 09:46:10 AM »

 i3, i5 and i7 are the designations for Intel's Core CPUs and are
followed by four numbers preceded by a 2 and may end in a letter (F,S or T).

Release #1: Sandy Bridge CPU has come and gone and the NDA is still on.
 Sandy Bridge as a name/designation is no longer used for The Intel® Core™ processor family.  

Note: There are two Intel Core i7 26XX CPUs and they are:
The advantages of the Core i7 2600 are enhanced Read Write SSDs, Syncing and Video Codec speed increases.
The advantage of the Core i7 2600K is unlocking for Overclocking; however, there are none of the advantages of the 2600.

                                                

        



The Inpai and Expreview Articles have comprehensive benchmarks and reports on the Z68 Chipset.
Most interesting are massive overclocking, SSD read, write improvements, syncing and video encoding acceleration.
"Made official just recently, the Z68 chipset comes as a hybrid between the P67 and the H67
and was designed in order to allow for overclocking Sandy Bridge CPUs while using the integrated graphics."
 http://www.expreview.com/13075.html
 http://www.expreview.com/13290-1.html

01. Intel Quick Sync HD video transcoding acceleration of Comparative
2011-01-13 17:37
02. SNB series of 11 bombs, Intel Quick Sync transcoding acceleration test
2011-01-12 17:00
03. SNB series of eight bomb, Sandy Bridge processor synchronization evaluation
2011-01-05 09:00
These topics discuss new additions to some of the i3, i5 and i7 Intel CPUs and may be available without the Intel to be released Z68 Chipset.
Of the new instrument: http://www.expreview.com/13290-1.html
http://www.expreview.com/13143.html

HD100 has been changed to HD2000
HD200 has been changed to HD3000

This is as good a place to begin the viewing as any:  http://en.inpai.com.cn/doc/enshowcont.asp?id=7949&pageid=7742
On the upper right hand side of the page are additional articles.

PAGE15: Final Words  http://en.inpai.com.cn/doc/enshowcont.asp?id=7949&pageid=7749  

Related reports:
An Inpai writer stated that a Software Lucid Logic Program makes it possible
to combine Radeon and nVidia Graphics Cards on the same MotherBoard.
It was not stated which MotherBoards have lucid logic embedded but probably MSI.

More on Hydra Here: ...31Dec10...  http://www.lucidlogix.com/download/product-adventure2800_2_3991769098.pdf

Zol.cn has a MSI Z68 MotherBoard pictured.  

MSI Z68 Mother Board: MSI Intel Z68 Motherboard photos
January 10th, 2011  http://news.softpedia.com/newsImage/MSI-Intel-Z68-Motherboard-Also-Poses-for-the-Camera-4.jpg/
 

                                                                    How to ID a unlocked Intel Core CPU:
                                                


How to overclock a non Z68 Chipset Mother Board:
Plug in a Graphics Card... walla massive overclocking at your fingertips.Smiley
No SSD updates or Syncing or accelerated video coding and decoding but what the hey?

Why: The P67 and H67 Chipset Mother Boards are designed to overclock in the absence of the Z68 Hybrid Chipset.
http://www.lucidlogix.com/download/product-adventure2800_2_3991769098.pdf

 P67 'OC' Bioses (internal PLL overvoltage fix): http://hwbot.org/forum/showthread.php?t=15952

 

Intel Will Work On Better Linux Timing For Ivy Bridge
http://www.phoronix.com/scan.php?page=news_item&px=ODk3Nw
Posted by Michael Larabel on January 04, 2011
Intel though admits it could have done better with its Linux launch support. In one of our active threads in the Phoronix Forums, Jesse Barnes admits they sort of messed up with the Sandy Bridge launch. Jesse is one of the open-source Linux developers at Intel responsible for the support upbringing and ongoing driver development across their DRM / Mesa / DDX.
No, this is our job, and we blew it for Sandy Bridge. We're supposed to do development well ahead of product release, and make sure distros include the necessary code to get things working (we have separate teams to do development and aid distros in backporting, though most of them can handle it by themselves these days).

I could give you all sorts of explanations as to why this is (Sandy Bridge is a big architectural change, we made some mistakes in defining our development milestones, and we didn't work hard enough to get our changes backported), but really there's no excuse. Fortunately we've learned from this and are giving ourselves more time and planning better for Sandy Bridge's successor, Ivy Bridge.
 
                                                        

« Last Edit: January 23, 2011, 07:23:04 AM by y eye » Logged

Pages: [1]   Go Up
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.11 | SMF © 2006-2009, Simple Machines LLC Valid XHTML 1.0! Valid CSS!