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

uartdpi: Use modern APIs for PTS device #83

Closed
imphil opened this issue Feb 7, 2019 · 7 comments
Closed

uartdpi: Use modern APIs for PTS device #83

imphil opened this issue Feb 7, 2019 · 7 comments
Assignees
Labels
Component:Software Issue related to Software Earlgrey-PROD Candidate Temporary label to triage issues into Earlgrey-PROD Milestones Type:Cleanup Cleanup tasks Type:FutureRelease Not relevant to currently planned releases/milestones

Comments

@imphil
Copy link
Contributor

imphil commented Feb 7, 2019

Currently we use a mix of old-school, non-standard BSD APIs to open a pseudo-terminal. There are newer APIs, which are unfortunately a bit underdocumented. However, the code at https://github.com/opensocdebug/osd-sw/blob/master/src/libosd/terminal.c#L188 does the trick.

@eunchan
Copy link
Contributor

eunchan commented Feb 12, 2019

Oh. I missed this. I should've wait until this PR is created.

@imphil
Copy link
Contributor Author

imphil commented Feb 12, 2019

Eunchan wrote:

One more thing to mention is, to make it work on macOS, I had to replace #include <pty.h> to #include <util.h> in hw/dv/dpi/ uart/ gpio DPI files.

We should keep macOS-compat in mind then when choosing the new APIs (if possible)

@lowrisc-bot lowrisc-bot transferred this issue from another repository Aug 31, 2019
@lowrisc-bot lowrisc-bot added Component:Software Issue related to Software Hotlist:SW Opinion Priority:P2 Priority: medium Type:Cleanup Cleanup tasks labels Aug 31, 2019
@aytong
Copy link

aytong commented Oct 30, 2019

@eunchan, @imphil , scrubbing stale issues... Is this still open?

@imphil
Copy link
Contributor Author

imphil commented Oct 30, 2019

yes

@msfschaffner
Copy link
Contributor

This issue came up in the D3 review for UART.
Is this something that we can close or re-categorize?

@a-will
Copy link
Contributor

a-will commented Jun 22, 2022

This seems like a nice-to-have cleanup that should not gate D3 for the IP. However, it hardly seems critical, given that the current APIs are present on all the platforms we target.

Even if we want to turn this into a requirement, the issue targets the simulation environment, so I feel that the associated milestone should be V3 (if at all). My opinion is that it shouldn't gate any of the chip milestones, though.

@msfschaffner
Copy link
Contributor

Thanks @a-will. Let's label this as V3 for now, and re-categorize once we are holding the V3 signoff review.

@msfschaffner msfschaffner added this to the Project: M3 milestone Jun 23, 2022
@GregAC GregAC added Type:FutureRelease Not relevant to currently planned releases/milestones Triaged and removed Milestone:V3 Priority:P2 Priority: medium labels Feb 23, 2023
@GregAC GregAC modified the milestones: Discrete: M3, Backlog Feb 23, 2023
@msfschaffner msfschaffner added the Earlgrey-PROD Candidate Temporary label to triage issues into Earlgrey-PROD Milestones label Oct 6, 2023
@msfschaffner msfschaffner modified the milestones: Backlog, Earlgrey-PROD.M5 Nov 7, 2023
@moidx moidx closed this as not planned Won't fix, can't repro, duplicate, stale Jun 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component:Software Issue related to Software Earlgrey-PROD Candidate Temporary label to triage issues into Earlgrey-PROD Milestones Type:Cleanup Cleanup tasks Type:FutureRelease Not relevant to currently planned releases/milestones
Projects
None yet
Development

No branches or pull requests

9 participants