commaai / commaai/vamOS

[todo] update firmware locations & paths

Open
#123 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Shell
Stars
27
Forks
17
Avg merge
2d 15h
Merged PRs (30d)
1

Description

in general the firmware-name should something like

`qcom/sdm845/mba.mbn` -> `qcom/sdm845/Comma/tizi/mba.mbn`
vendor can be `Comma`, `Comma.AI`, `comma`, whatever you decide for the project
codename can be `tizi` or `mici`, depends what came first or what is the preferred codename (can be shared by both models of course).

No need to do this changes ASAP, but for the proper mainlining it's needed, so going in that direction smooth the transition.

Contributor guide

No contributing guide indexed for this repository

Research direction

No file, test, or entry point is named. Start by locating the current firmware-name and path definitions, then inspect how firmware paths are consumed for the comma 3X and comma four. Confirm the vendor and codename convention, and consider the work done when both models use the agreed paths consistently.

Written by the indexing model from the issue text.

Assessment

Tech stack
shell
Domain
embedded-iot, operating-systems
Issue type
Refactor
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.