linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Phillip Susi <psusi@cfl.rr.com>
To: Siva Prasad <sprasad@bivio.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Device node - How does kernel know about it
Date: Thu, 27 Dec 2007 15:10:10 -0500	[thread overview]
Message-ID: <477406A2.2070904@cfl.rr.com> (raw)
In-Reply-To: <D83235F0F3C86D4D889D8B9A0DA8C6D7012AF95A@corpexc01.corp.networkrobots.com>

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.



  reply	other threads:[~2007-12-27 20:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-27  1:34 Device node - How does kernel know about it Siva Prasad
2007-12-27 20:10 ` Phillip Susi [this message]
2007-12-28  3:23   ` Siva Prasad

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=477406A2.2070904@cfl.rr.com \
    --to=psusi@cfl.rr.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sprasad@bivio.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).