On Thu, 17 Feb 2022 at 21:39, Stafford Horne wrote:
>
> On Thu, Feb 17, 2022 at 06:18:58PM +, Peter Maydell wrote:
> > If the user doesn't specify a kernel file, we'll still load the FDT,
> > at address zero. Is that sensible/intended behaviour ?
>
> Good point, I guess we can add some space
On Thu, Feb 17, 2022 at 06:18:58PM +, Peter Maydell wrote:
> On Thu, 10 Feb 2022 at 06:46, Stafford Horne wrote:
> >
> > Using the device tree means that qemu can now directly tell
> > the kernel what hardware is configured rather than use having
> > to maintain and update a separate device tr
On Thu, 10 Feb 2022 at 06:46, Stafford Horne wrote:
>
> Using the device tree means that qemu can now directly tell
> the kernel what hardware is configured rather than use having
> to maintain and update a separate device tree file.
>
> This patch adds device tree support for the OpenRISC simulat
On Thu, Feb 10, 2022 at 12:10:54PM +0100, Philippe Mathieu-Daudé wrote:
> Typo "device" in subject.
OK.
> On 10/2/22 07:30, Stafford Horne wrote:
> > Using the device tree means that qemu can now directly tell
> > the kernel what hardware is configured rather than use having
> > to maintain and u
Typo "device" in subject.
On 10/2/22 07:30, Stafford Horne wrote:
Using the device tree means that qemu can now directly tell
the kernel what hardware is configured rather than use having
to maintain and update a separate device tree file.
This patch adds device tree support for the OpenRISC si
Using the device tree means that qemu can now directly tell
the kernel what hardware is configured rather than use having
to maintain and update a separate device tree file.
This patch adds device tree support for the OpenRISC simulator.
A device tree is built up based on the state of the configur
