Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Marcus Osdoba <marcus.osdoba@googlemail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Dockstar (kirkwood derivative) support for buildroot
Date: Fri, 29 Oct 2010 11:51:55 +0200	[thread overview]
Message-ID: <4CCA993B.6040309@googlemail.com> (raw)

Hello Mailinglist,

I often worked after closing time to bring dockstar support into 
buildroot. I have a lot of images which boot smoothly and mount over 
nfs. If anyone is interested, I like to share my work with other 
dockstar owners:
http://gitorious.org/dockstar (repo: mynas)

The patchset is not very well documented/quick and dirty, but should 
work with some manual work steps.
Most of the special board configuration is outside the buildroot tree. 
Only one target/device/ file is patched.

Unfortunatly I got stuck at the point, where I had to configure all 
packages on my own. The "distributional" work is too much to overcome in 
rational time (after closing time) for one person. I gave one of the 
Buildroot "children?" or "cousins?" a try: OpenWRT. The packages are 
already configured to meet each other. I think buildroot is more 
interesting for very specialized tasks due to its generic principle. You 
can bloat it up to meet any of your requirements, but this costs time. 
In other projects, you have to follow their design, which may not work 
with your needs...

Anyway, if someone likes to try out the combination dockstar+buildroot, 
the gitorious repo above would be a good starting point.

Kind regards,
Ossy

                 reply	other threads:[~2010-10-29  9:51 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4CCA993B.6040309@googlemail.com \
    --to=marcus.osdoba@googlemail.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