From: Philipp Wagner <lists@philipp-wagner.com>
To: Paul Barker <paul@paulbarker.me.uk>,
Yocto Project <yocto@yoctoproject.org>
Subject: Re: [meta-raspberrypi][PATCH] linux-raspberrypi: Add version 3.8.13
Date: Sun, 08 Sep 2013 12:24:18 +0200 [thread overview]
Message-ID: <522C5052.8080600@philipp-wagner.com> (raw)
In-Reply-To: <1378211205-4866-2-git-send-email-paul@paulbarker.me.uk>
Hi,
a general question to start: 3.11.0 is out now as well (and it works, at
least in my tests), should we add that as well?
Am 03.09.2013 14:26, Paul Barker wrote:
> Upstream commit d996a1b91b2bf3dc06f4f4f822a56f4496457aa1, dated 2013-08-07.
>
> Signed-off-by: Paul Barker <paul@paulbarker.me.uk>
> ---
> recipes-kernel/linux/linux-raspberrypi_3.8.13.bb | 35 ++++++++++++++++++++++++
> 1 file changed, 35 insertions(+)
> create mode 100644 recipes-kernel/linux/linux-raspberrypi_3.8.13.bb
>
> diff --git a/recipes-kernel/linux/linux-raspberrypi_3.8.13.bb b/recipes-kernel/linux/linux-raspberrypi_3.8.13.bb
> new file mode 100644
> index 0000000..b482939
> --- /dev/null
> +++ b/recipes-kernel/linux/linux-raspberrypi_3.8.13.bb
> @@ -0,0 +1,35 @@
> +require linux.inc
> +
> +DESCRIPTION = "Linux kernel for the RaspberryPi board"
> +COMPATIBLE_MACHINE = "raspberrypi"
> +
> +PR = "r6"
I guess this does not matter, but would r1 not be more natural?
> +PV_append = "+git${SRCREV}"
> +
> +SRCREV = "d996a1b91b2bf3dc06f4f4f822a56f4496457aa1"
> +SRC_URI = "git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-3.8.y \
> + file://sl030raspberrypii2ckernel.patch \
> + "
> +S = "${WORKDIR}/git"
> +
> +# NOTE: For now we pull in the default config from the RPi kernel GIT tree.
> +KERNEL_DEFCONFIG = "bcmrpi_defconfig"
> +
> +# CMDLINE for raspberrypi
> +CMDLINE_raspberrypi = "dwc_otg.lpm_enable=0 console=ttyAMA0,115200 kgdboc=ttyAMA0,115200 root=/dev/mmcblk0p2 rootfstype=ext4 rootwait"
> +
> +UDEV_GE_141 ?= "1"
This is already part of linux.inc, is it necessary here again?
> +
> +do_configure_prepend() {
> + install -m 0644 ${S}/arch/${ARCH}/configs/${KERNEL_DEFCONFIG} ${WORKDIR}/defconfig || die "No default configuration for ${MACHINE} / ${KERNEL_DEFCONFIG} available."
> +}
> +
> +do_install_prepend() {
> + install -d ${D}/lib/firmware
> +}
> +
> +do_deploy_append() {
> + # Deploy cmdline.txt
> + install -d ${DEPLOYDIR}/bcm2835-bootfiles
> + echo "${CMDLINE}" > ${DEPLOYDIR}/bcm2835-bootfiles/cmdline.txt
> +}
>
next prev parent reply other threads:[~2013-09-08 10:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-03 12:26 [meta-raspberrypi][PATCH] 3.8.y series linux-raspberrypi kernel Paul Barker
2013-09-03 12:26 ` [meta-raspberrypi][PATCH] linux-raspberrypi: Add version 3.8.13 Paul Barker
2013-09-08 10:24 ` Philipp Wagner [this message]
2013-09-09 14:23 ` Paul Barker
2013-09-09 21:45 ` Andrei Gherzan
2013-09-09 21:46 ` [meta-raspberrypi][PATCH] 3.8.y series linux-raspberrypi kernel Andrei Gherzan
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=522C5052.8080600@philipp-wagner.com \
--to=lists@philipp-wagner.com \
--cc=paul@paulbarker.me.uk \
--cc=yocto@yoctoproject.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.