Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] can't create /dev/ttys0 on cirrus ARM EP93XX
Date: Sat, 7 Aug 2010 18:55:16 +0200	[thread overview]
Message-ID: <20100807185516.21da8fc0@surf> (raw)
In-Reply-To: <AANLkTikvxE-my1WWLsNAYZnXRY6RiP-NtyxpgsNoCyN6@mail.gmail.com>

Hello Anthony,

On Sat, 7 Aug 2010 17:10:42 +0100
anthony henderson <development@fair-games.com> wrote:

> So I've ran buildroot for the ARM 920T.  All seems fine.  As the board has
> no keyboard ect development is done via serial port.  This is set in the old
> rootfs from etc/initab via
> ttyAM0::askfirst:-/bin/sh

Correct.

> I tried to start the new rootfs, but it appears to want to start from video
> command prompt.  So I copied the inittab from the old working system to the
> new rootfs, this gave an error finding ttyAM0.

Just modify Buildroot /etc/inittab instead.

> On searching the new rootfs I can see dev doesn't have this node.

Yes, it must be created. So, add the following line to
target/generic/device_table.txt:

/dev/ttyAM     c       666     0       0       204     16      0	1       4

It will make that /dev/ttyAM0, /dev/ttyAM1, /dev/ttyAM2 and /dev/ttyAM3
are created when building the root filesystem.

If you want to automate the adaptation of the /etc/inittab, just add an
entry in target/generic/Config.in.

Regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

      reply	other threads:[~2010-08-07 16:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-07 16:10 [Buildroot] can't create /dev/ttys0 on cirrus ARM EP93XX anthony henderson
2010-08-07 16:55 ` Thomas Petazzoni [this message]

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=20100807185516.21da8fc0@surf \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.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