[ILUG] Linux community insulted by Intel with P4

[Scanlan, Brian (5188)]

Hey,

Linux kernel developers were pigheaded about putting support for
the changed CPUID in? How so? They did their best about keeping up to
date - As soon as they knew howto, they did. Intel could have been
a little more useful about things, and actually informed the Linux people
about forthcoming change to CPUID scheme - For a company who have been
making Linux noises [1] [2] [3] [4] [5] [6], and who've invested in Red Hat,
VA, eSoft, TurboLinux and SuSE, they're not exactly playing ball by not
informing
kernel folk of future changes to trivial things like CPUID long enough (or
at
all) so that the distribution makers have enough time to include support for
a new CPU when it's first on the market.

How was not forseeing Intel's CPUID movements a "mistake"? Are the Xfree86
folk correcting "mistakes" everytime they add support for a new graphics
device too, yeh? :)

(here follow random intel+linux stories)
[1] http://www.vnunet.com/News/104876
[2] http://www.canada.cnet.com/news/0-1003-200-1595588.html
[3] http://www.abcnews.go.com/sections/tech/DailyNews/linuxintel990225.html
[4] http://linuxtoday.com/stories/20846.html
[5] http://www.gamasutra.com/newswire/bit_blasts/20000915/index6.htm
[6] http://www.theregister.co.uk/content/1/13275.html

Brian.
-----Original Message-----
From: Dave O Connor [mailto:doc at redbrick.dcu.ie]
Sent: 14 December 2000 12:35
To: Brian Cullen
Cc: 'Scanlan, Brian (5188)'; 'ilug at linux.ie'; 'eeipshy at eei.ericsson.se'
Subject: Re: [ILUG] Linux community insulted by Intel with P4


Someone called Brian Cullen said on Thu, Dec 14, 2000 at 10:28:24AM -0000:
> Read that article, the register takes any chance to slag Intel and M$ 
> 
> Like most I like bad press for Intel and M$, 
> 
Even when it's contrived, like most of theregister's nitpickery?

Intel have the right to change their CPUID numbering scheme if they like,
and
if the linux developers are being pigheaded about it, and not keeping up to
date, then that's their fault.

I'm sure there are fixes out there for the developers' mistake. All is well.

	- DoC