From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Huth Date: Fri, 12 Feb 2016 06:27:32 +0000 Subject: Re: [kvm-unit-tests PATCH v2 06/14] powerpc/ppc64: add boot rom source Message-Id: <56BD7B54.4080006@redhat.com> List-Id: References: <1454957594-30601-1-git-send-email-drjones@redhat.com> <1454957594-30601-7-git-send-email-drjones@redhat.com> In-Reply-To: <1454957594-30601-7-git-send-email-drjones@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Andrew Jones , kvm@vger.kernel.org, kvm-ppc@vger.kernel.org Cc: dgibson@redhat.com, david@gibson.dropbear.id.au, agraf@suse.de, lvivier@redhat.com, pbonzini@redhat.com On 08.02.2016 19:53, Andrew Jones wrote: > Make a one line replacement for SLOF. This bootloader just > jumps to 0x400000, because we know the kernel will be there. > This commit allows rebuilding of the bootloader, as long > as the SLOF build_romfs tool is present, but since it would be > a pain to require that tool for ever build, we'll just commit > the binary rom image too with the next commit. > > Signed-off-by: Andrew Jones I haven't tested it yet, but I think this should also be doable without the build_romfs tool? Since QEMU does not care about the header that this tool creates, it should not matter whether there is some valid data in the first 256 or simply zeros. So simply linking with "-Wl,--oformat,binary -Ttext=0x100" or so should do the job, also? Thomas From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Huth Subject: Re: [kvm-unit-tests PATCH v2 06/14] powerpc/ppc64: add boot rom source Date: Fri, 12 Feb 2016 07:27:32 +0100 Message-ID: <56BD7B54.4080006@redhat.com> References: <1454957594-30601-1-git-send-email-drjones@redhat.com> <1454957594-30601-7-git-send-email-drjones@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Cc: dgibson@redhat.com, david@gibson.dropbear.id.au, agraf@suse.de, lvivier@redhat.com, pbonzini@redhat.com To: Andrew Jones , kvm@vger.kernel.org, kvm-ppc@vger.kernel.org Return-path: Received: from mx1.redhat.com ([209.132.183.28]:44846 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750816AbcBLG1h (ORCPT ); Fri, 12 Feb 2016 01:27:37 -0500 In-Reply-To: <1454957594-30601-7-git-send-email-drjones@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: On 08.02.2016 19:53, Andrew Jones wrote: > Make a one line replacement for SLOF. This bootloader just > jumps to 0x400000, because we know the kernel will be there. > This commit allows rebuilding of the bootloader, as long > as the SLOF build_romfs tool is present, but since it would be > a pain to require that tool for ever build, we'll just commit > the binary rom image too with the next commit. > > Signed-off-by: Andrew Jones I haven't tested it yet, but I think this should also be doable without the build_romfs tool? Since QEMU does not care about the header that this tool creates, it should not matter whether there is some valid data in the first 256 or simply zeros. So simply linking with "-Wl,--oformat,binary -Ttext=0x100" or so should do the job, also? Thomas