Thanks! I will try it out and let you know the result!
--
You received this message because you are subscribed to the Google Groups
"linux-sunxi" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to linux-sunxi+unsubscr...@googlegroups.com.
For more options,
于 2018年2月13日 GMT+08:00 上午4:25:35, "Mr. Fülöp" 写到:
>Hi Icenowy,
>
>Thank you for your reply!
>I worked much and got this close, so I really want to make this thing
>work
>:)
>Do you have any suggestions/patches/directions? This "ugly hack" is
>there
>somewhere? :)
The Linux version of this ha
Hi Icenowy,
Thank you for your reply!
I worked much and got this close, so I really want to make this thing work
:)
Do you have any suggestions/patches/directions? This "ugly hack" is there
somewhere? :)
I think the issue resides on the "switching" to the next cpu...
Thank you in advance!
Al
于 2018年2月8日 GMT+08:00 上午2:02:39, "Mr. Fülöp" 写到:
>Hi Guys,
>
>I think I reached a dead end...
>Can you please tell me why does it hang on "(XEN) Bringing up CPU1"?
>I compiled many xen version, but my feeling is that in the u-boot is
>sth. that makes Xen hang...
>
>Any suggestions?
>
>Thank you
Hi Guys,
I think I reached a dead end...
Can you please tell me why does it hang on "(XEN) Bringing up CPU1"?
I compiled many xen version, but my feeling is that in the u-boot is sth. that
makes Xen hang...
Any suggestions?
Thank you in advance!
=
Xen
On Monday 05 February 2018 09:05 PM, Mr. Fülöp wrote:
Thank you all for your help! I really appreciate your feedback!
Following your advice I booted XEN ... Yeeeyyy
BUT got stuck here:
Xen 4.11-unstable
(XEN) Xen version 4.11-unstable (@) (arm-linux-gnueabi-gcc (Debian 6.1.1-9)
6.1.1 2016070
Thank you all for your help! I really appreciate your feedback!
Following your advice I booted XEN ... Yeeeyyy
BUT got stuck here:
Xen 4.11-unstable
(XEN) Xen version 4.11-unstable (@) (arm-linux-gnueabi-gcc (Debian 6.1.1-9)
6.1.1 20160705) debug=y Fri Feb 2 16:48:36 UTC 2018
(XEN) Latest Ch
On Mon, Feb 5, 2018 at 7:05 PM, Mr. Fülöp wrote:
> This is the loop I was talking about:
>
> U-Boot 2018.03-rc1-00078-gb215307-dirty (Feb 05 2018 - 12:50:50 +)
>
> Loading Environment from FAT... Unable to use mmc 1:0... Failed (-5)
> Loading Environment from MMC... *** Warning - bad CRC, usin
This is the loop I was talking about:
U-Boot 2018.03-rc1-00078-gb215307-dirty (Feb 05 2018 - 12:50:50 +)
Loading Environment from FAT... Unable to use mmc 1:0... Failed (-5)
Loading Environment from MMC... *** Warning - bad CRC, using default environment
Failed (-5)
In:serial
Out: seri
Hello!
First of all I would like to thank you all for your amazing contribution! More
I dive into understanding the kernel, more I appreciate your work and more I
learn.
As Marc Zyngier said:
"Now, if someone could try and run guests on this turd and report whether
this works correctly or not,
On Sun, Jul 02, 2017 at 04:27:52PM +0100, Marc Zyngier wrote:
> It definitely requires extra testing (booting the kernel hardly shakes
> the GIC), but that's certainly encouraging. Can you run some
> significant workload in a guest (kernel compilation, hackbench) and
> report the results?
Also, en
Hi,
On Sun, Jul 02, 2017 at 04:40:20PM +0100, André Przywara wrote:
> On 02/07/17 15:17, Maxime Ripard wrote:
> > On Wed, Jun 07, 2017 at 03:06:55PM +0100, Marc Zyngier wrote:
> >>> If that is so fundamentally broken that this is the only benefit, I
> >>> guess we might as well use some old-style
On 02/07/17 15:17, Maxime Ripard wrote:
Hi,
> On Wed, Jun 07, 2017 at 03:06:55PM +0100, Marc Zyngier wrote:
>>> If that is so fundamentally broken that this is the only benefit, I
>>> guess we might as well use some old-style SMP ops.
>>
>> Broken, for sure. Which is why I'm asking about the bene
On Sun, 2 Jul 2017 20:36:04 +0800
wrote:
> 在 2017-07-02 19:22,Marc Zyngier 写道:
> > On Sun, 2 Jul 2017 15:08:12 +0800
> > wrote:
> >
> >> 在 2017-06-23 21:50,Chen-Yu Tsai 写道:
> >> > On Fri, Jun 23, 2017 at 9:39 PM, wrote:
> >> >> 在 2017-06-23 21:35,Maxime Ripard 写道:
> >> >>>
> >> >>> On
On Wed, Jun 07, 2017 at 03:06:55PM +0100, Marc Zyngier wrote:
> > If that is so fundamentally broken that this is the only benefit, I
> > guess we might as well use some old-style SMP ops.
>
> Broken, for sure. Which is why I'm asking about the benefits of running
> non-secure on something that ha
在 2017-07-02 19:22,Marc Zyngier 写道:
On Sun, 2 Jul 2017 15:08:12 +0800
wrote:
在 2017-06-23 21:50,Chen-Yu Tsai 写道:
> On Fri, Jun 23, 2017 at 9:39 PM, wrote:
>> 在 2017-06-23 21:35,Maxime Ripard 写道:
>>>
>>> On Fri, Jun 23, 2017 at 09:24:25PM +0800, icen...@aosc.io wrote:
在 2017-06-07 2
On Sun, 2 Jul 2017 15:08:12 +0800
wrote:
> 在 2017-06-23 21:50,Chen-Yu Tsai 写道:
> > On Fri, Jun 23, 2017 at 9:39 PM, wrote:
> >> 在 2017-06-23 21:35,Maxime Ripard 写道:
> >>>
> >>> On Fri, Jun 23, 2017 at 09:24:25PM +0800, icen...@aosc.io wrote:
>
> 在 2017-06-07 20:51,Marc Zyngier
在 2017-06-23 21:50,Chen-Yu Tsai 写道:
On Fri, Jun 23, 2017 at 9:39 PM, wrote:
在 2017-06-23 21:35,Maxime Ripard 写道:
On Fri, Jun 23, 2017 at 09:24:25PM +0800, icen...@aosc.io wrote:
在 2017-06-07 20:51,Marc Zyngier 写道:
> On 07/06/17 13:12, Icenowy Zheng wrote:
> >
> >
> > 于 2017年6月7日 GMT+08:00
On Fri, Jun 23, 2017 at 9:39 PM, wrote:
> 在 2017-06-23 21:35,Maxime Ripard 写道:
>>
>> On Fri, Jun 23, 2017 at 09:24:25PM +0800, icen...@aosc.io wrote:
>>>
>>> 在 2017-06-07 20:51,Marc Zyngier 写道:
>>> > On 07/06/17 13:12, Icenowy Zheng wrote:
>>> > >
>>> > >
>>> > > 于 2017年6月7日 GMT+08:00 下午8:11:12,
在 2017-06-23 21:35,Maxime Ripard 写道:
On Fri, Jun 23, 2017 at 09:24:25PM +0800, icen...@aosc.io wrote:
在 2017-06-07 20:51,Marc Zyngier 写道:
> On 07/06/17 13:12, Icenowy Zheng wrote:
> >
> >
> > 于 2017年6月7日 GMT+08:00 下午8:11:12, Marc Zyngier
> > 写到:
> > > On 07/06/17 08:00, Chen-Yu Tsai wrote:
> >
On Fri, Jun 23, 2017 at 09:24:25PM +0800, icen...@aosc.io wrote:
> 在 2017-06-07 20:51,Marc Zyngier 写道:
> > On 07/06/17 13:12, Icenowy Zheng wrote:
> > >
> > >
> > > 于 2017年6月7日 GMT+08:00 下午8:11:12, Marc Zyngier
> > > 写到:
> > > > On 07/06/17 08:00, Chen-Yu Tsai wrote:
> > > > > On Wed, Jun 7, 201
在 2017-06-07 20:51,Marc Zyngier 写道:
On 07/06/17 13:12, Icenowy Zheng wrote:
于 2017年6月7日 GMT+08:00 下午8:11:12, Marc Zyngier
写到:
On 07/06/17 08:00, Chen-Yu Tsai wrote:
On Wed, Jun 7, 2017 at 2:50 PM, Maxime Ripard
wrote:
On Wed, Jun 07, 2017 at 11:47:24AM +0800, Chen-Yu Tsai wrote:
On Wed,
On 07/06/17 14:04, Maxime Ripard wrote:
> On Wed, Jun 07, 2017 at 01:51:48PM +0100, Marc Zyngier wrote:
>> On 07/06/17 13:12, Icenowy Zheng wrote:
>>>
>>>
>>> 于 2017年6月7日 GMT+08:00 下午8:11:12, Marc Zyngier 写到:
On 07/06/17 08:00, Chen-Yu Tsai wrote:
> On Wed, Jun 7, 2017 at 2:50 PM, Maxime
On Wed, Jun 07, 2017 at 01:51:48PM +0100, Marc Zyngier wrote:
> On 07/06/17 13:12, Icenowy Zheng wrote:
> >
> >
> > 于 2017年6月7日 GMT+08:00 下午8:11:12, Marc Zyngier 写到:
> >> On 07/06/17 08:00, Chen-Yu Tsai wrote:
> >>> On Wed, Jun 7, 2017 at 2:50 PM, Maxime Ripard
> >>> wrote:
> On Wed, Jun 0
On 07/06/17 13:12, Icenowy Zheng wrote:
>
>
> 于 2017年6月7日 GMT+08:00 下午8:11:12, Marc Zyngier 写到:
>> On 07/06/17 08:00, Chen-Yu Tsai wrote:
>>> On Wed, Jun 7, 2017 at 2:50 PM, Maxime Ripard
>>> wrote:
On Wed, Jun 07, 2017 at 11:47:24AM +0800, Chen-Yu Tsai wrote:
> On Wed, Jun 7, 2017 at
于 2017年6月7日 GMT+08:00 下午8:11:12, Marc Zyngier 写到:
>On 07/06/17 08:00, Chen-Yu Tsai wrote:
>> On Wed, Jun 7, 2017 at 2:50 PM, Maxime Ripard
>> wrote:
>>> On Wed, Jun 07, 2017 at 11:47:24AM +0800, Chen-Yu Tsai wrote:
On Wed, Jun 7, 2017 at 11:40 AM, Icenowy Zheng
>wrote:
>
>
> 于
On 07/06/17 08:00, Chen-Yu Tsai wrote:
> On Wed, Jun 7, 2017 at 2:50 PM, Maxime Ripard
> wrote:
>> On Wed, Jun 07, 2017 at 11:47:24AM +0800, Chen-Yu Tsai wrote:
>>> On Wed, Jun 7, 2017 at 11:40 AM, Icenowy Zheng wrote:
于 2017年6月7日 GMT+08:00 上午11:36:27, Chen-Yu Tsai 写到:
> On We
On Wed, Jun 7, 2017 at 2:50 PM, Maxime Ripard
wrote:
> On Wed, Jun 07, 2017 at 11:47:24AM +0800, Chen-Yu Tsai wrote:
>> On Wed, Jun 7, 2017 at 11:40 AM, Icenowy Zheng wrote:
>> >
>> >
>> > 于 2017年6月7日 GMT+08:00 上午11:36:27, Chen-Yu Tsai 写到:
>> >>On Wed, Jun 7, 2017 at 8:47 AM, Icenowy Zheng wrot
于 2017年6月7日 GMT+08:00 下午2:50:36, Maxime Ripard
写到:
>On Wed, Jun 07, 2017 at 11:47:24AM +0800, Chen-Yu Tsai wrote:
>> On Wed, Jun 7, 2017 at 11:40 AM, Icenowy Zheng
>wrote:
>> >
>> >
>> > 于 2017年6月7日 GMT+08:00 上午11:36:27, Chen-Yu Tsai 写到:
>> >>On Wed, Jun 7, 2017 at 8:47 AM, Icenowy Zheng
>wr
On Wed, Jun 07, 2017 at 11:47:24AM +0800, Chen-Yu Tsai wrote:
> On Wed, Jun 7, 2017 at 11:40 AM, Icenowy Zheng wrote:
> >
> >
> > 于 2017年6月7日 GMT+08:00 上午11:36:27, Chen-Yu Tsai 写到:
> >>On Wed, Jun 7, 2017 at 8:47 AM, Icenowy Zheng wrote:
> >>> As we have now a basical implementation of PSCI for
On Wed, Jun 7, 2017 at 11:40 AM, Icenowy Zheng wrote:
>
>
> 于 2017年6月7日 GMT+08:00 上午11:36:27, Chen-Yu Tsai 写到:
>>On Wed, Jun 7, 2017 at 8:47 AM, Icenowy Zheng wrote:
>>> As we have now a basical implementation of PSCI for A83T, enable
>>> non-secure boot support and PSCI on A83T now.
>>>
>>> Sig
于 2017年6月7日 GMT+08:00 上午11:36:27, Chen-Yu Tsai 写到:
>On Wed, Jun 7, 2017 at 8:47 AM, Icenowy Zheng wrote:
>> As we have now a basical implementation of PSCI for A83T, enable
>> non-secure boot support and PSCI on A83T now.
>>
>> Signed-off-by: Icenowy Zheng
>> ---
>> arch/arm/mach-sunxi/Kconfi
On Wed, Jun 7, 2017 at 8:47 AM, Icenowy Zheng wrote:
> As we have now a basical implementation of PSCI for A83T, enable
> non-secure boot support and PSCI on A83T now.
>
> Signed-off-by: Icenowy Zheng
> ---
> arch/arm/mach-sunxi/Kconfig | 4
> 1 file changed, 4 insertions(+)
>
> diff --git
As we have now a basical implementation of PSCI for A83T, enable
non-secure boot support and PSCI on A83T now.
Signed-off-by: Icenowy Zheng
---
arch/arm/mach-sunxi/Kconfig | 4
1 file changed, 4 insertions(+)
diff --git a/arch/arm/mach-sunxi/Kconfig b/arch/arm/mach-sunxi/Kconfig
index 7ced
34 matches
Mail list logo