Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Some Questions - root placement, Initramfs, dev nodes
Date: Sat, 24 Jan 2009 09:05:51 +0100	[thread overview]
Message-ID: <878wp1i0ww.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <ecbbfeda0901231840q30263e2ax3ab8ba4708776c5@mail.gmail.com> (Andrew Wiley's message of "Fri\, 23 Jan 2009 20\:40\:43 -0600")

>>>>> "Andrew" == Andrew Wiley <debio264@gmail.com> writes:

Hi,

 Andrew> What's the normal approach to this? The board I'm working
 Andrew> with is being used for robotics projects by beginner
 Andrew> programmers, so I would like to have as complete a system as
 Andrew> possible to make programming simpler. Ideally, the board
 Andrew> would be it's own development system, with a native compiler
 Andrew> toolchain.  Is this a realistic goal? Have I understood the
 Andrew> initramfs correctly?  How would I set up something like this?

With initramfs you still waste RAM to store your files. The most
common approach is to put a file system in flash - E.G. jffs2 if you
need read/write access, and squashfs for read only (notice you need a
kernel patch for squashfs).

For development it's probably easier to boot over nfs (see the tarball
image option in buildroot).

Getting native compilation running with 16MB is pretty unrealistic though.

 Andrew> Also, my board has two serial ports, ttyAM0 and ttyAM1. I
 Andrew> copied the /dev nodes from the official Cirrus Labs firmware
 Andrew> (I sent another email about this a while back), and while
 Andrew> ttyAM0 works perfectly, ttyAM1 doesn't seem to respond to
 Andrew> anything I do. Programs can open the port, set speeds, and
 Andrew> write to it without errors, but these actions have no
 Andrew> effect. As I said, I've never had to work without uDev, so
 Andrew> how do I find the major and minor information for this serial
 Andrew> port?

Have a look at contents of /sys/class/tty/ttyAMx/dev or check the
kernel driver.

 Andrew> Thanks for any help you can offer, and feel free to tell me I'm a
 Andrew> clueless idiot,

No worries ;)

-- 
Bye, Peter Korsgaard

      reply	other threads:[~2009-01-24  8:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-24  2:40 [Buildroot] Some Questions - root placement, Initramfs, dev nodes Andrew Wiley
2009-01-24  8:05 ` Peter Korsgaard [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=878wp1i0ww.fsf@macbook.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --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