<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Jun 16, 2017 at 2:13 PM, Cillian O'Donnell <span dir="ltr"><<a href="mailto:cpodonnell8@gmail.com" target="_blank">cpodonnell8@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi,<br>
<br>
I am getting the RSB to build Couverture-Qemu and I just want to check<br>
a few things I have done so far.<br>
<br>
1. There are about 5 patches applied to the current qemu build. Only<br>
one of which applies cleanly to the Couverture build. Do you want me<br>
to try and fix these up, comment them out and leave a note for<br>
whoever wants to fix them or remove them completely? The patches that<br>
don't work are:<br>
<br>
%patch add qemu<br>
pw://<a href="http://patchwork.ozlabs.org/patch/406903/raw/Provide-the-missing-LIBUSB_LOG_LEVEL_-for-older-libusb-or-FreeBSD.-Providing-just-the-needed-value-as-a-defined..patch" rel="noreferrer" target="_blank">patchwork.ozlabs.org/<wbr>patch/406903/raw/Provide-the-<wbr>missing-LIBUSB_LOG_LEVEL_-for-<wbr>older-libusb-or-FreeBSD.-<wbr>Providing-just-the-needed-<wbr>value-as-a-defined..patch</a><br>
<br>
%patch add qemu<br>
<a href="https://gaisler.org/qemu/0001-LEON3-Add-emulation-of-AMBA-plug-" rel="noreferrer" target="_blank">https://gaisler.org/qemu/0001-<wbr>LEON3-Add-emulation-of-AMBA-<wbr>plug-</a><br>
play.patch<br>
<br>
%patch add qemu<br>
<a href="https://gaisler.org/qemu/0002-LEON3-Build-AMBA-plug-and-play-records-from-high-lev.patch" rel="noreferrer" target="_blank">https://gaisler.org/qemu/0002-<wbr>LEON3-Build-AMBA-plug-and-<wbr>play-records-from-high-lev.<wbr>patch</a><br>
<br>
%patch add qemu<br>
<a href="https://gaisler.org/qemu/0003-LEON3-Init-UART-timers-and-CPU-if-we-run-a-RAM-image.patch" rel="noreferrer" target="_blank">https://gaisler.org/qemu/0003-<wbr>LEON3-Init-UART-timers-and-<wbr>CPU-if-we-run-a-RAM-image.<wbr>patch</a><br>
<br>
<br></blockquote><div><br>I think they need to be proposed to the Couverture project to be evaluated. They should</div><div>be OK with the Gaisler ones without too much trouble. We can bring in Gaisler folks.</div><div>The other is a portability one. </div><div><br></div><div>So at least make the project aware of them.</div><div><br></div><div><a href="https://forge.open-do.org/projects/couverture-qemu/">https://forge.open-do.org/projects/couverture-qemu/</a><br></div><div><br></div><div>Make sure myself and chrisj@ are on any issue/email you file.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
2. For this source setting section, is the first part just dealing<br>
with the case were this a packaged release so a tar of the download is<br>
already included with it?<br>
<br>
%if %{rsb_released} && %{!defined without_release_url}<br>
%source set qemu<br>
%{rtems_release_url}/%{rtems_<wbr>version}/sources/qemu-git-<wbr>42d58e7.tar.xz<br>
%else<br>
%source set qemu<br>
<a href="https://github.com/AdaCore/qemu/archive/%{qemu_version}.tar.gz" rel="noreferrer" target="_blank">https://github.com/AdaCore/<wbr>qemu/archive/%{qemu_version}.<wbr>tar.gz</a><br>
%endif<br></blockquote><div><br></div><div>I think so but Chris should confirm that. </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
3. What does the -q option do in the %prep section of the build, this<br>
option shows up in examples in the docs but there is no description of<br>
what it does?<br>
<br>
%source setup qemu -q -n qemu-%{qemu_version}<br></blockquote><div><br></div><div>Chris will have to answer this.</div><div> <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
4. The current qemu build is configured with the default setting to<br>
build for all architectures but most of the arch's aren't used by<br>
RTEMS and/or don't have machine support for same bsps, so I've added a<br>
--target-list to only build the targets that have a corresponding bsp<br>
(sparc64-softmmu is missing as it runs into build issues, I forgot to<br>
mention in the initial results). However the list spills over 80 lines<br>
so should I make a %{qemu_targets} macro and if so where should I put<br>
it?<br></blockquote><div><br></div><div>I like the idea of limiting the targets built. You are right that we don't </div><div>care about the others.</div><div><br></div><div>The style and variable name are Chris questions.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
--make=%{__make} \<br>
72 --target-list=arm-softmmu,<wbr>i386-softmmu,lm32-softmmu,<wbr>mips-softmmu,ppc-softmmu,<wbr>sparc-softmmu<br>
\<br>
73 ${VDE_CONFIG} \<br>
74 --disable-smartcard-nss \<br>
<br>
Thanks,<br>
<br>
Cillian.<br>
</blockquote></div><br></div></div>