Date: Tue, 22 Feb 2005 17:55:08 -0500 From: Jung-uk Kim <jkim@niksun.com> To: cvs-src@freebsd.org Cc: John Baldwin <jhb@freebsd.org> Subject: Re: cvs commit: src/sys/dev/acpica acpivar.h src/sys/amd64/acpica madt.c src/sys/i386/acpica madt.c Message-ID: <200502221755.08652.jkim@niksun.com> In-Reply-To: <200502221657.06989.jhb@FreeBSD.org> References: <200502222152.j1MLqqRG085270@repoman.freebsd.org> <200502221657.06989.jhb@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tuesday 22 February 2005 04:57 pm, John Baldwin wrote: > On Tuesday 22 February 2005 04:52 pm, John Baldwin wrote: > > jhb 2005-02-22 21:52:52 UTC > > > > FreeBSD src repository > > > > Modified files: > > sys/dev/acpica acpivar.h > > sys/amd64/acpica madt.c > > sys/i386/acpica madt.c > > Log: > > - Add a new quirk to indicate that pin 0 of the first I/O APIC > > is really IRQ 0 and not an ExtINT pin. The MADT enumerators > > ignore the PC-AT flag and ignore overrides that map IRQ 0 to pin > > 2 when this quirk is present. - Add a block comment above the > > quirks to document each quirk so that we can use more verbose > > descriptions quirks. > > > > MFC after: 2 weeks > > Several "wonderful" amd64 chipsets by Nvidia have this issue. AFAIK, this is a common problem for every NVIDIA chipset. > You can test it by manually enabling the quirk via hints (the value > for this quirk is '4'). If you have a machine that needs this, > please send me your acpidump output. Thanks. Thanks for the commit, Jung-uk Kim
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200502221755.08652.jkim>