Robert X. Cringely on the Apple / Intel deal

Page 2 - Seeking answers? Join the Tom's Hardware community: where nearly two million members share solutions and discuss the latest tech.
Archived from groups: comp.sys.ibm.pc.hardware.chips (More info?)

On Sun, 12 Jun 2005 00:32:39 -0400, Yousuf Khan <bbbl67@ezrs.com>
wrote:

>Robert Myers wrote:
>> I'd be very surprised if Intel didn't regard Microsoft's x86-64
>> decision as a declaration of war. That is to say, Microsoft already
>> _has_ optimized its code for AMD.
>
>Why would it be offended? In the end, it saved Intel a lot of money
>having to adopt AMD's instruction set, instead of trying to develop its
>own from scratch. And Microsoft waited to release Windows until Intel
>was ready to release its own chips.
>
>And of course Microsoft has already optimized for AMD, who else were
>they going to optimize for? It was there 1.5 years before Intel, and
>much longer if you count pre-production chips which it would absolutely
>have given to Microsoft first. Hell, even Microsoft's programming header
>files call the platform "AMD64". Linux headers are actually more kind
>towards Intel by calling the platform by the more generic "x86-64".
>

Did you miss the episode of Intel trying to get Microsoft to implement
Windows for an incompatible Intel 64-bit x86 extension?

We seem to be off into speculation about what nice people do in a nice
world. Intel is unhappy with Microsoft over Microsoft's 64-bit
decisions, and it doesn't make the slightest difference to Intel's
attitude toward Microsoft what Linux calls x86-64.

>>>Also MSFT has even greater cash reserves than INTC, and
>>>can use some of it to help AMD increase production.
>>
>>
>> That would and should produce a shareholder revolt at Microsoft.
>
>Sort of like the shareholder revolt that happened after Microsoft gave
>cash infusions to Apple and Corel when they were looking shakey?
>
Intel spent that money in an attempt to obfuscate the fact that it
*is* a predatory monopoly.

<snip>

>> All the feathers are already ruffled. There is simply no way that
>> Gates cannot be taking a dark view of the Intel-Apple deal, and Intel
>> is already furious over 64-bit decisions (x86/Itanium) by Microsoft.
>> The only question is where the bodies lie when the shooting stops.
>
>Intel has nobody to blame but itself for its Itanium failures. As for
>x64, it had nothing of its own, so it was likely going to use AMD's
>stuff anyways.
>

The only reason Intel implemented x86-64 and not some proprietary
variant is because Gates left them no choice. Whether Intel has only
itself to blame or not for itanium failures doesn't matter. Intel
can't be happy at Microsoft decisions to support x86-64 and not
Itanium.

RM
 
Archived from groups: comp.sys.ibm.pc.hardware.chips (More info?)

On Sun, 12 Jun 2005 05:21:43 -0400, Robert Myers
<rmyers1400@comcast.net> wrote:


>>
>>Sort of like the shareholder revolt that happened after Microsoft gave
>>cash infusions to Apple and Corel when they were looking shakey?
>>
>Intel spent that money in an attempt to obfuscate the fact that it
>*is* a predatory monopoly.
>
You'll never let that one go. It should read that Microsoft spent the
money to obfuscate the fact that *it* is a predatory monopoly. As to
Intel being a predatory monopoly, it would like to be, I'm sure.

RM
 
Archived from groups: comp.sys.ibm.pc.hardware.chips (More info?)

George Macdonald <fammacd=!SPAM^nothanks@tellurian.com> writes:

> On Sat, 11 Jun 2005 11:05:39 -0400, Tony Hill <hilla_nospam_20@yahoo.ca>
> wrote:
>
>>On Fri, 10 Jun 2005 13:07:55 +0200, Grumble <devnull@kma.eu.org>
>>wrote:
>>No, they most definitely are not. There is absolutely no requirement
>>that the internal 24-bit numbers assigned by the companies are unique
>>and it is possible (and easy) to change a MAC address on many (most?)
>>ethernet devices.
>
> I'm not sure how the 48 bits are divided up but I think it's fair to say
> that the original intent was that it be a universally unique number.

It's a 24-bit OUI and a 24-bit serial number. At least on Ethernet,
bit 40 og the OUI is the multicast/unicast bit, and bit 41 is the
Local/Global bit.

Regards,


Kai
--
Kai Harrekilde-Petersen <khp(at)harrekilde(dot)dk>
 
Archived from groups: comp.sys.ibm.pc.hardware.chips (More info?)

On Sat, 11 Jun 2005 11:05:39 -0400, Tony Hill wrote:

> On Fri, 10 Jun 2005 17:23:20 +1200, "AD." <me@privacy.net> wrote:
>
>>On Fri, 10 Jun 2005 00:40:31 -0400, Tony Hill wrote:
>>
>>> "just as every network device has its unique MAC address"
>>>
>>> MAC address are NOT unique (just unique on a subnet).
>>
>>MAC addresses are unique, barring people changing them of course. Of
>>course your chances of accidentally changing it to match another devices
>>address on your subnet are very very small indeed.
>
> The fact that they can be changed (easily) and are not FORCED to be unique
> means that you can most definitely not *depend* on them being unique, ie
> trying to design some sort of DRM scheme around MAC addresses is an
> exercise in futility.

Agreed. I just misread your statement to mean something like "they are by
design unique on a subnet but not unique globally".

