From: Scott Wood <scottwood@freescale.com>
To: liran raz <liranrazlinux@gmail.com>
Cc: linuxppc-dev@ozlabs.org, Timur Tabi <timur@tabi.org>
Subject: Re: node /dev/ttyCPM2 not created
Date: Wed, 18 Mar 2009 13:37:26 -0500 [thread overview]
Message-ID: <20090318183726.GC3410@loki.buserror.net> (raw)
In-Reply-To: <e3b3ab5c0903160639u625a0fd3xa665896bb378b109@mail.gmail.com>
On Mon, Mar 16, 2009 at 05:39:08AM -0800, liran raz wrote:
> Thanks, I don't see any mdev process running.
Does it run during the boot scripts? Or do you have udev?
> Just wonder who is creating /dev/ttyCPM1 since in the device table file
> (device_table.txt)
> I have only node: 204 (major) 46 (minor) defined.
> But I can see /dev/ttyCPM1 (204 47)
Ideally, it would be a program such as udev or mdev. If you're using a
static /dev with no utility to automatically create nodes, then it's *you*
that creates it, with mknod. :-)
-Scott
next prev parent reply other threads:[~2009-03-18 18:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-13 18:56 node /dev/ttyCPM2 not created liran raz
2009-03-14 0:18 ` Timur Tabi
2009-03-16 13:39 ` liran raz
2009-03-18 18:37 ` Scott Wood [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-03-13 20:03 liran raz
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=20090318183726.GC3410@loki.buserror.net \
--to=scottwood@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=liranrazlinux@gmail.com \
--cc=timur@tabi.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.