Skip to content
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

Is the Wishbone in itself licensed/protected in any way? #24

Open
m-kru opened this issue Mar 30, 2022 · 13 comments
Open

Is the Wishbone in itself licensed/protected in any way? #24

m-kru opened this issue Mar 30, 2022 · 13 comments

Comments

@m-kru
Copy link

m-kru commented Mar 30, 2022

The Wishbone B3 specification doesn't have any copyright, Wishbone B4 has copyright. However, what about the whole Wishbone idea and the design concept? Is it protected by any license or patent? I am wondering how much can one be inspired by Wishbone when designing his own bus.

@wallento
Copy link
Contributor

The B4 spec has been highly disputed because of that (along technical issues). I would recommend starting from B3, which also was the initial goal when we tried to support the standard. Unfortunately, the steward @rherveille didn't further participate in the dicussions and the entire project is stalled since then.

Starting from the B3 spec was the initial goal and some work was done, we are happy to discuss proceeding under a different name if you are planning to permanently evolve it.

@m-kru
Copy link
Author

m-kru commented Mar 30, 2022

Is there any mailing list?

@rherveille
Copy link
Collaborator

rherveille commented Mar 30, 2022 via email

@m-kru
Copy link
Author

m-kru commented Mar 30, 2022

@rherveille personally I don't want anything. I am wondering how much I can take from the Wishbone when designing similar bus.

@rherveille
Copy link
Collaborator

rherveille commented Apr 4, 2022 via email

@m-kru
Copy link
Author

m-kru commented Apr 4, 2022

Besides the obvious question; why do you want to design a similar bus instead of using Wishbone?

Because I don't like what happened with Wishbone in B4. The specification is no longer orthogonal. Standard cycle with registered feedback bus cycle duplicates the functionality of pipelined cycle capabilities. Generally the pipelined mode is more robust and generic and this is the only advantage of B4. I think the standard mode should be removed. I don't like the fact that error is single bit information, this is not enough and extending it with data tag is not a solution that scales well. I also think that operand size and granularity should not be part of the bus specification. Maybe granularity, but for sure not the operand size.

@wallento
Copy link
Contributor

wallento commented Apr 4, 2022

Fully agree. We hat this discussion and therefore started a new spec from B3. Unfortunately it was stalled due to lack of time and responses. We can release an update from the current master branch if @rherveille agrees. We would welcome any further development of B3 towards further revisions. @rherveille is the steward here, maybe you can delegate the further development to interested developers that have the bandwidth?

@m-kru
Copy link
Author

m-kru commented May 18, 2023

@rherveille ping

@rherveille
Copy link
Collaborator

:) It's probably time to start again

@ams
Copy link

ams commented May 20, 2023

The Wishbone spec is placed in the public domain. The document, as is, can be used without restrictions. However ‘public domain’ does not mean free of copyright or other rights, especially given the large variety of legislation in the world around those subjects.

That is not the case. PD menas that it is indeed without restrictions and free of copyright. The vast legislation in the world is based on the Berne convention.

The real question is if WB is infact in the PD, how a work is put into the PD very specific in each country, and in some you cannot do so (other than dying and waiting many years).

@rherveille
Copy link
Collaborator

rherveille commented May 20, 2023 via email

@ams
Copy link

ams commented May 20, 2023 via email

@rherveille
Copy link
Collaborator

rherveille commented May 20, 2023 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants