From mboxrd@z Thu Jan 1 00:00:00 1970 From: Oleksandr Tyshchenko Subject: Re: [PATCH 0/4] mini-os: initial ARM support Date: Thu, 5 Jun 2014 21:07:46 +0300 Message-ID: References: <1401731397-29842-1-git-send-email-talex5@gmail.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============8457194899305918857==" Return-path: Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Wsc4u-0005ea-8q for xen-devel@lists.xenproject.org; Thu, 05 Jun 2014 18:07:52 +0000 Received: by mail-wi0-f177.google.com with SMTP id f8so4063746wiw.10 for ; Thu, 05 Jun 2014 11:07:46 -0700 (PDT) In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Thomas Leonard Cc: xen-devel@lists.xenproject.org, Stefano Stabellini , Samuel Thibault List-Id: xen-devel@lists.xenproject.org --===============8457194899305918857== Content-Type: multipart/alternative; boundary=089e01681cd442bc6b04fb1a9f19 --089e01681cd442bc6b04fb1a9f19 Content-Type: text/plain; charset=UTF-8 > Hi Oleksandr, > > The "proposed" branch currently contain's only Karim Raslan's initial > ARM work. I have a series of patches on top of this (on the next > branch), but I was planning to get this initial support in first. > > Possibly my "Fixed initialisation code" commit should be merged with > Karim's code into a single patch. On the other hand, it might be > clearer to keep them separate (especially for other people who have > built on Karim's original work, e.g. I see on github that Jonathan > Daugherty has a fork from there). > I have applied your commit "Fixed initialisation code" on top of "proposed" branch -> Mini-OS boots without crashes and works as expected. It is very important commit!) I have only one question. Why do you use those addresses for GIC for now: gic.gicd_base = (char *)0x2c001000ULL; gic.gicc_base = (char *)0x2c002000ULL; With this I have a hypervisor crash( I let the Mini-OS to read them from cpu regs. And in my case they are: - 0x48211000 - 0x48212000 > > > Also, could you, please, explain me some generic things about Mini-OS: > > 1. Is HAVE_LIBC a necessary config? I mean if I build Mini-OS without > proper > > LIBC support will the Mini-OS to operate fully > > (are there any restrictions?) > > You only need HAVE_LIBC if you want to use your own libc. Without > HAVE_LIBC, minios provides its own versions of some basic functions > (memcmp, sprintf, etc). Mirage works without it, for example. > OK. It is clear. Thank you. -- Oleksandr Tyshchenko | Embedded Dev GlobalLogic www.globallogic.com --089e01681cd442bc6b04fb1a9f19 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

=
Hi Oleksandr,

The "proposed" branch currently contain's only Karim Raslan&#= 39;s initial
ARM work. I have a series of patches on top of this (on the next
branch), but I was planning to get this initial support in first.

Possibly my "Fixed initialisation code" commit should be merged w= ith
Karim's code into a single patch. On the other hand, it might be
clearer to keep them separate (especially for other people who have
built on Karim's original work, e.g. I see on github that Jonathan
Daugherty has a fork from there).

I hav= e applied your commit "Fixed initialisation code" on top of &quo= t;proposed" branch -> Mini-OS boots without crashes
and works as= expected. It is very important commit!)

I have only one question. Why do you use those addresses for= GIC for now:

=C2=A0=C2=A0=C2=A0 gic.gicd_base =3D (char *)0x2c00100= 0ULL;
=C2=A0=C2=A0=C2=A0 gic.gicc_base =3D (char *)0x2c002000ULL;
With this I have a hypervisor crash(

I let the Mini-OS to read them from cpu regs. And in my case= they are:
- 0x48211000
- 0x48212000
<= div>=C2=A0
> Also, could you, please, explain me some generic things about Mini-OS:=
> 1. Is HAVE_LIBC a necessary config? I mean if I build Mini-OS without = proper
> LIBC support will the Mini-OS to operate fully
> (are there any restrictions?)

You only need HAVE_LIBC if you want to use your own libc. Without
HAVE_LIBC, minios provides its own versions of some basic functions
(memcmp, sprintf, etc). Mirage works without it, for example.

OK. It is clear.
Thank you.

--

Oleksandr Tyshchenko | = Embedded Dev
GlobalLogic
www.globallogic.com
--089e01681cd442bc6b04fb1a9f19-- --===============8457194899305918857== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel --===============8457194899305918857==--