From: Raymond Tan
Hi Bruce,
This is the patch to backport Intel Denverton
patches on iSMT that are available in mainline Linux Kernel.
Please review and provide feedback, if any.
Thanks,
Raymond Tan
Mika Westerberg (1):
i2c: ismt: Add Intel DNV PCI ID
On Sun, Jul 24, 2016 at 7:38 AM, Khem Raj wrote:
> On Sun, Jul 24, 2016 at 12:34 AM, Edward Wingate wrote:
>> Ah, I found it. I had inadvertently deleted one line
>> (DISTRO="mydistro") from my layer's conf/layer.conf.
>>
>> Am I doing this right
This mail was sent out by Recipe reporting system.
This message list those recipes which need to be upgraded. If maintainers
believe some of them needn't to upgrade at this time, they can fill
RECIPE_NO_UPDATE_REASON in respective recipe file to ignore this remainder
until newer upstream version
On 2016-07-23 8:02 AM, Tomas Winkler wrote:
Replay Protected Memory Block (RPMB) subsystem
The feature provides 3 configurations
1. Base : enables the subsystem
2. UAPI : enables user space api via /dev/rpmbX
3. Sim : RPMB HW simulation device
Looks fine to me. This is now merged. If there
On 2016-07-23 7:31 AM, Winkler, Tomas wrote:
Hi Bruce
Please pull RPMB patches for BXT. These patches tare waiting in LKML
on review.
Also here he patches are staged on standard/base but for now you may
want to consider margining them to bxt-rebase
similar to the mei ones, I put
On Sun, Jul 24, 2016 at 2:42 PM, Chris Sykes <
ch...@newforest-technology.co.uk> wrote:
> Hi,
>
> At the end of last week I hit a known kernel memory leak in the
> linux-yocto 4.1 branch, as delivered in 2.1 / krogoth. It rather quickly
> results in an OOM kernel panic on my platform (x86, 1G
On 2016-07-24 6:09 PM, Chris Tapp wrote:
I’m using the meta-intel “valley-island” BSP under “krogoth” and think I may
have run into https://bugzilla.kernel.org/show_bug.cgi?id=109051.
I’m using a J1900 (listed as affected) and the system locks up totally (running
a graphics-based application)
I’m using the meta-intel “valley-island” BSP under “krogoth” and think I may
have run into https://bugzilla.kernel.org/show_bug.cgi?id=109051.
I’m using a J1900 (listed as affected) and the system locks up totally (running
a graphics-based application) after an indeterminate period.
Using the
On Sun, Jul 24, 2016 at 11:42 AM, Chris Sykes
wrote:
> Hi,
>
> At the end of last week I hit a known kernel memory leak in the linux-yocto
> 4.1 branch, as delivered in 2.1 / krogoth. It rather quickly results in an
> OOM kernel panic on my platform (x86, 1G
Hi,
At the end of last week I hit a known kernel memory leak in the
linux-yocto 4.1 branch, as delivered in 2.1 / krogoth. It rather
quickly results in an OOM kernel panic on my platform (x86, 1G RAM).
The patch below fixed the problem for me:
On Sun, Jul 24, 2016 at 12:34 AM, Edward Wingate wrote:
> Ah, I found it. I had inadvertently deleted one line
> (DISTRO="mydistro") from my layer's conf/layer.conf.
>
> Am I doing this right though? Do I need DISTRO="mydistro" in both
> conf/layer.conf and
Ah, I found it. I had inadvertently deleted one line
(DISTRO="mydistro") from my layer's conf/layer.conf.
Am I doing this right though? Do I need DISTRO="mydistro" in both
conf/layer.conf and conf/distro/mydistro.conf? Removing it from
either doesn't work, but it seems redundant to put it in
On Sat, Jul 23, 2016 at 11:05 PM, Khem Raj wrote:
> Move these DISTRO settings above require conf/distro/poky.conf
That didn't change anything. And it had been working like that for a
long time now. Just a few days ago, it stopped taking effect and
reverting back to poky.
On Sat, Jul 23, 2016 at 10:49 PM, Edward Wingate wrote:
> This is in my layer's conf/distro/mydistro.conf file:
>
> require conf/distro/poky.conf
> DISTRO = "mydistro"
> DISTRO_NAME = "MyDistro"
Move these DISTRO settings above require conf/distro/poky.conf
>
>
14 matches
Mail list logo