All of lore.kernel.org
 help / color / mirror / Atom feed
From: Al Stone <ahs3 at redhat.com>
To: devel@acpica.org
Subject: Re: [Devel] Possible issue with iasl on big endian machines.
Date: Thu, 20 Mar 2014 11:19:57 -0600	[thread overview]
Message-ID: <532B233D.3040608@redhat.com> (raw)
In-Reply-To: 1395335011.3100.7.camel@localhost.localdomain

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

On 03/20/2014 11:03 AM, Marcel Apfelbaum wrote:
> Hi,
>
> Should iasl running on a big endian machine be able to
> disassemble a DSDT(and any other acpi table) taken from a
> little endian machine?
>
> I tried to do it and I receive:
> Error [...] TableHeader length [0xBB040000] greater than the input file size [0x4BB].
> As you can see the length bytes are swapped.
>
> The question is, shouldn't it work, ACPI protocol being always little-endian?
>
> Thanks,
> Marcel
>
>
> _______________________________________________
> Devel mailing list
> Devel(a)acpica.org
> https://lists.acpica.org/mailman/listinfo/devel
>

Which version of iasl are you using?  If you're using the version
straight from ACPICA, it needs patching to handle big-endian.

If you're using one of the recent Fedora/Debian versions, they have
been patched for big-endian support, but of course there could be an
issue with those patches.

Regardless, the ACPI data _should_ be in little-endian form.

-- 
ciao,
al
-----------------------------------
Al Stone
Software Engineer
Red Hat, Inc.
ahs3(a)redhat.com
-----------------------------------

             reply	other threads:[~2014-03-20 17:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-20 17:19 Al Stone [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-03-20 19:10 [Devel] Possible issue with iasl on big endian machines Moore, Robert
2014-03-20 18:54 Marcel Apfelbaum
2014-03-20 18:41 Moore, Robert
2014-03-20 17:48 Al Stone
2014-03-20 17:24 Marcel Apfelbaum
2014-03-20 17:03 Marcel Apfelbaum

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=532B233D.3040608@redhat.com \
    --to=devel@acpica.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.