On 8 December 2017 at 18:39, Jason A. Donenfeld wrote:
> On Fri, Dec 8, 2017 at 12:49 PM, Peter Maydell
> wrote:
>> My suggestion is that we should add a second non-secure UART
>> to the virt board, so if you're using secure=no then you
>> get serial 1
On Fri, Dec 8, 2017 at 12:49 PM, Peter Maydell wrote:
> Now that the 2.11 release is mostly out of the way, I've been
> working through some of my other todo list items so I've
> come back to this thread.
>
> My suggestion is that we should add a second non-secure UART
>
On 26 October 2017 at 18:31, Jason A. Donenfeld wrote:
> On Thu, Oct 26, 2017 at 6:41 PM, Peter Maydell
> wrote:
>> Those are primarily about migration compatibility -- you should
>> be able to live migrate a guest from QEMU 2.6's virt-2.6 machine to
On Thu, Oct 26, 2017 at 6:41 PM, Peter Maydell wrote:
> Those are primarily about migration compatibility -- you should
> be able to live migrate a guest from QEMU 2.6's virt-2.6 machine to
> QEMU 2.7's virt-2.6 machine. That's a stricter requirement than
> the
On 26 October 2017 at 17:36, Jason A. Donenfeld wrote:
> On Thu, Oct 26, 2017 at 6:34 PM, Peter Maydell
> wrote:
>> Reordering it would break existing users of the trustzone uart,
>> whose command lines would stop working.
>
> I thought this was the
On Thu, Oct 26, 2017 at 6:34 PM, Peter Maydell wrote:
> Reordering it would break existing users of the trustzone uart,
> whose command lines would stop working.
I thought this was the reason for all of those virt26, virt28,etc
types -- people who want stability code
On 26 October 2017 at 17:15, Jason A. Donenfeld wrote:
> On Thu, Oct 26, 2017 at 4:36 PM, Peter Maydell
> wrote:
>> I'm still thinking about this. (You definitely can't have four,
>> though, because we already have 2 in the trustzone-enabled
>> config,
On Thu, Oct 26, 2017 at 4:36 PM, Peter Maydell wrote:
> This has *never* been guaranteed or indeed true. It's just happened
> to be true for the x86 PC machine and perhaps for some others that
> you've been using. For instance, the MIPS boston board only has
> one uart.
On 26 October 2017 at 15:13, Jason A. Donenfeld wrote:
> The problem with this approach is that then different architectures
> need different fancy options, which makes things a hassle. With the
> old guarantee of each machine providing four serial ports
This has *never* been
On Thu, Oct 26, 2017 at 3:34 PM, Andrew Jones wrote:
> You could make the PL011 user instantiate-able and make the necessary
> changes to use the dynamic FDT node generation framework (sysbus-fdt),
> and then you'd be able to add as many additional UARTs as you like to
>
On Tue, Oct 24, 2017 at 07:57:37PM +0200, Jason A. Donenfeld wrote:
> Hey folks,
>
> In case you're curious, this is the kind of hideous workaround
> required until this is fixed:
>
> https://git.zx2c4.com/WireGuard/commit/?id=2456a56729f7247bf88476317fed0ac822a31e92
>
> Please let me know if
Hey folks,
In case you're curious, this is the kind of hideous workaround
required until this is fixed:
https://git.zx2c4.com/WireGuard/commit/?id=2456a56729f7247bf88476317fed0ac822a31e92
Please let me know if you intend to fix this or if you will accept
working patches from me for it, or if
Hey Peter,
I really do need more serial ports. Two, actually. I'm using qemu on
build.wireguard.com for CI. I have normal output come on ttyS0
(ttyAMA0) and then if it's successful, the final step is writing
"success" into ttyS1 (ttyAMA1), so that I can confirm with certainty
that the tests
Hi Peter,
On 10/23/2017 10:11 AM, Peter Maydell wrote:
> This is really the documentation being wrong -- that is actually
> a PC specific thing. In QEMU generally, -serial can be used
> for as many serial ports as the machine model provides, up
> to a maximum of four.
FYI I'm still working on
On 23 October 2017 at 13:27, Jason A. Donenfeld wrote:
> The QEMU man page says:
>
>-serial dev
>This option can be used several times to
>simulate up to 4 serial ports.
>
> However, the ARM virt machine erroneously only provides 1 serial port.
>
15 matches
Mail list logo