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 3/4 v2] arm: Support new Xilinx Zynq platform
Date: Thu, 13 Sep 2012 13:24:31 +0200	[thread overview]
Message-ID: <5051C26F.8030602@monstr.eu> (raw)
In-Reply-To: <201209131231.08843.marex@denx.de>

On 09/13/2012 12:31 PM, Marek Vasut wrote:
> Dear Michal Simek,
>
>> On 09/13/2012 11:31 AM, Marek Vasut wrote:
>>> Dear Michal Simek,
>>>
>>> [...]
>>>
>>>> +#include <config.h>
>>>> +#include <linux/linkage.h>
>>>> +
>>>> +ENTRY(lowlevel_init)
>>>> +        mov     pc, lr
>>>> +ENDPROC(lowlevel_init)
>>>
>>> inline void lowlevel_init(void) {} works as well and you don't need the
>>> assembly file.
>> :
>> :-) yes. The reason why I have done it in this way that we have some asm
>> :code
>>
>> which will go to this area. That's why I have kept it in asm instead of C.
>
> What code? Will the code go into lowlevel_init() ?

For example SLCR locking if is not locked from the first stage bootloader.
Also if necessary OCM and DDR remap, FPGA reset can be also there
based on configuration.

Thanks,
Michal


-- 
Michal Simek, Ing. (M.Eng)
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel 2.6 Microblaze Linux - http://www.monstr.eu/fdt/
Microblaze U-BOOT custodian

  reply	other threads:[~2012-09-13 11:24 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-16  6:30 [U-Boot] [PATCH 1/4 v2] serial: Add Zynq serial driver Michal Simek
2012-08-16  6:30 ` [U-Boot] [PATCH 2/4 v2] net: Add driver for Zynq Gem IP Michal Simek
2012-09-12 10:19   ` Michal Simek
2012-09-13  9:28   ` Marek Vasut
2012-09-13 10:16     ` Michal Simek
2012-09-13 12:30       ` Marek Vasut
2012-09-14  3:49     ` Joe Hershberger
2012-09-14  4:45       ` Marek Vasut
     [not found]         ` <CANr=Z=aejhXoGabpcderroSeQSWJM+cbXS7yg6NVeHKJLqQhRQ@mail.gmail.com>
2012-09-14  7:34           ` Marek Vasut
2012-08-16  6:30 ` [U-Boot] [PATCH 3/4 v2] arm: Support new Xilinx Zynq platform Michal Simek
2012-09-12 10:23   ` Michal Simek
2012-09-13  9:32     ` Marek Vasut
2012-09-13  9:36       ` Michal Simek
2012-09-13  9:31   ` Marek Vasut
2012-09-13  9:52     ` Michal Simek
2012-09-13 10:31       ` Marek Vasut
2012-09-13 11:24         ` Michal Simek [this message]
2012-09-13 12:32           ` Marek Vasut
2012-09-13 12:52             ` Michal Simek
2012-09-13 13:01               ` Marek Vasut
2012-08-16  6:30 ` [U-Boot] [PATCH 4/4 v3] xilinx: Add new Zynq board Michal Simek
2012-09-12 10:23   ` Michal Simek
2012-09-13  9:35   ` Marek Vasut
2012-09-13  9:55     ` Michal Simek
2012-09-13 12:31       ` Marek Vasut
2012-09-13 12:17     ` Michal Simek
2012-09-14  4:03   ` Joe Hershberger
2012-09-14  5:42     ` Michal Simek
2012-09-12 10:20 ` [U-Boot] [PATCH 1/4 v2] serial: Add Zynq serial driver Michal Simek
2012-09-13  9:21 ` Marek Vasut
2012-09-13  9:45   ` Michal Simek
2012-09-13 12:33     ` Marek Vasut
2012-09-13 13:54       ` Michal Simek
2012-09-13 14:01         ` Marek Vasut
2012-09-14  4:09           ` Joe Hershberger
2012-09-14  4:47             ` Marek Vasut
2012-09-14  5:23               ` Joe Hershberger
2012-09-14  7:39                 ` Marek Vasut

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=5051C26F.8030602@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