I would tend yo disagree a bit with the other comments. First of all, let’s talk about the scratch. It does not looks very deep, so most likely no damage to traces. In order to have a short you would also need to have two traces exposed and some metallic object between the two. This also look unlikely to me. I would clean the area with isopropyl alcohol, check it visually. You could also cover up the scratch with nail polish.

Then, the missing capacitor. First of, I cannot make from the picture if there was a capacitor soldered there in the first place. Sometimes there are purposfuly unpopulated components. In any case, all of the capacitors you are seeing on the backside of the CPU are decoupling capacitor. They serve no other purpose than to help stabilize the voltage versus the dynamic power draw. This means that less capacitors equals less stabilisation, but not necessarily incapacity to function. I would clean also clean it up and ensure that no metallic object touches the pads. I would probably not try to replace it, as you have no way of knowing what value the capacitor is supposed to be (usually no schematic/boardview for modern products).

It is theoretically possible to damage the CPU due to a short, but likelihood seems very low to me in this case. I would clean it up, check visually, and try to turn it on.

Pocketbook makes nice e readers too! Issue then is mostly with getting books, especially non-drm ones

It’s not a matter of “him” personally. Permissive license allow for a work to be taken and redistributed by other entities, without enforcing them to release their changes. This creates a one way relationship that is generally detrimental to the open source ecosystem, allowing work to be stolen away from the public. That being said, choosing a license is situational, and a permissive one can be a great choice in certain instances. For that particular case, I don’t see much benefit to having a permissive licence.

I believe it does. Weakly reciprocal license like LGPL is not equivalent as a permissive license like Apache. I see two main things on the top of my head:

1. This ensure that no one can license wash ffmpg and e.g. use rockchip’s repo to distribute their own private product based on ffmpeg without publishing their changes
2. It ensures proper attribution of the work, which can have an impact on the developer’s careers and ffmpeg as a whole.

On top of this, it really should not be complicated to license this code properly (unless rockchip wants to allow point 1, which is illegal)

Turns out that this is common in Japan for tea fields. They mount big fans on poles all accross the field for it (you provably have to zoom in to see them)

For edits whithin a page, I use inkscape. Both program combined have covered all my needs until now.