The md5 checksum in LIC_FILES_CHKSUM was taken from an older version of
the Freescale EULA. This leads to build errors like
ERROR: imx-gpu-viv: md5 data is not matching for
file://[...]/meta-fsl-arm/EULA;md5=6df184a9b1950b68e17fdcd7513bdb97
ERROR: imx-gpu-viv: The new md5 checksum
Hi,
here are two fixes for my last patch
[PATCH] fsl-eula-unpack: deploy Freescale EULA
to the meta-freescale list.
The first patch corrects the md5 checksum for the Freescale EULA file and the
second fixes a problem when a recipe redefines the LIC_FILES_CHKSUM variable.
In that case the "+=
If a recipe, which uses the fsl-eula-unpack bbclass, defines the
variable LIC_FILES_CHKSUM like
LIC_FILES_CHKSUM = "[...]"
(not using "+=") the content of ${FSL_EULA_FILE}, which is added in
fsl-eula-unpack, is overwritten. So the EULA isn't deployed to the
${LICENSE_DIRECTORY}.
Using 'LIC_F
Hello,
When I have enabled PREEMPT_RT_FULL on kernel, and see that the
/proc/meminfo shows
only 660 MB of RAM, where as physical RAM that is attached is 4GB.
CONFIG_PREEMPT_RT_FULL=y
CONFIG_HZ_1000=y
CONFIG_HZ=1000
the meminfo reported 4GB when in normal case. This is seen on both
P3041Ds a
On Wed, Jun 3, 2015 at 6:18 AM, Stefan Christ wrote:
> Hi,
>
> here are two fixes for my last patch
> [PATCH] fsl-eula-unpack: deploy Freescale EULA
> to the meta-freescale list.
>
> The first patch corrects the md5 checksum for the Freescale EULA file and the
> second fixes a problem when a r
On Mon, Jun 1, 2015 at 8:14 PM, Otavio Salvador wrote:
> Hello everyone,
>
> it seems Daiane, Eric and I are the only ones considering the FSL
> Community meeting something important. I think there is no need for a
> meeting for three people to discuss things that concerns the whole
> community. I
Hello everyone,
excuse me for asking, as I have just spent a few years no longer developing
for OpenEmbedded (my most active period was 2006-2011 when I started adding
Freescale PowerPC devices), only using it occasionally during the 2011-2015.
My main question: What is at stake? Are there any u
Hi Daiane,
On Wed, Jun 3, 2015 at 3:00 PM, Daiane Angolini
wrote:
> For me, this silence means people are not interest on being part of
> decisions. The directions we take are not important.
>
> I think they are important in the end, but most people are reactive rather
than proactive when it c
2015-05-29 22:17 GMT+02:00 Simone :
> Dear All,
> I'm trying to use Xorg server on iMX53 and qt4.8
> I got a working system, without too much difficulties.
>
> The only one problem I have is that I'm not able to run Xorg as a separated
> server (I must run it togheter with my application).
> To do
On Wed, Jun 3, 2015 at 11:11 AM, Marco Cavallini
wrote:
> I've just tried to switch YP core-image-sato from 'dizzy' to 'fido'
> 1.8, but unfortunately seems that Xorg is broken (it worked with
> 'dizzy').
> Any hint would be appreciated.
>
Which board? I bet this is a non-supported board. My gue
Hello,
I've just tried to switch YP core-image-sato from 'dizzy' to 'fido'
1.8, but unfortunately seems that Xorg is broken (it worked with
'dizzy').
Any hint would be appreciated.
TIA
root@imx6solosabresd:~# xinit
X.Org X Server 1.16.3
Release Date: 2014-12-20
X Protocol Version 11, Revision 0
This patch is going to cause a HUGE problem on all our proprietary packages.
MX53's bound license is an precursor to current license. With this change MX53
is now broken. The old license did not require an SCR so an SCR is not
available for mx53.
We are going to get many new versions of our
On Wed, Jun 3, 2015 at 11:13 AM, Lauren Post wrote:
>
> This patch is going to cause a HUGE problem on all our proprietary packages.
>
> MX53's bound license is an precursor to current license. With this change
> MX53 is now broken. The old license did not require an SCR so an SCR is not
> av
Here is the problem: The EULA is updated frequently with changes that really
don't matter to existing packages. New 3rd party requirements are added that
apply to new packages, typos are occasionally fixed, and so on.
If this patch is limiting us to only one EULA in all packages, that means a
On Wed, Jun 3, 2015 at 11:56 AM, Ann Thornton
wrote:
>
> Here is the problem: The EULA is updated frequently with changes that really
> don't matter to existing packages. New 3rd party requirements are added that
> apply to new packages, typos are occasionally fixed, and so on.
>
> If this pat
Hi Ann and Lauren,
On 06/03/2015 09:15 AM, Otavio Salvador wrote:
> On Wed, Jun 3, 2015 at 11:56 AM, Ann Thornton
> wrote:
>>
>> Here is the problem: The EULA is updated frequently with changes
>> that really don't matter to existing packages. New 3rd party
>> requirements are added that appl
On Thu, May 7, 2015 at 8:24 AM, Andreas Müller
wrote:
> On Wed, May 6, 2015 at 6:38 PM, Prabhu S wrote:
>> There is no option to report to as ES 2.0. ES 2.0 is subset of ES3.0. Can
>> you able to patch kwin?
>>
> I will try that - see how far I get.
>
OK I would like to come back to this: Shouldn
The current license does that but it is not embedded into the older packages.
Current license evolved from the previous license. We feel comfortable that
users building legacy devices will be covered same as before.
The current patch assumes the license will checksum match the license in the
try after eglMakeCurrent, it should provide correct value.
On Wed, Jun 3, 2015 at 12:21 PM, Andreas Müller <
schnitzelt...@googlemail.com> wrote:
> On Thu, May 7, 2015 at 8:24 AM, Andreas Müller
> wrote:
> > On Wed, May 6, 2015 at 6:38 PM, Prabhu S wrote:
> >> There is no option to report to as
On Wed, Jun 3, 2015 at 2:19 PM, Lauren Post wrote:
> The current license does that but it is not embedded into the older packages.
> Current license evolved from the previous license. We feel comfortable that
> users building legacy devices will be covered same as before.
>
> The current patch
Hi Fabio,
We're looking for your input on the following question - do you think
that my patch should cover also sabreauto board, in order to avoid the
VIDEO_ARGS define "hack"?
If you prefer such approach, it would be great if you can test the
patch on the actual board and confirm that it works,
Hello Marco,
Nice to hear you!
I saw that Xorg start correctly, then it try to launch xterm, but since this is
not present in our system, it exit and close up everything.
I just replaced the execution of xterm with the execution of my application,
and it works perfectly. I also know that by defa
Hello,
This is my first time posting so I hope I am doing this right :)
I have been trying to get bluetooth working on a wandboard-dual (Rev A0) on
Yocto 1.7.1 for the last few weeks and have run into issue after issue. At this
point I am having a hard time even making the hci device show up, e
config HIGHMEM
bool "High memory support"
depends on PPC32 && !PREEMPT_RT_FULL
The highly helpful commit message of the patch that does this is:
power-disable-highmem-on-rt.patch
Signed-off-by: Thomas Gleixner
Some vague details here:
https://bugzilla.yoctoproject.org/s
24 matches
Mail list logo
