Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Brian Beattie <beattie@beattie-home.net>
To: buildroot@busybox.net
Subject: [Buildroot] pcduino
Date: Tue, 03 Dec 2013 20:02:45 -0800	[thread overview]
Message-ID: <1386129765.18658.57.camel@kokopelli> (raw)

I'm working on adding support for the pcDuino V1 board, this is an
Allwinner A10 based board so I'm using the cubieboard as a staring
point.  The issue I have is that or U-Boot and the kernel this is not a
problem, however for sunxi-boards and sunxi-tools, the commit id is in
the Makefile.  I'd like to know what the experts think the best approach
is.  I currently have the Makefiles patched.

I could update the Makefiles, but I don't have a cubieboard to test
with.

I could modify the *.mk and Config files to make the commit id a
configurable item and if not set use the current commit ID.  I started
to do this, but sunxi-tools has a Config.in and a Config.in.host and I'm
not sure how to handle setting one variable that would be used in both
files.  Suggestions, pointers welcome.

Some other approach I have not thought of.

BTW I did the original KB9202 support many years ago though I have been
away for a while. (that board just bit the dust which is why I bought
the pcDuino).
-- 
"For every complex problem there is an answer that is clear, simple, and
wrong." -- H. L. Mencken

Brian Beattie<beattie@beattie-home.net> -- www.brian-beattie.com
LFS12947

             reply	other threads:[~2013-12-04  4:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-04  4:02 Brian Beattie [this message]
2013-12-05 17:59 ` [Buildroot] pcduino Arnout Vandecappelle

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=1386129765.18658.57.camel@kokopelli \
    --to=beattie@beattie-home.net \
    --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