Opencl and OpenMp rewrite Linux base.
Rewrite implementation.
Opencl and OpenMP
Directly add at first if needed rewrite.
Example: https:/
But to build linux in the special way...
Offloading to gpu and multithreading
We need to go back to the beginning of this basic concept.
And take the smallest things that make everything basic
Work... Transfigure all of it.
It's not allot of rewriting code.
You simply add the basics first.
You then run it through the
Builder and see what happens.
If all is good... And the basics of everything is complete?
Then we have our working Alpha stage.
We must test just the functionality of the idea by simply
Adding easy things.. running it and see if our changes are
Effective.
Then we can get specifics associated.
If you would like to help make this possible?
Why not join in and help with anything your good at :-)
Nothing is stopping you or me ;-)
Get in contact with me right?
Just leave a message..
hey i can do some stuff and want to help.
Maybe you know someone or people that might be interested.
Blueprint information
- Status:
- Not started
- Approver:
- Chris Brown
- Priority:
- Medium
- Drafter:
- Chris Brown
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- New
- Series goal:
- Accepted for trunk
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
Add all the basics that compile the buildroot
Examine what we can use. Stability first ,basics
We pick the versions that work across the spectrum.
This defines our standards.
A common good standards practice ,evolves from
what is stable and working and effective.
The 1 goal is to download the basics.
A linux stable kernal
A compiler we can jack into with opencl and openMp
The standards we can start with are
The basics.. what works togeather first!
Stability ,then change what's needed ,step by step.
Let's get the basics rolling first.
Unification of what works with buildroot.
Because that's our automated system we will use.
We are only after the basics at first.
The extreme basic uniformity.
The basic compiler.
The boot sequence.
The tools that create the partitions.
The versions of everything that works.
So this will provide our basics and standards to
Gain system wide multiplex effectiveness ,with everything we
do.
Just because a compiler doesn't support opencl or openMP 5x that doesn't mean we can't invoke that stupid compiler with the 5x code and get that stupid compiler ,compiled with a supported compiler no?
Example: Clang supported features can compile gcc unsupported features.
Why? To get the ball rolling forward. The point? = The project!
Focus on the solutions not the problems.
Become a self driven solutions provider ;-)
Look beyond the problem ,into the future.. because that's where we are supposed to be at.
Please excuse my terminology of stupid , it's only a figure of speech and expression.
Work Items
Dependency tree
* Blueprints in grey have been implemented.
