From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] cannot log to my build root
Date: Tue, 14 Dec 2010 14:25:44 +0100 [thread overview]
Message-ID: <20101214142544.7863d2d2@surf> (raw)
In-Reply-To: <AANLkTine190SpsTRLjzsOvdTFjAXiEwDK4yd8Vmkhsj_@mail.gmail.com>
On Tue, 14 Dec 2010 15:06:43 +0200
Diego Iastrubni <diegoiast@gmail.com> wrote:
> I am using buitdroot to create my development environment (the
> production is something bigger and slower made manually once...). I
> am using codesourcery for arm as the toolchain. the HW (which is not
> relevant to the scenario) is an OMAP3 device boots with my old
> firmware).
>
> I forked (I use git and not released versions) buildroot a few
> months and its worked after I manually mknod'ed some devices. Now I
> pulled from you guys, and now I cannot even login to my new clean
> environment (last time it was /dev/tty ,which was not correct). Does
> anyone have an idea?
What is your boot log ?
Quite likely, you should read
http://buildroot.org/downloads/buildroot.html#faq-boot-hangs, but there
may be other problems as well, of course.
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2010-12-14 13:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-14 13:06 [Buildroot] cannot log to my build root Diego Iastrubni
2010-12-14 13:25 ` Thomas Petazzoni [this message]
2010-12-14 13:39 ` Diego Iastrubni
2010-12-14 14:05 ` Thomas Petazzoni
2010-12-14 14:38 ` Diego Iastrubni
2010-12-14 14:42 ` Thomas Petazzoni
2010-12-14 14:54 ` Diego Iastrubni
2010-12-14 15:05 ` Thomas Petazzoni
2010-12-14 15:28 ` Diego Iastrubni
2010-12-14 15:37 ` Thomas Petazzoni
2010-12-14 15:56 ` Diego Iastrubni
2010-12-14 16:00 ` Thomas Petazzoni
2010-12-14 15:50 ` William Wagner
2010-12-14 16:00 ` Thomas Petazzoni
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=20101214142544.7863d2d2@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