From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: linux-kernel@vger.kernel.org, linux-kbuild@torque.net
Subject: Re: [PATCH] Processor autodetection (when configuring kernel)
Date: Fri, 29 Dec 2000 15:09:14 +0100 [thread overview]
Message-ID: <20001229150913.A18678@lug-owl.de> (raw)
In-Reply-To: <3A4C941E.EA824F87@student.ethz.ch>
In-Reply-To: <3A4C941E.EA824F87@student.ethz.ch>; from cate@student.ethz.ch on Fri, Dec 29, 2000 at 02:39:42PM +0100
On Fri, Dec 29, 2000 at 02:39:42PM +0100, Giacomo A. Catenazzi wrote:
> + case $cpu_id in
> + GenuineIntel:5:[0123] ) echo CONFIG_M586TSC ;;
> + GenuineIntel:5:[48] ) echo CONFIG_M586MMX ;;
> + GenuineIntel:6:[01356] ) echo CONFIG_M686 ;;
> + GenuineIntel:6:{8,9,11} ) echo CONFIG_M686FXSR ;;
> + AuthenticAMD:5:[0123] ) echo CONFIG_M586 ;;
> + AuthenticAMD:5:{8,9,10,11} ) echo CONFIG_MK6 ;;
> + AuthenticAMD:6:[0124] ) echo CONFIG_MK7 ;;
> + UMC:4:[12] ) echo CONFIG_M486 ;; # "UMC" !
> + NexGenDriven:5:0 ) echo CONFIG_M386 ;;
> + {TransmetaCPU,GenuineTMx86}:* ) echo CONFIG_MCROSUE ;;
What about non-ia32 processor based systems? I'd ivolunteer to
extend the patch, but I'd need *your* /proc/cpuinfo... I think
that's worth it...
MfG, JBG
--
Fehler eingestehen, Größe zeigen: Nehmt die Rechtschreibreform zurück!!!
/* Jan-Benedict Glaw <jbglaw@lug-owl.de> -- +49-177-5601720 */
keyID=0x8399E1BB fingerprint=250D 3BCF 7127 0D8C A444 A961 1DBD 5E75 8399 E1BB
"insmod vi.o and there we go..." (Alexander Viro on linux-kernel)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-12-29 14:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-29 13:39 [PATCH] Processor autodetection (when configuring kernel) Giacomo A. Catenazzi
2000-12-29 14:09 ` David Relson
2000-12-29 14:09 ` Jan-Benedict Glaw [this message]
2000-12-29 14:41 ` David Relson
2000-12-29 15:41 ` Ingo Oeser
2000-12-29 16:46 ` Re:[PATCH, v2] " Giacomo A. Catenazzi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20001229150913.A18678@lug-owl.de \
--to=jbglaw@lug-owl.de \
--cc=linux-kbuild@torque.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox