Re: [Devel] Possible issue with iasl on big endian machines.

[Marcel Apfelbaum <marcel.a at redhat.com>]

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

On Thu, 2014-03-20 at 11:19 -0600, Al Stone wrote:
> 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.
> 
Hi Al,
Thanks for the prompt reply.

I am using acpica-tools-20130823-5.fc19.ppc64 (The one that comes with Fedora 19 on a big endian ppc64 machine)
Should I file a bug?

Thanks,
Marcel