WEBVTT - AMD Up To Today

0:00:04.240 --> 0:00:07.240
<v Speaker 1>Welcome to tech Stuff, a production of I Heart Radios,

0:00:07.320 --> 0:00:13.800
<v Speaker 1>How Stuff Works. Hey there, and welcome to tech Stuff.

0:00:13.840 --> 0:00:16.800
<v Speaker 1>I'm your host, Jonathan Strickland. I'm an executive producer with

0:00:16.840 --> 0:00:19.000
<v Speaker 1>How Stuff Works and I heart Radio and I love

0:00:19.160 --> 0:00:22.680
<v Speaker 1>all things tech. And in our last episode, which was

0:00:22.880 --> 0:00:26.079
<v Speaker 1>requested by listener Stephen, I left off with a m

0:00:26.200 --> 0:00:30.280
<v Speaker 1>d's history in ninety six, when the company found itself

0:00:30.440 --> 0:00:35.200
<v Speaker 1>reeling when Intel decided to cut ties. Up to that point,

0:00:35.520 --> 0:00:38.120
<v Speaker 1>a m D had been in an agreement to act

0:00:38.200 --> 0:00:42.480
<v Speaker 1>as a second source for Intel designed chips. Intel would

0:00:42.520 --> 0:00:44.720
<v Speaker 1>get a licensing fee and a m D would be

0:00:44.800 --> 0:00:49.120
<v Speaker 1>able to manufacture chips based on Intel's designs. But when

0:00:49.159 --> 0:00:52.040
<v Speaker 1>a m D chips started to do better in performance

0:00:52.120 --> 0:00:57.720
<v Speaker 1>tests than the Intel originals, things changed. Until ended a

0:00:57.760 --> 0:01:01.760
<v Speaker 1>ten year agreement several years early, and the two companies

0:01:01.800 --> 0:01:05.200
<v Speaker 1>would enter into a lengthy court battle that would ultimately

0:01:05.280 --> 0:01:07.600
<v Speaker 1>go all the way to the U. S. Supreme Court.

0:01:07.959 --> 0:01:10.319
<v Speaker 1>But we've got a few years to get through before

0:01:10.360 --> 0:01:14.080
<v Speaker 1>we get to that. So Intel had introduced the eighty

0:01:14.240 --> 0:01:18.640
<v Speaker 1>three eighty six microprocessor in nineteen eighty five, a year

0:01:18.680 --> 0:01:21.399
<v Speaker 1>before it severed the agreement with a m D. The

0:01:21.480 --> 0:01:24.920
<v Speaker 1>three eight six, as it was known, was a thirty

0:01:24.959 --> 0:01:28.920
<v Speaker 1>two bit micro processor. It could run most older code

0:01:29.040 --> 0:01:32.759
<v Speaker 1>designed for its predecessors, and was capable of faster clock rates,

0:01:33.040 --> 0:01:36.440
<v Speaker 1>meaning it could run more operations per second, and it

0:01:36.520 --> 0:01:39.560
<v Speaker 1>had a greater data bandwidth, which means it could run

0:01:39.600 --> 0:01:44.120
<v Speaker 1>operations on larger amounts of information than the earlier chips could.

0:01:44.600 --> 0:01:46.600
<v Speaker 1>Intel an a m D had set the stage for

0:01:46.680 --> 0:01:50.080
<v Speaker 1>creating the standard in computer processing, and now Intel was

0:01:50.160 --> 0:01:53.480
<v Speaker 1>determined to stand alone. A m D, for its part,

0:01:53.720 --> 0:01:56.680
<v Speaker 1>have been designing its own version of the three eight six,

0:01:57.040 --> 0:02:01.040
<v Speaker 1>called the get Ready for It a M three eight six,

0:02:01.360 --> 0:02:05.080
<v Speaker 1>but Intel's decision to end the agreement through things into disarray.

0:02:05.480 --> 0:02:08.520
<v Speaker 1>Intel argued that their agreement with a m D only

0:02:08.639 --> 0:02:11.920
<v Speaker 1>covered the eight eighty six through the e D two

0:02:11.960 --> 0:02:15.720
<v Speaker 1>eighty six family of micro processors, and that the three

0:02:15.760 --> 0:02:19.720
<v Speaker 1>eight six and later iterations were excluded. A and D

0:02:19.880 --> 0:02:24.760
<v Speaker 1>obviously disagreed with this interpretation of their agreement, claiming that

0:02:24.840 --> 0:02:28.480
<v Speaker 1>all x eighty six derivatives were covered under this ten

0:02:28.560 --> 0:02:31.160
<v Speaker 1>year plan that they had struck with Intel back in

0:02:31.240 --> 0:02:35.360
<v Speaker 1>nineteen eighty two. At this same time, things were shifting

0:02:35.600 --> 0:02:38.600
<v Speaker 1>in the PC market. You might remember from my episode

0:02:38.800 --> 0:02:41.639
<v Speaker 1>about early computer systems that there used to be a

0:02:41.680 --> 0:02:44.920
<v Speaker 1>ton of different types of PCs on the market in

0:02:44.960 --> 0:02:48.080
<v Speaker 1>the late seventies and early eighties, each with its own

0:02:48.120 --> 0:02:51.400
<v Speaker 1>hardware and operating system. The ones we think about today

0:02:51.720 --> 0:02:55.560
<v Speaker 1>are Windows based machines and Mac computers as far as

0:02:55.600 --> 0:02:59.239
<v Speaker 1>personal machines are concerned. But up through the early nineteen eighties,

0:02:59.280 --> 0:03:03.480
<v Speaker 1>the field was much more crowded. You had companies like Tandy, Commodore,

0:03:03.520 --> 0:03:07.880
<v Speaker 1>and Amiga and others competing with Apple and IBM. However,

0:03:08.000 --> 0:03:12.440
<v Speaker 1>by the mid nineteen eighties the field had thinned out significantly.

0:03:13.000 --> 0:03:17.520
<v Speaker 1>IBM had secured valuable deals with corporations, becoming known as

0:03:17.560 --> 0:03:21.840
<v Speaker 1>the computer of choice for office workstations. Apple maintained a

0:03:21.880 --> 0:03:25.320
<v Speaker 1>more niche market of users interested in the creative power

0:03:25.400 --> 0:03:29.840
<v Speaker 1>of the Macintosh. Everyone else sort of began to fade away,

0:03:29.880 --> 0:03:33.560
<v Speaker 1>and this left the IBM PC and it's compatible clones

0:03:33.680 --> 0:03:36.960
<v Speaker 1>with the lion's share of the market. In fact, by

0:03:37.000 --> 0:03:39.600
<v Speaker 1>the time Intel was trying to block a m D,

0:03:40.200 --> 0:03:43.400
<v Speaker 1>the IBM PC market share had grown to about eighty

0:03:43.600 --> 0:03:47.880
<v Speaker 1>four percent of all personal computers, so this was a

0:03:48.000 --> 0:03:51.640
<v Speaker 1>really big deal. A m D had helped cement the

0:03:51.840 --> 0:03:55.839
<v Speaker 1>X eight six chip as the go to microprocessor for computers,

0:03:56.280 --> 0:03:58.480
<v Speaker 1>and now it looks like Intel was going to run

0:03:58.480 --> 0:04:02.200
<v Speaker 1>away with the whole thing. Things were starting to smell

0:04:02.520 --> 0:04:06.360
<v Speaker 1>a little anti competitive. Am D did still have an

0:04:06.360 --> 0:04:09.960
<v Speaker 1>agreement to the underlying instruction set for the X eight

0:04:10.080 --> 0:04:14.000
<v Speaker 1>six family of processors, so in some respects a m

0:04:14.080 --> 0:04:16.840
<v Speaker 1>D was still in the game, but Intel wasn't going

0:04:16.880 --> 0:04:20.320
<v Speaker 1>to share the actual physical design of the three six

0:04:20.360 --> 0:04:24.040
<v Speaker 1>microprocessor with a m D. So the engineers at a

0:04:24.160 --> 0:04:27.520
<v Speaker 1>m D set out to reverse engineer the three six

0:04:27.720 --> 0:04:30.320
<v Speaker 1>and build their own version of it while the legal

0:04:30.360 --> 0:04:34.760
<v Speaker 1>battle continued in the courts. Reverse engineering alone is a

0:04:34.800 --> 0:04:39.880
<v Speaker 1>pretty fascinating subject. The basic concept is fairly intuitive. You

0:04:39.960 --> 0:04:43.520
<v Speaker 1>take a technology and you examine it closely and you

0:04:43.560 --> 0:04:46.200
<v Speaker 1>figure out what makes it tick, how does the tech

0:04:46.560 --> 0:04:49.960
<v Speaker 1>actually do whatever it does. Then you go back and

0:04:50.000 --> 0:04:53.440
<v Speaker 1>you build your own version of that technology based upon

0:04:53.520 --> 0:04:58.080
<v Speaker 1>your understanding of how the starting example worked. So you're

0:04:58.080 --> 0:05:00.480
<v Speaker 1>not starting off with some sort of blueprint or set

0:05:00.520 --> 0:05:03.560
<v Speaker 1>of plans or instructions. You're sussing it out on your

0:05:03.560 --> 0:05:07.280
<v Speaker 1>own based on existing instances of the technology. So it's

0:05:07.279 --> 0:05:11.080
<v Speaker 1>a bit like detective work. Between reverse engineering and the

0:05:11.200 --> 0:05:13.680
<v Speaker 1>legal battles. It would be years before a m D

0:05:13.800 --> 0:05:16.480
<v Speaker 1>could bring its own three eight six chips to market.

0:05:16.920 --> 0:05:21.839
<v Speaker 1>The company began releasing its version starting in nineteen, and

0:05:22.080 --> 0:05:25.359
<v Speaker 1>once again a m D S version of Intel's chips

0:05:25.480 --> 0:05:29.400
<v Speaker 1>were clocking in at a faster clock rate than the competition.

0:05:29.920 --> 0:05:32.919
<v Speaker 1>Intel's three eight six chips maxed out at thirty three

0:05:32.920 --> 0:05:36.159
<v Speaker 1>mega hurts, whereas a m D S could hit forty

0:05:36.440 --> 0:05:40.000
<v Speaker 1>mega hurts. The legal battles continued, and a m D

0:05:40.160 --> 0:05:43.800
<v Speaker 1>began to invest in designing its own microcode for chips.

0:05:44.279 --> 0:05:49.599
<v Speaker 1>Intel's next microprocessor was predictably the eight four eight six,

0:05:49.920 --> 0:05:52.400
<v Speaker 1>and a m D created its own version the A

0:05:52.640 --> 0:05:56.200
<v Speaker 1>M four eight six. Some A M for eight six

0:05:56.279 --> 0:05:59.400
<v Speaker 1>chips had Intel microcode from the x A D six

0:05:59.440 --> 0:06:03.279
<v Speaker 1>agreement and others had a m D microcode, making it

0:06:03.320 --> 0:06:07.880
<v Speaker 1>a little confusing, and all of them were outpacing Intel's

0:06:08.080 --> 0:06:11.080
<v Speaker 1>version of the same chip. Even the top of the

0:06:11.200 --> 0:06:16.000
<v Speaker 1>line microprocessor in Intel's forty six line was left behind.

0:06:16.400 --> 0:06:19.040
<v Speaker 1>The fastest four D six from Intel had the top

0:06:19.080 --> 0:06:22.000
<v Speaker 1>clock speed of one hundred mega hurts. A m D

0:06:22.200 --> 0:06:24.880
<v Speaker 1>S version was able to reach speeds of one D

0:06:25.000 --> 0:06:30.200
<v Speaker 1>twenty mega hurts. Now this was in When that legal

0:06:30.240 --> 0:06:33.960
<v Speaker 1>battle I talked about finally concluded, the courts found in

0:06:34.080 --> 0:06:37.160
<v Speaker 1>favor of A m D, granting the company some royalty

0:06:37.200 --> 0:06:40.480
<v Speaker 1>free use of some of Intel's patents and awarding A

0:06:40.600 --> 0:06:43.760
<v Speaker 1>m D millions of dollars in the process. But the

0:06:43.800 --> 0:06:46.400
<v Speaker 1>whole endeavor had taught the engineers at A m D

0:06:46.600 --> 0:06:49.960
<v Speaker 1>a valuable lesson. While they had won this battle, there

0:06:50.040 --> 0:06:53.120
<v Speaker 1>was no guarantee that things would remain stable between Intel

0:06:53.160 --> 0:06:56.440
<v Speaker 1>and a m D, so the company did release another

0:06:56.600 --> 0:06:59.000
<v Speaker 1>x E D six derived chip. This one was called

0:06:59.040 --> 0:07:02.440
<v Speaker 1>the A m D five x eight six, or five

0:07:02.560 --> 0:07:04.960
<v Speaker 1>by eighty six if you wanted to think of it

0:07:05.000 --> 0:07:07.640
<v Speaker 1>that way. And you may be thinking, ha, I never

0:07:07.680 --> 0:07:10.520
<v Speaker 1>heard of a five eight six computer. I'm pretty sure

0:07:10.560 --> 0:07:14.120
<v Speaker 1>that Intel switched over from four A D six to pentium,

0:07:14.160 --> 0:07:16.440
<v Speaker 1>and you would be right. The A m D five

0:07:16.800 --> 0:07:20.160
<v Speaker 1>x eight six chip was based off the same architecture

0:07:20.440 --> 0:07:23.920
<v Speaker 1>as the A M four eight six microprocessor, but it

0:07:24.000 --> 0:07:27.400
<v Speaker 1>did manage an even faster clock speed out of the box.

0:07:27.440 --> 0:07:30.040
<v Speaker 1>It was a hundred thirty Mega hurts, but original equipment

0:07:30.080 --> 0:07:33.640
<v Speaker 1>manufacturers or o e m s in the biz could

0:07:33.680 --> 0:07:35.800
<v Speaker 1>get an even faster version than maxed out at a

0:07:35.880 --> 0:07:40.600
<v Speaker 1>hundred fifty Mega hurts now according to Tom's Hardware, a website,

0:07:40.640 --> 0:07:43.160
<v Speaker 1>which is, by the way, a great resource if you

0:07:43.160 --> 0:07:45.280
<v Speaker 1>ever want to learn everything there is to know about

0:07:45.360 --> 0:07:48.640
<v Speaker 1>just about any computer component you can think of. The

0:07:48.680 --> 0:07:50.960
<v Speaker 1>A M four, A D six, and the five X

0:07:51.000 --> 0:07:55.480
<v Speaker 1>eighty six processors also moved the floating point unit or

0:07:55.600 --> 0:07:59.760
<v Speaker 1>FPU over to the central processing unit or CPU itself.

0:08:00.240 --> 0:08:02.720
<v Speaker 1>Up until then, it had been customary to have separate

0:08:02.760 --> 0:08:06.240
<v Speaker 1>CPUs and FPUs that would connect to each other through

0:08:06.240 --> 0:08:09.160
<v Speaker 1>the motherboard. So I guess it's time to give a

0:08:09.240 --> 0:08:13.480
<v Speaker 1>quick explanation about what these things actually mean. The CPU,

0:08:13.680 --> 0:08:15.920
<v Speaker 1>I'm sure you've all heard of, right, It's sort of

0:08:15.960 --> 0:08:20.040
<v Speaker 1>the head manager of your computer. It executes basic instructions.

0:08:20.520 --> 0:08:22.720
<v Speaker 1>In the event that the instructions require the use of

0:08:22.760 --> 0:08:26.920
<v Speaker 1>a specialized chip like a graphics processing unit also known

0:08:26.920 --> 0:08:30.120
<v Speaker 1>as a GPU, the CPU can delegate those tasks to

0:08:30.200 --> 0:08:34.720
<v Speaker 1>the appropriate hardware. It's a high functioning component of a computer.

0:08:34.960 --> 0:08:37.280
<v Speaker 1>We often refer to it as the brains of the computer,

0:08:37.320 --> 0:08:40.600
<v Speaker 1>but really it's just calling the shots at the highest level.

0:08:41.040 --> 0:08:44.160
<v Speaker 1>The floating point unit carries out instructions on what are

0:08:44.160 --> 0:08:47.880
<v Speaker 1>called floating point numbers. A floating point number is a

0:08:47.920 --> 0:08:51.040
<v Speaker 1>workaround for a particular problem, which is how a computer

0:08:51.120 --> 0:08:55.360
<v Speaker 1>represents real numbers. The range of real numbers is infinite,

0:08:55.800 --> 0:08:58.320
<v Speaker 1>but a computer can't handle that. A computer has a

0:08:58.360 --> 0:09:02.640
<v Speaker 1>limited capacity, so programmers use floating point numbers, so called

0:09:02.640 --> 0:09:06.000
<v Speaker 1>because the decimal point has no fixed number of digits

0:09:06.040 --> 0:09:09.720
<v Speaker 1>that have to appear before or after it. This allows

0:09:09.760 --> 0:09:13.600
<v Speaker 1>programmers to represent numbers separated by many orders of magnitude.

0:09:13.600 --> 0:09:16.960
<v Speaker 1>You can have incredibly large numbers paired with incredibly small

0:09:17.040 --> 0:09:21.600
<v Speaker 1>numbers using this approach. UH typically you would use a

0:09:21.679 --> 0:09:25.319
<v Speaker 1>variant of scientific notation for those really big or really

0:09:25.360 --> 0:09:28.440
<v Speaker 1>small numbers. However, this does mean that much of the

0:09:28.440 --> 0:09:34.080
<v Speaker 1>work computers do happens as approximations rather than as precise calculations,

0:09:34.720 --> 0:09:38.559
<v Speaker 1>and this introduces the possibility of error. The more you

0:09:38.760 --> 0:09:42.880
<v Speaker 1>are approximating something, the less accurate or precise it's going

0:09:42.920 --> 0:09:46.440
<v Speaker 1>to be, particularly as you perform more calculations based on

0:09:46.559 --> 0:09:51.360
<v Speaker 1>previous approximations. As these approximations start to add up, you

0:09:51.440 --> 0:09:55.160
<v Speaker 1>can potentially get further and further away from a correct

0:09:55.280 --> 0:09:58.520
<v Speaker 1>or true answer. But never mind that that's a discussion

0:09:58.520 --> 0:10:01.439
<v Speaker 1>for a different episode. Now, after the four a D six,

0:10:01.800 --> 0:10:05.600
<v Speaker 1>Intel came out with the first Pentium processor. So why

0:10:05.600 --> 0:10:08.439
<v Speaker 1>did Intel change things up? Why did Intel go from

0:10:08.440 --> 0:10:11.679
<v Speaker 1>four D six to pentium? Because the Pentium still followed

0:10:11.720 --> 0:10:14.720
<v Speaker 1>the x A D six architecture and instruction set and

0:10:14.760 --> 0:10:19.280
<v Speaker 1>spoiler alert, so do today's computers. So why would Intel

0:10:19.400 --> 0:10:22.760
<v Speaker 1>choose pentium instead of sticking with the naming convention it

0:10:22.800 --> 0:10:25.880
<v Speaker 1>had created. Why wasn't it the five eight six? Well,

0:10:25.920 --> 0:10:28.520
<v Speaker 1>the main reason was, as I'm sure many of you

0:10:28.720 --> 0:10:33.040
<v Speaker 1>have guessed that companies like A m D were the

