From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Add support for the Calao-systems USB-A9263
Date: Fri, 6 Jul 2012 14:30:08 +0200 [thread overview]
Message-ID: <20120706143008.64d0e023@skate> (raw)
In-Reply-To: <4FF6BA67.3070207@calao-systems.com>
Hello Gr?gory,
Le Fri, 06 Jul 2012 12:13:59 +0200,
gregory hermant <gregory.hermant@calao-systems.com> a ?crit :
> Hi,
> Attached a patch for the USB-A9263.
> More info at <http://www.calao-systems.com>.
>
>
> Signed-off-by: Gregory Hermant <gregory.hermant@calao-systems.com>
> ---
> .../usb-a9263/at91bootstrap-1.16-usb-a9263.patch | 851 ++++++++++
> board/calao/usb-a9263/usb-a9263_defconfig | 1662 ++++++++++++++++++++
> configs/usb_a9263_defconfig | 1247 +++++++++++++++
> 3 files changed, 3760 insertions(+), 0 deletions(-)
> create mode 100644 board/calao/usb-a9263/at91bootstrap-1.16-usb-a9263.patch
> create mode 100644 board/calao/usb-a9263/usb-a9263_defconfig
> create mode 100644 configs/usb_a9263_defconfig
Thanks for this contribution.
Both the kernel configuration and the bootloader configuration, we
prefer to use defconfig files, which are smaller.
To generate the Buildroot defconfig file:
make savedefconfig
To generate the Linux defconfig file:
make linux-savedefconfig
Also, do you know if at some point Atmel will create an upstream for
at91bootstrap? I've seen they have created some Github repository with
at91bootstrap sources. I'm a bit worried about integrating a patch that
has no upstream to be submitted, which means that we will have to carry
it around forever.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-07-06 12:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-06 10:13 [Buildroot] [PATCH] Add support for the Calao-systems USB-A9263 gregory hermant
2012-07-06 12:30 ` Thomas Petazzoni [this message]
2012-07-06 13:37 ` gregory hermant
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=20120706143008.64d0e023@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