Hi Paul,

I don't think there is an external mailing list for chromium OS EC development.

To see the manifest which the repo utility requires you need to setup the Chrome OS chroot environment first (aka cros SDK), I am not sure if you did that, but this is a pretty expensive procedure, requiring a lot of disk space and time.
 
You should be able to clone the EC git repository and run pre-upload checks and push patches to the EC gerrit server, but you'd need an account on the server for that.

To be honest with you, I don't know the exact procedure to follow to get the account created, you could inquire at chromium-os-dev@chromium.org 

the entry threshold is a big high, but I am sure the Chome OS EC team would appreciate your contributions.

--vb




On Mon, Oct 2, 2017 at 12:04 AM, Paul Menzel <paulepanter@users.sourceforge.net> wrote:
Dear coreboot folks,


GCC 7.2 found several issues in the Chromium EC code base, like #770209
[4], and I prepared  patches, but unfortunately, I do not know how to
push them for review.

1. The instructions don’t work for me [5]. I can’t find the manifest
file, which seems to be required by the utility `repo`.

2. Also, in the preferences menu of the Google Chromium review system,
I cannot find a way to upload my SSH key.

3. Is there a mailing list for the Chromium Embedded Controller
development?


Thanks,

Paul


[4] https://bugs.chromium.org/p/chromium/issues/detail?id=770209
[5] https://dev.chromium.org/chromium-os/ec-development
[6] https://chromium-review.googlesource.com/admin/projects/chromiumos/platform/ec,access
--
coreboot mailing list: coreboot@coreboot.org
https://mail.coreboot.org/mailman/listinfo/coreboot