>On 2016-11-14 07:43 AM, Jukka Laitinen wrote:
>> The i915 module stopped compiling in 4.4.30 rebase. These patches fix
>> the merge errors causing this.
>>
>
> I tried the patches here, and ones directly from gmail/the mailing list and
> they are all showing up as corrupted.
>
> I tried to fix
On 11/15/16 8:56 PM, Jianxun Zhang wrote:
> Add detection of current path for -I option, also update
> type definitions for EFI compiling.
>
> Signed-off-by: Jianxun Zhang
> ---
> Makefile| 4 +++-
> Makefile.efi| 4 +++-
> inc/rmc_types.h | 9
d-id]:
> Bad value\n')
>
> Actually, I got 438 of them :-(
>
> Build Configuration:
> BB_VERSION= "1.32.0"
> BUILD_SYS = "x86_64-linux"
> NATIVELSBSTRING = "universal"
> TARGET_SYS= "powerpc-amltd-linux-gnuspe&quo
On 11/15/16 3:56 AM, 신택현 (Taek Hyun Shin) wrote:
> I did use only image-mklibs TT
>
> And, I did try modify some project make file for mklibs. add *_pic.a
>
> So, I did resolve not pic file found for error message. just modified package.
>
> But, other error occurred as follow:
>
>
Remove code, which was originally removed in
cbadb9d9de33 "Revert "drm/i915: Check live status before reading edid"
but crept back later in commit
1c8841ccca2e "Merge branch 'standard/base' into standard/intel/base"
Signed-off-by: Jukka Laitinen
---
The i915 module stopped compiling in 4.4.30 rebase. These patches fix the
merge errors causing this.
Jukka Laitinen (2):
Revert "UPSTREAM: drm/i915: take a power domain ref only when needed
during HDMI detect"
Fix merge errors for i915 to compile
drivers/gpu/drm/i915/intel_drv.h | 3
Add detection of current path for -I option, also update
type definitions for EFI compiling.
Signed-off-by: Jianxun Zhang
---
Makefile| 4 +++-
Makefile.efi| 4 +++-
inc/rmc_types.h | 9 ++---
3 files changed, 12 insertions(+), 5 deletions(-)
diff
It's a little crude and certainly not optimal performance-wise, but we
can support querying for recipes that inherit a particular class without
too much trouble. This allows you to add "inherits:cmake" to the query
and have it return only recipes that inherit the cmake class. You can
use more than
At the moment it's a bit difficult to get update logs out of the
environment in which the update script is being run. In order to make
the logs more accessible, create a LayerUpdate model to record the
output of update_layer.py separately for each layerbranch and tie the
created LayerUpdates
If you specified printerr=False we were referring to the output variable
that hadn't been set. Looks like I broke this back in 2013 in
93ce26f21cdbbd8a645792359cde87acf05144d7.
Signed-off-by: Paul Eggleton
---
layerindex/utils.py | 4 ++--
1 file changed, 2
Add an action to duplicate a Branch object, along with all of the
LayerBranches (and LayerMaintainers and LayerDependencies) underneath
it.
Signed-off-by: Paul Eggleton
---
layerindex/admin.py | 26 ++
1 file changed, 26 insertions(+)
diff
> On Nov 1, 2016, at 15:48, Tracy Graydon wrote:
>
> Hello,
>
> The latest release of the Yocto Project 2.2 (morty-16.0.0) is now available
> for download at:
>
> http://downloads.yoctoproject.org/releases/yocto/yocto-2.2/poky-morty-16.0.0.tar.bz2
>
These are likely appropriate for standard/intel/base as well (we have
the same drm backport). Once a non-mangled version is sent please try
applying there first.
Thanks,
Cal
On 11/15/2016 06:09 AM, Bruce Ashfield wrote:
On 2016-11-14 07:43 AM, Jukka Laitinen wrote:
The i915 module stopped
The short version is that the SWAT process document has been updated,
if you're a member of the SWAT team please take a few moments to read
this mail and update the wiki.
We're making a concerted effort in the 2.3 cycle to improve the SWAT
process and ensure that it's operating effectively.
To
On 2016-11-14 07:43 AM, Jukka Laitinen wrote:
The i915 module stopped compiling in 4.4.30 rebase. These patches fix the
merge errors causing this.
I tried the patches here, and ones directly from gmail/the mailing list
and they are all showing up as corrupted.
I tried to fix them up, but
Hi Jussi,
> On 13 November 2016 at 16:51, Lukasz Majewski
> wrote:
>
> > Dear All,
> >
> > Maybe here I would find answer to question which puzzles me from
> > some time.
> >
> > The problem:
> >
> > Disable syslog service on startup of sysvinit based board.
> > (syslog is
On 2016-11-14 07:43 AM, Jukka Laitinen wrote:
The i915 module stopped compiling in 4.4.30 rebase. These patches fix the
merge errors causing this.
It looks like exchange mangled these patches on the way through, I'm
seeing line wraps in the header, which lead to:
Applying: Revert "UPSTREAM:
s"
DISTRO = "amltd"
DISTRO_VERSION= "2.2+snapshot-20161115"
TUNE_FEATURES = "m32 spe ppce500v2"
TARGET_FPU= "ppc-efd"
meta = "master:43e652f3d1fee5ce7fad67e6400315eab1b34270&quo
Build the core-image-sato SDK with API documentation enabled to verify that this
doesn't regress.
Signed-off-by: Ross Burton
---
buildset-config.controller/nightly-qa-extras.conf | 4
1 file changed, 4 insertions(+)
diff --git
I did use only image-mklibs TTAnd, I did try modify some project make file for mklibs. add *_pic.aSo, I did resolve not pic file found for error message. just modified package.But, other error occurred as follow:__dso_handle undefinedDoes mklibs can't support c++? only support c library??
On 13 November 2016 at 16:51, Lukasz Majewski wrote:
> Dear All,
>
> Maybe here I would find answer to question which puzzles me from some
> time.
>
> The problem:
>
> Disable syslog service on startup of sysvinit based board.
> (syslog is defined in e.g.
Hi.
Michael was right, the new subpackage was renamed and it is now called
linux-firmware-bcm43430.
I have sent the patch with fixed typo.
Piotr
On 14.11.2016 18:45, Khem Raj wrote:
are you using linux-firmware-bcm43430
On Mon, Nov 14, 2016 at 4:27 AM, Piotr Lewicki
From: "piotr.lewicki"
New linux-firmware subpackage is called "bcm43430" and not "bcrm43430".
Renaming it because the test image is not building with the typo.
piotr.lewicki (1):
raspberrypi3.conf: fix typo for BCM43430
conf/machine/raspberrypi3.conf | 2 +-
1 file
23 matches
Mail list logo