cvs commit: src/sys/dev/acpica5 acpi.c acpi_acad.c acpi_button.c acpi_cmbat.c acpi_ec.c acpi_isab.c acpi_lid.c acpi_resource.c acpivar.h src/sys/dev/disk/fd fd.c src/sys/dev/misc/atkbdc_layer atkbdc_isa.c src/sys/dev/misc/joy joy.c src/sys/dev/misc/ppc ppc.c ...

[YONETANI Tomokazu]

y0netan1    2007/10/22 20:04:49 PDT

DragonFly src repository

  Modified files:
    sys/dev/acpica5      acpi.c acpi_acad.c acpi_button.c 
                         acpi_cmbat.c acpi_ec.c acpi_isab.c 
                         acpi_lid.c acpi_resource.c acpivar.h 
    sys/dev/disk/fd      fd.c 
    sys/dev/misc/atkbdc_layer atkbdc_isa.c 
    sys/dev/misc/joy     joy.c 
    sys/dev/misc/ppc     ppc.c 
    sys/dev/serial/sio   sio.c 
    sys/platform/pc32/acpica5 acpi_toshiba.c 
  Log:
  Merge ACPI resource manager changes From FreeBSD:
  
  acpi.c,v 1.158, acpivar.h,v 1.70
    Associate a device_t with an ACPI_HANDLE.  This make AcpiWalkNamespace more
    useful.  If ACPI-CA allowed null object handlers, we wouldn't need the
    placeholder function.
  
  acpi.c,v 1.159-1.160 and others:
    Add support to ACPI to manage its own resources.  Previously, resource
    allocation was passed up to nexus.  Now, we probe sysresource objects and
    manage the resources they describe in a local rman pool.  This helps
    devices which attach/detach varying resources (like the _CST object) and
    module loads/unloads.  The allocation/release routines now check to see if
    the resource is described in a child sysresource object and if so,
    allocate from the local rman.  Sysresource objects add their resources to
    the pool and reserve them upon boot.  This means sysresources need to be
    probed before other ACPI devices.
  
    Changes include:
    * Add ordering to the child device probe.  The current order is:  system
    resource objects, embedded controllers, then everything else.
    * Make acpi_MatchHid take a handle instead of a device_t arg.
    * Replace acpi_{get,set}_resource with the generic equivalents.
  
  acpi.c,v 1.175:
    Call device_identify routines after doing the namespace walk.  This is
    needed so that sysresource objects are created first to reserve all regions,
    then other devices can allocate from them.  Otherwise, acpi_timer (the only
    ACPI device with an identify routine), would allocate its resources from
    the nexus, causing the later sysresource reserve to fail.
  
    Debugging by:   Taku YAMAMOTO, Andrea Campi
  
  And add ACPI attachment to some devices trying to obtain resources
  from the ISA bus.
  
  Revision  Changes    Path
  1.32      +156 -60   src/sys/dev/acpica5/acpi.c
  1.8       +2 -2      src/sys/dev/acpica5/acpi_acad.c
  1.5       +7 -5      src/sys/dev/acpica5/acpi_button.c
  1.11      +3 -3      src/sys/dev/acpica5/acpi_cmbat.c
  1.13      +3 -3      src/sys/dev/acpica5/acpi_ec.c
  1.4       +4 -2      src/sys/dev/acpica5/acpi_isab.c
  1.5       +2 -2      src/sys/dev/acpica5/acpi_lid.c
  1.9       +92 -38    src/sys/dev/acpica5/acpi_resource.c
  1.12      +13 -2     src/sys/dev/acpica5/acpivar.h
  1.41      +1 -0      src/sys/dev/disk/fd/fd.c
  1.10      +1 -0      src/sys/dev/misc/atkbdc_layer/atkbdc_isa.c
  1.12      +1 -0      src/sys/dev/misc/joy/joy.c
  1.15      +1 -0      src/sys/dev/misc/ppc/ppc.c
  1.42      +1 -0      src/sys/dev/serial/sio/sio.c
  1.6       +5 -5      src/sys/platform/pc32/acpica5/acpi_toshiba.c


http://www.dragonflybsd.org/cvsweb/src/sys/dev/acpica5/acpi.c.diff?r1=1.31&r2=1.32&f=u
http://www.dragonflybsd.org/cvsweb/src/sys/dev/acpica5/acpi_acad.c.diff?r1=1.7&r2=1.8&f=u
http://www.dragonflybsd.org/cvsweb/src/sys/dev/acpica5/acpi_button.c.diff?r1=1.4&r2=1.5&f=u
http://www.dragonflybsd.org/cvsweb/src/sys/dev/acpica5/acpi_cmbat.c.diff?r1=1.10&r2=1.11&f=u
http://www.dragonflybsd.org/cvsweb/src/sys/dev/acpica5/acpi_ec.c.diff?r1=1.12&r2=1.13&f=u
http://www.dragonflybsd.org/cvsweb/src/sys/dev/acpica5/acpi_isab.c.diff?r1=1.3&r2=1.4&f=u
http://www.dragonflybsd.org/cvsweb/src/sys/dev/acpica5/acpi_lid.c.diff?r1=1.4&r2=1.5&f=u
http://www.dragonflybsd.org/cvsweb/src/sys/dev/acpica5/acpi_resource.c.diff?r1=1.8&r2=1.9&f=u
http://www.dragonflybsd.org/cvsweb/src/sys/dev/acpica5/acpivar.h.diff?r1=1.11&r2=1.12&f=u
http://www.dragonflybsd.org/cvsweb/src/sys/dev/disk/fd/fd.c.diff?r1=1.40&r2=1.41&f=u
http://www.dragonflybsd.org/cvsweb/src/sys/dev/misc/atkbdc_layer/atkbdc_isa.c.diff?r1=1.9&r2=1.10&f=u
http://www.dragonflybsd.org/cvsweb/src/sys/dev/misc/joy/joy.c.diff?r1=1.11&r2=1.12&f=u
http://www.dragonflybsd.org/cvsweb/src/sys/dev/misc/ppc/ppc.c.diff?r1=1.14&r2=1.15&f=u
http://www.dragonflybsd.org/cvsweb/src/sys/dev/serial/sio/sio.c.diff?r1=1.41&r2=1.42&f=u
http://www.dragonflybsd.org/cvsweb/src/sys/platform/pc32/acpica5/acpi_toshiba.c.diff?r1=1.5&r2=1.6&f=u