8 Commits

Include renames

Author	SHA1	Message	Date
Jonathan BennettandGitHub	7adfc3f992	Remove incorrect LED_STATE_ON definition for t-beam-s3 (#10280) ... Fixes #9912 and #10170	2026-04-24 15:17:33 +10:00
Jonathan BennettandGitHub	200e79e800	You get an RTC, and you get an RTC! (delete HAS_RTC as it wasn't actually doing much) (#9493)	2026-01-30 11:54:49 -06:00
JorropoandGitHub	beb268ff25	Revert "add a .clang-format file (#9154)" (#9172) ... I thought git would be smart enough to understand all the whitespace changes but even with all the flags I know to make it ignore theses it still blows up if there are identical changes on both sides. I have a solution but it require creating a new commit at the merge base for each conflicting PR and merging it into develop. I don't think blowing up all PRs is worth for now, maybe if we can coordinate this for V3 let's say. This reverts commit 0d11331d18.	2026-01-04 05:15:53 -06:00
JorropoandGitHub	0d11331d18	add a .clang-format file (#9154)	2026-01-03 14:19:24 -06:00
5 people	8fdba1f1e2	RTC: PCF85063 support, port to SensorLib 0.3.1 (#8061) ... * RTC: PCF85063 support, port to SensorLib 0.3.1 * Tidy up defines * Remove RTC/PCF8563 mentions from unrelated variants * Bump SensorLib 0.3.2 * Use SensorRtcHelper * Consistent warning message * Fix oversight Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> --------- Co-authored-by: Manuel <71137295+mverch67@users.noreply.github.com> Co-authored-by: Ben Meadors <benmmeadors@gmail.com> Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>	2025-12-20 19:10:21 -06:00
Marius FaberandGitHub	001654e90a	Add basic LR1121 support for T-Beam S3, full support needs #4775 fixed (#8349)	2025-11-01 09:38:37 +11:00
m1nl	ba26d03b1b	standarize values of HAS_32768HZ capability flag	2025-08-25 19:44:13 +02:00
AustinandGitHub	475cfe4af2	ESP32s3: Migrate variants to new structure (#7343)	2025-07-20 16:47:37 -05:00