Re: Why does FBSD always assume it's on an 8080 CPU?

2007-01-31 Thread Chris H.
Thank you Kris, and all who took the time to respond. Quoting Kris Kennaway [EMAIL PROTECTED]: On Fri, Jan 26, 2007 at 08:45:15PM -0800, Chris H. wrote: Hello and thank you for your response... Quoting Mike Jakubik [EMAIL PROTECTED]: Chris H. wrote: CPU: AMD Athlon(tm) XP (1102.51-MHz

Why does FBSD always assume it's on an 8080 CPU?

2007-01-26 Thread Chris H.
...or when will FreeBSD support Pentium features? I want to apologize in advance if this should be on the kern@ But it seemed apropriate for this list too and I'm already on it. I've noticed building kernels, that since v. = 5 that during the phase 2/3 all the lines echoed to the screen contain:

Why does FBSD always assume it's on an 8080 CPU?

2007-01-26 Thread Chris H.
...or when will FreeBSD support Pentium features? I want to apologize in advance if this should be on the kern@ But it seemed apropriate for this list too and I'm already on it. I've noticed building kernels, that since v. = 5 that during the phase 2/3 all the lines echoed to the screen contain:

Re: Why does FBSD always assume it's on an 8080 CPU?

2007-01-26 Thread Dimitry Andric
Chris H. wrote: I've noticed building kernels, that since v. = 5 that during the phase 2/3 all the lines echoed to the screen contain: -mno-mmx -mno-3dnow -mno-sse -mno-sse2 ... See /usr/share/examples/etc/make.conf. As Pentium have been the norm for many years now, why aren't these

Re: Why does FBSD always assume it's on an 8080 CPU?

2007-01-26 Thread John Merryweather Cooper
Chris H. wrote: ...or when will FreeBSD support Pentium features? I want to apologize in advance if this should be on the kern@ But it seemed apropriate for this list too and I'm already on it. I've noticed building kernels, that since v. = 5 that during the phase 2/3 all the lines echoed to

Re: Why does FBSD always assume it's on an 8080 CPU?

2007-01-26 Thread Chris H.
Context switching. We already preserve the core CPU state and the FPU state between context switches. Adding MMX into the mix means preserving an MMX state (since it can clobber the FPU state) and so forth. jmc Quoting Dimitry Andric [EMAIL PROTECTED]: Chris H. wrote: I've noticed building

Re: Why does FBSD always assume it's on an 8080 CPU?

2007-01-26 Thread Chris H.
Quoting Dimitry Andric [EMAIL PROTECTED]: Chris H. wrote: I've noticed building kernels, that since v. = 5 that during the phase 2/3 all the lines echoed to the screen contain: -mno-mmx -mno-3dnow -mno-sse -mno-sse2 ... See /usr/share/examples/etc/make.conf. Sigh, the obvious is so

Re: Why does FBSD always assume it's on an 8080 CPU?

2007-01-26 Thread Mike Jakubik
Chris H. wrote: CPU: AMD Athlon(tm) XP (1102.51-MHz 686-class CPU) Origin = AuthenticAMD Id = 0x680 Stepping = 0 Features=0x383fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE AMD Features=0xc0400800SYSCALL,MMX+,3DNow+,3DNow That I simply build

Re: Why does FBSD always assume it's on an 8080 CPU?

2007-01-26 Thread Chris H.
Hello and thank you for your response... Quoting Mike Jakubik [EMAIL PROTECTED]: Chris H. wrote: CPU: AMD Athlon(tm) XP (1102.51-MHz 686-class CPU) Origin = AuthenticAMD Id = 0x680 Stepping = 0

Re: Why does FBSD always assume it's on an 8080 CPU?

2007-01-26 Thread Kris Kennaway
On Fri, Jan 26, 2007 at 08:45:15PM -0800, Chris H. wrote: Hello and thank you for your response... Quoting Mike Jakubik [EMAIL PROTECTED]: Chris H. wrote: CPU: AMD Athlon(tm) XP (1102.51-MHz 686-class CPU) Origin = AuthenticAMD Id = 0x680 Stepping = 0