Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [STABLE][PATCH v3] linux-libc-headers 2.6.23: add newer ARM hwcap flags
Date: Thu, 15 Apr 2010 09:04:09 +0200	[thread overview]
Message-ID: <hq6dp9$62o$1@dough.gmane.org> (raw)
In-Reply-To: <1271270768-6212-1-git-send-email-marcin@juszkiewicz.com.pl>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 14-04-10 20:46, Marcin Juszkiewicz wrote:
> From: Marcin Juszkiewicz <marcin@buglabs.net>
> 
> OpenJDK uses HWCAP_THUMBEE which is not present in 2.6.23 headers.


Acked-by: Koen Kooi <koen@openembedded.org>


> 
> Signed-off-by: Marcin Juszkiewicz <marcin@juszkiewicz.com.pl>
> ---
>  .../arm-hwcap-add-new-entries.patch                |   21 ++++++++++++++++++++
>  .../linux-libc-headers_2.6.23.bb                   |    5 ++-
>  2 files changed, 24 insertions(+), 2 deletions(-)
>  create mode 100644 recipes/linux-libc-headers/linux-libc-headers-2.6.23/arm-hwcap-add-new-entries.patch
> 
> diff --git a/recipes/linux-libc-headers/linux-libc-headers-2.6.23/arm-hwcap-add-new-entries.patch b/recipes/linux-libc-headers/linux-libc-headers-2.6.23/arm-hwcap-add-new-entries.patch
> new file mode 100644
> index 0000000..934db51
> --- /dev/null
> +++ b/recipes/linux-libc-headers/linux-libc-headers-2.6.23/arm-hwcap-add-new-entries.patch
> @@ -0,0 +1,21 @@
> +---
> + include/asm-arm/hwcap.h |    4 ++++
> + 1 file changed, 4 insertions(+)
> +
> +--- linux-2.6.23.orig/include/asm-arm/hwcap.h
> ++++ linux-2.6.23/include/asm-arm/hwcap.h
> +@@ -13,10 +13,14 @@
> + #define HWCAP_VFP	64
> + #define HWCAP_EDSP	128
> + #define HWCAP_JAVA	256
> + #define HWCAP_IWMMXT	512
> + #define HWCAP_CRUNCH	1024
> ++#define HWCAP_THUMBEE	2048
> ++#define HWCAP_NEON	4096
> ++#define HWCAP_VFPv3	8192
> ++#define HWCAP_VFPv3D16	16384
> + 
> + #if defined(__KERNEL__) && !defined(__ASSEMBLY__)
> + /*
> +  * This yields a mask that user programs can use to figure out what
> +  * instruction set this cpu supports.
> diff --git a/recipes/linux-libc-headers/linux-libc-headers_2.6.23.bb b/recipes/linux-libc-headers/linux-libc-headers_2.6.23.bb
> index 95152f1..b4766bc 100644
> --- a/recipes/linux-libc-headers/linux-libc-headers_2.6.23.bb
> +++ b/recipes/linux-libc-headers/linux-libc-headers_2.6.23.bb
> @@ -2,11 +2,12 @@ require linux-libc-headers.inc
>  
>  INHIBIT_DEFAULT_DEPS = "1"
>  DEPENDS += "unifdef-native"
> -PR = "r4"
> +PR = "r6"
>  
>  SRC_URI = "${KERNELORG_MIRROR}/pub/linux/kernel/v2.6/linux-${PV}.tar.bz2 \
>             file://procinfo.h \
> -           file://unifdef.patch;patch=1"
> +           file://unifdef.patch;patch=1 \
> +           file://arm-hwcap-add-new-entries.patch;patch=1"
>  
>  S = "${WORKDIR}/linux-${PV}"
>  

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFLxrppMkyGM64RGpERAsaaAJ93gZArcrMiufcUSGDNmYAmKWUVXACaA4VX
TeeiM7IQ0DL3xrZhM7F9qXA=
=RKq6
-----END PGP SIGNATURE-----




  reply	other threads:[~2010-04-15  7:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-14 18:46 [STABLE][PATCH v3] linux-libc-headers 2.6.23: add newer ARM hwcap flags Marcin Juszkiewicz
2010-04-15  7:04 ` Koen Kooi [this message]
2010-04-15  7:35 ` Marco Cavallini
2010-04-15 12:17 ` Philip Balister

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='hq6dp9$62o$1@dough.gmane.org' \
    --to=k.kooi@student.utwente.nl \
    --cc=openembedded-devel@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox