Re: Tonight on Top Gear: ACPI problems, me learning a thing, and accusations of theft (was Re: [9front] Libaml does not recognize opcode 0x86)

[Jacob Moody <moody@posixcafe.org>]

On 10/23/23 22:55, Ellenor Bjornsdottir wrote:
> And that's the third direct accusation of theft? Kurt? Bruh. Lay off it. 
> "If false" was merely stating that libel law in the US excludes truthful 
> libel (as it should).
> 
> Hawk: http://man.9front.org/1/sysinfo this is what a "sysinfo" is, which 
> khm is rightly requesting (the only right thing he's doing here) amid 
> his baseless and offensive accusations of theft. You came in on a bad 
> start, so folks here are understandably wary of you as a "customer 
> service suck".
> 
> [mucks around on man.9front.org, asking it for libaml, then aml] You 
> correctly gathered that libaml had something to do with acpi, although 
> the failure itself may or may not be related to your opcode thing - aml 
> is the ACPI machine language interpreter. I must confess this isn't 
> something I too well understand, but [downloads the 
> plan9front/plan9front source code to their UNIX workstation] the text 
> "invalid opcode" appears nowhere in sys/src/libaml, possibly leading me 
> to believe the original subject line is a misreading of the situation, 
> or something like a red herring? Again I don't really understand how all 
> this fits together.
> 
> May I ask how you're finding 9front in general, other than this battery 
> issue?
> 

I mentioned this on IRC but should mention it here as well. This specific
issue with libaml has already been (partially) fixed thanks to uramekus.

http://git.9front.org/plan9front/plan9front/2f457e75a5d614710a6683875d17d9c552a52a05/commit.html

Only partially because all this does is consume the instruction as a nop. More work may be require,
but this would at least fix the immediately present error.


Thanks,
Moody