On Mon, Dec 09, 2019 at 05:10:30PM +, Peter Maydell wrote:
> On Mon, 9 Dec 2019 at 17:08, Daniel Thompson
> wrote:
> > I don't object to making it command line dependant (it is certainly
> > lower risk) but, out of interest, has using /aliases to force the
> > k
On Mon, Dec 09, 2019 at 03:36:17PM +, Peter Maydell wrote:
> On Mon, 9 Dec 2019 at 15:25, Daniel Thompson
> wrote:
> >
> > The virt machine can have two UARTs but the second UART is only
> > registered when secure-mode support is enabled. Change the machine so
similar to how a TZPC would typically
make a UART inaccessible to normal world on physical hardware.
Signed-off-by: Daniel Thompson
---
Notes:
It is difficult to add a UART without some kind of odd difference of
behaviour somewhere. As far as I could tell the choices are:
1. Move
On 30/10/14 22:12, Greg Bellows wrote:
> From: Fabian Aggeler
>
> GICs with grouping (GICv2 or GICv1 with Security Extensions) have a
> different exception generation model which is more complicated than
> without interrupt grouping. We add a new function to handle this model.
>
> Signed-off-by:
On 30/10/14 22:12, Greg Bellows wrote:
> From: Fabian Aggeler
>
> ICDDCR/GICD_CTLR is banked in GICv1 implementations with Security
> Extensions or in GICv2 in independent from Security Extensions.
> This makes it possible to enable forwarding of interrupts from
> Distributor to the CPU interface
On 18/04/14 05:34, Nicolas Pitre wrote:
>> I'm not suggesting to break anything or changing existing platforms,
>> > but how do we improve the Image format in a compatible way. If
>> > bootloaders want to support booting Image files or vmlinux directly,
>> > then we should support that including an
On 17/04/14 22:35, Russell King - ARM Linux wrote:
> On Thu, Apr 17, 2014 at 04:18:45PM -0500, Rob Herring wrote:
>> The problem here is more than just the TEXT_OFFSET changed. From what
>> I've heard, there are some QC chips which need much more reserved RAM
>> than the 2MB discussed here. Changin
On 17/04/14 21:35, Jason Gunthorpe wrote:
>>> The above is useful for loading the raw uncompressed Image without
>>> carrying the full ELF baggage.
>>
>> What exactly is the full ELF baggage? Aren't there existing mechanisms to
>> omit
>> debugging symbols, for example, if size is of concern?
>
On 22/04/14 11:40, Russell King - ARM Linux wrote:
> On Tue, Apr 22, 2014 at 11:26:53AM +0100, Daniel Thompson wrote:
>> On 18/04/14 05:34, Nicolas Pitre wrote:
>>>> I'm not suggesting to break anything or changing existing platforms,
>>>>> but how do we
