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 21:06:09 +0200	[thread overview]
Message-ID: <4A6CA921.7040807@atmel.com> (raw)
In-Reply-To: <874oszshqp.fsf@macbook.be.48ers.dk>

Peter Korsgaard skrev:
>>>>>> "Ulf" == Ulf Samuelsson <ulf.samuelsson@atmel.com> writes:
> 
> Hi,
> 
>  >> 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?
>  >> 
>  Ulf> As far as I see, the major/minor version numbers provided
>  Ulf> are the same as requested, but the naming is different.
> 
> OK, what driver / setup exactly? Isn't the problem just that we need
> to bump the linux-fusion package version?

The module is 8.0 and the requirement is 8.0
but since they use different defines it wont work.

It is really very simple

#define	A 8
#define B 8
#if A == B_PROVIDED
/* OK */
#else
#warning ""
#endif

The code should emit a warning if version A and B are not the same.
They are the same, but the warning will still occur,
since there is no definition of B_PROVIDED.

BR
Ulf Samuelsson

  reply	other threads:[~2009-07-26 19:06 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
2009-07-26 13:20     ` Peter Korsgaard
2009-07-26 19:06       ` Ulf Samuelsson [this message]
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=4A6CA921.7040807@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