Skip to content
This repository has been archived by the owner on Sep 7, 2020. It is now read-only.

[TASK] Clean up bwl interface #477

Closed
arnout opened this issue Nov 7, 2019 · 0 comments
Closed

[TASK] Clean up bwl interface #477

arnout opened this issue Nov 7, 2019 · 0 comments
Labels
enhancement New feature or request

Comments

@arnout
Copy link
Collaborator

arnout commented Nov 7, 2019

Description

The current BWL interface has evolved historically into its current shape. Because of that, it is a bit more complicated than strictly necessary for prplMesh purposes. In addition, there are probably a few functions that are not really needed.

Several new bwl backends will be added for different chipsets. Therefore, the BWL interface will become external API that is going to be more difficult to change. Thus, we should freeze that API. It is therefore important to do any refactoring now, before more backends are added.

Look at BWL as a whole and determine which API is really needed, and refactor it in that direction.

This ties in with #448 and #435.

This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant