Date: Thu, 15 Jul 2004 14:18:01 -0400 From: John Baldwin <jhb@FreeBSD.org> To: Mark Santcroos <marks@ripe.net> Cc: cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/dev/acpica acpi_pci.c Message-ID: <200407151418.01839.jhb@FreeBSD.org> In-Reply-To: <20040715161403.GA741@laptop.6bone.nl> References: <200406231508.i5NF8egh052377@repoman.freebsd.org> <200406231122.04154.jhb@FreeBSD.org> <20040715161403.GA741@laptop.6bone.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thursday 15 July 2004 12:14 pm, Mark Santcroos wrote: > On Wed, Jun 23, 2004 at 11:22:04AM -0400, John Baldwin wrote: > > On Wednesday 23 June 2004 11:08 am, John Baldwin wrote: > > > jhb 2004-06-23 15:08:40 UTC > > > > > > FreeBSD src repository > > > > > > Modified files: > > > sys/dev/acpica acpi_pci.c > > > Log: > > > Now that we associate a device_t with ACPI device handles, lookup the > > > device associated with any PCI devices that are enumerated in the > > > ACPI tree when adding children to an ACPI PCI bus and remove the > > > duplicate ACPI-only device_t and replace the device_t associated with > > > the handle with the ACPI and PCI aware device_t. > > > > Mostly this just means fewer unknown devices in devinfo -v output. > > You forgot to mention that this commit breaks acpi_video ;-) > > The fact that "\_SB_.PCI0.AGP_.VID_" now no longer is "unknown", means that > it is not probed anymore. > > The result of that is that acpi_video can't attach anymore of course. That's because acpi_video is really a PCI driver. :) The device it is attaching too is a PCI device, not an ACPI device, hence the confusion. I have some early work started on a vga_pci driver that would have child devices like acpi_video0, drm0, agp0 (for Intel onboard graphics), and dpms0. -- 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?200407151418.01839.jhb>