From: Fu Wei <[email protected]>
This is a update of Chinese documentation: Documentation/zh_CN/arm64/booting.txt
It is based on the modifications of Documentation/arm64/booting.txt in submission:
"a7f8de16".
Signed-off-by: Fu Wei <[email protected]>
---
Documentation/zh_CN/arm64/booting.txt | 20 ++++++++++++--------
1 file changed, 12 insertions(+), 8 deletions(-)
diff --git a/Documentation/zh_CN/arm64/booting.txt b/Documentation/zh_CN/arm64/booting.txt
index 1145bf8..c1dd968 100644
--- a/Documentation/zh_CN/arm64/booting.txt
+++ b/Documentation/zh_CN/arm64/booting.txt
@@ -8,7 +8,7 @@ or if there is a problem with the translation.
M: Will Deacon <[email protected]>
zh_CN: Fu Wei <[email protected]>
-C: 1926e54f115725a9248d0c4c65c22acaf94de4c4
+C: 55f058e7574c3615dea4615573a19bdb258696c6
---------------------------------------------------------------------
Documentation/arm64/booting.txt 的中文翻译
@@ -20,7 +20,7 @@ Documentation/arm64/booting.txt 的中文翻译
中文版维护者： 傅炜 Fu Wei <[email protected]>
中文版翻译者： 傅炜 Fu Wei <[email protected]>
中文版校译者： 傅炜 Fu Wei <[email protected]>
-本文翻译提交时的 Git 检出点为： 1926e54f115725a9248d0c4c65c22acaf94de4c4
+本文翻译提交时的 Git 检出点为： 55f058e7574c3615dea4615573a19bdb258696c6
以下为正文
---------------------------------------------------------------------
@@ -125,18 +125,22 @@ AArch64 内核当前没有提供自解压代码，因此如果使用了压缩内
1 - 4K
2 - 16K
3 - 64K
- 位 3-63: 保留。
+ 位 3: 内核物理位置
+ 0 - 2MB 对齐基址应尽量靠近内存起始处，因为
+ 其基址以下的内存无法通过线性映射访问
+ 1 - 2MB 对齐基址可以在物理内存的任意位置
+ 位 4-63: 保留。
- 当 image_size 为零时，引导装载程序应试图在内核映像末尾之后尽可能
多地保留空闲内存供内核直接使用。对内存空间的需求量因所选定的内核
特性而异, 并无实际限制。
-内核映像必须被放置在靠近可用系统内存起始的 2MB 对齐为基址的
-text_offset 字节处，并从该处被调用。当前，对 Linux 来说在此基址以下的
-内存是无法使用的，因此强烈建议将系统内存的起始作为这个基址。2MB 对齐
-基址和内核映像起始地址之间的区域对于内核来说没有特殊意义，且可能被
-用于其他目的。
+内核映像必须被放置在任意一个可用系统内存 2MB 对齐基址的 text_offset
+字节处，并从该处被调用。2MB 对齐基址和内核映像起始地址之间的区域对于
+内核来说没有特殊意义，且可能被用于其他目的。
从映像起始地址算起，最少必须准备 image_size 字节的空闲内存供内核使用。
+注： v4.6 之前的版本无法使用内核映像物理偏移以下的内存，所以当时建议
+将映像尽量放置在靠近系统内存起始的地方。
任何提供给内核的内存（甚至在映像起始地址之前），若未从内核中标记为保留
(如在设备树（dtb）的 memreserve 区域），都将被认为对内核是可用。
--
2.5.5
On Thu, Apr 21, 2016 at 09:45:40PM +0800, [email protected] wrote:
> From: Fu Wei <[email protected]>
>
> This is a update of Chinese documentation: Documentation/zh_CN/arm64/booting.txt
>
> It is based on the modifications of Documentation/arm64/booting.txt in submission:
> "a7f8de16".
>
> Signed-off-by: Fu Wei <[email protected]>
> ---
> Documentation/zh_CN/arm64/booting.txt | 20 ++++++++++++--------
> 1 file changed, 12 insertions(+), 8 deletions(-)
>
> diff --git a/Documentation/zh_CN/arm64/booting.txt b/Documentation/zh_CN/arm64/booting.txt
> index 1145bf8..c1dd968 100644
> --- a/Documentation/zh_CN/arm64/booting.txt
> +++ b/Documentation/zh_CN/arm64/booting.txt
> @@ -8,7 +8,7 @@ or if there is a problem with the translation.
>
> M: Will Deacon <[email protected]>
> zh_CN: Fu Wei <[email protected]>
> -C: 1926e54f115725a9248d0c4c65c22acaf94de4c4
> +C: 55f058e7574c3615dea4615573a19bdb258696c6
Just curious, but what are these SHAs supposed to represent? Neither of
them looks particularly relevant to me.
Will
On Thu, 21 Apr 2016 17:42:28 +0100
Will Deacon <[email protected]> wrote:
> > -C: 1926e54f115725a9248d0c4c65c22acaf94de4c4
> > +C: 55f058e7574c3615dea4615573a19bdb258696c6
>
> Just curious, but what are these SHAs supposed to represent? Neither of
> them looks particularly relevant to me.
I'm kind of assuming it's the head of the repo at the time the update was
done.
I've applied the patch to the docs tree, anyway.
Thanks,
jon
Hi Will
On 04/22/2016 12:42 AM, Will Deacon wrote:
> On Thu, Apr 21, 2016 at 09:45:40PM +0800, [email protected] wrote:
>> From: Fu Wei <[email protected]>
>>
>> This is a update of Chinese documentation: Documentation/zh_CN/arm64/booting.txt
>>
>> It is based on the modifications of Documentation/arm64/booting.txt in submission:
>> "a7f8de16".
>>
>> Signed-off-by: Fu Wei <[email protected]>
>> ---
>> Documentation/zh_CN/arm64/booting.txt | 20 ++++++++++++--------
>> 1 file changed, 12 insertions(+), 8 deletions(-)
>>
>> diff --git a/Documentation/zh_CN/arm64/booting.txt b/Documentation/zh_CN/arm64/booting.txt
>> index 1145bf8..c1dd968 100644
>> --- a/Documentation/zh_CN/arm64/booting.txt
>> +++ b/Documentation/zh_CN/arm64/booting.txt
>> @@ -8,7 +8,7 @@ or if there is a problem with the translation.
>>
>> M: Will Deacon <[email protected]>
>> zh_CN: Fu Wei <[email protected]>
>> -C: 1926e54f115725a9248d0c4c65c22acaf94de4c4
>> +C: 55f058e7574c3615dea4615573a19bdb258696c6
>
> Just curious, but what are these SHAs supposed to represent? Neither of
> them looks particularly relevant to me.
Sorry for late response.
This is the checkout point when I translated the documentation.
I learn it from "MAINTAINERS", I would like to upstream my script patch
to keep track of the Documentation status. It can tell me
(1)which English doc is updated since I submitted the translation.
(2)which doc haven't been translated(a list)
M: original doc Maintainer(Maybe I should use "En" ro "E" for English)?
zh_CN: Chinese doc maintainer
C: Commit number or Checkout point
And my plan is that the patch can also be used in other languages, like
"ja_JP" and "ko_KR". I hope that can help or encourage more and more
people to do the doc translation work. And that can help people using
another language to learn and enjoy the kernel development more easily.
>
> Will
>
Hi Jonathan,
On 04/28/2016 09:16 PM, Jonathan Corbet wrote:
> On Thu, 21 Apr 2016 17:42:28 +0100
> Will Deacon <[email protected]> wrote:
>
>>> -C: 1926e54f115725a9248d0c4c65c22acaf94de4c4
>>> +C: 55f058e7574c3615dea4615573a19bdb258696c6
>>
>> Just curious, but what are these SHAs supposed to represent? Neither of
>> them looks particularly relevant to me.
>
> I'm kind of assuming it's the head of the repo at the time the update was
> done.
yes, you are right. :-)
next time, I just need to do
"git diff 55f058e7574c3615dea4615573a19bdb258696c6..HEAD <English doc> >
doc.patch" to see the difference :-)
>
> I've applied the patch to the docs tree, anyway.
Great thanks for your help! :-)
>
> Thanks,
>
> jon
>