The tty Layer

In the first of a series of articles on device-driver development, we'll start with how the kernel handles the system console and serial ports.
Conclusion

We have covered the basics of the tty layer, explaining all of the different fields in the tty_driver structure for the 2.4 kernel tree and pointing out which ones are necessary for a driver to implement. The tiny_tty.c driver, see Listing 3 [available at ftp.linuxjournal.com/pub/lj/listings/issue100/5896.tgz], is a good example of a very minimal tty driver that successfully works. Feel free to use this code as an example for your own tty drivers in the future.

Resources

Greg Kroah-Hartman is currently the Linux USB and PCI Hot Plug kernel maintainer. He works for IBM, doing various Linux kernel-related things and can be reached at greg@kroah.com.

______________________

Comments

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Needs some explanation

Sathish Kumar's picture

The explanation is fine... but if we add the flow graph it will be useful for newbies.....
Please explain detail about tty driver, device, layer...... beacuse the flow is not clear

Need flow diagram

Ajay Thakur's picture

Yes this article is good but it takes time to understand
the flow of data from application to hardware and vice-versa.
It would be good if you can add data flow diagram.
Thanks
Ajay

Re: The tty Layer

Anonymous's picture

the section of "why no Read" is not clear, can you explain more ?

Re: The tty Layer

Anonymous's picture

Excellet article, one suggestion.
Adding a listing section which carries a Test code to perform
test on tty driver will be very usefull for newbies.

Brilliant article !!!

Romel's picture

Brilliant article !!!
but more codes example would have been helpful for newbies like me..
thanks..
cheers
romel
INDIA

White Paper
Fabric-Based Computing Enables Optimized Hyperscale Data Centers

Today’s modular x86 servers are compute-centric, designed as a least common denominator to support a wide range of IT workloads. Those generic, virtualized IT workloads have much different resource optimization requirements than hyperscale and cloud applications. They have resulted in a “one size fits all” enterprise IT architecture that is not optimized for a specific set of IT workloads, and especially not emerging hyperscale workloads, such as web applications, big data, and object storage. In this report, you will learn how shifting the focus from traditional compute-centric IT architectures to an innovative disaggregated fabric-based architecture can optimize and scale your data center.

Learn More

Sponsored by AMD

White Paper
Red Hat White Paper: Using an Open Source Framework to Catch the Bad Guy

Built-in forensics, incident response, and security with Red Hat Enterprise Linux 6

Every security policy provides guidance and requirements for ensuring adequate protection of information and data, as well as high-level technical and administrative security requirements for a system in a given environment. Traditionally, providing security for a system focuses on the confidentiality of the information on it. However, protecting the data integrity and system and data availability is just as important. For example, when processing United States intelligence information, there are three attributes that require protection: confidentiality, integrity, and availability.

Learn more about catching the bad guy in this free white paper.

Learn More

Sponsored by DLT Solutions