rust-raspberrypi-OS-tutorials/.editorconfig

# editorconfig.org

root = true

[*]
charset = utf-8
end_of_line = lf
insert_final_newline = true
indent_style = space
trim_trailing_whitespace = true
max_line_length = 100

[Dockerfile]
indent_size = 4

[{Makefile,*.mk}]
indent_style = tab
indent_size = 8

[*.rb]
indent_size = 4

[*.rs]
indent_size = 4

[*.s]
indent_style = tab
indent_size = 8

[*.sh]
indent_size = 4

[*.toml]
indent_size = 4

[*.{yml,yaml}]
indent_size = 2
Add editorconfig 2019-11-26 07:46:13 +00:00			`# editorconfig.org`

			`root = true`

			`[*]`
			`charset = utf-8`
			`end_of_line = lf`
			`insert_final_newline = true`
			`indent_style = space`
			`trim_trailing_whitespace = true`
Add line length to editorconfig 2020-09-24 21:30:56 +00:00			`max_line_length = 100`
Add editorconfig 2019-11-26 07:46:13 +00:00
			`[Dockerfile]`
			`indent_size = 4`

Add tutorial 17 2022-04-25 21:23:26 +00:00			`[{Makefile,*.mk}]`
Add editorconfig 2019-11-26 07:46:13 +00:00			`indent_style = tab`
			`indent_size = 8`

			`[*.rb]`
			`indent_size = 4`

			`[*.rs]`
			`indent_size = 4`

Revert to assembly boot code It is too risky to rely on the compiler to not insert any operations using the stack. Having a stack-setting call in Rust using the cortex-a crate as the first action in a Rust-only _start() function does not work if you're subsequently using the stack, because the compiler often inserts the operations to make room on the stack to prepare a function call BEFORE the call to set the stack, which crashes the boot process. Hence, keep on using a small piece of assembly boot code throughout. 2021-03-20 08:41:43 +00:00			`[*.s]`
			`indent_style = tab`
			`indent_size = 8`
Add editorconfig 2019-11-26 07:46:13 +00:00
			`[*.sh]`
			`indent_size = 4`

			`[*.toml]`
			`indent_size = 4`

			`[*.{yml,yaml}]`
			`indent_size = 2`