0:10:33.080 --> 0:10:35.760
<v Speaker 1>cause of this. Intel decided because of a m D,

0:10:36.240 --> 0:10:40.640
<v Speaker 1>Intel couldn't trademark a number. Intel couldn't have five eighty

0:10:40.720 --> 0:10:44.080
<v Speaker 1>six trademarked. You can't just trademarket basic number like that.

0:10:44.200 --> 0:10:47.760
<v Speaker 1>So if it had stuck with the numbering system, a

0:10:47.920 --> 0:10:50.000
<v Speaker 1>m D could then come out with its A m

0:10:50.120 --> 0:10:53.040
<v Speaker 1>D five a D six and with its reputation for

0:10:53.080 --> 0:10:59.520
<v Speaker 1>outpacing Intel's comparable chips, that could hurt Intel's sales. But Pentium,

0:11:00.080 --> 0:11:02.439
<v Speaker 1>that was different because Pentium was a name. You can

0:11:02.480 --> 0:11:06.240
<v Speaker 1>trademark a name, and that's what Intel did. It trademarked

0:11:06.280 --> 0:11:10.000
<v Speaker 1>the term pentium, which prevented a m D and other

0:11:10.040 --> 0:11:14.280
<v Speaker 1>competitors from using that name on their own chips. So

0:11:14.480 --> 0:11:19.120
<v Speaker 1>now it added a marketing concern for these competitors. How

0:11:19.160 --> 0:11:22.600
<v Speaker 1>would they be able to market their own chips and

0:11:22.720 --> 0:11:28.120
<v Speaker 1>compare them against Intel's chips without using a trademarked name

0:11:28.200 --> 0:11:30.199
<v Speaker 1>that they did not have the rights to. It was

0:11:30.280 --> 0:11:33.160
<v Speaker 1>kind of throwing a monkey wrench into things. Now. The

0:11:33.200 --> 0:11:36.480
<v Speaker 1>way companies got around this was to include a number

0:11:36.640 --> 0:11:40.640
<v Speaker 1>that they referred to as PR, which essentially stood for

0:11:40.800 --> 0:11:45.080
<v Speaker 1>pentium rating. The number next to the PR designation would

0:11:45.120 --> 0:11:48.800
<v Speaker 1>indicate the comparable pentium clock speed that the chip in

0:11:48.920 --> 0:11:53.800
<v Speaker 1>question would be most like. So if you came out

0:11:53.840 --> 0:11:56.600
<v Speaker 1>with a microchip and you gave it a PR rating

0:11:56.679 --> 0:12:00.520
<v Speaker 1>of one hundred, what that tells the end consumer is

0:12:00.559 --> 0:12:03.440
<v Speaker 1>that the chip you have put out is equivalent to

0:12:03.520 --> 0:12:06.360
<v Speaker 1>an Intel pentium processor that has a clock speed of

0:12:06.440 --> 0:12:08.960
<v Speaker 1>one mega hurts. So it's kind of a way of

0:12:09.000 --> 0:12:12.400
<v Speaker 1>getting around the fact that they could not call their

0:12:12.400 --> 0:12:16.640
<v Speaker 1>own chips their variance of the Pendium processor. Now it

0:12:16.720 --> 0:12:18.840
<v Speaker 1>was clear that Intel was going to put up a

0:12:18.880 --> 0:12:21.880
<v Speaker 1>fight and resist as much as it could. It would

0:12:21.920 --> 0:12:24.400
<v Speaker 1>make little sense for a m D to depend solely

0:12:24.480 --> 0:12:28.560
<v Speaker 1>upon being a second source for Intel. Chips, particularly when

0:12:28.600 --> 0:12:32.640
<v Speaker 1>Intel wasn't really interested in cooperating fully, and so A

0:12:32.800 --> 0:12:35.800
<v Speaker 1>m D began work on designing its own x eight

0:12:35.960 --> 0:12:40.920
<v Speaker 1>six based microprocessor, which would be released in n and

0:12:40.960 --> 0:12:43.840
<v Speaker 1>it became known as the A m D K five.

0:12:44.559 --> 0:12:47.760
<v Speaker 1>Well why was it called the K five? Well, by

0:12:47.840 --> 0:12:50.920
<v Speaker 1>A m D s reckoning, it represented the fifth generation

0:12:51.000 --> 0:12:54.080
<v Speaker 1>microprocessor family that A m D had built, the other

0:12:54.120 --> 0:12:57.640
<v Speaker 1>four being second source Intel chips, but the K five

0:12:58.080 --> 0:13:01.040
<v Speaker 1>was a totally new architecture that was based on the

0:13:01.200 --> 0:13:07.240
<v Speaker 1>x A D six instruction set. So why the K Well,

0:13:07.280 --> 0:13:12.199
<v Speaker 1>because K is also the letter that starts the word kryptonite,

0:13:12.600 --> 0:13:16.280
<v Speaker 1>the substance that could bring down Superman. And I think

0:13:16.280 --> 0:13:21.400
<v Speaker 1>we can all guess who was Superman in this particular scenario.

0:13:22.360 --> 0:13:25.320
<v Speaker 1>A m D designed the K five entirely in house,

0:13:25.640 --> 0:13:27.720
<v Speaker 1>and it was the first x A D six processor

0:13:27.800 --> 0:13:30.000
<v Speaker 1>from A m D to have architecture designed by the

0:13:30.040 --> 0:13:33.320
<v Speaker 1>A m D team itself, as opposed to either following

0:13:33.320 --> 0:13:38.040
<v Speaker 1>Intel's detailed instructions to make a clone of their chips

0:13:38.160 --> 0:13:42.320
<v Speaker 1>or through reverse engineering and existing Intel microchip. The K

0:13:42.480 --> 0:13:46.000
<v Speaker 1>five copied some elements from the earlier A M twenty

0:13:46.080 --> 0:13:50.280
<v Speaker 1>nine thousand microprocessor that was a risk or R I

0:13:50.640 --> 0:13:53.720
<v Speaker 1>s C microchip the company made a few years earlier.

0:13:53.760 --> 0:13:57.360
<v Speaker 1>I talked about that in the previous episode, and I

0:13:57.400 --> 0:14:00.640
<v Speaker 1>think that was a pretty good choice. It gave them

0:14:00.679 --> 0:14:04.080
<v Speaker 1>a starting point to work from, and they were able

0:14:04.080 --> 0:14:06.439
<v Speaker 1>to really build on that and make a success out

0:14:06.480 --> 0:14:11.080
<v Speaker 1>of it. The K five's design was a little bit complicated,

0:14:11.120 --> 0:14:13.640
<v Speaker 1>and that placed limits on how much clock speed a

0:14:13.800 --> 0:14:15.280
<v Speaker 1>m D could get out of it. But at the

0:14:15.320 --> 0:14:18.240
<v Speaker 1>same time, the A m D engineers had made the

0:14:18.240 --> 0:14:22.240
<v Speaker 1>operations really efficient, so while it might have a technically

0:14:22.360 --> 0:14:28.040
<v Speaker 1>lower clock speed than a competing microprocessor, this increased efficiency

0:14:28.080 --> 0:14:31.200
<v Speaker 1>helped balance things out so that at the end result

0:14:32.040 --> 0:14:34.520
<v Speaker 1>it seemed like the K five was actually faster than

0:14:34.560 --> 0:14:38.280
<v Speaker 1>its counterparts that technically had higher clock speeds. Yes, the

0:14:38.320 --> 0:14:42.720
<v Speaker 1>other microprocessors could run more operations per second, but K

0:14:42.880 --> 0:14:45.280
<v Speaker 1>five's efficiency was such that was able to make up

0:14:45.280 --> 0:14:48.080
<v Speaker 1>for that lost ground. Now, when we come back, i'll

0:14:48.120 --> 0:14:50.720
<v Speaker 1>talk more about a m d s experiences in the

0:14:50.800 --> 0:14:55.040
<v Speaker 1>nineteen nineties and beyond, but first let's take a quick break.

0:15:02.440 --> 0:15:04.520
<v Speaker 1>A m D would follow up the K five with

0:15:04.560 --> 0:15:08.960
<v Speaker 1>a microprocessor called the now wait for it, the Case six,

0:15:09.360 --> 0:15:12.680
<v Speaker 1>But the K six wasn't designed by a m D engineers,

0:15:13.000 --> 0:15:16.520
<v Speaker 1>nor did it follow the K five architecture. Instead, A

0:15:16.680 --> 0:15:20.880
<v Speaker 1>m D acquired another microchip manufacturing company called next Gen

0:15:21.160 --> 0:15:24.400
<v Speaker 1>an e x G E N. Next Gen was getting

0:15:24.440 --> 0:15:27.560
<v Speaker 1>ready to release a CPU it called the n X

0:15:27.640 --> 0:15:30.680
<v Speaker 1>six eight six, but then A m D swooped in,

0:15:31.000 --> 0:15:34.200
<v Speaker 1>bought up next Gen, and then repurpose the as yet

0:15:34.320 --> 0:15:38.200
<v Speaker 1>unreleased n X six eight six to become the K six.

0:15:38.560 --> 0:15:41.680
<v Speaker 1>A m D marketed it as an alternative for Intel's

0:15:41.680 --> 0:15:45.440
<v Speaker 1>Pentium two processor, claiming that for less money you could

0:15:45.440 --> 0:15:49.280
<v Speaker 1>get the same level of performance, and that was mostly true,

0:15:49.480 --> 0:15:52.920
<v Speaker 1>though the Pentium two had some advantages over the Case six,

0:15:53.240 --> 0:15:57.880
<v Speaker 1>namely a better math coprocessor or FPU. At this point,

0:15:58.240 --> 0:16:00.840
<v Speaker 1>the K six and the variance I'll talk about in

