Date: Mon, 5 Dec 2005 15:22:40 -0500 From: John Baldwin <jhb@freebsd.org> To: freebsd-hardware@freebsd.org Cc: Joe Rhett <jrhett@svcolo.com>, hardware@freebsd.org Subject: Re: com1 incorrectly associated with ttyd1, com2 with ttyd0 Message-ID: <200512051522.41965.jhb@freebsd.org> In-Reply-To: <20051205200546.GB13194@svcolo.com> References: <20051117050336.GB67653@svcolo.com> <20051201204625.W41849@delplex.bde.org> <20051205200546.GB13194@svcolo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Monday 05 December 2005 03:05 pm, Joe Rhett wrote: > On Thu, Dec 01, 2005 at 08:58:04PM +1100, Bruce Evans wrote: > > It's not clear that disabling in the BIOS should disable for all OSes. > > What? That's a fairly weird interpretation. If I want to disable inside a > given OS, I do that inside the OS. If I want to disable for _ALL_ OSes, > then I disable in the BIOS. What reasonable logic can argue otherwise? The BIOS doesn't say "X is disabled", it just doesn't have any resources setup for X. One of the few things the BIOS can say "X is disabled" for is CPUs, which is what the Hyperthreading knob in the BIOS does, it just flags HT CPUs as disabled in the MADT table. -- John Baldwin <jhb@FreeBSD.org> <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200512051522.41965.jhb>