How to add Medion AKOYA S2013 (google/veyron_jaq)

[Paul Menzel]

Dear coreboot folks,

I got the Rockchip RK3288 based Google Chromebook Medion AKOYA S2013
which is or is based on the google/veyron_jaq board.

In the tree, there is currently the Haier Chromebook 11, also based on
`google/veyron_jaq`. `src/mainboard/google/veyron/Kconfig.name`
contains:

5 config BOARD_GOOGLE_VEYRON_JAQ
  6   bool "Haier Chromebook 11 (Veyron_Jaq)"
  7   select BOARD_GOOGLE_VEYRON
  8   select SYSTEM_TYPE_LAPTOP

How can the Medion AKOYA S2013 be added, so that it is available in the
list? Just add it to the description as it’s the same board?

Thanks,

Paul

[Paul Kocialkowski]

Hi,

Le dimanche 07 août 2016 à 15:50 +0200, Paul Menzel via coreboot a écrit :
> I got the Rockchip RK3288 based Google Chromebook Medion AKOYA S2013
> which is or is based on the google/veyron_jaq board.
>
> In the tree, there is currently the Haier Chromebook 11, also based on
> `google/veyron_jaq`. `src/mainboard/google/veyron/Kconfig.name`
> contains:
>
> 5 config BOARD_GOOGLE_VEYRON_JAQ
>   6   bool "Haier Chromebook 11 (Veyron_Jaq)"
>   7   select BOARD_GOOGLE_VEYRON
>   8   select SYSTEM_TYPE_LAPTOP
>
> How can the Medion AKOYA S2013 be added, so that it is available in the
> list? Just add it to the description as it’s the same board?

I don't think that's a reasonable way to go in the long term. Veyron boards are
used in lots of different devices. For the record, here is a list of these
devices:

* Medion Akoya S2013, codename veyron_jaq
* True IDC Chromebook 11, codename veyron_jaq
* Xolo Chromebook, codename veyron_jaq
* Haier Chromebook 11, codename veyron_jaq
* NComputing Chromebook CX100, codename veyron_jerry
* eduGear Chromebook K Series, codename veyron_jerry
* CTL J2 / J4 Chromebook for Education, codename veyron_jerry
* HiSense Chromebook 11, codename veyron_jerry
* Poin2 Chromebook 11, codename veyron_jerry
* Asus Chromebit CS10, codename veyron_mickey
* MEDION Chromebook S2015, codename veyron_mighty
* Chromebook PCM-116E, codename veyron_mighty
* Lumos Education Chromebook, codename veyron_mighty
* Viglen Chromebook 11, codename veyron_mighty
* Sector 5 E1 Rugged Chromebook, codename veyron_mighty
* eduGear Chromebook M Series, codename veyron_mighty
* Nexian Chromebook 11.6-inch, codename veyron_mighty
* Haier Chromebook 11e, codename veyron_mighty
* ASUS Chromebook Flip C100PA, codename veyron_minnie
* ASUS Chromebook C201, codename veyron_speedy

So it's clearly not doable to include all the names in the Kconfig description
when the board is shared across devices.

Note that the Kconfig option relates to the board name, not the device name, so
I don't think putting the device name in there makes a lot of sense. It's a
common practice when the board itself doesn't really have a name, but when it
does, I'd rather have it instead of the device name in there (at all). CrOS
devices are remarkable occurrences of this situation.

I always thought it was somewhat confusing to talk about boards instead of
devices. Maybe it's time to resolve the confusion, for instance by adding a
separate Kconfig option for each device, that would select the right board?

I don't expect that end users know what board they should use: instead, they
know what device they have.

Otherwise, we could provide a table associating devices and boards on the wiki.

What do you think?

[Peter Stuge]

Paul Kocialkowski wrote:
> I don't expect that end users know what board they should use:
> instead, they know what device they have.

IMO end users aren't the primary target demographic for coreboot.

I think it makes most sense to have the board name in Kconfig and not
a device name if they differ, or at least when it's 1:many.
> Otherwise, we could provide a table associating devices and boards
> on the wiki.

I think that's a good idea! Another good place to put this information
is in the Kconfig help text.

//Peter