0:16:00.880 --> 0:16:05.560
<v Speaker 1>a second we're still compatible with Intel designed motherboards. The

0:16:05.640 --> 0:16:09.000
<v Speaker 1>Case six was also cheaper than the pent Um two chips,

0:16:09.280 --> 0:16:11.640
<v Speaker 1>and so the Case six became a popular choice for

0:16:11.720 --> 0:16:14.360
<v Speaker 1>both O E M s and people building their own machines.

0:16:14.920 --> 0:16:17.080
<v Speaker 1>A m D would follow up the Case six with

0:16:17.160 --> 0:16:21.840
<v Speaker 1>the Case six two and the Case six three in nine.

0:16:23.240 --> 0:16:26.320
<v Speaker 1>The Case six three paired two hundred fifty six L

0:16:26.400 --> 0:16:29.480
<v Speaker 1>two cash memory on the CPU die in an effort

0:16:29.480 --> 0:16:32.800
<v Speaker 1>to speed up processing and increasing the amount of data

0:16:32.920 --> 0:16:36.000
<v Speaker 1>the CPU could access at any given time. The Case

0:16:36.000 --> 0:16:40.160
<v Speaker 1>six too, was phenomenally successful, so much so that some

0:16:40.240 --> 0:16:44.720
<v Speaker 1>analysts estimated that seventy percent of the under one thousand

0:16:44.720 --> 0:16:48.800
<v Speaker 1>dollar PC market in nine had a m D K

0:16:49.000 --> 0:16:52.520
<v Speaker 1>six two chips powering them. So, if you were building

0:16:52.840 --> 0:16:54.680
<v Speaker 1>a computer on a budget and you wanted to get

0:16:54.720 --> 0:16:58.360
<v Speaker 1>the most umph for your dollars, chances are you were

0:16:58.360 --> 0:17:01.120
<v Speaker 1>going with a m D. The company would also release

0:17:01.200 --> 0:17:04.440
<v Speaker 1>the Case six two plus in the Case six three

0:17:04.480 --> 0:17:08.320
<v Speaker 1>plus in two thousands. These were microprocessors meant specifically for

0:17:08.359 --> 0:17:12.119
<v Speaker 1>the mobile market, and they'd be the final entries in

0:17:12.160 --> 0:17:17.200
<v Speaker 1>the Case six line of CPUs. Meanwhile, Jerry Sanders, whom

0:17:17.240 --> 0:17:18.960
<v Speaker 1>you might remember from the first episode, he was the

0:17:19.000 --> 0:17:21.359
<v Speaker 1>first president of a m D. He was a co

0:17:21.520 --> 0:17:25.480
<v Speaker 1>founder and at this point was the CEO of the company,

0:17:25.760 --> 0:17:29.760
<v Speaker 1>was riding high. He predicted astronomical share prices for the

0:17:29.760 --> 0:17:33.320
<v Speaker 1>company in the near future. He continued the company's practice

0:17:33.640 --> 0:17:37.560
<v Speaker 1>of building fabrication plants at a breakneck pace. He was

0:17:37.600 --> 0:17:42.360
<v Speaker 1>building plants to manufacture microprocessors and semiconductor chips all over

0:17:42.359 --> 0:17:46.040
<v Speaker 1>the world. A m D had been incredibly aggressive in

0:17:46.119 --> 0:17:49.480
<v Speaker 1>building and staffing these fabrication facilities in order to meet

0:17:49.520 --> 0:17:54.000
<v Speaker 1>the demand for microprocessors and actually to anticipate the next

0:17:54.160 --> 0:17:58.760
<v Speaker 1>demand for them, and Sanders had adopted a reportedly lavish lifestyle,

0:17:58.880 --> 0:18:02.360
<v Speaker 1>maintaining an off us in Beverly Hills, which is pretty

0:18:02.440 --> 0:18:06.080
<v Speaker 1>darn far from Silicon Valley and the headquarters of a

0:18:06.200 --> 0:18:08.359
<v Speaker 1>m D. I guess he never really gave up his

0:18:08.480 --> 0:18:12.240
<v Speaker 1>dream of going into the recording industry, but a lavish

0:18:12.280 --> 0:18:15.400
<v Speaker 1>lifestyle might be fine if things continued to go well

0:18:15.440 --> 0:18:18.320
<v Speaker 1>for the company, and sadly that would not be the case.

0:18:18.760 --> 0:18:22.199
<v Speaker 1>Sanders spending also seemed to trickle its way into the

0:18:22.240 --> 0:18:25.440
<v Speaker 1>corporate culture of a m D overall, with executives and

0:18:25.520 --> 0:18:29.000
<v Speaker 1>high ranking salesforce professionals spending greater amounts of money to

0:18:29.040 --> 0:18:34.000
<v Speaker 1>curate an image of luxury and sophistication. Spending was getting

0:18:34.000 --> 0:18:36.320
<v Speaker 1>out of hand, and a lot of that spending had

0:18:36.359 --> 0:18:40.400
<v Speaker 1>to do with those fabrication facilities. According to Autika Raza,

0:18:40.600 --> 0:18:43.959
<v Speaker 1>who had led next Gen before a m D had

0:18:43.960 --> 0:18:47.080
<v Speaker 1>acquired that company and then later became the president and

0:18:47.160 --> 0:18:51.960
<v Speaker 1>chief operating officer or CEO of a m D. Sanders

0:18:52.240 --> 0:18:55.960
<v Speaker 1>was in a bad habit of building fabrication facilities too

0:18:55.960 --> 0:19:01.240
<v Speaker 1>far in advance, at least according to Raza's analysis. His perspective,

0:19:01.400 --> 0:19:04.760
<v Speaker 1>that is, Roza's perspective, was that the company should hold

0:19:04.840 --> 0:19:09.480
<v Speaker 1>off building new facilities until the need was there. Sanders

0:19:09.760 --> 0:19:12.400
<v Speaker 1>was building them ahead of the game, but that would

0:19:12.480 --> 0:19:15.560
<v Speaker 1>mean that a m D was constantly raising money to

0:19:15.600 --> 0:19:18.720
<v Speaker 1>build out the next facility in advance of any revenue

0:19:18.840 --> 0:19:21.919
<v Speaker 1>it was generating, and if the industry were to ever dip,

0:19:22.160 --> 0:19:25.040
<v Speaker 1>then it would leave a m D over extended. So

0:19:25.160 --> 0:19:28.000
<v Speaker 1>Raza wanted to take a different route. He wanted to

0:19:28.119 --> 0:19:32.320
<v Speaker 1>use revenues from current successes to fuel expansion on an

0:19:32.359 --> 0:19:34.879
<v Speaker 1>as needed basis. In other words, you don't need to

0:19:34.880 --> 0:19:37.320
<v Speaker 1>go out and build a new fabrication plant until the

0:19:37.400 --> 0:19:41.080
<v Speaker 1>demand requires you to do it. Raza, who at one

0:19:41.080 --> 0:19:44.000
<v Speaker 1>time had been viewed as a potential successor to Sanders,

0:19:44.240 --> 0:19:47.879
<v Speaker 1>found himself in direct disagreement with the founder, and he

0:19:47.920 --> 0:19:51.760
<v Speaker 1>would actually leave a m D in n reportedly after

0:19:51.840 --> 0:19:54.440
<v Speaker 1>a massive falling out with Sanders, with whom he would

0:19:54.480 --> 0:19:58.520
<v Speaker 1>never speak again. Now his successor was a guy named

0:19:58.640 --> 0:20:02.480
<v Speaker 1>Hector Ruez, who had up to that time been heading

0:20:02.560 --> 0:20:06.240
<v Speaker 1>up a division over at Motorola. Ruez was first wary

0:20:06.400 --> 0:20:11.040
<v Speaker 1>of taking this job. It was more technically oriented industry

0:20:11.080 --> 0:20:13.800
<v Speaker 1>than he had been used to, and he knew about

0:20:13.880 --> 0:20:18.520
<v Speaker 1>Sanders and his reputation of alienating senior level staff. And

0:20:18.640 --> 0:20:20.440
<v Speaker 1>he saw that there had been a string of chief

0:20:20.440 --> 0:20:24.960
<v Speaker 1>operating officers, several of whom were rumored to be groomed

0:20:25.080 --> 0:20:28.000
<v Speaker 1>as the heir apparent to a m D who had

0:20:28.000 --> 0:20:31.640
<v Speaker 1>subsequently left the company. But he figured that Sanders might

0:20:31.720 --> 0:20:36.360
<v Speaker 1>have issues relinquishing control to others, that this could cause issues,

0:20:36.560 --> 0:20:42.280
<v Speaker 1>but Sanders was still a very impressive person. A m

0:20:42.359 --> 0:20:44.880
<v Speaker 1>D was an impressive company, so Hector decided to take

0:20:44.880 --> 0:20:48.879
<v Speaker 1>the job. Then Jerry Sanders would retire in the early

0:20:48.920 --> 0:20:51.879
<v Speaker 1>two thousand's and Ruez would take over the company, and

0:20:51.920 --> 0:20:54.639
<v Speaker 1>he began to clean house. He got rid of several

0:20:54.680 --> 0:20:57.920
<v Speaker 1>top executives who had been around for quite some time

0:20:57.920 --> 0:21:01.240
<v Speaker 1>in the Sanders era, and he started bring in new people,

0:21:01.320 --> 0:21:05.160
<v Speaker 1>new talent. So Ruiz also saw that the market was changing,

0:21:05.760 --> 0:21:08.440
<v Speaker 1>and while a m D was being innovative in CPUs

0:21:08.520 --> 0:21:12.760
<v Speaker 1>and other microchips meant for personal computers, it was really

0:21:12.800 --> 0:21:17.520
<v Speaker 1>making most of its profits from selling flash memory not CPUs,

