Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add Routastic hardware model #628

Merged
merged 1 commit into from
Dec 4, 2024
Merged

Conversation

Jorropo
Copy link
Contributor

@Jorropo Jorropo commented Nov 25, 2024

What does this PR do?

Allow to differentiate nodes running my own implementation VS meshtastic's code.

Checklist before merging

  • All top level messages commented
  • All enum members have unique descriptions

@Jorropo
Copy link
Contributor Author

Jorropo commented Nov 25, 2024

Copy pasting of my discord question:

For my new implementation I want to indicate I'm not using meshtastic's firmware in the nodeinfo.
Would you mind if I highjack the hardware field to indicate Routastic similar to PORTDUINO ? (just add a new enum entry)
Or should there be two fields one for the hardware and one for the implementation ? I think that make most sense but imo that overcomplicated I'll be running on linux exclusively and I doubt there will be dedicated hardware worth differentiating for anytime soon.

@thebentern thebentern merged commit 00c9c99 into meshtastic:master Dec 4, 2024
2 checks passed
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.

2 participants