Skip to content

Add new chapter for carrier board development#88

Open
mhei wants to merge 1 commit intoeverest/charge_somfrom
everest/charge_som_dt_eeprom
Open

Add new chapter for carrier board development#88
mhei wants to merge 1 commit intoeverest/charge_somfrom
everest/charge_som_dt_eeprom

Conversation

@mhei
Copy link
Member

@mhei mhei commented Feb 26, 2026

Start this new section with some idea/background for the DT EEPROM. Later we can make this a sub-chapter and add other hints as well.

Copy link
Contributor

@barsnick barsnick left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some minor grammar nits.

I'm also missing a few "the" or "a" before some nouns, will add these remarks later.

@mhei mhei force-pushed the everest/charge_som_dt_eeprom branch 2 times, most recently from 77cf4a8 to a13d60a Compare February 26, 2026 15:15
Copy link
Member

@lategoodbye lategoodbye left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks nices. Just a few nits.

@mhei mhei force-pushed the everest/charge_som_dt_eeprom branch from a13d60a to 2906778 Compare February 27, 2026 12:01
- The same applies to the DT Overlay Signature Blob.
- The vendor specific header part can be used also for customer specific data. The C structure reflects what chargebyte
is going to use as example.
- The Vendor ID can be used by customers to identify different carrier boards and/or to determine how the vendor
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Vendor code?

Start this new section with some idea/background for the DT EEPROM.
Later we can make this a sub-chapter and add other hints as well.

Signed-off-by: Michael Heimpold <michael.heimpold@chargebyte.com>
@mhei mhei force-pushed the everest/charge_som_dt_eeprom branch from 2906778 to b446f32 Compare March 4, 2026 10:17
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.

3 participants