8000 Path to make actual changes in HLS · Issue #5 · nlsynth/karuta · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Path to make actual changes in HLS #5

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.

Sign up for GitHub

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

Jump to bottom
Open
yt76 opened this issue Mar 14, 2020 · 3 comments
Open

Path to make actual changes in HLS #5

yt76 opened this issue Mar 14, 2020 · 3 comments

Comments

@yt76
Copy link
Contributor
yt76 commented Mar 14, 2020

IMHO, HLS technology is stuck with C/C++ for decades while software industry adopts per ecosystem new programming languages with new technology and they actually bring us improved development experience.
So, the objective of this project is to explore the potential of HLS without restriction of C/C++ by designing a new language. New language should allow users to describe essentials of circuits easily.
Here are some options we might consider:

  1. Continue on the current efforts to improve the quality and features.
    This is current plan anyway for now. However, it will take very long time to achieve production quality. Possibly I can get ask more investment in some future when I will be more confident with the direction and implementation.
  2. Build attractive IPs easily and showcase them.
    Attractive applications might be useful to explain the potential. This will also drive quality improvement.
  3. Let someone reuse the idea.
    If someone find this concept useful and implement similar language for their ecosystem, it would be nice for us as well.
  4. Let someone fork the code.
    As Karuta (and Iroha) is released under an Open Source license, someone with more development resource than us can improve it to production quality
  5. Let someone buy the code.
    This is also fine. The buyer can optionally get an engineer :p
@TenzinCHW
Copy link
TenzinCHW commented Nov 5, 2020 •
edited
Loading

Hi, I would like to contribute to 1 as I currently need some IPs which are really obfuscated in tools like Vivado, and which might have different implementations for other brands of FPGA (or no implementation at all). I really like the way things work in Karuta because it seems like it's a very natural way to implement concurrent logic as processes in sequential code.

I am currently developing an SD card reader using Karuta, but I think I have found a few bugs which happen here and there, which probably result from me not really understanding many constructs of the language. I think a basic syntax documentation will help (how to do conditionals, what do functions like wait do, differences between process and func, things like that).

@yt76
Copy link
Contributor Author
yt76 commented Nov 7, 2020

Thank you for encouraging comment again!

I see. I am going to add more description to the document about the basic structures of Karuta code.
Please let me known any suspicious behaviors, unclear documentation or even your own confisions. These information should be useful to improve Karuta and for new users to use it.

As of now, my priority is on new features especially pipelining, but I am glad to get back to basic quality improvements.

@TenzinCHW
Copy link

:)

Alright that sounds good. Yup maybe I can help document in case I find anything that doesn't work/is confusing.

Ah yes, pipelining sounds important. Thank you for your hard work!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@yt76 @TenzinCHW
0