On 04.06.20 00:19, jorgeluis.martinezgarc...@gmail.com wrote:
> Hi,
> I forgot to mention that I am using Jailhouse v0.9.1 and hence the
What's the reason for that old version?
> actual config and dts files are
>
Hi,
I forgot to mention that I am using Jailhouse v0.9.1 and hence the actual
config and dts files are
https://github.com/siemens/jailhouse/blob/v0.9.1/configs/arm64/dts/inmate-zynqmp-zcu102-2.dts
and
Dear all,
I am trying to have three Linux instances on the ZCU102 ZynqMP Ultrascale+ (The
root cell and two guests). I followed the steps specified in
https://github.com/siemens/jailhouse/blob/master/Documentation/setup-on-zynqmp-zcu102.md
and have two Linux instances successfully running on
On 03.06.20 17:53, Jan Kiszka wrote:
> On 03.06.20 17:45, Jan Kiszka wrote:
>> On 03.06.20 15:30, dd wrote:
>>> Hello jan!
>>> I encountered network problems when I boot linux image built from
>>> jailhouse-images repository on my rpi4.
>>> I found there is no network on this system, i could not
On 03.06.20 17:45, Jan Kiszka wrote:
> On 03.06.20 15:30, dd wrote:
>> Hello jan!
>> I encountered network problems when I boot linux image built from
>> jailhouse-images repository on my rpi4.
>> I found there is no network on this system, i could not get a ipv4
>> address using eth0.
>> and I
No new features, just a few updates of Isar, kernel and kas.
Jan
Jan Kiszka (4):
u-boot-*: Do not use ftp URLs anymore
Update Isar revision
linux-jailhouse: Update stable kernel versions
Update to kas 2.1.1
.gitlab-ci.yml| 2 +-
From: Jan Kiszka
Signed-off-by: Jan Kiszka
---
.gitlab-ci.yml | 2 +-
build-images.sh | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index b91f2dd..7fed103 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -1,4 +1,4 @@
-image:
From: Jan Kiszka
Signed-off-by: Jan Kiszka
---
...-jailhouse-rpi_5.4.29.bb => linux-jailhouse-rpi_5.4.42.bb} | 4 ++--
...se-rt_5.4.28-rt19.bb => linux-jailhouse-rt_5.4.43-rt24.bb} | 4 ++--
.../{linux-jailhouse_5.4.31.bb => linux-jailhouse_5.4.43.bb} | 4 ++--
3 files changed, 6
From: Jan Kiszka
Signed-off-by: Jan Kiszka
---
kas.yml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kas.yml b/kas.yml
index 8cff59a..f710cae 100644
--- a/kas.yml
+++ b/kas.yml
@@ -21,7 +21,7 @@ repos:
isar:
url: https://github.com/ilbers/isar
-refspec:
From: Jan Kiszka
Those are legacy and can break with certain proxies.
Signed-off-by: Jan Kiszka
---
recipes-bsp/u-boot/u-boot-macchiatobin_2019.10-atf2.2.bb | 2 +-
recipes-bsp/u-boot/u-boot-pine64-plus_2019.10-atf2.2.bb | 2 +-
recipes-bsp/u-boot/u-boot-ultra96_2019.10-atf2.2.bb | 2 +-
On 03.06.20 15:54, peng@nxp.com wrote:
> From: Peng Fan
>
> There is a implication that the pin_base in the cell file
> should be "32 + 128 * i" with "i >= 0". However there is no checking
> for that. Pepole might choose other pin_base, such as 160, 224 and etc.
>
> Saying the 1st irqchip
On 03.06.20 15:30, dd wrote:
> Hello jan!
> I encountered network problems when I boot linux image built from
> jailhouse-images repository on my rpi4.
> I found there is no network on this system, i could not get a ipv4
> address using eth0.
> and I haven't found a way to configure the network
On 03.06.20 12:25, Jan Kiszka wrote:
> On 03.06.20 11:10, peng@nxp.com wrote:
>> From: Peng Fan
>>
>> There is a implication that the pin_base in the cell file
>> should be "32 + 128 * i" with "i >= 0". However there is no checking
>> for that. Pepole might choose other pin_base, such as 160,
Branch: refs/heads/next
Home: https://github.com/siemens/jailhouse
Commit: 4ce7658dddfd5a1682a379d5ac46657e93fe1ff0
https://github.com/siemens/jailhouse/commit/4ce7658dddfd5a1682a379d5ac46657e93fe1ff0
Author: Peng Fan
Date: 2020-06-03 (Wed, 03 Jun 2020)
Changed paths:
Hello jan!
I encountered network problems when I boot linux image built from
jailhouse-images repository on my rpi4.
I found there is no network on this system, i could not get a ipv4 address
using eth0.
and I haven't found a way to configure the network And i can't install
tools.
So
From: Peng Fan
There is a implication that the pin_base in the cell file
should be "32 + 128 * i" with "i >= 0". However there is no checking
for that. Pepole might choose other pin_base, such as 160, 224 and etc.
Saying the 1st irqchip pin_base is 224, the 2nd irqchip pin_base is
160. When
On 02/06/20 8:16 pm, Jan Kiszka wrote:
On 11.04.20 20:55, Jan Kiszka wrote:
On 11.04.20 20:37, Nikhil Devshatwar wrote:
Hi Jan,
On 11/04/20 11:28 pm, Jan Kiszka wrote:
On 11.04.20 19:25, 'Nikhil Devshatwar' via Jailhouse wrote:
Hi Jan,
On 11/04/20 4:31 pm, Jan Kiszka wrote:
From: Jan
On 03.06.20 11:10, peng@nxp.com wrote:
> From: Peng Fan
>
> There is a implication that the pin_base in the cell file
> should be "32 + 128 * i" with "i >= 0". However there is no checking
> for that. Pepole might choose other pin_base, such as 160, 224 and etc.
>
> Saying the 1st irqchip
From: Peng Fan
There is a implication that the pin_base in the cell file
should be "32 + 128 * i" with "i >= 0". However there is no checking
for that. Pepole might choose other pin_base, such as 160, 224 and etc.
Saying the 1st irqchip pin_base is 224, the 2nd irqchip pin_base is
160. When
19 matches
Mail list logo
