public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Barr <barr.156-ZbGKxL/pcrQ@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: ignore invalid AccessType if RegionType only allows for one AccessType?
Date: Mon, 19 Jul 2004 16:24:31 -0400	[thread overview]
Message-ID: <1595322977.20040719162431@osu.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 1173 bytes --]

Hash: SHA1

Interesting. I have a Dell 300m that has that same problem.

Andrew

P.S. forgot to CC the list. Sorry. :(

=====================
When in doubt, do what the President does -- guess.
=====================

On Monday, July 19, 2004, 4:53:29 AM, Dominik Brodowski <linux@dominikbrodowski.de> wrote:

> Hi!

> The DSDTs of many Samsung notebooks contain one bug which forces users to
> use a "DSDT override":

>                     OperationRegion (ECR, EmbeddedControl, 0x00, 0xFF)
>                     Field (ECR, DWordAcc, Lock, Preserve)


> As can be seen in table 15-6 of ACPI spec 1.0b and in table 16-6 of ACPI
> spec 2.0, TypeRegion EmbeddedControl only allows for "ByteAcc", not
> "DWordAcc". iasl also says the same:

> ../dsdt.dsl  2660:                     Field (ECR, DWordAcc, Lock, Preserve)
> Error    1048 -                                 ^ Host Operation Region requires ByteAcc access

> Given the fact that EmbeddedControl _only_ allows ByteAcc, how about
> "ignoring" DWordAcc or any other (invalid) AccType in this case if
> !acpi_strict, and "assuming" a value of ByteAcc instead?

> Thanks,
> 	Dominik

[-- Attachment #2: Type: application/pgp-signature, Size: 186 bytes --]

             reply	other threads:[~2004-07-19 20:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-19 20:24 Andrew Barr [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-07-19  8:53 ignore invalid AccessType if RegionType only allows for one AccessType? Dominik Brodowski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1595322977.20040719162431@osu.edu \
    --to=barr.156-zbgkxl/pcrq@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox