Promote dev to main: DeepLethe brand capitalization#10
Merged
Merged
Conversation
…#2) Companion to the new branch protection rules just applied to the repo: - main is release-grade, PR-only, linear history, no force-push/delete - dev is integration, accepts direct push but still no force/delete - feat/* is documented convention only; no GitHub-side rule — contributors push freely, rebase freely, PR to dev when done Adds a typical-loop snippet so contributors don't have to read GitHub settings to figure out the workflow. Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
DCP firmware now runs on a second physical board. The lamp example flashed to a LILYGO T-Panel S3 and passed all 13 round-trip cases (tools/test_uart_roundtrip.py) over the S3's native USB-Serial/JTAG interface — no CH340-class USB-UART bridge chip in the path. This adds a second runtime-validated target alongside ESP32-WROOM-32, and a second ISA generation (Xtensa LX7 vs LX6). It also exercises DCP over a native-USB CDC link for the first time: same firmware, no transport-specific code, FQBN options USBMode=hwcdc + CDCOnBoot=cdc route the Arduino `Serial` to the USB-Serial/JTAG controller. S3 build footprint: 322 KB flash / 22.7 KB globals (PSRAM disabled, which is the safe bring-up config — the lamp example does not need PSRAM, so this avoids any QSPI-vs-OPI boot-loop risk). Changes: - README "Validated on real hardware": now states two boards; adds the native-USB detail - README cross-compile matrix: ESP32-S3 row added with runtime ✓ - README roadmap bullet updated - docs/paper/main.tex §validation: two-board statement + S3 added to the portability footprint list Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
The company brand is DeepLethe (camelCase), not deeplethe. Fixed the
lowercase occurrences in the public-facing author/affiliation fields:
- docs/paper/main.tex: \affil[1]{DeepLethe}
- firmware/esp32/library.properties: author / maintainer
- pyproject.toml: authors[].name (shows on the PyPI project page)
- docs/paper/README.md: submission-checklist reference
Not touched: examples/smart_panel_manifest.yaml still has
`vendor: deeplethe`, which is a separate question — the `vendor`
field elsewhere (lamp) uses a domain form (example.dev), so that one
should likely become a domain rather than just be recapitalized.
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Brings in PR #9.