Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] New Board Support and process
Date: Tue, 7 Feb 2012 20:12:38 +0100	[thread overview]
Message-ID: <20120207201238.32c4047b@skate> (raw)
In-Reply-To: <CAC78GpfSiOFDHwJ243n+t81ub-Bchs7gWs_16wjrEseiVCLF_A@mail.gmail.com>

Hello,

Le Mon, 6 Feb 2012 16:53:25 -0500,
"J.C. Woltz" <jwoltz@gmail.com> a ?crit :

> I have been maintaining my own branch of buildroot for the Synapse
> Wireless E10.
> http://www.synapse-wireless.com/index.php?mainID=3&subID=10&type=product&prodID=10

Great.

> From a linux point of view, it is an Atmel AT91SAM9G20 based machine.
> I have patches for u-boot, linux, a linux config, and a buildroot
> e10_defconfig.
> Except for the e10_defconfig, the files are located under
> board/synapse/e10/.
> Can I submit these as a patch, or is there a preferred alternative?

This sounds good. However, we would appreciate if there was an effort
to push these patches upstream to the respective project, so that
Buildroot does not need to carry these patches forever.

> I have also updated usb_modeswitch to version 1.2.3 and created a
> package for usb_modeswitch_data which contains udev rules among other
> things.
> 
> I would like to submit these and have them available in future
> releases. That way other users of the E10 have an easier time making
> custom builds.
> 
> Thoughts? Objections? Other?

Sounds good. Submit your patches, we'll review them.

Thanks for your contribution!

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

      reply	other threads:[~2012-02-07 19:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-06 21:53 [Buildroot] New Board Support and process J.C. Woltz
2012-02-07 19:12 ` Thomas Petazzoni [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=20120207201238.32c4047b@skate \
    --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