All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@linaro.org>
To: Andrii Tseglytskyi <andrii.tseglytskyi@globallogic.com>
Cc: Tim Deegan <tim@xen.org>,
	Oleksandr Dmytryshyn <oleksandr.dmytryshyn@globallogic.com>,
	Stefano Stabellini <stefano.stabellini@citrix.com>,
	Ian Campbell <ian.campbell@citrix.com>,
	xen-devel@lists.xen.org
Subject: Re: [PATCH] xen: arm: introduce uImage probe function for Dom0
Date: Wed, 20 Aug 2014 10:24:02 -0500	[thread overview]
Message-ID: <53F4BD92.8020104@linaro.org> (raw)
In-Reply-To: <CAH_mUMOeHgnXgo=GU0zinTbEMbzmA6s6M9kC03RFZes28RyVoQ@mail.gmail.com>



On 20/08/14 00:17, Andrii Tseglytskyi wrote:
> Hi Julien,

Hello Andrii,

>>> +    /*
>>> +     * Check for an appended DTB.
>>> +     */
>>> +    if ( addr + len + sizeof(dtb_hdr) <= size )
>>> +    {
>>> +        copy_from_paddr(&dtb_hdr, addr + len, sizeof(dtb_hdr));
>>> +
>>> +        if ( be32_to_cpu(dtb_hdr.magic) == DTB_MAGIC )
>>> +            len += be32_to_cpu(dtb_hdr.total_size);
>>> +
>>> +            if ( len - start > addr + size )
>>> +                return -EINVAL;
>>> +    }
>>
>>
>> This is a legacy on zImage, I don't really want to see it on implementation
>> of a new format. Xen is creating the device tree for DOM0, the developer
>> should not append a device tree.
>>
>
> Sorry this is not a topic of this patch, but what about appending
> device tree to domU kernel? I found that similar functionality was
> removed from tools by the following patch:
>
> http://permalink.gmane.org/gmane.comp.emulators.xen.cvs/31110

Only the check has been removed. The full binary is now loading in the 
memory. So appending device tree to kernel should still work.

>
> But in case if some HW is present in domU you may need this
> functionality. Code which supports HW in domU is going to be merged
> (iomem and your irq routing series), so maybe appended devtree is also
> OK?

IIRC, the plan is to allow the user to pass a snippet describing your 
device. The toolstack will add it in the generated device tree.

I don't think someone is working on it.

Regards,

-- 
Julien Grall

  reply	other threads:[~2014-08-20 15:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-19 10:37 [PATCH] xen: arm: introduce uImage probe function for Dom0 Oleksandr Dmytryshyn
2014-08-19 17:06 ` Julien Grall
2014-08-20  5:17   ` Andrii Tseglytskyi
2014-08-20 15:24     ` Julien Grall [this message]
2014-08-20 10:01   ` Oleksandr Dmytryshyn

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=53F4BD92.8020104@linaro.org \
    --to=julien.grall@linaro.org \
    --cc=andrii.tseglytskyi@globallogic.com \
    --cc=ian.campbell@citrix.com \
    --cc=oleksandr.dmytryshyn@globallogic.com \
    --cc=stefano.stabellini@citrix.com \
    --cc=tim@xen.org \
    --cc=xen-devel@lists.xen.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.