Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 18 Apr 2018 18:36:56 +0000
From:      bugzilla-noreply@freebsd.org
To:        acpi@FreeBSD.org
Subject:   [Bug 224096] [PATCH] acpi bus driver: support resource allocation for buggy _CRS entries where fixed I/O ranges are defined like relocatable ones
Message-ID:  <bug-224096-16045-NDSJhepWWU@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-224096-16045@https.bugs.freebsd.org/bugzilla/>
References:  <bug-224096-16045@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D224096

--- Comment #2 from commit-hook@freebsd.org ---
A commit references this bug:

Author: jhb
Date: Wed Apr 18 18:36:26 UTC 2018
New revision: 332733
URL: https://svnweb.freebsd.org/changeset/base/332733

Log:
  Workaround fixed I/O port resources encoded as I/O port ranges in _CRS.

  ACPI I/O port descriptors use _MIN and _MAX fields to specify the set
  of allowable base (start) addresses for an I/O port resource along with
  a _LEN field specifying the length.  A fixed resource is supposed to be
  encoded with _MIN =3D=3D _MAX, but some buggy firmwares instead set _MAX =
to
  the end of the fixed range.  Relocating I/O ranges only make sense in
  _PRS (possible resource settings), not in _CRS (current resource settings=
),
  so if an I/O port range with _MAX set set to the end of the range is
  present in _CRS, treat it as a fixed I/O port resource starting at
  _MIN.

  PR:           224096
  Submitted by: Harald B?hm <harald@boehm.codes>
  Pointy hat to:        jhb (taking so long to actually commit this)
  MFC after:    1 week

Changes:
  head/sys/dev/acpica/acpi_resource.c

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-224096-16045-NDSJhepWWU>