Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] directfb: remove cle266 and unichrome support
Date: Sun, 20 Dec 2015 13:54:59 +0100	[thread overview]
Message-ID: <20151220135459.673aa46e@free-electrons.com> (raw)
In-Reply-To: <1450615477-11659-1-git-send-email-gustavo.zacarias@free-electrons.com>

Dear gustavo.zacarias at free-electrons.com,

On Sun, 20 Dec 2015 09:44:37 -0300, gustavo.zacarias at free-electrons.com
wrote:
> From: Gustavo Zacarias <gustavo.zacarias@free-electrons.com>
> 
> They're broken for the latest version and directfb upstream is gone.
> 
> cle266 is an old chipset for AMD K7 (32 bit) athlons with integrated
> graphics - very odd hardware.
> 
> unichrome is another VIA graphics standalone chip/chipset used for some
> odd video cards and VIA CPUs (x86-based: C7, Nano and so on).
> 
> Add options to legacy as well. Fixes:
> 
> http://autobuild.buildroot.net/results/ab9/ab9a6dd044b5f3e8e42629a2aaf598fd0e0357ed/
> 
> Signed-off-by: Gustavo Zacarias <gustavo.zacarias@free-electrons.com>
> ---
>  Config.in.legacy             | 16 ++++++++++++++++
>  package/directfb/Config.in   | 10 ----------
>  package/directfb/directfb.mk |  2 --
>  3 files changed, 16 insertions(+), 12 deletions(-)

Applied, thanks.

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2015-12-20 12:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-20 12:44 [Buildroot] [PATCH] directfb: remove cle266 and unichrome support gustavo.zacarias at free-electrons.com
2015-12-20 12:54 ` Thomas Petazzoni [this message]
2015-12-20 12:55 ` Yann E. MORIN

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=20151220135459.673aa46e@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --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