-
Notifications
You must be signed in to change notification settings - Fork 57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
1st-CLaaS Kernel in WARP-V Configurator #115
base: master
Are you sure you want to change the base?
Conversation
✅ Deploy Preview for warp-v ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Generally looks good, but let's get the template a bit cleaner before merging.
formattingSettings = settings.formattingSettings.filter(formattingArg => formattingArg !== "--fmtNoSource") | ||
} | ||
let boilerplate_1st_ClaaS = `\\m5_TLV_version 1d${formattingSettings.length > 0 ? ` ${formattingSettings.join(" ")}` : ""}: tl-x.org | ||
\\m5 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We want as much of this file as possible to be placed in a library file and included. Anything the user might want to configure should remain here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You mean the functions like kernel module def and random tb should be part of a library file? lines 180-221.
And what about the kernel 1,2,3 pipelines from lines 276 to 378
A radio button in the configurator allows the option to generate 1st-CLaaS WARP-V kernel from the configurator