I also have an ES47 (running Linux)! Would you send me an email to my username at gmail? I've been working on a remote management tool for the ES47 that allows controlling the fan speeds that you might be interested in.
I think they're also super useless, to be honest. Incredibly slow. Linux support continued to degrade the entire time I owned mine. The keyboard and display are far too small to be usable. The graphics chip accelerates basically nothing.
I sold mine [1] on eBay back in October. I hope the new owner enjoys it more than I did :)
Yoooo, small world! I'm the guy in Hawaii who bought it from you :)
I haven't done anything too exciting with it yet, still have to get around to seeing if T2 SDE works on it, but it's joined me a number of times on trips to the library for writing, and it's been delightful for that. The keyboard is surprisingly good, and it feels like a supercomputer compared to a WorkPad Z50, hah.
I've loaded the PROM in Ghidra. The ability to decompile to C is great.
I looked at some particular parts of the PROM that took a while to understand to see if I could have understood them quicker with Ghidra. In particular, the part of `sloader` that searches for the `post1` and `firmware` sections and then calls `post1(&firmware)`. Given that I already understand how this works, I can see that this is happening from the decompiled C, but the lack of labels, comments, etc really hampers my ability to understand from the decompiled C alone.
This might all be down to inexperience with the tool.
The ability to iteratively add a label, rerun the decompiler, reread the decompiled assembly, make more inferences was really the key to building an understanding for me.
Another aspect I'm unsure how to handle in Ghidra is that the base address differs between sections of the firmware. E.g. the `firmware` section is copied to RAM and executed from `0x81000000`. It's not clear to me how to configure this in a granular way, rather than a single base address for the whole PROM image.
Annotating the decompiled code is very much part of the workflow in using Ghidra, but the UI is not really intuitive. If you right-click on variables, function names etc there are a bunch of options for annotation. You can also edit the function signature, which can cause the decompilation to improve.
I know you can do various base address manipulations, but your case seems like it would be hard -- the base address is in the file, or has to be calculated.
> Burnout is your brain giving up because it doesn’t think the benefit is worth the effort anymore. If you don’t have a purpose for what you are doing all your brain will do is obsess over the negatives. Every job in the world has massive negatives. You have to find a positive purpose for what you are doing to balance the negative.
This is spot on and was exactly my experience at my last job.
The one thing I'll add is that for me it wasn't about not having a purpose, it was about not feeling appreciated for all of the time/effort/energy I'd poured into that purpose.
