From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1 v2] xdriver_xf86-video-intel: Bump version to 2.99.911
Date: Sun, 30 Mar 2014 17:24:13 +0200 [thread overview]
Message-ID: <20140330172413.049cd7d0@skate> (raw)
In-Reply-To: <t9jl0bxj2h.ln2@ID-313208.user.individual.net>
Dear Bernd Kuhls,
On Sun, 30 Mar 2014 15:37:33 +0200, Bernd Kuhls wrote:
> > Do we want KMS vs. UMS to be a configurable option?
>
> this is not necessary because the driver can have both options compiled,
> therefore I removed the kms/ums-related options.
Ok.
> > Then in the Config.in file, if BR2_PACKAGE_MESA3D_DRI_DRIVER_I965 is
> > enabled, you want to select MESA3D.
>
> + select BR2_PACKAGE_MESA3D if BR2_PACKAGE_MESA3D_DRI_DRIVER_I965
>
> leads to
>
> package/mesa3d/Config.in:1:error: recursive dependency detected!
> package/mesa3d/Config.in:1: symbol BR2_PACKAGE_MESA3D is selected by BR2
> _PACKAGE_MESA3D_DRI_DRIVER_I965
> package/mesa3d/Config.in:70: symbol BR2_PACKAGE_MESA3D_DRI_DRIVER_I965
> depends on BR2_PACKAGE_MESA3D
Aaah, yes, I was mistaken. If BR2_PACKAGE_MESA3D_DRI_DRIVER_I965 is
enabled, then of course BR2_PACKAGE_MESA3D is already enabled. Sorry
for the noise.
Can you look into the other circular dependency that your patch series
has introduced? I've reported it to you yesterday evening.
Also, by any chance, are you on IRC ? It would sometimes be useful to
be able to discuss things directly with you. Thanks!
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-03-30 15:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-30 11:22 [Buildroot] [PATCH 1/1 v2] xdriver_xf86-video-intel: Bump version to 2.99.911 Bernd Kuhls
2014-03-30 13:11 ` Thomas Petazzoni
2014-03-30 13:37 ` Bernd Kuhls
2014-03-30 15:24 ` Thomas Petazzoni [this message]
2014-03-30 15:48 ` Bernd Kuhls
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=20140330172413.049cd7d0@skate \
--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