On 02/27/2012 11:38 AM, Peter Maydell wrote:
From: Grant Likely
If compiled with CONFIG_FDT, allow user to specify a device tree file using
the -dtb argument. If the machine supports it then the dtb will be loaded
into memory and passed to the kernel on boot.
Signed-off-by: Jeremy Kerr
Signed-
From: Grant Likely
If compiled with CONFIG_FDT, allow user to specify a device tree file using
the -dtb argument. If the machine supports it then the dtb will be loaded
into memory and passed to the kernel on boot.
Signed-off-by: Jeremy Kerr
Signed-off-by: Grant Likely
[Peter Maydell: Use mac
From: Grant Likely
If compiled with CONFIG_FDT, allow user to specify a device tree file using
the -dtb argument. If the machine supports it then the dtb will be loaded
into memory and passed to the kernel on boot.
Signed-off-by: Jeremy Kerr
Signed-off-by: Grant Likely
[Peter Maydell: Use mac
On Mon, Jan 30, 2012 at 09:54:45AM +1000, Peter Crosthwaite wrote:
> On Mon, Jan 30, 2012 at 6:42 AM, Edgar E. Iglesias > On Sat, Jan 28, 2012 at 11:48:37AM -0700, Grant Likely wrote:
> > > On Fri, Jan 27, 2012 at 10:34:01PM +, Paul Brook wrote:
> Another major issue with that is DTBs have lit
On Sun, Jan 29, 2012 at 09:29:58PM +, Peter Maydell wrote:
> On 29 January 2012 18:48, Andreas Färber wrote:
> > Am 29.01.2012 17:01, schrieb Grant Likely:
> >> Okay, well at least let's start with this. Here is an updated version of
> >> the
> >> patch that doesn't touch the board code. It
On Mon, Jan 30, 2012 at 12:36:40PM +0100, Andreas Färber wrote:
> Am 29.01.2012 21:36, schrieb Grant Likely:
> > On Sun, Jan 29, 2012 at 07:13:55PM +, Peter Maydell wrote:
> >> On 29 January 2012 16:01, Grant Likely wrote:
> >>> +DEF("dtb", HAS_ARG, QEMU_OPTION_dtb, \
> >>> +"-dtb file use
Am 29.01.2012 21:36, schrieb Grant Likely:
> On Sun, Jan 29, 2012 at 07:13:55PM +, Peter Maydell wrote:
>> On 29 January 2012 16:01, Grant Likely wrote:
>>> +DEF("dtb", HAS_ARG, QEMU_OPTION_dtb, \
>>> +"-dtb file use 'file' as a device tree image\n", QEMU_ARCH_ARM)
>>
>> Needs more spaces
On Sun, Jan 29, 2012 at 07:13:55PM +, Peter Maydell wrote:
> On 29 January 2012 16:01, Grant Likely wrote:
> > diff --git a/configure b/configure
> > index f69e08f..0c2deab 100755
> > --- a/configure
> > +++ b/configure
> > @@ -3411,6 +3411,9 @@ case "$target_arch2" in
> > gdb_xml_files="a
On Mon, Jan 30, 2012 at 5:13 AM, Peter Maydell wrote:
> On 29 January 2012 16:01, Grant Likely wrote:
>> On Sun, Jan 29, 2012 at 11:15:42AM +, Paul Brook wrote:
>>> Clearly we need to have some sort of FDT support. However I'm unconvinced
>>> that it's the correct format for the primary data
On Mon, Jan 30, 2012 at 6:42 AM, Edgar E. Iglesias wrote:
> On Sat, Jan 28, 2012 at 11:48:37AM -0700, Grant Likely wrote:
> > On Fri, Jan 27, 2012 at 10:34:01PM +, Paul Brook wrote:
> > > > If compiled with CONFIG_FDT, allow user to specify a device tree
> file using
> > > > the -dtb argument
On 29 January 2012 18:48, Andreas Färber wrote:
> Am 29.01.2012 17:01, schrieb Grant Likely:
>> Okay, well at least let's start with this. Here is an updated version of the
>> patch that doesn't touch the board code. It makes the -dtb option available
>> to all ARM platforms.
>>
>> Even if dtb i
On Sat, Jan 28, 2012 at 11:48:37AM -0700, Grant Likely wrote:
> On Fri, Jan 27, 2012 at 10:34:01PM +, Paul Brook wrote:
> > > If compiled with CONFIG_FDT, allow user to specify a device tree file
> > > using
> > > the -dtb argument. If the machine supports it then the dtb will be loaded
> > >
On 29 January 2012 16:01, Grant Likely wrote:
> On Sun, Jan 29, 2012 at 11:15:42AM +, Paul Brook wrote:
>> Clearly we need to have some sort of FDT support. However I'm unconvinced
>> that it's the correct format for the primary data structure. For one thing
>> it's a hierarchical tree struc
Am 29.01.2012 17:01, schrieb Grant Likely:
> Okay, well at least let's start with this. Here is an updated version of the
> patch that doesn't touch the board code. It makes the -dtb option available
> to all ARM platforms.
>
> Even if dtb is not the primary structure, we absolutely need this op
On Sun, Jan 29, 2012 at 11:15:42AM +, Paul Brook wrote:
> Clearly we need to have some sort of FDT support. However I'm unconvinced
> that it's the correct format for the primary data structure. For one thing
> it's a hierarchical tree structure, and in my experience describing links
> out
> There is a lot of configuration in the .dts file that the QEMU user may
> want to manipulate; particularly when using QEMU for testing embedded
> platforms. The direction I want to go is to select the machine model based
> on the top level DT compatible property (making -M optional), and then
> a
Hi Grant,
The patch series for dts driven machine creation we (myself and Edgar) use
that you are referring to was rejected a few months ago on the grounds that
it conflicted with QOM:
http://lists.gnu.org/archive/html/qemu-devel/2011-08/msg02953.html
I am maintaining it our of tree, although I
On Fri, Jan 27, 2012 at 10:34:01PM +, Paul Brook wrote:
> > If compiled with CONFIG_FDT, allow user to specify a device tree file using
> > the -dtb argument. If the machine supports it then the dtb will be loaded
> > into memory and passed to the kernel on boot.
>
> Adding annother machine f
> If compiled with CONFIG_FDT, allow user to specify a device tree file using
> the -dtb argument. If the machine supports it then the dtb will be loaded
> into memory and passed to the kernel on boot.
Adding annother machine feels wrong. Why does the board specific code need to
know about this
If compiled with CONFIG_FDT, allow user to specify a device tree file using
the -dtb argument. If the machine supports it then the dtb will be loaded
into memory and passed to the kernel on boot.
This version of the patch only adds support to the arm versatile and versatile
express platforms. Ot
20 matches
Mail list logo
