Code query on /usr/src/linux/drivers/serial/uart00.c
ProgrammingThis forum is for all programming questions.
The question does not have to be directly related to Linux and any language is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Code query on /usr/src/linux/drivers/serial/uart00.c
Hi,
Is there anyone here working on serial drivers? Specifically on serial ports. I cant seem to find any forums (linuxforums and kernelnewbies) that is actively answering any kernel code questions so I came back here. I would want to know your opinion on what does this piece of code in /usr/src/linux/drivers/serial/uart00.c means because I am trying to create a similar functionality based on its algorithm but I not sure what does this code does. What does the highlighted code does? It seems to be dividing the fifosize by 2, and uses the result as count of transmit transaction. But why is this so?
I see no reason for that piece of code other than something in that uart documentation. From what I see the size is 16, so count is set to 4. Internal buffer, maybe? I can't find out which chip the driver is for exactly, unfortunately.
If you're writing for a different chip, than simply continue with full size, but check documentation of your chip carefully here.
I see no reason for that piece of code other than something in that uart documentation. From what I see the size is 16, so count is set to 4. Internal buffer, maybe? I can't find out which chip the driver is for exactly, unfortunately.
Ah the size is 16, and it becomes 8 after the shift.
What do you mean by N octets at once? N bytes at once?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.