Since it seems AI is pretty good at reverse-engineering stuff like this, is there any educational material on how to use it for that purpose? Seems like it could really help port things like postmarketOS to new devices (and improve support on existing ones)?

▲

pullshark91 2 hours ago | parent | next [-]

You should try asking AI itself about it

▲

realusername 3 hours ago | parent | prev | next [-]

I have some experience on this and could make an article if you are interested.

The key is to have downstream sources and be very very conservative with the AI, slowly build step by step.

You also have to know C and have a spider sense of what's acceptable or not.

Another key is to ask for approval before editing any source with a patch of what it intends to do. This way you can judge what it wants to do and ask for a double check of the patch. Go quality over quantity.

This isn't web frontend with Tailwind, you have to be very strict and somewhat knowledgeable. Nobody can use AI to write kernel code without some good low level and engineering knowledge.

▲

tech4bot 22 minutes ago | parent | next [-]

I’d be interested in that.

I completely agree, this is not the place to let AI blindly edit kernel code. The useful approach is to use it conservatively: understand the error, compare against downstream sources, propose a small patch, review it, test it, and then move one step further.

I’d be happy to work together on an article or guidance document, where to start, how to approach debugging, what to never let AI touch blindly, and how to build confidence step by step. That could help others avoid a lot of mistakes and maybe give a second chance to other devices.

▲

waweic an hour ago | parent | prev | next [-]

Please do write an article! I've wanted to get into reusing old android hardware for quite some time now, but never knew where to look for good instructions to get started. Especially PostmarketOS seems very interesting, but rather underdocumented in some places.

	▲	realusername an hour ago \| parent [-]
		I will then, didn't know it would be interesting for other people. As for PostmarketOS, I've built my own tooling scripts around it to make it easier to build patches, debug hex variables, switch between downstream/mainline and rebuilding everything with a single command. (Unrelased yet though). I find their tooling okay for a release for end-users but a bit clunky for debugging.

▲

ksh09 an hour ago | parent | prev [-]

Interested!

▲

dakolli 2 hours ago | parent | prev [-]

Ahh yes, rely on AI to avoid learning how to do something. Our brains are cooked if we keep up these attitudes.

	▲	ksh09 an hour ago \| parent \| next [-]
		It helps for fuzzing, maintaining and is actually a great help for seniors, maybe not for the ones who don't care for the project and publish slop. It could now actually help a lot in some ways not just coding though but things surrounding project management.
	▲	exe34 2 hours ago \| parent \| prev \| next [-]
		There are things I will just not bother to learn. I can either not do them, or let AI do them for me. There are things I can do for myself, but can't be bothered. I can either not do them or let AI do them for me. I prefer spending my time doings I actually want to do. Let the machine do the boring things.
	▲	blizdiddy 2 hours ago \| parent \| prev [-]
		All you do is go around the site complaining about AI. Someone porting Linux to ewaste is valuable, AI helped… go touch grass