Date: Thu, 21 Dec 2000 10:13:06 -0600 From: seebs@plethora.net (Peter Seebach) To: freebsd-hackers@freebsd.org Subject: Re: Supporting VirtualPC... Message-ID: <200012211613.KAA26240@guild.plethora.net> In-Reply-To: Your message of "21 Dec 2000 12:32:52 %2B0100." <xzpu27yf1qz.fsf@flood.ping.uio.no>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <xzpu27yf1qz.fsf@flood.ping.uio.no>, Dag-Erling Smorgrav writes: >seebs@plethora.net (Peter Seebach) writes: >> I am wondering what would be considered a "good" way to encode the knowledge >> that machines with "ConnectixCPU" in the mode string need specific special >> treatment in two widely disparate places. >Assuming the ident code correctly sets cpu_vendor to "ConnectixCPU" >(rather than e.g. "GenuineIntel" or "AuthenticAMD") you can just check >against that. It's declared in <machine/md_var.h>. Yeah, but in an ideal world, I wouldn't be calling strcmp on the CPU type every time the ethernet card interrupts... Is there a good place to add a dummy variable that can be tested? Perhaps md_var.h could have #ifdef VPC_CPU int cpu_is_vpc; #endif and not break anyone's heart? I'm just trying to avoid stepping on namespace conventions. ;) -s To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200012211613.KAA26240>