DragonFly bugs List (threaded) for 2009-12
Re: BTX Halted on X86_64 master
Thomas E. Spanjaard wrote:
Bill Hacker wrote:
Well this is rather embarassing. This aint a 64bit processor. I bought
this thing like half a year after I bought my AMD64 workstation and I had
assumed (Core Duo) would be 64 bit.
Odd, that. Just which specific CPU do you have? Mobility-something,
Not only the Core-2, but the earlier Core-D had Intel's '64-bit
extensions' (mostly) cross-licensed from AMD.
My Core-D happily ran FreeBSD ADM64 (6.2 beta onward).
Is DFLY that different?
None of the Core Duo chips support EM64T. Are you perhaps confusing the
Pentium D with the Core Duo? Also, all Core Duo chips were mobile ones,
save for the Xeon ULV ("Sossaman"), which was for dual-socket servers
(short-lived though, as a couple of months later Woodcrest and friends
(Core 2-based) were released).
ACK 'marketing Nomenclature' - (the 'Core-D' / Pentium D eg - pre 'Core 2'
having been presented as meaning 'Core Duo')
. .. which is why I asked about the *number*. Though of course a dmesg would show
that ... so long as the booting stage got that far:
CPU: Intel(R) Pentium(R) D CPU 3.00GHz (3000.14-MHz K8-class CPU)
Origin = "GenuineIntel" Id = 0xf62 Stepping = 2
Cores per package: 2
Perhaps we should boot with an i32 image, detect what's there, throw a flag -
much as an OpenBSD insall selects an MP kernel (or not), and logs that action.
Doesn't need a lot of extra CD/DVD space ... or code.
I'll worry about all that when VIA Nano dualcore become common or ARM gets faster.
Meanwhile, after half a century of listening to fan noise, I'm chasing lower
power instead of raw speed and have come to rather enjoy what Simon & Garfunkel
called 'the sounds of silence'.