AMD-K6-2 processor with 3DNow! technology is recorded in the 1998 CPU research cohort under AMD. The current display name and classification are normalization proposals.
Source product name
AMD-K6-2 processor with 3DNow! technology
Source model number
Not established
Source manufacturer
Advanced Micro Devices Inc.
Research scope
Microsoft Windows compatible PCs
Why it existed
manufacturer stated
AMD addresses differentiated Windows computing and 3D imaging/sound performance
Intended users: Microsoft Windows PC users and desktop OEMs
Engineering response: AMD-K6-2 family adds 3DNow! instructions and Windows-oriented differentiation
AMD explicitly states the problem and engineering response and names IBM, HP, and Fujitsu systems.
AMD's stated benefits are not independently measured here.
What difference it made
Comparable benchmark evidence has not been established for this record. Missing results do not imply poor performance.
Release evidence
The year above is a research-cohort label. Announcement, production, shipment and retail availability are distinct events.
Proposed event
family introduction and shipments
Proposed timing
1998-05-28 · exact precision
Assessment
proposed
Advanced Micro Devices Inc. is normalized to AMD; family-level display wording retains 3DNow! technology. The exact date belongs only to the family introduction.
AMD's filed exhibit states 'On May 28 we successfully introduced' the next-generation AMD-K6-2 processor family and reports more than 500,000 shipped in the quarter.
Open questions and review
Launch speed-grade composition and orderable SKU boundaries are not established; manufacturer-controlled sources are not independent corroboration.
No owner discrepancy decision is recorded. This does not mean there are no unresolved issues.
family variant overlap · follow up
The AMD-K6-2 family and speed-grade records overlap intentionally but are different granularities; the family must not be counted as an additional speed-grade SKU.
AMD states a family introduction on May 28 and shipment volume but does not enumerate launch speed grades.
Follow-up: Retain the family as a family-level candidate; represent 350 and 400 as variants only when their quarter evidence is kept separate.
date inheritance · resolved no change
The current verification correctly avoids copying the family May 28 date onto the 350 or 400 variants; this remains a high-risk import guardrail rather than a present data error.
AMD gives Q3 timing for 350 MHz while the family date is earlier; the family date does not establish the variant date.
Follow-up: Require typed event rows or explicit variant timing before normalization; retain quarter precision.
family variant overlap · follow up
The AMD-K6-2 family and four speed-grade records intentionally overlap across granularities; the family must not be counted as a fifth speed-grade record or used to infer an exhaustive launch-SKU list.
AMD states a May 28 family introduction and quarterly shipment totals but does not enumerate the family launch speed grades.
Follow-up: Retain the family as a family-level candidate and each speed grade only as separately evidenced variants; do not use the group as a count of five comparable SKU claims.
date inheritance · resolved no change
The exact May 28 AMD-K6-2 family date cannot be inherited by any speed-grade candidate. The 350 MHz variant is Q3 evidence and the 366 MHz 380 MHz and 400 MHz variants are Q4 evidence only.
AMD's Q4 filing identifies 366 MHz 380 MHz and 400 MHz versions as introduced and shipped in volume during Q4; it does not supply an exact date.
Follow-up: Keep the family exact date and each speed-grade interval separately typed; reject any normalization that converts quarter evidence to day or month precision.
category error · resolved no change
The mobile 300 MHz AMD-K6 record is not documented as an AMD-K6-2 speed variant. Its mobile AMD-K6 wording must remain separate from the AMD-K6-2 family and speed-grade hierarchy.
AMD states that it introduced a 300 MHz AMD-K6 processor for mobile applications during Q3 without calling it AMD-K6-2.
Follow-up: Do not assign AMD-K6-2 parentage or May family timing to the mobile AMD-K6 record; retain a separate family/category label pending product-identity evidence.
Original intake sources
These notes preserve the state at intake. Later verification is shown under Release evidence above; an original note saying verification had not occurred is not the current assessment.