0:21:18.000 --> 0:21:21.520
<v Speaker 1>and so he started to refocus the company to that endeavor,

0:21:21.680 --> 0:21:24.159
<v Speaker 1>but he also found that a m D was holding

0:21:24.240 --> 0:21:27.040
<v Speaker 1>an odd place in the market. Ruez would write a

0:21:27.040 --> 0:21:30.879
<v Speaker 1>book about his experiences, stating that Sanders had created this

0:21:31.200 --> 0:21:34.439
<v Speaker 1>sort of weird paradox in a m D because Sanders

0:21:34.480 --> 0:21:37.080
<v Speaker 1>had a real can do attitude, a a never say

0:21:37.280 --> 0:21:41.040
<v Speaker 1>die approach to business. But at the same time, no

0:21:41.119 --> 0:21:43.600
<v Speaker 1>one in the company ever seemed convinced that a m

0:21:43.680 --> 0:21:46.320
<v Speaker 1>D could really go toe to toe with Intel, that

0:21:46.400 --> 0:21:49.400
<v Speaker 1>a m D would always be a tiny company compared

0:21:49.440 --> 0:21:53.480
<v Speaker 1>to Intel, that could never really take over as the

0:21:53.680 --> 0:21:58.040
<v Speaker 1>leading microchip manufacturer in the industry. That that was just

0:21:58.080 --> 0:22:02.000
<v Speaker 1>sort of this underlineing philosophy at a m D. And

0:22:02.000 --> 0:22:04.640
<v Speaker 1>as possibly because a m D had built its business

0:22:04.720 --> 0:22:08.400
<v Speaker 1>largely on being a second source chip company. So Rule

0:22:08.440 --> 0:22:10.840
<v Speaker 1>has tried to change things, directing a m d s

0:22:10.880 --> 0:22:14.360
<v Speaker 1>efforts at not just flash memory, but also developing premium

0:22:14.400 --> 0:22:18.200
<v Speaker 1>processors for stuff like Internet servers, which were just starting

0:22:18.200 --> 0:22:21.240
<v Speaker 1>to become a serious thing at the time. Now, around

0:22:21.280 --> 0:22:23.920
<v Speaker 1>that same time, a m D and Intel faced off

0:22:24.000 --> 0:22:27.840
<v Speaker 1>again in courtrooms. This time it was in the European Union.

0:22:28.280 --> 0:22:31.199
<v Speaker 1>A m D complained to the European Commission that Intel

0:22:31.280 --> 0:22:35.399
<v Speaker 1>was engaging in anti competitive behavior, violating the law, primarily

0:22:35.720 --> 0:22:39.960
<v Speaker 1>through what am D described as abusive marketing campaigns. A

0:22:40.119 --> 0:22:42.520
<v Speaker 1>m D even tried to use legal means to secure

0:22:42.560 --> 0:22:46.359
<v Speaker 1>documents from a separate case against Intel. This one was

0:22:46.400 --> 0:22:50.080
<v Speaker 1>brought against Intel by a company called Intergraph. But then

0:22:50.160 --> 0:22:54.080
<v Speaker 1>the Intergraph case eventually settled out of court and things

0:22:54.119 --> 0:22:58.760
<v Speaker 1>were obviously still very choppy between a m D and Intel,

0:22:58.920 --> 0:23:02.600
<v Speaker 1>despite the fact that they still had this cross licensing agreement.

0:23:03.359 --> 0:23:05.639
<v Speaker 1>The next chip from a m D, the Case seven,

0:23:05.800 --> 0:23:10.320
<v Speaker 1>better known as the Athlon processor, changed things up again.

0:23:10.600 --> 0:23:13.760
<v Speaker 1>Now the details get pretty technical, but an easy thing

0:23:13.800 --> 0:23:16.320
<v Speaker 1>to understand is that the company was able to push

0:23:16.359 --> 0:23:19.840
<v Speaker 1>clock rates up to one giga hurts. A m D

0:23:20.000 --> 0:23:23.879
<v Speaker 1>also began to manufacture its own motherboards, anticipating that the

0:23:23.960 --> 0:23:27.840
<v Speaker 1>day might come when compatibility with Intel's motherboards would come

0:23:27.880 --> 0:23:30.600
<v Speaker 1>to an end. So, hey, what the heck is a motherboard?

0:23:30.600 --> 0:23:32.600
<v Speaker 1>I mentioned it a couple of times in this episode.

0:23:33.040 --> 0:23:36.480
<v Speaker 1>A motherboard is just a printed circuit board. It's sort

0:23:36.520 --> 0:23:40.560
<v Speaker 1>of the highway system for information inside a computer. The

0:23:40.640 --> 0:23:44.560
<v Speaker 1>motherboard typically has connectors into which you can plug other

0:23:44.680 --> 0:23:47.520
<v Speaker 1>circuits like a CPU as a circuit, so you can

0:23:47.520 --> 0:23:51.520
<v Speaker 1>plug a CPU into a motherboard or a GPU a

0:23:51.520 --> 0:23:56.080
<v Speaker 1>graphics processing unit. The motherboard provides the physical connections between

0:23:56.119 --> 0:23:59.399
<v Speaker 1>all these different components so that these circuits can send

0:23:59.400 --> 0:24:02.360
<v Speaker 1>proper command ends to the right places. Now, not all

0:24:02.440 --> 0:24:07.480
<v Speaker 1>CPUs or GPUs for that matter, are compatible with all motherboards.

0:24:07.800 --> 0:24:11.240
<v Speaker 1>Motherboards can accept certain types of CPUs and not others,

0:24:11.640 --> 0:24:14.679
<v Speaker 1>and that's one of the reasons it's really important to

0:24:14.800 --> 0:24:17.880
<v Speaker 1>research first before you set out to build your first computer.

0:24:18.240 --> 0:24:22.160
<v Speaker 1>It's entirely possible to pick up sweet components that look

0:24:22.240 --> 0:24:26.520
<v Speaker 1>great on paper but ultimately won't work together because they're incompatible.

0:24:26.760 --> 0:24:29.240
<v Speaker 1>So a m D set out to build its own

0:24:29.280 --> 0:24:33.040
<v Speaker 1>computer platform. But in this case, Intel was able to

0:24:33.160 --> 0:24:36.320
<v Speaker 1>outperform a m D. While a m d S processors

0:24:36.320 --> 0:24:40.000
<v Speaker 1>were blazing, the motherboard chip set as a whole wasn't

0:24:40.040 --> 0:24:45.639
<v Speaker 1>quite able to match Intel's four four zero b X component. Still,

0:24:45.720 --> 0:24:47.520
<v Speaker 1>it showed that a m D was going to push

0:24:47.640 --> 0:24:51.320
<v Speaker 1>hard to compete with Intel. A m D also introduced

0:24:51.520 --> 0:24:54.880
<v Speaker 1>a new line of chips designed for entry level machines.

0:24:55.240 --> 0:24:58.600
<v Speaker 1>These were running on a similar architecture as the Athalon processors,

0:24:58.720 --> 0:25:01.040
<v Speaker 1>but that will lower clock speed. They called the new

0:25:01.119 --> 0:25:05.400
<v Speaker 1>line of processors DURAN, and they competed against Intel's Cellern

0:25:05.560 --> 0:25:08.639
<v Speaker 1>line of processors meant for the same market. A m

0:25:08.760 --> 0:25:12.000
<v Speaker 1>D upgraded the Athlon family steadily year over year with

0:25:12.160 --> 0:25:16.600
<v Speaker 1>names like Thunderbird, Palomino, Thoroughbred, and Barton. With each chip,

0:25:16.760 --> 0:25:18.959
<v Speaker 1>a m D built upon what it had learned from

0:25:19.000 --> 0:25:23.560
<v Speaker 1>the previous generation. The components sizes got smaller, Thoroughbred and

0:25:23.600 --> 0:25:27.320
<v Speaker 1>Barton were built using a one thirty nanometer process and

0:25:27.359 --> 0:25:30.440
<v Speaker 1>the clock speeds were climbing past two giga hurts. A

0:25:30.600 --> 0:25:33.560
<v Speaker 1>m D was optimizing the architecture for memory access. Things

0:25:33.600 --> 0:25:37.280
<v Speaker 1>were going pretty smoothly, and then a m D dropped

0:25:37.359 --> 0:25:40.320
<v Speaker 1>a bombshell. The company that had built a business out

0:25:40.359 --> 0:25:45.200
<v Speaker 1>of being a second source chip manufacturer actually beat Intel

0:25:45.280 --> 0:25:49.680
<v Speaker 1>to the punch by releasing the first consumer oriented sixty

0:25:49.760 --> 0:25:54.800
<v Speaker 1>four bit x eight six processor, the Athalon sixty four. Now,

0:25:54.840 --> 0:25:57.480
<v Speaker 1>I've been explaining a lot of basic computer concepts here,

0:25:57.520 --> 0:26:00.520
<v Speaker 1>so why not include sixty four bit? Ver is thirty

0:26:00.520 --> 0:26:03.679
<v Speaker 1>two bit? So the consumer focused processors up to that

0:26:03.760 --> 0:26:07.560
<v Speaker 1>point where thirty two bit processors. That means the processors

0:26:07.560 --> 0:26:10.040
<v Speaker 1>were able to work with data units that were thirty

0:26:10.040 --> 0:26:14.080
<v Speaker 1>two bits wide. Now, remember a bit is a single

0:26:14.200 --> 0:26:17.119
<v Speaker 1>unit of information. It can be either a zero or

0:26:17.160 --> 0:26:20.720
<v Speaker 1>a one. Eight bits is a byte or an octet,

0:26:21.080 --> 0:26:24.159
<v Speaker 1>and thirty two bits would be four octets wide. A

0:26:24.240 --> 0:26:27.280
<v Speaker 1>thirty two bit system can handle a range of two

