From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Problem with starting TI Graphics
Date: Wed, 05 Mar 2014 22:09:00 +0100 [thread overview]
Message-ID: <5317926C.30207@mind.be> (raw)
In-Reply-To: <20140304200948.619fc7fe@skate>
On 04/03/14 20:09, Thomas Petazzoni wrote:
> Dear Peter Kuemmel,
>
> On Fri, 14 Feb 2014 11:24:06 +0100, Peter Kuemmel wrote:
>
>> Thanks, I found the issue: it was the missing user binary thumb support in the kernel.
>
> Interesting. Were you building the kernel with Buildroot, or separately?
>
> If you built your kernel with Buildroot, then maybe we should add
> something like:
>
> $(if $(BR2_ARM_INSTRUCTIONS_THUMB)$(BR2_ARM_INSTRUCTIONS_THUMB2),
> $(call KCONFIG_ENABLE_OPT,CONFIG_ARM_THUMB,$(@D)/.config))
>
> This way we would ensure that the kernel gets built with
> CONFIG_ARM_THUMB=y when the Thumb or Thumb-2 instruction sets have been
> selected for userspace.
This is a good idea, but wouldn't help with Peter's problem: the
pvrsrvctl binary is not built by buildroot, so the problem occurs even if
buildroot is build with ARM instructions.
Regards,
Arnout
>
> Thoughts?
>
> Thomas
>
--
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:[~2014-03-05 21:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-13 8:11 [Buildroot] Problem with starting TI Graphics Peter Kuemmel
2014-02-13 21:35 ` Marcelo Gutierrez
2014-02-14 10:24 ` Peter Kuemmel
2014-03-04 19:09 ` Thomas Petazzoni
2014-03-05 21:09 ` Arnout Vandecappelle [this message]
2014-03-06 12:47 ` Peter Kümmel
2014-03-06 17:47 ` 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=5317926C.30207@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