Date: Thu, 17 May 2012 18:33:56 +0300 From: Andriy Gapon <avg@FreeBSD.org> To: John Baldwin <jhb@FreeBSD.org> Cc: Bruce Cran <bruce@cran.org.uk>, freebsd-acpi@FreeBSD.org, freebsd-current <freebsd-current@FreeBSD.org>, Jung-uk Kim <jkim@FreeBSD.org> Subject: Re: ACPI 'driver bug: Unable to set devclass' Message-ID: <4FB51A64.6090906@FreeBSD.org> In-Reply-To: <201205171005.19736.jhb@freebsd.org> References: <4FAF7343.8010808@cran.org.uk> <4FB3D351.6030804@FreeBSD.org> <201205161607.43286.jhb@freebsd.org> <201205171005.19736.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
on 17/05/2012 17:05 John Baldwin said the following: > On Wednesday, May 16, 2012 4:07:43 pm John Baldwin wrote: >> Oh, whoops. Actually, the right way to do this I think is bus_hint_device_unit() >> (and/or, not make the unit number in cpuX mean anything at all, but use a separate >> ivar to track what PCPU_GET(cpuid) a given cpuX device corresponds to). I think >> the last approach is really the right way to fix this. > > I haven't been able to try this yet, but I have a first cut at > www.freebsd.org/~jhb/patches/acpi_cpu.patch > The patch has not been compile-tested? :) -- Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4FB51A64.6090906>