Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Christian SCHWARZ <christian.schwarz@st.com>
To: buildroot@busybox.net
Subject: [Buildroot] link to busybox
Date: Wed, 07 May 2008 09:15:35 +0200	[thread overview]
Message-ID: <48215717.9090808@st.com> (raw)
In-Reply-To: <102389.57784.qm@web94112.mail.in2.yahoo.com>

Hi Tiju,

I believe root filesystems are not an exact science, thus I can only 
provide you with some generic stuff, which mostly works.
For me, a simple device layout like the following (using busybox or 
buildroot) works on several different embedded platforms:

mknod initrd b 1 250
mknod console c 5 1
mknod mem c 1 1
mknod null c 1 3
mknod ram1 b 1 1
mknod ttyAM0 c 204 16
mknod ram0 b 1 0
ln -s ram1 ram
ln -s ram0 ramdisk

In your case you'd probably replace ttyAM0 with ttySAC0..

> I am very new to this. Could you please tell me how to modify these files to my requirement or atleast the links from where I will get more information regarding this?
Even though this is the buildroot mailing list, I would recommend to 
first try a rootfs with only busybox, thus without buildroot. You can 
easily use the buildroot-generated cross-compiling toolchain with busybox..
  make CROSS_COMPILE=<xtoolchain-prefix> all install

The rc.S file is not required by busybox, it makes some smart assumptions.

hope this helps,
Christian

  reply	other threads:[~2008-05-07  7:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-07  5:33 [Buildroot] link to busybox Tiju Jacob
2008-05-07  7:15 ` Christian SCHWARZ [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-05-06  5:11 Tiju Jacob
2008-05-06  5:16 ` Thiago A. Corrêa
2008-05-06  7:23   ` Christian SCHWARZ

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=48215717.9090808@st.com \
    --to=christian.schwarz@st.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