Skip to content

Import earlgrey target#92

Draft
cfrantz wants to merge 2 commits intoOpenPRoT:mainfrom
cfrantz:earlgrey
Draft

Import earlgrey target#92
cfrantz wants to merge 2 commits intoOpenPRoT:mainfrom
cfrantz:earlgrey

Conversation

@cfrantz
Copy link
Collaborator

@cfrantz cfrantz commented Feb 5, 2026

This PR imports the pigweed target definitions for the OpenTitan Earlgrey chip.

  1. Make the repo in to a bazel module and reference the upstream pigweed repo and language/compiler bazel rules repos.
  2. Remove the /target/-type ignores from .gitignore. We'll have to consider how we want to handle this as we migrate this repo from being cargo-based to bazel-based. I'd be OK with renaming //target/ealrgrey to something else; this is currently the pigweed convention.
  3. Move the original root-level //tooling and //signing subdirs into //target/earlgrey. Both of these subdirectories have earlgrey-specific definitions and probably shouldn't live at the root of the repo.

This is a draft PR initially meant to create some discussion. Namely:

  • How do we want to organize the repository?
  • How do we migrate from cargo/xtask to bazel for existing flows?
  • What additional automation do we want to put in place in the repo?
  • What form of license header do we want to apply to files? (currently the imported files say "copyright pigweed authors")

Import the earlgrey Pigweed target definition.

Signed-off-by: Chris Frantz <cfrantz@google.com>
@cfrantz cfrantz requested a review from rusty1968 February 5, 2026 16:50
@linux-foundation-easycla
Copy link

linux-foundation-easycla bot commented Feb 5, 2026

CLA Not Signed

@cfrantz cfrantz requested a review from moidx February 5, 2026 16:51
Move the tooling and signing subdirectories into `//target/earlgrey` as
they are specific to the earlgrey target.

Signed-off-by: Chris Frantz <cfrantz@google.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant