I've been thinking there have been hints of this for a while. Moving the EOS M to the "powershot" codebase implies a lot of EOS / ILC stuff has been made portable, and G7X II picked up things like "picture styles"

It makes sense, the death of the low end and rise of the higher end mirrorless means there's less difference and two separate codebases (and possibly teams) adds quite a bit of overhead.

I had an EOS R in my hands lately. The menu was much more similar to my M3 than a SLR camera. What does that mean in practice for CHDK?

Nothing, unfortunately. a1ex thinks the R may have a firmware that differs from the new EOS based PowerShots (and EOS Ms).

Making CHDK work on an EOS based firmware would mean the following (and even more):- no propcases, params, UI properties -> no overrides possible with current CHDK code- no capt_seq task -> no raw or raw operations- completely different Canon UI code (CHDK core relies on some known UI structures)These would have to be replaced using wrappers or a complete rework - huge work.What's left from powershots is: there's Canon Basic (but it's not known how to run those scripts), there are event procedures (the EOS ones, no compatibility with powershot code), there is a physw task (the keyboard handler).

Since the firmware can't be dumped using scripts, we would have no more excuse for publishing it (as we do now) or using disassembled parts of it.

In short: I don't think anyone will take on this huge job.

Pre-D8 cameras will remain portable, but not too many people care about that either.