On Sat, Oct 7, 2017 at 7:03 PM, Mirza Krak wrote:
> As I started digging to check the current state of the different
> layers it was quite clear to me that there where two different sets.
> One is maintained by Rockchip [1] and the other one by the community
> [2].
Don't forget https://github.com
On Sat, Oct 7, 2017 at 4:03 PM, Mirza Krak wrote:
> Hi all.
>
> I recently started working with Rockchip SoC`s and I currently have a
> Tinkerboard and a FireFly-RK3288 board. And as I recently enter the
> Yocto Rockchip world I have some comments and questions on the current
> setup/workflow whic
needed to pass yocto-check-layer
Signed-off-by: Armin Kuster
---
meta-tpm/README | 4
1 file changed, 4 insertions(+)
diff --git a/meta-tpm/README b/meta-tpm/README
index e69de29..bbc70bb 100644
--- a/meta-tpm/README
+++ b/meta-tpm/README
@@ -0,0 +1,4 @@
+meta-tpm layer
+==
+
+
if cuse is enabled, depend on fuse which is in meta-filesystems
throw error is layer is missing.
Signed-off-by: Armin Kuster
---
meta-tpm/recipes-tpm/swtpm/swtpm_1.0.bb | 10 --
1 file changed, 8 insertions(+), 2 deletions(-)
diff --git a/meta-tpm/recipes-tpm/swtpm/swtpm_1.0.bb
b/meta-
Hi all.
I recently started working with Rockchip SoC`s and I currently have a
Tinkerboard and a FireFly-RK3288 board. And as I recently enter the
Yocto Rockchip world I have some comments and questions on the current
setup/workflow which I found a bit confusing when starting out.
As I started dig
On Sat, Oct 7, 2017 at 9:38 AM, Bill Jenkins wrote:
>
>> On Sep 15, 2017, at 8:02 AM, Bill Jenkins wrote:
>>
>>
>>> On Sep 15, 2017, at 7:43 AM, Khem Raj wrote:
>>>
>>> On Fri, Sep 15, 2017 at 7:35 AM, Bill Jenkins wrote:
> On Sep 15, 2017, at 6:54 AM, Khem Raj wrote:
>
> On T
> On Sep 15, 2017, at 8:02 AM, Bill Jenkins wrote:
>
>
>> On Sep 15, 2017, at 7:43 AM, Khem Raj wrote:
>>
>> On Fri, Sep 15, 2017 at 7:35 AM, Bill Jenkins wrote:
>>>
On Sep 15, 2017, at 6:54 AM, Khem Raj wrote:
On Thu, Sep 14, 2017 at 10:14 PM, Bill Jenkins wrote:
> Af
(Yocto Pyro, using systemd configured with resolved, networkd, timedated,
timesyncd)
/etc/resolv.conf is supposed to be symlinked to
/run/systemd/resolve/resolv.conf, which gets updated with the DNS address
received from DHCP, but it's not. Looking through systemd_232.bb, I see
that do_install() u
