-
Notifications
You must be signed in to change notification settings - Fork 61
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
Feature: TTY abstraction layer #14
Comments
Could you please post prototype and spec for this feature here? |
@yenwu Would you like to use pull request and make a WIP for this feature? |
@yenwu Just helping you developing... |
@tonghuix , thank for your interest and concern. I prefer to do it by myself, but there's truly lots of work to do. But It also welcomes to improve or extend it after I finished a POC. I could provide a brief impl guideline.
However, we just need a simplified version and retrieve the critical characteristics to re-impl all the stuff. That's all I thought important features. Any suggestions or cooperative tactic? |
@tonghuix , Sorry, I thought I use a misleading word, |
Thank you very much! I think your proposal are full fill for the feature, waiting your code now. |
Hi folks,
This a feature I'm working on. In the current implementation, we use
printk
without buffering. That would cause a poor performance and a huge section with interrupt disable. However, that's one of the reasons we want to import TTY abstraction layer. TTY layer could provide not only performance improvement but also better abstraction for the various device, such as UART, BLE, USB ... . It's also an good target to measure softirq we impl.By the way, this's feature would be released soon. Furthermore, folks should not work on this feature directly, because we already have a preliminary idea and some progress on it.
The text was updated successfully, but these errors were encountered: