Improve project description, structure update #3
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* introduce an example boot tree
* explain the macro toolset
* use auto-fill-mode (linebreaks around column 75-80)
* add Creative Common License
* remove hardcoded ${prefix}/${p_conf}/kernel
- all files are collected under ${p_conf} subdirectory
- references should be handled via symlinks (kernel, initramfs, dts, uEnv)
Signed-off-by: Ralf Zerres <[email protected]>
Intend: Proposal Motivation: The original project name is a bit war movie centric. I'd like to propose that a U-Boot's original interpretation is more `boot-loader` oriented. But the nautic correlation is inteded and well suited. Why not using this metapher and give U-Boot a dock: create and revamp its productive configuration and environment? Signed-off-by: Ralf Zerres <[email protected]>
* mainline u-boot is capable of btrfs boot * create a Makefile target to support it Signed-off-by: Ralf Zerres <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hey Uli,
i was busy to create a working boot environment for my vim3 and vim3l. I wanted to include your ideas proposed in this project.
While digging around and poking inside the board subdir i wanted to improve the option to support btrfs - which is quite simple, since u-boot is already supporting it.
Please take all a an RFC.
While understanding the toolstack and the macro creation, i thought others will probably stumble at the same bricks:
"Howto make a functional boot tree?" So i tried to implement a reference description inside the README.md that will make it more compehensable.
Please not on the changed macros, where i isolated the hardcoded subdir path to
kernel.While i was thinking about its purpose it wasn't clear to me, what i will gain from that.
In any way, i need to construct my boot-tree. If the underlying filesystem allows symlinks, i can introduce softlinks from the conf.d/${p_conf} targets directly to the proposed kernel.d substructure, or introduce a second stop - an arch structure. This is even more flexible, since i can have different "arch"-defaults consuming default kernel.d structures. Given the uEnv.txt it's still easy to overwrite all u-boot env variables as needed. ....
I also included a CC-License section which is hopefully in line with your intention.
Last but not least my comments on the project name. It's all up to you - just my 2 cents!
Lieben Gruss
Ralf