Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] Add HW decoding support for Hantro x170
Date: Mon, 29 Apr 2013 15:20:39 +0200	[thread overview]
Message-ID: <87ip354gns.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <CAHt8ZCOMTcEa71OsgLOvW0QcydhqRUHNqymJcNNsxtbkLGU3NA@mail.gmail.com> (Simon Dawson's message of "Mon, 29 Apr 2013 14:12:13 +0100")

>>>>> "Simon" == Simon Dawson <spdawson@gmail.com> writes:

 >>> +config BR2_PACKAGE_GST_PLUGIN_X170
 >>> +     bool "gst-plugin-x170"
 >>> +     depends on BR2_PACKAGE_GSTREAMER
 >> 
 >> A "depends on BR2_arm" should be added here. We generally try to hide
 >> such architecture-specific packages when they really don't make sense.
 >> Of course, technically speaking, it should only appear if the SoC is an
 >> AT91 SoC that has this specific video unit, but we are not able to do
 >> that with the existing Buildroot options. But we still try to make such
 >> options depend on BR2_arm.

 Simon> I think it's ARM9 only, so we can probably be slightly more specific:

 Simon>   depends on (BR2_arm920t || BR2_arm922t || BR2_arm926t)

And the only device I've ever seen with this IP block integrated are
at91sam9m10/11, both of which are arm926t.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2013-04-29 13:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-04 22:26 [Buildroot] [PATCH 1/2] Add defconfig for ATMEL at91sam9g45m10ek board Alexandre Belloni
2013-02-04 22:26 ` [Buildroot] [PATCH 2/2] Add HW decoding support for Hantro x170 Alexandre Belloni
2013-02-04 22:51   ` Thomas Petazzoni
2013-02-05 20:41     ` Alexandre Belloni
2013-04-29 13:12     ` Simon Dawson
2013-04-29 13:20       ` Peter Korsgaard [this message]
2013-04-28 19:00   ` Peter Korsgaard
2013-05-25 22:41     ` Alexandre Belloni
2013-04-28 18:57 ` [Buildroot] [PATCH 1/2] Add defconfig for ATMEL at91sam9g45m10ek board Peter Korsgaard

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=87ip354gns.fsf@dell.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --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