From: David Gibson <david@gibson.dropbear.id.au>
To: Peter Crosthwaite <peter.crosthwaite@xilinx.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
edgar.iglesias@gmail.com, qemu-devel@nongnu.org,
pbonzini@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2 1/1] configure: dtc: Probe for libfdt_env.h
Date: Fri, 31 May 2013 13:32:45 +1000 [thread overview]
Message-ID: <20130531033245.GB5408@boomeroo.fritz.box> (raw)
In-Reply-To: <CAEgOgz4L1RwRDHPjJk5YNA0vsnho+vt0XMEasC+JL2nv0S+6HQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3343 bytes --]
On Fri, May 31, 2013 at 11:48:47AM +1000, Peter Crosthwaite wrote:
> Hi David,
>
> On Wed, May 29, 2013 at 7:31 PM, David Gibson
> <david@gibson.dropbear.id.au> wrote:
> > On Wed, May 29, 2013 at 10:14:19AM +0100, Peter Maydell wrote:
> >> On 29 May 2013 09:18, David Gibson <david@gibson.dropbear.id.au> wrote:
> >> > On Mon, May 27, 2013 at 02:20:57PM +1000, peter.crosthwaite@xilinx.com wrote:
> >> >> From: Peter Crosthwaite <peter.crosthwaite@xilinx.com>
> >> >> Currently QEMU provides a local clone of the file libfdt_env.h in
> >> >> /include. This file is supposed to come with the libfdt package and is
> >> >
> >> > So, this patch might be the right thing anyway, but the statement
> >> > above is entirely false. libfdt_env.h is explicitly intended to be
> >> > supplied by the build environment embedding libfdt. The version
> >> > provided in the libfdt package is a example version which will do
> >> > (although it might not be ideal) for userspace builds with a
> >> > sufficiently normal C library.
> >>
> >> (You're upstream for libfdt, yes?)
> >
> > More or less, yes.
> >
> >> If you're expecting that build environments provide a libfdt_env.h
> >> then shouldn't you be avoiding making breaking changes to libfdt
> >> that require build environments to fix their libfdt_env.h?
> >> This came up in the first place because we no longer build with
> >> new libfdt...
> >
> > I missed that discussion, what exactly was the problem?
>
> In file included from /usr/local/include/libfdt.h:55,
> from
> /home/peterc/Petalogix/Internal/plgx_src/qemu-arm-microblazeel/device_tree.c:28:
> /usr/local/include/fdt.h:7: error: expected specifier-qualifier-list
> before ‘fdt32_t’
> /usr/local/include/fdt.h:26: error: expected specifier-qualifier-list
> before ‘fdt64_t’
> /usr/local/include/fdt.h:31: error: expected specifier-qualifier-list
> before ‘fdt32_t’
> /usr/local/include/fdt.h:36: error: expected specifier-qualifier-list
> before ‘fdt32_t’
>
> The type fdt32_t (and friends) is undefined.
>
> Heres the patch DTC side that introduces these types.
>
> commit feafcd972cb744750a65728440c99526e6199a6d
> Author: Kim Phillips <kim.phillips@freescale.com>
> Date: Wed Nov 28 17:33:01 2012 -0600
>
> dtc/libfdt: introduce fdt types for annotation by endian
> checkers
Ah, that one. Basically, we decided that the benefit gained was worth
the pain of the required change to libfdt_env.h
> > Then again, although we certainly
> > want to keep changes which require updates to libfdt_env.h rare, I'm
> > not going to rule out extensions to libfdt which add new (minor)
> > external dependencies, and therefore changes to libfdt_env.h.
> >
> > That said, I did put my correction a bit too strongly. While
> > libfdt_env.h is notionally always provided by the surrounding
> > environment, if the packaged one works for your environment, it's
> > probably a good idea to use it.
>
> I think we should be able to consider QEMU as normal enough to use
> prepacked DTC and just fix the commit message?
I concur.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2013-05-31 4:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-27 4:20 [Qemu-devel] [PATCH v2 1/1] configure: dtc: Probe for libfdt_env.h peter.crosthwaite
2013-05-29 8:18 ` David Gibson
2013-05-29 9:14 ` Peter Maydell
2013-05-29 9:31 ` David Gibson
2013-05-31 1:48 ` Peter Crosthwaite
2013-05-31 3:32 ` David Gibson [this message]
2013-05-31 8:25 ` Paolo Bonzini
2013-05-31 9:44 ` Peter Maydell
2013-05-31 9:54 ` Paolo Bonzini
2013-05-31 12:37 ` Peter Crosthwaite
2013-06-01 5:38 ` David Gibson
2013-06-01 23:13 ` Peter Crosthwaite
2013-06-07 2:54 ` Peter Crosthwaite
2013-06-07 8:32 ` Peter Maydell
2013-06-01 5:22 ` David Gibson
2013-06-01 8:26 ` Peter Maydell
2013-06-01 23:09 ` Peter Crosthwaite
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130531033245.GB5408@boomeroo.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=edgar.iglesias@gmail.com \
--cc=pbonzini@redhat.com \
--cc=peter.crosthwaite@xilinx.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).