From mboxrd@z Thu Jan 1 00:00:00 1970 From: Julien Grall Subject: Re: [PATCH ARM v5 18/20] mini-os: import libfdt Date: Sat, 28 Jun 2014 16:14:35 +0100 Message-ID: <53AEDBDB.1080301@linaro.org> References: <1403782117-15125-1-git-send-email-talex5@gmail.com> <1403782117-15125-19-git-send-email-talex5@gmail.com> <53AEAEAF.3010805@linaro.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1X0uKs-0006uF-Ss for xen-devel@lists.xenproject.org; Sat, 28 Jun 2014 15:14:38 +0000 Received: by mail-we0-f171.google.com with SMTP id q58so6475494wes.30 for ; Sat, 28 Jun 2014 08:14:37 -0700 (PDT) In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Thomas Leonard Cc: xen-devel@lists.xenproject.org, Stefano Stabellini , David Scott , Samuel Thibault , Anil Madhavapeddy List-Id: xen-devel@lists.xenproject.org On 28/06/14 13:27, Thomas Leonard wrote: > On 28 June 2014 13:01, Julien Grall wrote: >> Hi Thomas, >> >> >> On 26/06/14 12:28, Thomas Leonard wrote: >>> >>> From: Karim Raslan >>> >>> Looks like this is revision v1.3.0-47-gbe60268 from >>> http://git.jdl.com/gitweb/?p=dtc.git >> >> >> Unfortunately I can find this commit in the git tree. Do you have the full >> sha1? > > It works for me: Hmmm right, sorry for the noise. Even though, you shell command below show a tag but a commit ;). > $ git clone git://git.jdl.com/software/dtc.git > $ cd dtc > $ git show be60268 > commit be6026838e45b67800ac803f4ad8cca3cde57d6d > Author: David Gibson > Date: Fri Jun 1 14:12:38 2012 +1000 > > libfdt: Add helper function to create a trivial, empty tree > >> AFAIU, you are using the version 1.3.0, right? If so, why didn't you get the >> latest version (i.e 1.4.0)? > > I don't know why this particular version was chosen. I could upgrade > it if you want. I don't think there are any functional changes > (uint32_t has been replaced by fdt32_t all over the place, and there > are a couple of extra functions, which we don't need). Just looking to the libfdt already embedded in xen (xen/common/libfdt) and it looks like we are using the same version. I'm wondering if you could share the same code and avoid to have the libfdt imported twice in Xen. Any thoughts? Regards, -- Julien Grall