> For the complete documentation index, see [llms.txt](https://book.bsdcn.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://book.bsdcn.org/rpicn/qian-yan/changelog.md). # 编辑日志 * 2024.6.5 同步至 * 2024.6.5-2024.7.11 完全重译“树莓派启动盘制作工具” * 2024.7.11 同步至 * 2024.7.11 “入门”校对完成 * 2024.7.12 “树莓派系统（Raspberry Pi OS）”校对完成 * 2024.7.16 对 16 个树莓派系统部件进行了翻译，已合并 15 个。1 个项目已弃用 * 2024.6.5-2024.7.16 改正了官方文档原文中的两个错误，补充了一个摄像机型号。已合并 * 2024.7.21 "系统配置"校对完成 * 2024.8.1 * “config.txt”校对完成 * “RP1”校对完成 * 2024.8.9 同步至官方文档的 2024.8.9 版本 * 2024.8.15 实现代码高亮 * 2024.9.4 * 同步至官方文档的 2024.9.4 版本。 * “旧版 `config.txt` 参数”校对完成 * 将发现的一个命令错误，一个排版问题提交到树莓派上游，已合并 * 2024.9.7 请求树莓派上游更新树莓派启动盘制作工具的版本以包含最新的简中翻译， * 2024.9.8 同步至官方文档的 [2024.9.8 版本](https://github.com/raspberrypi/documentation/commit/1b7709fea907aed7af8950f936ccfd1b82a29edd)。 * 2024.9.12 * 树莓派上游发布了树莓派启动盘制作工具v1.9.0 * 测试了树莓派启动盘制作工具v1.9.0 * 将本项目的翻译、图片同步到树莓派启动盘制作工具v1.9.0 * 修正了关于树莓派启动盘制作工具v1.9.0 翻译的几处小错误 ，已经合并，预计随 v1.9.1 分发 * “Linux 内核”校对完成 * 2024.9.14 “远程访问”图片本地化 * 2026.10.18 * 重写 AGENTS.md 使其适配本项目（原为 FreeBSD 手册项目模板）：更正同步基线为 1b7709f（2024.9.8，此前误记为 f0511a2），补充原文获取、同步上游、翻译校对等工作流及本项目实际格式规范 * 核对 27 个中文页面与上游 1b7709f 结构一一对应，SUMMARY.md 无缺失条目 * 修复 mu-lu.md 微控制器表格：5 张卡片误入 3 列表格，导致 MicroPython、C/C++ SDK 两卡在渲染时被丢弃；C/C++ SDK 卡片误链 micropython.md 并误用 TV HAT 配图，已改为正确链接与官方 C-and-CPP.png 配图 --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://book.bsdcn.org/rpicn/qian-yan/changelog.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.