Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ulf Samuelsson <ulf.samuelsson@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Fix naming mismatch between directfb and kernel on "fusion" version numbers
Date: Sun, 26 Jul 2009 11:43:16 +0200	[thread overview]
Message-ID: <4A6C2534.3000503@atmel.com> (raw)
In-Reply-To: <87k51vsxz0.fsf@macbook.be.48ers.dk>

Peter Korsgaard skrev:
>>>>>> "Ulf" == Ulf Samuelsson <ulf.samuelsson@atmel.com> writes:
>>>>>>             
>
>  Ulf> directfb expects FUSION_API_MAJOR_PROVIDED and FUSION_API_MINOR_REQUIRED
>  Ulf> At least some kernel versions provides FUSION_API_MAJOR and FUSION_API_MINOR
>  Ulf> Since the expected names are not defined, directfb will break with the
>  Ulf> error message:
>
>  Ulf> "../../../lib/fusion/types.h:42:2: error: #error Major version of Fusion
>  Ulf> Kernel Module too low! Upgrade your kernel."
>
>  Ulf> This patch will set XXX_PROVIDED from XXX.
>
> But aren't those kernel modules part of directfb? If not, does stuff
> actually work (not just build) if you workaround this version
> incompatibility? Wouldn't it make more sense to fix where the define
> is set in the first place? Have you sent this by the directfb
> developers?
>   
As far as I see, the major/minor version numbers provided
are the same as requested, but the naming is different.

BR
Ulf Samuelsson

  reply	other threads:[~2009-07-26  9:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-26  5:16 [Buildroot] [PATCH] Fix naming mismatch between directfb and kernel on "fusion" version numbers Ulf Samuelsson
2009-07-26  7:30 ` Peter Korsgaard
2009-07-26  9:43   ` Ulf Samuelsson [this message]
2009-07-26 13:20     ` Peter Korsgaard
2009-07-26 19:06       ` Ulf Samuelsson
2009-07-26 19:16         ` Peter Korsgaard
     [not found]           ` <4A6CBAEA.2010002@atmel.com>
2009-07-26 20:37             ` 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=4A6C2534.3000503@atmel.com \
    --to=ulf.samuelsson@atmel.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