The Inquirer-Home

Intel confirms Tejas, Jayhawk dead

Confirms dual core chip moves
Fri May 07 2004, 17:43
CHIP GIANT INTEL has now confirmed many details of our exclusive story yesterday, and said today that Tejas and Jayhawk have exited from its desktop processor roadmap.

See Intel may have canned Tejas project.

An Intel representative said: "We have re-prioritised our resources and we now no longer plan to produce the processor known as Tejas". Jayhawk, being the server equivalent, is also for the chopping block.

Intel said that the reason for the move was that it had accessed the needs of home/officer users and accelerated its dual core for a desktop client. This, we reported in February, will use Pentium M technology. Intel said today it will reveal more details of this dual core technology at a future date.

He said that Intel had bolstered its design team to make that happen in 2005.

But Intel said there would be no changes in the chipset "stable platforms" codenamed Grantsdale and Alderwood.

We asked Intel if there would be future Prescotts based on 65 nanometre technology, and the firm has indicated that's likely to be the case. Well, it didn't deny it, anyway. Sixty five nanometre technology is slated to appear in 2005.

Intel is assessing the Tulsa strategy but described our earlier reports of the canning of the Potomac as rumour and speculation.

Mind you, our Tejas story yesterday was just that, wasn't it?

And here's some more speculation and rumour. We're hearing that some IA-64 roadmap parts that weren't dropped before, are being dropped now or not too long from now.

What does AMD think about this? We talked to AMD about our story yesterday before we filed it. All it would say was, "interesting". Well yes. There is an interesting opportunity ahead for AMD to take if it's clever and does its marketing right. And we'll have more to say about its marketing in a minute or two. µ

See Also
Intel's Potomac team gets dissolved
Intel to formally confirm Tejas canned today
Intel prepares to can Pentium 4


Share this:

blog comments powered by Disqus
Subscribe to INQ newsletters

Sign up for INQbot – a weekly roundup of the best from the INQ

INQ Poll

Heartbleed bug discovered in OpenSSL

Have you reacted to Heartbleed?