linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Jon Smirl" <jonsmirl@gmail.com>
To: "Siva Prasad" <sprasad@bivio.net>
Cc: linuxppc-dev@ozlabs.org, linuxppc-embedded@ozlabs.org
Subject: Re: Device node - How does kernel know about it
Date: Wed, 26 Dec 2007 21:55:51 -0500	[thread overview]
Message-ID: <9e4733910712261855p74a64c48pc7e89ebdd97d4a76@mail.gmail.com> (raw)
In-Reply-To: <D83235F0F3C86D4D889D8B9A0DA8C6D7012AF958@corpexc01.corp.networkrobots.com>

On 12/26/07, Siva Prasad <sprasad@bivio.net> wrote:
> Hi,
>
> I am really interested in finding out how kernel knows about device
> nodes and how the whole thing work. This is as part of my debugging
> effort on 8641D based PowerPC board.
>
> * 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.

Does adding console=ttyS0,baud to the kernel boot command line fix it?

-- 
Jon Smirl
jonsmirl@gmail.com

  reply	other threads:[~2007-12-27  2:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-27  1:31 Device node - How does kernel know about it Siva Prasad
2007-12-27  2:55 ` Jon Smirl [this message]
2007-12-28  8:39 ` Nicholas Mc Guire
2007-12-28  3:27   ` Siva Prasad
2007-12-28  4:15     ` Jon Smirl
2007-12-28  4:55       ` Siva Prasad
2007-12-30 23:43     ` Brad Boyer

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=9e4733910712261855p74a64c48pc7e89ebdd97d4a76@mail.gmail.com \
    --to=jonsmirl@gmail.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=linuxppc-embedded@ozlabs.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).