Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Anders Darander <anders.darander@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 4/5] beaglebone: add am33x-cm3
Date: Thu,  9 May 2013 22:31:30 +0200	[thread overview]
Message-ID: <1368131491-14115-5-git-send-email-anders.darander@gmail.com> (raw)
In-Reply-To: <1368131491-14115-1-git-send-email-anders.darander@gmail.com>

From: Anders Darander <anders@chargestorm.se>

Add the FW needed for the Cortex M3 on the beaglebone. This is required for
a working power management.

Signed-off-by: Anders Darander <anders@chargestorm.se>
---
 configs/beaglebone_defconfig |    1 +
 1 file changed, 1 insertion(+)

diff --git a/configs/beaglebone_defconfig b/configs/beaglebone_defconfig
index f80dd79..a6df39b 100644
--- a/configs/beaglebone_defconfig
+++ b/configs/beaglebone_defconfig
@@ -7,6 +7,7 @@ BR2_TARGET_GENERIC_HOSTNAME="beaglebone"
 BR2_ROOTFS_DEVICE_CREATION_DYNAMIC_DEVTMPFS=y
 BR2_TARGET_GENERIC_GETTY_PORT="ttyO0"
 # BR2_TARGET_GENERIC_REMOUNT_ROOTFS_RW is not set
+BR2_PACKAGE_AM33X_CM3=y
 BR2_TARGET_ROOTFS_EXT2=y
 # BR2_TARGET_ROOTFS_TAR is not set
 BR2_TARGET_UBOOT=y
-- 
1.7.10.4

  parent reply	other threads:[~2013-05-09 20:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-09 20:31 [Buildroot] [PATCH 0/5] Upgrade BeagleBone kernel to 3.8 Anders Darander
2013-05-09 20:31 ` [Buildroot] [PATCH 1/5] beaglebone: update to linux 3.8 Anders Darander
2013-05-10 22:44   ` Arnout Vandecappelle
2013-05-09 20:31 ` [Buildroot] [PATCH 2/5] beaglebone: reduce defconfig Anders Darander
2013-05-10 22:45   ` Arnout Vandecappelle
2013-05-09 20:31 ` [Buildroot] [PATCH 3/5] am33x-cm3: add FW for suspend/resume Anders Darander
2013-05-10 22:56   ` Arnout Vandecappelle
2013-05-09 20:31 ` Anders Darander [this message]
2013-05-09 20:31 ` [Buildroot] [PATCH 5/5] beaglebone: enable NFS root Anders Darander

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=1368131491-14115-5-git-send-email-anders.darander@gmail.com \
    --to=anders.darander@gmail.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