AMD rejects ARM and continues to focus on x86 architecture

In response to rumors that AMD sought to obtain an ARM technology license, John Taylor, the company's client product leader, denied it and said it will continue to focus on developing tablet chips based on the x86 architecture.

Sina Technology reported that Taylor explicitly stated that AMD's CPU and GPU technology is excellent and suitable for the development of tablet PC chips, so it will not seek to obtain ARM's technology license. Taylor said in an interview, “We have high hopes for the APU using the x86 architecture.” AMD may not intend to adopt the ARM architecture, but it is an indisputable fact that the two companies have shown each other in recent months.

Jem Davies, vice president of ARM media technology division, will attend the keynote speech at the AMD Developers Conference in June, while ARM CEO Warren East also stated that he We saw the potential of AMD's adoption of the ARM architecture in the future. One of the reasons for this rumbling is that ultra low-power processors and ARM Cortex products using Atom, Bobcat, and other architectures will be available in the next two years.

Another reason is that AMD reorganized management in February this year, with CEO Dirk Meyer, COO Robert Rivet and senior vice president of Corporate Strategy Matthias The departure of Marty Seyer at least indicates that Meier has become a scapegoat for failing to seize the company's future opportunities in the ultra-mobile and portable markets.

None of AMD's current directors has extensive experience in the x86 market, and most of the companies joining this company have only two or three years of time, and some have a background in the mobile phone business. The only "conservative" member is Rick Bergman, the current senior vice president of the company, who joined the company after AMD bought ATI in 2006. Analysts pointed out that AMD can easily defuse current rumors, that is, publicly announce the product roadmap.

Speaker With Battery

Speaker Box Co., Ltd. , http://www.nsspeaker.com

This entry was posted in on