Messages in this thread | | | Subject | RE: Device node - How does kernel know about it | Date | Thu, 27 Dec 2007 19:23:28 -0800 | From | "Siva Prasad" <> |
| |
Thanks for the response Phillip. See below for response.
I already am using "console=ttyS0" as well as set the inittab correctly.
I would like to debug this node behavior. Can you please let me know which routine gets called first when there is, for example a read() call from user program. Eventually it will result in a call to what ever read routine registered, but that must be a call back function or some thing. Right?
- Siva
-----Original Message----- From: Phillip Susi [mailto:psusi@cfl.rr.com] Sent: Thursday, December 27, 2007 12:10 PM To: Siva Prasad Cc: linux-kernel@vger.kernel.org Subject: Re: Device node - How does kernel know about it
Siva Prasad wrote: > Hi, > > How do the device nodes work as an interface between user and kernel > programs, and how to go debugging it? > This is as part of my debugging effort on an embedded board.
The filesystem sets specific bits in the mode mask and elsewhere in the inode to mark the file as a dev node, and which major/minor device number it should be linked to. The kernel device drivers register to handle a given device number.
> * It all started with the problem of "not printing" any thing that comes > from ramdisk (echo and printf statements), while kernel printk's work > perfectly fine. > * Ramdisk is also executing fine, just that prints are not coming out of > serial. I can see the execution of various user programs with a printk > in sys_execve() routine. Ramdisk has all the required files like > /dev/console, /dev/ttyS0, etc.
So you did you pass the console=ttyS0 parameter to the kernel? Did you configure your inittab to spawn the getty on the serial port instead of /dev/ttyN? You might want to take a look at the Linux Serial Console HOWTO.
| |