In message <[EMAIL PROTECTED]>, Dag-Erling Smorgrav writes:
>[EMAIL PROTECTED] (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 [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
