From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/5] beaglebone: update to linux 3.8
Date: Sat, 11 May 2013 00:44:09 +0200 [thread overview]
Message-ID: <518D7839.70709@mind.be> (raw)
In-Reply-To: <1368131491-14115-2-git-send-email-anders.darander@gmail.com>
Hi Anders,
On 09/05/13 22:31, Anders Darander wrote:
> From: Anders Darander <anders@chargestorm.se>
>
> The kernel config here, is basically the default one from the TI kernel.
> Thus, it's omap2plus_defconfig, which is rather generic.
So why include a config in buildroot? If it's just the defconfig that
is already in the kernel tree, you can use it.
>
> As the beaglebone support is mainlined, there's no support for the old
> board setup files, and the only supported run-time configuration is through
> the device tree.
>
> We're also setting the kernel headers to follow the 3.8 series.
>
> Signed-off-by: Anders Darander <anders@chargestorm.se>
> ---
> board/beaglebone/linux-3.2.9.config | 252 ----------------------------
> board/beaglebone/linux-3.8.config | 315 +++++++++++++++++++++++++++++++++++
Please create your patches with the -M option to send-email or
format-patch, so that we can actually see the diff crossing the rename.
Otherwise it's pretty hard to review.
> configs/beaglebone_defconfig | 22 +--
> 3 files changed, 321 insertions(+), 268 deletions(-)
> delete mode 100644 board/beaglebone/linux-3.2.9.config
> create mode 100644 board/beaglebone/linux-3.8.config
>
[snip]
> diff --git a/configs/beaglebone_defconfig b/configs/beaglebone_defconfig
> index 2177068..f80dd79 100644
> --- a/configs/beaglebone_defconfig
> +++ b/configs/beaglebone_defconfig
> @@ -1,24 +1,14 @@
> -# architecture
> BR2_arm=y
> BR2_cortex_a8=y
> +BR2_KERNEL_HEADERS_3_8=y
> BR2_EXTRA_GCC_CONFIG_OPTIONS="--with-fpu=vfpv3 --with-float=hard"
> # BR2_SOFT_FLOAT is not set
> -
> -# system
Please don't remove these comments, they're useful. You can selectively
undo changes with 'git checkout -p configs/beaglebone_defconfig'.
> 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
> -
> -# filesystem
> BR2_TARGET_ROOTFS_EXT2=y
> # BR2_TARGET_ROOTFS_TAR is not set
> -
> -# lock down headers to avoid breaking with new defaults
> -BR2_KERNEL_HEADERS_VERSION=y
> -BR2_DEFAULT_KERNEL_VERSION="3.2.9"
> -
> -# bootloader
> BR2_TARGET_UBOOT=y
> BR2_TARGET_UBOOT_BOARDNAME="am335x_evm"
> BR2_TARGET_UBOOT_CUSTOM_VERSION=y
> @@ -26,11 +16,11 @@ BR2_TARGET_UBOOT_CUSTOM_VERSION_VALUE="2013.04"
> BR2_TARGET_UBOOT_FORMAT_IMG=y
> BR2_TARGET_UBOOT_SPL=y
> BR2_TARGET_UBOOT_SPL_NAME="MLO"
> -
> -# kernel
> BR2_LINUX_KERNEL=y
> BR2_LINUX_KERNEL_CUSTOM_GIT=y
> -BR2_LINUX_KERNEL_CUSTOM_GIT_REPO_URL="git://github.com/koenkooi/linux.git"
> -BR2_LINUX_KERNEL_CUSTOM_GIT_VERSION="linux-ti33x-psp-3.2-r5a+gitr09e9651bcf2ee8d86685f2a8075bc6557b1d3b91"
> +BR2_LINUX_KERNEL_CUSTOM_GIT_REPO_URL="git://git.ti.com/ti-linux-kernel/ti-linux-kernel.git"
> +BR2_LINUX_KERNEL_CUSTOM_GIT_VERSION="935f6c2f82056d538b528272e2bdbb5c08d69a58"
Isn't there a tag you can clone from? That's much faster, because then
we can (usually) do a shallow clone.
Regards,
Arnout
> BR2_LINUX_KERNEL_USE_CUSTOM_CONFIG=y
> -BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE="board/beaglebone/linux-3.2.9.config"
> +BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE="board/beaglebone/linux-3.8.config"
> +BR2_LINUX_KERNEL_DTS_SUPPORT=y
> +BR2_LINUX_KERNEL_INTREE_DTS_NAME="am335x-bone"
>
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2013-05-10 22:44 UTC|newest]
Thread overview: 13+ 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 [this message]
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 ` [Buildroot] [PATCH 4/5] beaglebone: add am33x-cm3 Anders Darander
2013-05-09 20:31 ` [Buildroot] [PATCH 5/5] beaglebone: enable NFS root Anders Darander
-- strict thread matches above, loose matches on Subject: below --
2013-05-11 4:37 [Buildroot] [PATCH 1/5] beaglebone: update to linux 3.8 Anders Darander
2013-05-11 6:10 ` Arnout Vandecappelle
2013-05-11 12:41 ` Anders Darander
2013-05-12 17:15 ` 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=518D7839.70709@mind.be \
--to=arnout@mind.be \
--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