@Julius/Patrick, I have no experience on this - should we put the blob to Coreboot's 3rdparty/blob (which is a submodule, but I don't know where to find its real repo?) or ChromiumOS's 3rdparty/blob ?

coreboot's 3rdparty/blob. For landing the patch upstream, it's important that it works upstream. Afterwards, we can consider whether we want to create a separate coreboot-private-files ebuild for Chromium for this or just use the blob from the upstream repo. (Since we're not planning to build the blob from source -- right? -- maybe special handling is not needed.)

The real upstream blobs repo is at https://review.coreboot.org/blobs.git. If you have a normal upstream checkout of coreboot, it is automatically checked out as a submodule. You can just do cd 3rdparty/blobs and then create a branch, add a commit and push it to Gerrit like with any other git repo. (Note that MediaTek should upload this blob since it's their IP they're releasing. They should make sure that they're submitting a suitable license file with it that allows unlimited, irrevocable, royalty-free distribution.)

View Change

To view, visit change 31835. To unsubscribe, or for help writing mail filters, visit settings.