Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Technology Stocks : Advanced Micro Devices - Moderated (AMD) -- Ignore unavailable to you. Want to Upgrade?

To: Pravin Kamdar who wrote (76700)	4/8/2002 4:53:22 PM
From: ptanner	Read Replies (2) \| Respond to of 275872

From EE Times Article on AU1100: The chip is targeted for the mobile information appliance market, which is expected to reach $26 billion and 1.3 billion units shipped by the year 2007, according to Edwards. The 1.3B units seems pretty high given the number of people in the world. This seems like a "100% annual growth compounded for five years" type projection. Maybe I am missing the potential for the mobile information appliance market since I presently don't own one. But would people have more than one? This would seem to defeat some of the purpose. The mobile info app market dollar projection is also comparable to current PC processors ( [INTC @ $6B/qtr *4 + some others) and this seems pretty optimistic IMO. At $26B / 1.3B units this is an ASP of $20 for the processors. I assumed based on both this value and the $30/AU1100(400MHz) these processors are small like other embedded processors noted by others here (10-20mm^2)? I am just questioning the future market projection - I don't yet have a specific opinion on the Alchemy purchase though I wonder how this architecture will fare in a market with competition from StrongARM and other processors. -PT

To: Pravin Kamdar who wrote (76700)	4/8/2002 7:51:30 PM
From: milo_morai	Read Replies (1) \| Respond to of 275872

<font color=blue>Emailed today from x86-64.org Date: Thu, 28 Mar 2002 03:42:11 +0100 From: Andi Kleen <ak@suse.de> To: linux-kernel@vger.kernel.org, announce@x86-64.org Message-ID: <20020328034211.A14622@wotan.suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: [ANNOUNCEMENT] New x86-64 kernel snapshot based on 2.4.19pre4 A new 2.4.19pre4 based x86-64 linux kernel snapshot has been released. This is a port of the Linux kernel to the x86-64 architecture, as implemented by the AMD Hammer family of CPUs and the Virtutech VirtuHammer simulator. For more information about x86-64 see x86-64.org This is a major update for the x86-64 kernel. It has so many bugs fixed over previous kernels that I would recommend every x86-64 user to update to this kernel version. This release requires new binutils and a recent gcc to build. The changed signal ABI requires a new glibc. Working versions of gcc, glibc and binutils can be downloaded from ftp://ftp.x86-64.org/pub/stable-tools/current/ It also requires an updated gdb. Documentation on how to build the toolchain and glibc can be found at x86-64.org This is a newer x86-64 codebase than the version in the 2.5 kernel with much more testing. 2.5 will be synced with this tree soon. Please report any problems to bugs@x86-64.org. The discussion list is discuss@x86-64.org. See x86-64.org for archives and subscribe/unsubscribe options. You can download the x86-64 kernel source as a full tarball at: ftp://ftp.x86-64.org/pub/linux-x86_64/v2.4/linux-x86_64-2.4.19pre4-1.tar.bz2 MD5: e90765227be6956ffd002e18aa2a9e3a linux-x86_64-2.4.19pre4-1.tar.bz2 or as a patch against plain Linux 2.4.19pre4 as released by Marcelo: ftp://ftp.x86-64.org/pub/linux-x86_64/v2.4/x86_64-2.4.19pre4-1.bz2 MD5: 807df0308052b4065df2089cc9a49499 x86_64-2.4.19pre4-1.bz2 This is a snapshot of the CVS tree at cvs.x86-64.org. The current CVS tree can be accessed anonymously, for details see x86-64.org Note that the code in the CVS tree HEAD can be unstable sometimes. Known problems: - MTRR breaks on SMP and can oops at booting. It is disabled ATM. - Still some problems in 64bit LTP runs, which could be partly kernel bugs. - 32bit lspci breaks on the 64bit kernel because the /proc/pci structures are not compatible. - 32bit personality setting ("linux32") doesn't work. - NMI watchdog doesn't work. - String/memory functions unoptimized and use a lot of CPU time. - 32bit setserial crashes. Changes: - Merge to 2.4.19pre4. This has a reduced struct page which saves several MB of memory in a 64bit build. - SMP and APIC code functional now - 8257 timer is now accurate - Some signal handling bugs fixed. - modify_ldt for 32bit and 64bit implemented - IA32 emulation enhanced with a few new calls and ioctls and various bugs fixed. - 32bit ptrace support. - Some driver support for AMD 8111: Sound card, IDE, USB 2.0 (Vojtech Pavlik) - AMD 8111 Random Generator based on the AMD768 RNG driver. - Audited on all inline assembly: this found and fixed various bugs. - New struct user and signal frame formats. This is an ABI change. - Doesn't require 32bit tools for building anymore. - New kernel mapping that in theory supports ~120TB of physical memory per system. - Kernel modules functional now. Fixed some vmalloc/ioremap bugs. - More efficient signal handling. Does FXSAVE directly into and out of user space now. - WCHAN support added. - Various other bug fixes. -Andi Kleen, SuSE Labs.

To: Pravin Kamdar who wrote (76700)	4/9/2002 12:17:49 AM
From: Dan3	Respond to of 275872

Re: $50 million seems like a steal for Alchemy Maybe instead of buying Alchemy for $50 million, AMD should have let Intel pay $500 million for it, then micromanage the engineers until they quit and went to AMD anyway. Intel has nonetheless been beaten to market, as in the case of Atheros Communications Inc.'s 802.11a chip, which Intel is using in lieu of its own. It's also been outdone, as when its Gigabit Ethernet PHY proved inadequate, prodding Intel to use a PHY from Marvell Semiconductor Inc. (Intel is "very happy" with the Marvell relationship, Maloney said, but he refused to comment on whether Intel still hopes to produce its own Gigabit Ethernet PHY.) Those might seem like small setbacks, but they get magnified in the communications arena, foreign turf for Intel and a world where it can't call the shots. "They're used to being the de facto standard in everything, but standards have to be in place first in communications, and that takes away their natural advantage," one analyst said. Intel has been good in areas where it controls the infrastructure, but "when it's an open-market jump ball, they do less well," said Gauna of UBS Warburg. For example, he noted that Intel's chips for 10-Gbit/second Ethernet have found one major buyer — Intel's own network interface card — while the rest of the market has embraced Broadcom Corp. It's not just individual products that have fizzled. Acquisitions have stalled as well, or failed to produce the results Intel wanted. DSP Communications, for example, was supposed to be Intel's ticket into the CDMA market. But those plans faded when Qualcomm Inc. stole DSP Communications' lone customer — Kyocera Corp. — and held its lead in CDMA. Separately, the Basis acquisition yielded some digital subscriber line chips that have already been discontinued, analysts said. eet.com