public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Michal Simek <monstr@monstr.eu>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3 1/3] dts: re-write dts/Makefile more simply with Kbuild
Date: Mon, 02 Jun 2014 08:18:06 +0200	[thread overview]
Message-ID: <538C171E.7020702@monstr.eu> (raw)
In-Reply-To: <CAPnjgZ3BcR3BeSqQfJPf47g9218w7GWMSw4PcAYA6eejXVD36w@mail.gmail.com>

On 06/01/2014 06:34 PM, Simon Glass wrote:
> Hi,
> 
> On 27 May 2014 18:54, Masahiro Yamada <yamada.m@jp.panasonic.com> wrote:
>> Hi York,
>>
>>>> diff --git a/arch/arm/lib/board.c b/arch/arm/lib/board.c
>>>> index b770e25..38b9c7d 100644
>>>> --- a/arch/arm/lib/board.c
>>>> +++ b/arch/arm/lib/board.c
>>>> @@ -280,7 +280,7 @@ void board_init_f(ulong bootflag)
>>>>     gd->mon_len = _bss_end_ofs;
>>>>  #ifdef CONFIG_OF_EMBED
>>>>     /* Get a pointer to the FDT */
>>>> -   gd->fdt_blob = _binary_dt_dtb_start;
>>>> +   gd->fdt_blob = __dtb_db_begin;
>>>
>>> Is this a typo? I believe it should be __dtb_dt_begin. Did anyone see the
>>> compiling error?
>>
>>
>> Yes, it's a typo.
>> I had already posted a patch.
>> http://patchwork.ozlabs.org/patch/342815/
>>
>> Even such a simple one has been waiting for more than one month
>> in Patchwork queue.
>> :-(
>>
>> For now, CONFIG_OF_EMBED is defined for MicroBlaze.
>> I guess nobody saw the compile error.
> 
> I suspect all boards that use CONFIG_OF_CONTROL also use generic board
> now. I expect that this file will be deleted at the end of the year.

No. Microblaze has no generic board support yet.
For zynq I have sent patches out but they will be merged in the next
merge window.

Thanks,
Michal

-- 
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Microblaze cpu - http://www.monstr.eu/fdt/
Maintainer of Linux kernel - Xilinx Zynq ARM architecture
Microblaze U-BOOT custodian and responsible for u-boot arm zynq platform


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 263 bytes
Desc: OpenPGP digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20140602/b25c01bd/attachment.pgp>

  reply	other threads:[~2014-06-02  6:18 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-05  2:28 [U-Boot] [PATCH v3 0/3] Simplify dts/Makefile and support multiple DTBs generation Masahiro Yamada
2014-02-05  2:28 ` [U-Boot] [PATCH v3 1/3] dts: re-write dts/Makefile more simply with Kbuild Masahiro Yamada
2014-02-15 23:41   ` Simon Glass
2014-02-19 21:11   ` [U-Boot] [U-Boot, v3, " Tom Rini
2014-02-20  9:30     ` Masahiro Yamada
2014-02-20 13:39       ` Tom Rini
2014-05-27 18:32   ` [U-Boot] [PATCH v3 " York Sun
2014-05-28  0:54     ` Masahiro Yamada
2014-06-01 16:34       ` Simon Glass
2014-06-02  6:18         ` Michal Simek [this message]
2014-02-05  2:28 ` [U-Boot] [PATCH v3 2/3] dts: move device tree sources to arch/$(ARCH)/dts/ Masahiro Yamada
2014-02-19 21:11   ` [U-Boot] [U-Boot, v3, " Tom Rini
2014-02-20  9:22     ` Masahiro Yamada
2014-02-20 13:43       ` Tom Rini
2014-02-05  2:28 ` [U-Boot] [PATCH v3 3/3] dts: generate multiple device tree blobs Masahiro Yamada
2014-02-15 23:41   ` Simon Glass
2014-02-19 21:11   ` [U-Boot] [U-Boot, v3, " Tom Rini

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=538C171E.7020702@monstr.eu \
    --to=monstr@monstr.eu \
    --cc=u-boot@lists.denx.de \
    /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