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

Chapter 3.3 - excercise on decoupled arbiter is confusing #156

Open
wunderabt opened this issue May 30, 2021 · 0 comments
Open

Chapter 3.3 - excercise on decoupled arbiter is confusing #156

wunderabt opened this issue May 30, 2021 · 0 comments

Comments

@wunderabt
Copy link
Contributor

wunderabt commented May 30, 2021

The hints contained 3 points that confused me:

  • "consider having an internal wire of the selected channel" but the solution has no such wire. Is there really a point in using a wire or can this hint be removed?
  • "PriorityMux(List[Bool, Bits]), which takes in a list of valid signals and bits, returning the first element that is valid" where I figured bits would refer to the bits from the decoupled interface. But I guess any data works, right? Maybe a more general term like data can be used? [reading it again it's clear that the Chisel bits type is meant so I don't know why I got on the wrong the track here]
  • the solution uses foreach which was not introduced in the chapter. Would a map work too?
@wunderabt wunderabt changed the title Chapter 3.3 - excercise on decoupled arbiter is confusting Chapter 3.3 - excercise on decoupled arbiter is confusing May 30, 2021
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

1 participant