0:26:27.359 --> 0:26:31.520
<v Speaker 1>to the thirty second power number of values. So if

0:26:31.520 --> 0:26:34.119
<v Speaker 1>we want to describe all the values that a thirty

0:26:34.119 --> 0:26:36.840
<v Speaker 1>two bit number can describe, and we start with the

0:26:36.920 --> 0:26:39.720
<v Speaker 1>number zero, we would go all the way up to

0:26:40.160 --> 0:26:44.040
<v Speaker 1>four billion, two hundred ninety four million, nine hundred sixty

0:26:44.080 --> 0:26:48.159
<v Speaker 1>seven thousand, two hundred nine five. That's the range of

0:26:48.240 --> 0:26:51.520
<v Speaker 1>values a thirty two bit system can handle. Now, as

0:26:51.560 --> 0:26:55.320
<v Speaker 1>the name implies, a sixty four bit system can handle

0:26:55.320 --> 0:26:59.240
<v Speaker 1>a data width of sixty four bits, And you might

0:26:59.280 --> 0:27:01.440
<v Speaker 1>be tempted to think that that means it can handle

0:27:01.480 --> 0:27:04.399
<v Speaker 1>twice as much data as a thirty two bit system,

0:27:04.480 --> 0:27:07.560
<v Speaker 1>but that's not how binary works. A sixty four bit

0:27:07.640 --> 0:27:10.199
<v Speaker 1>system can handle a value range of two to the

0:27:10.320 --> 0:27:14.840
<v Speaker 1>sixty four power of values, which is more than eighteen

0:27:15.080 --> 0:27:21.240
<v Speaker 1>quintillion values. That is a very big number, much much

0:27:21.280 --> 0:27:23.880
<v Speaker 1>bigger than the eight and a half billion or so

0:27:24.440 --> 0:27:27.440
<v Speaker 1>that would be twice the thirty two bit range values,

0:27:27.440 --> 0:27:31.480
<v Speaker 1>so you're not talking about doubling, you're talking much much

0:27:31.600 --> 0:27:34.400
<v Speaker 1>larger than that. So a sixty four bit system can

0:27:34.440 --> 0:27:38.200
<v Speaker 1>perform many more calculations per second. It can also support

0:27:38.240 --> 0:27:41.200
<v Speaker 1>more RAM. A thirty two bit system maxes out at

0:27:41.200 --> 0:27:43.840
<v Speaker 1>four gigabytes of RAM, or two to the thirty second

0:27:43.920 --> 0:27:47.480
<v Speaker 1>power bytes of memory. A sixty four bit system would

0:27:47.520 --> 0:27:51.320
<v Speaker 1>max out at least in theory at eighteen XO bytes

0:27:51.640 --> 0:27:55.760
<v Speaker 1>of RAM, which I can't describe as anything other than

0:27:55.880 --> 0:28:00.280
<v Speaker 1>a crap ton of random access memory. But six four

0:28:00.320 --> 0:28:04.280
<v Speaker 1>bit CPUs can't quite reach that theoretical limit, and they

0:28:04.320 --> 0:28:08.080
<v Speaker 1>max out in the terrabyte scale, not the exo byte scale. Still,

0:28:08.119 --> 0:28:11.360
<v Speaker 1>that's a lot more memory than thirty two bit systems

0:28:11.400 --> 0:28:14.520
<v Speaker 1>can handle. Now, sixty four bit systems had been around

0:28:14.520 --> 0:28:17.320
<v Speaker 1>since the nineteen sixties, but had only seen use in

0:28:17.359 --> 0:28:21.440
<v Speaker 1>academic settings and internally in various companies. No one had

0:28:21.520 --> 0:28:24.479
<v Speaker 1>yet made a sixty four bit processor for the general

0:28:24.520 --> 0:28:28.520
<v Speaker 1>public before A. M D and Microsoft released a sixty

0:28:28.520 --> 0:28:31.919
<v Speaker 1>four bit version of Windows that such processors could leverage.

0:28:32.240 --> 0:28:34.600
<v Speaker 1>And just to be clear, a thirty two bit system

0:28:34.720 --> 0:28:38.200
<v Speaker 1>can't run sixty four bit software, but most sixty four

0:28:38.200 --> 0:28:40.840
<v Speaker 1>bit systems can run either a thirty two bit or

0:28:40.880 --> 0:28:44.240
<v Speaker 1>a sixty four bit version of operating systems. Now, I've

0:28:44.280 --> 0:28:46.040
<v Speaker 1>got some more to say about what a m D

0:28:46.160 --> 0:28:49.360
<v Speaker 1>has been up to, but first let's take another quick break.

0:28:56.760 --> 0:28:59.160
<v Speaker 1>Am D, for the first time, had been the first

0:28:59.240 --> 0:29:03.240
<v Speaker 1>to market with a microchip innovation. This led to Intel

0:29:03.320 --> 0:29:06.800
<v Speaker 1>licensing the sixty four bit instruction set from a m D.

0:29:07.440 --> 0:29:12.960
<v Speaker 1>Ah how the tables have turned Now, Intel, so used

0:29:13.000 --> 0:29:16.760
<v Speaker 1>to being the entity to define standards was instead having

0:29:16.800 --> 0:29:20.200
<v Speaker 1>to follow the lead of the upstart company. No never

0:29:20.240 --> 0:29:22.400
<v Speaker 1>mind that both Intel and am D had been around

0:29:22.400 --> 0:29:24.360
<v Speaker 1>since the late nineteen sixties, and a m D was

0:29:24.400 --> 0:29:27.280
<v Speaker 1>really just a year younger than Intel was. I can

0:29:27.280 --> 0:29:30.720
<v Speaker 1>only imagine things were tense in some of those meetings

0:29:30.720 --> 0:29:33.680
<v Speaker 1>over at Intel headquarters, and a m D wasn't done

0:29:33.760 --> 0:29:36.600
<v Speaker 1>knocking the socks off computer nerds like me. In two

0:29:36.600 --> 0:29:42.360
<v Speaker 1>thousand five, the company released the athlont X two micro processor,

0:29:42.600 --> 0:29:46.960
<v Speaker 1>which was the first x a D six dual core processor. Now,

0:29:47.000 --> 0:29:50.040
<v Speaker 1>these days, multi core processors are the norm for many

0:29:50.120 --> 0:29:53.680
<v Speaker 1>computer systems and even handheld devices, but this was brand

0:29:53.680 --> 0:29:56.400
<v Speaker 1>new for the consumer market back in two thousand five,

0:29:56.720 --> 0:29:59.360
<v Speaker 1>So what the heck is a dual core or multi

0:29:59.360 --> 0:30:02.440
<v Speaker 1>core proces sessor. Now, I always like to use the

0:30:02.480 --> 0:30:06.760
<v Speaker 1>analogy of a math class that has one superstar pupil

0:30:07.040 --> 0:30:09.480
<v Speaker 1>and then a bunch of smart math students who don't

0:30:09.520 --> 0:30:14.400
<v Speaker 1>quite measure up to superstar status. The superstar pupil represents

0:30:14.440 --> 0:30:18.920
<v Speaker 1>a single core CPU that is significantly powerful. The smart

0:30:19.000 --> 0:30:24.040
<v Speaker 1>math students represent a multi core processor. Each individual core

0:30:24.520 --> 0:30:27.920
<v Speaker 1>of this multi core processor is less powerful than the

0:30:28.040 --> 0:30:33.720
<v Speaker 1>super strong single CPU, but collectively those students can tackle

0:30:33.800 --> 0:30:37.160
<v Speaker 1>some problems and solve them faster than the superstar. And

0:30:37.200 --> 0:30:40.720
<v Speaker 1>we refer to those types of problems as being parallel problems,

0:30:40.960 --> 0:30:45.240
<v Speaker 1>and that the cores are all executing operations in parallel

0:30:45.280 --> 0:30:49.800
<v Speaker 1>with each other rather than in sequence. So here's the example.

0:30:49.960 --> 0:30:53.600
<v Speaker 1>A math teacher hands out a pop quiz. The superstar

0:30:53.800 --> 0:30:57.360
<v Speaker 1>has to answer eight questions on the quiz, all eight.

0:30:57.840 --> 0:31:00.920
<v Speaker 1>The smart math students, of which there are eight, must

0:31:01.000 --> 0:31:04.320
<v Speaker 1>each answer just one of those questions. So students one

0:31:04.360 --> 0:31:07.080
<v Speaker 1>gets questioned one, student two gets questioned two, and so on.

0:31:07.520 --> 0:31:10.920
<v Speaker 1>So who finishes first? Now, while the superstar might get

0:31:10.960 --> 0:31:14.680
<v Speaker 1>through a couple of problems before any of the classmates

0:31:14.680 --> 0:31:18.840
<v Speaker 1>have finished his or her individual problem, Ultimately, the class

0:31:18.920 --> 0:31:22.480
<v Speaker 1>is going to finish First, they solved the test in parallel,

0:31:22.560 --> 0:31:25.440
<v Speaker 1>each taking one part of the problem. So even though

0:31:25.440 --> 0:31:28.920
<v Speaker 1>the superstar is technically better at math than they are,

0:31:29.720 --> 0:31:34.200
<v Speaker 1>they can't answer those questions in sequence as quickly as

0:31:34.240 --> 0:31:37.360
<v Speaker 1>the group can in parallel. Now, it's important to note

0:31:37.560 --> 0:31:41.560
<v Speaker 1>that not all computational problems are parallel in nature, So

0:31:41.600 --> 0:31:45.400
<v Speaker 1>for those problems, a really powerful single core processor is

0:31:45.440 --> 0:31:48.600
<v Speaker 1>going to do better than the multi core approach, and

0:31:48.760 --> 0:31:51.600
<v Speaker 1>a m D s early dual core processor couldn't work

0:31:51.680 --> 0:31:54.400
<v Speaker 1>on the same thread at all, but one core could

0:31:54.440 --> 0:31:57.320
<v Speaker 1>work on a thread of operations while the other core

0:31:57.400 --> 0:32:02.200
<v Speaker 1>worked on unrelated computational problems, and that sped things up. Overall,

0:32:02.720 --> 0:32:06.640
<v Speaker 1>both the sixty four bit consumer processor and the dual

0:32:06.680 --> 0:32:11.719
<v Speaker 1>core innovation were phenomenal achievements in the world of consumer computers.

0:32:12.120 --> 0:32:15.080
<v Speaker 1>A m D will never quite catching up to Intel's

0:32:15.160 --> 0:32:19.280
<v Speaker 1>marketing with the whole Intel inside thing, was proving itself

0:32:19.320 --> 0:32:22.040
<v Speaker 1>to be a capable and competitive player in the space,

0:32:22.400 --> 0:32:26.720
<v Speaker 1>at least on a technological level. Business Wise, things were

0:32:26.800 --> 0:32:29.560
<v Speaker 1>a bit less peppy. A m D was producing more

0:32:29.640 --> 0:32:32.840
<v Speaker 1>chips than it could sell, and that was probably part

0:32:32.880 --> 0:32:36.480
<v Speaker 1>of that whole crazy fabrication plant strategy Sanders had pursued

0:32:36.480 --> 0:32:39.880
<v Speaker 1>in the nineties. They were literally making more chips than

0:32:39.920 --> 0:32:42.880
<v Speaker 1>they had orders for. In two thousand one, a m

0:32:42.960 --> 0:32:46.760
<v Speaker 1>D posted a net loss of sixty one million dollars,

0:32:46.800 --> 0:32:49.640
<v Speaker 1>but the following year it was incredible. It was a

0:32:49.640 --> 0:32:54.000
<v Speaker 1>loss of one point three billion dollars. In two thousand

0:32:54.040 --> 0:32:57.400
<v Speaker 1>three it was another two seventy four million dollar loss.

0:32:57.960 --> 0:33:01.160
<v Speaker 1>This is not a trend you want to see, Tenue. Now,

0:33:01.160 --> 0:33:04.200
<v Speaker 1>while the company was introducing innovations, it was still battling

0:33:04.280 --> 0:33:07.920
<v Speaker 1>its nemesis, Intel in the courtrooms. A m D brought

0:33:07.960 --> 0:33:11.280
<v Speaker 1>another anti competitive suit against Intel in two thousand four

0:33:11.440 --> 0:33:14.200
<v Speaker 1>two thousand five, this time in the United States. The

0:33:14.240 --> 0:33:17.760
<v Speaker 1>complaint was forty eight pages long and accused Intel of

0:33:17.880 --> 0:33:21.520
<v Speaker 1>using a monopolistic approach to strong armed companies to work

0:33:21.520 --> 0:33:25.080
<v Speaker 1>with Intel rather than with a m D. At this point,

0:33:25.320 --> 0:33:29.280
<v Speaker 1>a m D had several lawsuits against Intel pending in

0:33:29.440 --> 0:33:33.280
<v Speaker 1>various courts, and in two thousand nine, Intel bargained a

0:33:33.360 --> 0:33:37.400
<v Speaker 1>settlement agreement with a m D. Intel executives promised that

0:33:37.440 --> 0:33:39.840
<v Speaker 1>their company would abide by a list of rules to

0:33:39.880 --> 0:33:43.520
<v Speaker 1>avoid anti competitive practices. Now, according to c NET, The

0:33:43.560 --> 0:33:45.680
<v Speaker 1>settlement included a payout to a m D to the

0:33:45.680 --> 0:33:50.400
<v Speaker 1>tune of one point to five billion dollars wolf That

0:33:50.480 --> 0:33:53.440
<v Speaker 1>certainly can help in an era where the company is

0:33:53.520 --> 0:33:58.760
<v Speaker 1>losing money through sales. Intel also would introduce its famous

0:33:58.840 --> 0:34:01.680
<v Speaker 1>tick talk Strata G, in which the company would first

0:34:01.760 --> 0:34:06.080
<v Speaker 1>design a new microchip architecture, typically by reducing the size

0:34:06.160 --> 0:34:10.759
<v Speaker 1>of the individual components from the previous generation's architecture and

0:34:10.800 --> 0:34:13.640
<v Speaker 1>then cramming more components onto a single chips So, in

0:34:13.640 --> 0:34:16.120
<v Speaker 1>other words, you say, let's take the design from the

0:34:16.239 --> 0:34:20.839
<v Speaker 1>last generation of microchips, make everything smaller, add more to it,

0:34:20.960 --> 0:34:23.600
<v Speaker 1>and release that. Then they would follow this up with

0:34:23.640 --> 0:34:26.720
<v Speaker 1>the talk part of the cycle. They would dedicate research

0:34:26.760 --> 0:34:29.840
<v Speaker 1>and development to find out how to best optimize the

0:34:29.920 --> 0:34:33.600
<v Speaker 1>new smaller components to create a new architecture that makes

0:34:33.640 --> 0:34:36.680
<v Speaker 1>the best use out of that. So the tick is

0:34:36.719 --> 0:34:41.040
<v Speaker 1>the new architecture or the new the smaller components, and

0:34:41.080 --> 0:34:44.840
<v Speaker 1>the talk was the new optimization of that. Each generation

0:34:44.880 --> 0:34:48.200
<v Speaker 1>of chips represented either a take or a talk. This

0:34:48.320 --> 0:34:52.440
<v Speaker 1>helped reduce risk and expenses on Intel's research and development

0:34:52.719 --> 0:34:55.759
<v Speaker 1>and helped the company mount a counter attack against a

0:34:55.960 --> 0:34:58.959
<v Speaker 1>m D. A m D got aggressive in the wake

0:34:59.239 --> 0:35:02.719
<v Speaker 1>of their innovation. In two thousand six, the company acquired

0:35:02.760 --> 0:35:06.879
<v Speaker 1>a graphics card company called A t I Technologies Incorporated

0:35:07.200 --> 0:35:10.880
<v Speaker 1>for more than five billion dollars. A t I had

0:35:10.960 --> 0:35:13.880
<v Speaker 1>launched in the mid eighties in Canada and had become

0:35:13.920 --> 0:35:16.880
<v Speaker 1>known for their graphics processing units, and for a while

0:35:17.120 --> 0:35:19.920
<v Speaker 1>a m D would market graphics processing cards under the

0:35:20.040 --> 0:35:23.320
<v Speaker 1>A t I brand name. In fact, in many ways,

0:35:23.520 --> 0:35:25.759
<v Speaker 1>a TI continued to perform as if it were a

0:35:25.800 --> 0:35:29.200
<v Speaker 1>subsidiary company and not a true part of a m D,

0:35:29.640 --> 0:35:33.080
<v Speaker 1>something that in hindsight, critics have suggested was a problem.

0:35:33.440 --> 0:35:36.120
<v Speaker 1>According to an Ours Technica article that was titled up

0:35:36.160 --> 0:35:38.760
<v Speaker 1>the Rise and Fall of a m D. Highly recommend

0:35:38.800 --> 0:35:40.359
<v Speaker 1>you read that, by the way, it's a two part article,

0:35:40.400 --> 0:35:44.400
<v Speaker 1>and it's fantastic. People within the company tended to gravitate

0:35:44.520 --> 0:35:47.560
<v Speaker 1>toward either the CPU side of the business or the

0:35:47.719 --> 0:35:51.200
<v Speaker 1>GPU side of the business, and both sides were competing

0:35:51.239 --> 0:35:54.680
<v Speaker 1>over the same set of resources. Now, competition within a

0:35:54.719 --> 0:35:57.839
<v Speaker 1>single company isn't always a great thing, and it led

0:35:57.880 --> 0:36:00.880
<v Speaker 1>to tension within a m D. As well's delays in

0:36:00.920 --> 0:36:05.200
<v Speaker 1>product development. A m d S CPU quality was starting

0:36:05.200 --> 0:36:10.000
<v Speaker 1>to slide as well. The Optron processor called Barcelona didn't

0:36:10.040 --> 0:36:12.719
<v Speaker 1>ship on time, and when it did finally come out,

0:36:13.080 --> 0:36:15.560
<v Speaker 1>it had a bug in the design that, when fixed,

0:36:15.880 --> 0:36:19.960
<v Speaker 1>slowed the chips performance speed by about ten percent. A

0:36:20.000 --> 0:36:25.080
<v Speaker 1>few years later, the Bulldozer processor had similar issues. In retrospect,

0:36:25.320 --> 0:36:29.160
<v Speaker 1>some engineers fault the acquisition for dividing the focus of

0:36:29.200 --> 0:36:32.480
<v Speaker 1>the company and the lack of an overall roadmap for

0:36:32.560 --> 0:36:36.480
<v Speaker 1>being the reason that the company was reeling a little bit. Meanwhile,

0:36:36.800 --> 0:36:40.520
<v Speaker 1>PC sales in general were slowing down as the world

0:36:40.520 --> 0:36:44.000
<v Speaker 1>began to shift more toward mobile computing. A m D

0:36:44.080 --> 0:36:47.319
<v Speaker 1>found itself in choppy waters again. Ru has managed to

0:36:47.360 --> 0:36:50.480
<v Speaker 1>take care of one big problem, the fabrication facilities that

0:36:50.520 --> 0:36:52.520
<v Speaker 1>were making far too many chips for a m D

0:36:52.680 --> 0:36:55.040
<v Speaker 1>to sell. He arranged a deal with a group of

0:36:55.080 --> 0:36:58.239
<v Speaker 1>investors from Abu Dhabi to sell off a m D

0:36:58.400 --> 0:37:01.839
<v Speaker 1>s fabrication plants. The idea was that m D would

0:37:01.880 --> 0:37:06.120
<v Speaker 1>negotiate production contracts with this new company, and that new

0:37:06.120 --> 0:37:10.880
<v Speaker 1>company could also accept fabrication contracts from other manufacturers, since

0:37:10.880 --> 0:37:14.480
<v Speaker 1>the production capacity for all the fabrication plants exceeded what

0:37:14.640 --> 0:37:18.200
<v Speaker 1>am D needed. Not long after that, Ruez would step

0:37:18.280 --> 0:37:21.560
<v Speaker 1>down as CEO. Dirk Meyer, who had worked on the

0:37:21.600 --> 0:37:24.640
<v Speaker 1>design of a m D s K seven chip, became

0:37:24.680 --> 0:37:27.560
<v Speaker 1>the new CEO. Alan Remember when I said A m

0:37:27.640 --> 0:37:30.399
<v Speaker 1>D and Intel settled that lawsuit in two thousand nine.

0:37:30.760 --> 0:37:33.600
<v Speaker 1>One reason a m D might have agreed to come

0:37:33.640 --> 0:37:36.640
<v Speaker 1>to the table with a settlement was that Intel lawyers

0:37:36.719 --> 0:37:39.760
<v Speaker 1>were claiming the agreement between a m D and Intel

0:37:39.880 --> 0:37:43.520
<v Speaker 1>to cross license the X eight six instruction set was

0:37:43.680 --> 0:37:46.759
<v Speaker 1>only valid if a m D was both the designer

0:37:47.080 --> 0:37:50.440
<v Speaker 1>and the fabricator of the chips. But now am D

0:37:50.520 --> 0:37:55.120
<v Speaker 1>was outsourcing fabrication and that, according to Intel's lawyers, was

0:37:55.160 --> 0:37:58.239
<v Speaker 1>in violation of the agreement. So it's possible a m

0:37:58.320 --> 0:38:00.640
<v Speaker 1>D came to the table to negotiate a settlement in

0:38:00.719 --> 0:38:04.480
<v Speaker 1>order to avoid a judgment on that point. Meyer would

0:38:04.480 --> 0:38:07.400
<v Speaker 1>serve as CEO from two thousand eight to two thousand eleven.

0:38:07.760 --> 0:38:10.080
<v Speaker 1>He was effectively removed from the position by the A

0:38:10.280 --> 0:38:13.319
<v Speaker 1>m D board analysts at the time, We're a bit surprised.

0:38:13.440 --> 0:38:16.920
<v Speaker 1>Meyer had been focusing on the traditional CPU market and

0:38:17.000 --> 0:38:20.120
<v Speaker 1>making a MD competitive there, with plans to address the

0:38:20.160 --> 0:38:22.680
<v Speaker 1>mobile market a little bit later further down the road.

0:38:22.719 --> 0:38:25.920
<v Speaker 1>He wanted to get the CPU thing right first and

0:38:25.960 --> 0:38:29.319
<v Speaker 1>then switch over to mobile. Now, it's possible that the

0:38:29.320 --> 0:38:32.279
<v Speaker 1>board objected to that strategy and wanted someone who would

0:38:32.360 --> 0:38:35.560
<v Speaker 1>lead the company to compete in the mobile space more aggressively,

0:38:35.960 --> 0:38:39.120
<v Speaker 1>as that was the perceived area for growth. This was

0:38:39.160 --> 0:38:41.359
<v Speaker 1>an era where it became clear that mobile was going

0:38:41.400 --> 0:38:44.600
<v Speaker 1>to be the future of computers. After a CEO search,

0:38:45.000 --> 0:38:48.400
<v Speaker 1>Rory Reid was selected to lead the company. Read diversified

0:38:48.400 --> 0:38:51.239
<v Speaker 1>a m d S approach beyond the PC market, and

0:38:51.320 --> 0:38:53.919
<v Speaker 1>Read was able to guide the company into entering new

0:38:54.000 --> 0:38:57.880
<v Speaker 1>markets while lowering operating costs. In two thousand fourteen, he

0:38:57.920 --> 0:39:00.960
<v Speaker 1>would step down as CEO. He said that that was

0:39:01.000 --> 0:39:03.279
<v Speaker 1>the plan the whole time, that he was there just

0:39:03.320 --> 0:39:06.680
<v Speaker 1>as sort of an interim CEO to make some business

0:39:06.760 --> 0:39:09.480
<v Speaker 1>level changes to a m D and get the company

0:39:09.520 --> 0:39:11.600
<v Speaker 1>on the right track. But he didn't have a deep

0:39:11.640 --> 0:39:17.080
<v Speaker 1>background in engineering. A m d's next and current CEO did,

0:39:17.480 --> 0:39:21.480
<v Speaker 1>and that is Lisa Sue. Since the nineteen nineties, Lisa

0:39:21.520 --> 0:39:25.279
<v Speaker 1>Sue has worked in the semiconductor industry. She started over

0:39:25.320 --> 0:39:28.520
<v Speaker 1>at Texas Instruments on the technical staff. She's also worked

0:39:28.560 --> 0:39:32.239
<v Speaker 1>at IBM and Free Scale Semiconductor. Before she joined a

0:39:32.400 --> 0:39:35.480
<v Speaker 1>m D. She served as the chief operating officer before

0:39:35.560 --> 0:39:38.640
<v Speaker 1>being named the new president and CEO of the company,

0:39:38.680 --> 0:39:42.200
<v Speaker 1>and under her leadership, a m D has done rather well.

0:39:42.760 --> 0:39:45.319
<v Speaker 1>In two thousand seventeen, the company had a revenue of

0:39:45.400 --> 0:39:49.600
<v Speaker 1>five point three three billion dollars. That was a growth

0:39:49.680 --> 0:39:54.319
<v Speaker 1>over the previous year. Also, and remarkably, seventeen would be

0:39:54.320 --> 0:39:56.200
<v Speaker 1>the first year that a m D would post a

0:39:56.280 --> 0:39:59.640
<v Speaker 1>full year of profitability, meaning there were no quarters where

0:39:59.640 --> 0:40:02.440
<v Speaker 1>they post in a loss. While the company would come

0:40:02.480 --> 0:40:06.080
<v Speaker 1>out profitable in previous years, it always had quarters that

0:40:06.120 --> 0:40:09.280
<v Speaker 1>had a loss in those years, so things really had changed.

0:40:09.680 --> 0:40:12.040
<v Speaker 1>Not just a few years ago, lots of people were

0:40:12.040 --> 0:40:14.600
<v Speaker 1>ready to write off a m D. The company was

0:40:14.640 --> 0:40:18.239
<v Speaker 1>posting massive losses and it cut back jobs. It looked

0:40:18.239 --> 0:40:21.200
<v Speaker 1>like it over extended itself. It looked like it was

0:40:21.360 --> 0:40:23.880
<v Speaker 1>just not going to measure up against the competition, and

0:40:23.920 --> 0:40:27.320
<v Speaker 1>the product quality appeared to be slipping. But more recently

0:40:27.520 --> 0:40:30.520
<v Speaker 1>things have seemed to turn around, and perhaps we've yet

0:40:30.560 --> 0:40:33.040
<v Speaker 1>to see the greatest achievements from a company that was

0:40:33.080 --> 0:40:36.200
<v Speaker 1>able to shock the world by beating Intel to the punch.

0:40:36.680 --> 0:40:39.840
<v Speaker 1>Who knows what they might do next. When that wraps

0:40:39.960 --> 0:40:42.880
<v Speaker 1>up these episodes about the history of a m D.

0:40:43.320 --> 0:40:47.080
<v Speaker 1>Thanks again, Stephen for sending in that request. I greatly

0:40:47.080 --> 0:40:51.200
<v Speaker 1>appreciate it. I hope you guys enjoyed learning more about

0:40:51.320 --> 0:40:57.120
<v Speaker 1>this semiconductor and microprocessor company. They are fascinating. They continue

0:40:57.160 --> 0:41:01.440
<v Speaker 1>to be fascinating. So uh, that's that for that story.

0:41:01.600 --> 0:41:04.480
<v Speaker 1>If you guys have suggestions for future episodes of tech Stuff,

0:41:04.600 --> 0:41:08.200
<v Speaker 1>whether it's a company, a technology, maybe a personality in tech,

0:41:08.680 --> 0:41:11.360
<v Speaker 1>whatever it may be, why not send me an email

0:41:11.400 --> 0:41:14.280
<v Speaker 1>about it. The addresses tech Stuff at how stuff works

0:41:14.320 --> 0:41:16.920
<v Speaker 1>dot com. You can pop on over to our website

0:41:16.960 --> 0:41:20.359
<v Speaker 1>that's tech stuff podcast dot com. You're gonna find an

0:41:20.480 --> 0:41:23.640
<v Speaker 1>archive of all of our previous episodes, links to our

0:41:23.680 --> 0:41:26.799
<v Speaker 1>social media presence, as well as a link to our

0:41:26.840 --> 0:41:29.719
<v Speaker 1>online store, where every purchase you make goes to help

0:41:29.800 --> 0:41:32.560
<v Speaker 1>the show. And we greatly appreciate it, and I'll talk

0:41:32.600 --> 0:41:41.440
<v Speaker 1>to you again really soon. Tech Stuff is a production

0:41:41.480 --> 0:41:44.480
<v Speaker 1>of I Heart Radio's How Stuff Works. For more podcasts

0:41:44.480 --> 0:41:47.240
<v Speaker 1>from my heart Radio, visit the i heart Radio app,

0:41:47.360 --> 0:41:50.520
<v Speaker 1>Apple Podcasts, or wherever you listen to your favorite shows.