Intel Announce Collaboration With TSMC On Atom Platform

"Intel will be working with TSMC in hopes of expanding the Atom line to support more platforms."

Search News

Intel Announce Collaboration With TSMC On Atom Platform

As previously known, Intel and the Taiwan Semiconductor Manufacturing Company (TSMC) made a joint announcement of future collaboration today, dubbed a memorandum of understanding (MOU).  In this agreement, the Atom processor will be ported to TSMC's technology platform.  This, however, does not mean that Intel is outsourcing the production of the Atom processor.  The manufacturing of the current generation will remain in Intel's field.  Instead, it means that both companies will have access to each other's technologies in order to further develop and expand the Atom line into other mobile platforms.  Intel hopes to implement their Atom System-on-Chip solution is a multitude of platforms, such as mobile internet Devices (MIDs), smart-phones, netbooks, nettops, and AC-powered consumer electronics devices.

"We believe this effort will make it easier for customers with significant design expertise to take advantage of benefits of the Intel Architecture in a manner that allows them to customize the implementation precisely to their needs," said Paul Otellini, Intel president and CEO. "The combination of the compelling benefits of our Atom processor combined with the experience and technology of TSMC is another step in our long-term strategic relationship."

"TSMC values our strategic relationship with Intel. This MOU brings together the Intel Architecture and the TSMC technology platform. We expect this collaboration will help proliferate the Atom processor SoC and foster overall semiconductor growth," said Dr. Rick Tsai, president and CEO of TSMC. "With this agreement, our technology platform extends beyond the two companies’ current collaboration to support future Intel embedded x86 products."

What do you think of this partnership between giants of the chip world?

Discuss in our Forums
«Prev 1 Next»

Most Recent Comments

25-02-2009, 14:52:11

lasher
Ok finally bashed my way through a couple of Gromacs , one core sent fine the other is struggling to send.

Apologies for long cut/ paste

[19:37:49] Finished Work Unit:
[19:37:49] - Reading up to 3977832 from "work/wudata_05.arc": Read 3977832
[19:37:49] - Reading up to 37559620 from "work/wudata_05.xtc": Read 37559620
[19:37:50] goefile size: 0
[19:37:50] logfile size: 147402
[19:37:50] Leaving Run
[19:37:53] - Writing 41703018 bytes of core data to disk...
[19:37:54] ... Done.
[19:37:55] - Shutting down core
[19:37:55]
[19:37:55] Folding@home Core Shutdown: FINISHED_UNIT
[19:38:00] CoreStatus = 64 (100)
[19:38:00] Sending work to server


[19:38:00] + Attempting to send results
[19:38:32] Couldn't send HTTP request to server (wininet)
[19:38:32] + Could not connect to Work Server (results)
[19:38:32] (171.65.103.160:80)
[19:38:32] - Error: Could not transmit unit 05 (completed February 25) to work server.
[19:38:32] Keeping unit 05 in queue.


[19:38:32] + Attempting to send results
[19:39:03] Couldn't send HTTP request to server (wininet)
[19:39:03] + Could not connect to Work Server (results)
[19:39:03] (171.65.103.160:80)
[19:39:03] - Error: Could not transmit unit 05 (completed February 25) to work server.