Not having read the article (whadya you mean this isn't Slashdot?), I
didn't realise the context was around their usefulness in DRM schemes.
That little extra bit of context makes your meaning much clearer now :)

--
Cheers
Anton
 
Archived from groups: comp.sys.ibm.pc.hardware.chips (More info?)

On Sat, 11 Jun 2005 11:05:39 -0400, Tony Hill wrote:

> And will Apple PCs using Intel chips also run Windows?

Probably IMO.

> Will Apple SELL PCs with Windows?

No chance. Then they'd have to support it like all the other OEMs. I can't
imagine Apple being willing to do that.

Then again when 'support' these days consists of "pop in the recovery CD
and reboot", maybe they would?

--
Cheers
Anton
 
Archived from groups: comp.sys.ibm.pc.hardware.chips (More info?)

keith wrote:

>There have been for at least ten years, maybe longer. The manufacturers
>ran out of MACs long ago and have been forced to repeat them. As long as
>two don't show up on the same subnet, who cares? If by some unlucky
>coincidence they do, simply change one. AIUI, that's the reason they're
>changable.

Hmm... They're not customer-changable on the products my company
makes...
 
Archived from groups: comp.sys.ibm.pc.hardware.chips (More info?)

On Sun, 12 Jun 2005 13:43:19 +0200, Kai Harrekilde-Petersen
<khp@harrekilde.dk> wrote:

>George Macdonald <fammacd=!SPAM^nothanks@tellurian.com> writes:
>
>> On Sat, 11 Jun 2005 11:05:39 -0400, Tony Hill <hilla_nospam_20@yahoo.ca>
>> wrote:
>>
>>>On Fri, 10 Jun 2005 13:07:55 +0200, Grumble <devnull@kma.eu.org>
>>>wrote:
>>>No, they most definitely are not. There is absolutely no requirement
>>>that the internal 24-bit numbers assigned by the companies are unique
>>>and it is possible (and easy) to change a MAC address on many (most?)
>>>ethernet devices.
>>
>> I'm not sure how the 48 bits are divided up but I think it's fair to say
>> that the original intent was that it be a universally unique number.
>
>It's a 24-bit OUI and a 24-bit serial number. At least on Ethernet,
>bit 40 og the OUI is the multicast/unicast bit, and bit 41 is the
>Local/Global bit.

Ah, OK - now I see... there's even a list of OUI "known" mfrs:
http://standards.ieee.org/regauth/oui/oui.txt. Certainly I can see that,
now that mbrds can have on-board NICs -- and some more than one -- where
they are going to run out of serial numbers... and maybe quite quickly. I
also wonder about all the OUIs which are locked up through mergers etc.
over the years being badly distributed.

--
Rgds, George Macdonald
 
Archived from groups: comp.sys.ibm.pc.hardware.chips (More info?)

On Mon, 13 Jun 2005 12:56:55 -0500, chrisv wrote:

> keith wrote:
>
>>There have been for at least ten years, maybe longer. The manufacturers
>>ran out of MACs long ago and have been forced to repeat them. As long as
>>two don't show up on the same subnet, who cares? If by some unlucky
>>coincidence they do, simply change one. AIUI, that's the reason they're
>>changable.
>
> Hmm... They're not customer-changable on the products my company
> makes...

Really? They've been changable on everything I've worked on for years
(and no, I've not had any reason to look recently). The utility to change
them (it's in the serial EEPROM) may not be obvious, but it's there.

--
Keith
 
Archived from groups: comp.sys.ibm.pc.hardware.chips (More info?)

On Mon, 13 Jun 2005 20:13:58 -0400, George Macdonald wrote:

> On Sun, 12 Jun 2005 13:43:19 +0200, Kai Harrekilde-Petersen
> <khp@harrekilde.dk> wrote:
>
>>George Macdonald <fammacd=!SPAM^nothanks@tellurian.com> writes:
>>
>>> On Sat, 11 Jun 2005 11:05:39 -0400, Tony Hill <hilla_nospam_20@yahoo.ca>
>>> wrote:
>>>
>>>>On Fri, 10 Jun 2005 13:07:55 +0200, Grumble <devnull@kma.eu.org>
>>>>wrote:
>>>>No, they most definitely are not. There is absolutely no requirement
>>>>that the internal 24-bit numbers assigned by the companies are unique
>>>>and it is possible (and easy) to change a MAC address on many (most?)
>>>>ethernet devices.
>>>
>>> I'm not sure how the 48 bits are divided up but I think it's fair to say
>>> that the original intent was that it be a universally unique number.
>>
>>It's a 24-bit OUI and a 24-bit serial number. At least on Ethernet,
>>bit 40 og the OUI is the multicast/unicast bit, and bit 41 is the
>>Local/Global bit.
>
> Ah, OK - now I see... there's even a list of OUI "known" mfrs:
> http://standards.ieee.org/regauth/oui/oui.txt. Certainly I can see that,
> now that mbrds can have on-board NICs -- and some more than one -- where
> they are going to run out of serial numbers... and maybe quite quickly. I
> also wonder about all the OUIs which are locked up through mergers etc.
> over the years being badly distributed.

I believe we've had the same argument here over IP addresses. 64bits
should be enough for *everyone*! ...except that reality steps in.

I still have a hard-wired IP address (perhaps two) out of the 32bit space.

--
Keith