want help for writing device driver for printer on Redhat Linux 9
Linux - GeneralThis forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
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.
I'm writing device driver for dot matrix printer EPSON LP-300
The prob is, m not getting how drivers for printer works
I google for it bt m nt getting any information ...
Can anyone is in a position to let me know the theory abt the functionality of these printer drivers...
{like what happen when we gv print cmd & so on...???)
I'm writing device driver for dot matrix printer EPSON LP-300
The prob is, m not getting how drivers for printer works
I google for it bt m nt getting any information ...
Can anyone is in a position to let me know the theory abt the functionality of these printer drivers...
{like what happen when we gv print cmd & so on...???)
pls pls help me as early as possible ...
m kindly waiting for u...
You want to write a kernel driver by asking people how to proceed in an online discussion group? Don't you think it would be more productive to actually study the topic in depth, by for example browsing the Web and reading the many detailed articles on the topic?
There is a name for what you are doing ... it's called "programming by newsgroup." It doesn't work.
Quote:
Originally Posted by pops13
The prob is, m not getting how drivers for printer works I google for it bt m nt getting any information
Also, you need to pay attention to communication issues, or you will never succeed as a programmer. When you try to abbreviate everything and type as fast as humanly possible, you create a result that cannot be parsed -- by either a compiler or a human being.
This also explains how you managed not to find any of the numerous Web articles about kernel driver design. Chances are they were written in complete, comprehensible sentences, which bored you so much that you fell asleep at the keyboard.
So.....it turns out that you already have the book I recommended. I also note that you did not post any follow-up in your first thread on this topic. I would suggest that you tell us something specific in the LDD book that you do not understand.
Quote:
pls pls help me as early as possible ...
When you say something like this, and then don't respond to people's help, you will not have much credibility here.
Last edited by pixellany; 09-26-2009 at 11:15 AM..
Hello pixellany, lutusp, John VV
Please don't miss understood me.
Actually I didn't expected this early replay from u friends.
I am actually new to this online discussion's.
Specially to lutusp, I will take care while asking questions & also towards my communication.
So here I will explain you till the date what I have done.
- I already have the copy of "Linux Device Drivers" from O'Reily.
- I'm using RHL-9.0(kernel 2.4.x)
- I downloaded Kernel source tree (kernel 2.6.17.11) & configured, Build & installed it.
- I registered my driver(/proc/devices & /dev entries are made with major & minor number)
- now I stuck up because I am not getting what to do next(I searched a lot nut I might be firing a wrong query that's why required some help).
As a fresher, I'm going step by step.
According to me before moving ahead, I should know that how these printer driver works exactly(that's why that post).
==> I only gone through some chapters of that book(still reading & it take times to understand each an everything till its implementation)
==> Do I need some more patience?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.