[19:39:03] + Attempting to send results
[19:39:04] Error: Got status code 503 from server
[19:39:04] + Could not connect to Work Server (results)
[19:39:04] (171.67.108.17:80)
[19:39:04] Could not transmit unit 05 to Collection server; keeping in queue.
[19:39:04] - Preparing to get new work unit...
[19:39:04] + Attempting to get work packet
[19:39:04] - Connecting to assignment server
[19:39:04] - Successful: assigned to (171.65.103.162).
[19:39:04] + News From Folding@Home: Welcome to Folding@Home
[19:39:04] Loaded queue successfully.
[19:39:05] Error: Got status code 503 from server
[19:39:05] + Could not connect to Work Server
[19:39:05] - Error: Attempt #1 to get work failed, and no other work to do.
Waiting before retry.
[19:39:14] + Attempting to get work packet
[19:39:14] - Connecting to assignment server
[19:39:15] Couldn't send HTTP request to server (wininet)
[19:39:15] + Could not connect to Assignment Server
[19:39:16] - Successful: assigned to (171.65.103.160).
[19:39:16] + News From Folding@Home: Welcome to Folding@Home
[19:39:16] Loaded queue successfully.
[19:39:53] + Could not get Work unit data from Work Server
[19:39:53] - Error: Attempt #2 to get work failed, and no other work to do.
Waiting before retry.
[19:40:17] + Attempting to get work packet
[19:40:17] - Connecting to assignment server
[19:40:18] Couldn't send HTTP request to server (wininet)
[19:40:18] + Could not connect to Assignment Server
[19:40:21] Couldn't send HTTP request to server (wininet)
[19:40:21] + Could not connect to Assignment Server 2
[19:40:21] + Couldn't get work instructions.
[19:40:21] - Error: Attempt #3 to get work failed, and no other work to do.
Waiting before retry.
[19:40:48] + Attempting to get work packet
[19:40:48] - Connecting to assignment server
[19:40:49] Couldn't send HTTP request to server (wininet)
[19:40:49] + Could not connect to Assignment Server
[19:40:49] Couldn't send HTTP request to server (wininet)
[19:40:49] + Could not connect to Assignment Server 2
[19:40:49] + Couldn't get work instructions.
[19:40:49] - Error: Attempt #4 to get work failed, and no other work to do.
Waiting before retry.
[19:41:30] + Attempting to get work packet
[19:41:30] - Connecting to assignment server
[19:41:31] Couldn't send HTTP request to server (wininet)
[19:41:31] + Could not connect to Assignment Server
[19:41:31] Couldn't send HTTP request to server (wininet)
[19:41:31] + Could not connect to Assignment Server 2
[19:41:31] + Couldn't get work instructions.
[19:41:31] - Error: Attempt #5 to get work failed, and no other work to do.
Waiting before retry.
[19:42:57] + Attempting to get work packet
[19:42:57] - Connecting to assignment server
[19:42:58] Couldn't send HTTP request to server (wininet)
[19:42:58] + Could not connect to Assignment Server
[19:42:59] Couldn't send HTTP request to server (wininet)
[19:42:59] + Could not connect to Assignment Server 2
[19:42:59] + Couldn't get work instructions.
[19:42:59] - Error: Attempt #6 to get work failed, and no other work to do.
Waiting before retry.



Any ideas fellas??
Other core has another WU already started fine.

25-02-2009, 14:59:04

themcman1
When it happened to me it was for downloading work, but I just closed it and then restarted.

25-02-2009, 15:00:39

tinytomlogan
Check firewall

25-02-2009, 15:15:20

lasher
Checked that,

The rigs just collected another WU on the second core now so folding again on 2 cores but it's only sent one.

[20:05:32] Could not transmit unit 05 to Collection server; keeping in queue.
[20:05:33]
[20:05:33] *------------------------------*
[20:05:33] Folding@Home Gromacs Core
[20:05:33] Version 1.90 (March 8, 2006)
[20:05:33]
[20:05:33] Preparing to commence simulation
[20:05:33] - Looking at optimizations...
[20:05:33] - Created dyn
[20:05:33] - Files status OK
[20:05:35] - Expanded 2993312 -> 15101089 (decompressed 504.4 percent)
[20:05:35] - Starting from initial work packet
[20:05:35]
[20:05:35] Project: 2483 (Run 225, Clone 19, Gen 7)



So it looks like its queued it but when does it have another go and send it?




Edit.... think i sorted it , had to go configonly and alter internet setting as was trying to go via proxy by the looks.... fingers crossed.

25-02-2009, 15:30:46

monkey7
I had it with my SMP too, but succeeded in sending after a few tries. I'd say see if it's still failing tomorrow.
Reply
x

Register for the OC3D Newsletter

Subscribing to the OC3D newsletter will keep you up-to-date on the latest technology reviews, competitions and goings-on at Overclock3D. We won't share your email address with ANYONE, and we will only email you with updates on site news, reviews, and competitions and you can unsubscribe easily at any time.

Simply enter your name and email address into the box below and be sure to click on the links in the confirmation emails that will arrive in your e-mail shortly after to complete the registration.

If you run into any problems, just drop us a message on the forums.