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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
