Date: Sun, 2 Apr 2006 06:07:34 -0500 From: "Conrad J. Sabatier" <conrads@cox.net> To: John Baldwin <jhb@freebsd.org> Cc: bms@spc.org, freebsd-current@freebsd.org Subject: Re: device atpic to be deprecated? Message-ID: <20060402060734.0cc8fdd0.conrads@cox.net> In-Reply-To: <200603291315.56671.jhb@freebsd.org> References: <20060329020527.f8f087a4.conrads@cox.net> <200603291157.54467.jhb@freebsd.org> <442ABF1B.5040305@samsco.org> <200603291315.56671.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 29 Mar 2006 13:15:54 -0500 John Baldwin <jhb@freebsd.org> wrote: > On Wednesday 29 March 2006 12:08, Scott Long wrote: > > John Baldwin wrote: > > > > > > I think that once the lapic timer stuff was added almost all of the APIC > > > issues I was aware of went away on amd64 that were fixed by using device > > > atpic instead. Most of the earlier problems were due to chipsets not > > > setting up pin 0 as extint, etc. but all that is no longer relevant when > > > we switched to using the lapic timer and stopped using irq0 and irq8 with > > > APIC. This is the first I've heard since the lapic timer stuff that APIC > > > didn't work on an amd64 box, and device atpic has been off by default in > > > HEAD for quite a while now. If we were able to require APIC on amd64, then > > > we might be able to try out some optimizations and other things I haven't > > > bothered with since they wouldn't be feasible on i386. > > > > > > > Fine, remove it. > > I have to make sure it really works for everyone first though before > removing it would really be viable. :-/ So, would it be necessary to upgrade to HEAD in order to make sure that this problem won't still occur on my box? Or has this stuff already been merged to STABLE? -- Conrad J. Sabatier <conrads@cox.net> -- "In Unix veritas"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060402060734.0cc8fdd0.conrads>