rockchip specific logo container format

[armijnhemel]

This PR adds a spec for a format used by Rockchip on at least some of their eInk devices. I could not find any specification about what the fields are whatsoever, but it seems to be fairly simple (height and width are quite obvious when searching for the particular chipset). My guess is that what I am calling unknown_2 is probably a setting for the image quality and unknown_3 could perhaps be X/Y coordinates.

The data itself: possibly something raw or BMPs without a header (which is not uncommon on Android).

[KOLANICH]

One field is called magic and another one is signature... Feels a bit inconsistent.

[KOLANICH]

size: 64
....
size-eos: true

May it have sense to just replace size-eos with the needed size?

[armijnhemel]

One field is called magic and another one is signature... Feels a bit inconsistent.

Perhaps. One is for the top level identifier, the other for the individual image entries. I don't really care about what it's called.

[armijnhemel]

size: 64
....
size-eos: true

May it have sense to just replace size-eos with the needed size?

I don't see a good reason to. This looked like the cleanest solution to me at the moment, because there are no specifications whatsoever so I don't even know what the rest of the data means (and I only have two test files).

[KOLANICH]

I guess image_entry should be nested into images, shouldn't it?

[armijnhemel]

I guess image_entry should be nested into images, shouldn't it?

As far as I know it is nested (clicking through it in the Web IDE now), so I don't know what you mean exactly.

[KOLANICH]

Now it is

types:
  images:
    ...
  image_entry:

, but I propose it be

types:
  images:
    ...
    types:
      image_entry:

[armijnhemel]

Now it is

types:
  images:
    ...
  image_entry:

, but I propose it be

types:
  images:
    ...
    types:
      image_entry:

Ah. Personally I think it is just fine as it is and functionality wise it doesn't matter.

@generalmimon what do you think? The style guide doesn't have a recommendation for this.