RT-Thread / RT-Thread/rt-thread
[Feature] rt_null.c 初始化顺序太低 无法作为默认的日志口
Open
Beginner friendly
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 12.2k
- Forks
- 5.4k
- Avg merge
- 4d 12h
- Merged PRs (30d)
- 40
Description
Describe problem solved by the proposed feature
实际应用中 日志口与其它上行通信口复用，在需要调试时，特殊命令触发将上行协议通信口切换为常规日志口，但是如果想上电就不打印日志就需要将日志口切到无关的设备上，而 null设备就是一个理想的设备口，但是发现在初始化流程中 初始化日志口顺序比null高， 建议提高null初始顺序到 RT_USING_CONSOLE 之前
Describe your preferred solution
No response
Describe possible alternatives
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading rt_null.c and the initialization ordering around RT_USING_CONSOLE. Confirm how the null device and logging console are registered, then verify that the null device initializes early enough to serve as the default logging port and prevent startup logs from using the uplink port.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- embedded-iot, operating-systems
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100