All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@citrix.com>
To: Wei Liu <wei.liu2@citrix.com>
Cc: Ian Jackson <ian.jackson@eu.citrix.com>,
	xen-devel@lists.xenproject.org, stefano.stabellini@citrix.com,
	ian.campbell@citrix.com,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [PATCH for-4.6] tools: Don't try to update the firmware directory on ARM
Date: Sun, 9 Aug 2015 14:49:23 +0100	[thread overview]
Message-ID: <55C75A63.3030906@citrix.com> (raw)
In-Reply-To: <20150808151632.GC14214@zion.uk.xensource.com>

Hi Wei,

On 08/08/2015 16:16, Wei Liu wrote:
> On Fri, Aug 07, 2015 at 06:27:18PM +0100, Julien Grall wrote:
>> The firmware directory is not built at all on ARM. Attempting to update
>> it using the target subtree-force-update will fail when try to update
>> seabios.
>>
>> Signed-off-by: Julien Grall <julien.grall@citrix.com>
>>
>> ---
>> Cc: Ian Jackson <ian.jackson@eu.citrix.com>
>> Cc: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
>> Cc: Ian Campbell <ian.campbell@citrix.com>
>> Cc: Wei Liu <wei.liu2@citrix.com>
>>
>>      I've noticed it while trying to update the QEMU tree used by Xen on
>>      a platform where iasl is not present (required by seabios in order
>>      to update it).
>>
>>      I think this should go in Xen 4.6 and possibly backport to Xen 4.5
>> ---
>>   tools/Makefile | 2 ++
>>   1 file changed, 2 insertions(+)
>>
>> diff --git a/tools/Makefile b/tools/Makefile
>> index 45cb4b2..2618559 100644
>> --- a/tools/Makefile
>> +++ b/tools/Makefile
>> @@ -305,7 +305,9 @@ endif
>>   ifeq ($(CONFIG_QEMU_TRAD),y)
>>   	$(MAKE) qemu-xen-traditional-dir-force-update
>>   endif
>> +ifeq ($(CONFIG_X86),y)
>>   	$(MAKE) -C firmware subtree-force-update
>> +endif
>>
>
> This is not optimal. What if you want to build OVMF on arm in the
> future? You also can't preclude you don't have any other firmwares that
> need to be built on ARM in the future.
> I think a proper way of doing this is to make CONFIG_SEABIOS=n when
> you're building on ARM. See tools/configure.ac.

tools/Makefile only build the firmware directory for x86 see:

SUBDIRS-$(CONFIG_X86) += firmware

Hence why I wrote the patch in the current way.

Building the firmware directory for would require more work than replace 
SUBDIRS-$(CONFIG_X86) to SUBDIRS-y.
In general, I do agree that we enable this with configure.ac but, IHMO 
this is not Xen 4.6 material...

Although I would be happy to fix it for Xen 4.7.

Regards,

-- 
Julien Grall

  reply	other threads:[~2015-08-09 13:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-07 17:27 [PATCH for-4.6] tools: Don't try to update the firmware directory on ARM Julien Grall
2015-08-08 15:16 ` Wei Liu
2015-08-09 13:49   ` Julien Grall [this message]
2015-08-11 12:22     ` Ian Campbell
2015-08-11 12:28       ` Wei Liu
2015-08-13  9:44 ` Wei Liu
2015-08-13 10:31   ` Ian Campbell

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=55C75A63.3030906@citrix.com \
    --to=julien.grall@citrix.com \
    --cc=ian.campbell@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=stefano.stabellini@citrix.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xenproject.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.