From: Michal Simek <michal.simek@xilinx.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 3/3] dm: sf: Add support for all targets which requires MANUAL_RELOC
Date: Fri, 6 Nov 2015 10:01:21 +0100 [thread overview]
Message-ID: <563C6C61.6020707@xilinx.com> (raw)
In-Reply-To: <CAPnjgZ085TC+OKmHthajWdoUeK_YKmpu8rC4=_7cuvjq71ukvw@mail.gmail.com>
On 11/06/2015 04:15 AM, Simon Glass wrote:
> On 30 October 2015 at 08:56, Michal Simek <michal.simek@xilinx.com> wrote:
>> It is follow up patch based on
>> "dm: Add support for all targets which requires MANUAL_RELOC"
>> (sha1: 484fdf5ba058b07be5ca82763aa2b72063540ef3)
>> to update function pointers for DM.
>>
>> Using post_bind is not ideal but it is one on current option what can be
>> used. Variable reloc_done has to be used do not call relocation after
>> every bind. Maybe new core functions should be introduced for this case.
>>
>> Signed-off-by: Michal Simek <michal.simek@xilinx.com>
>> ---
>>
>> Changes in v2:
>> - Add checking for MANUAL_RELOC code only
>>
>> drivers/mtd/spi/sf-uclass.c | 23 +++++++++++++++++++++++
>> 1 file changed, 23 insertions(+)
>
> The ugly continues...
>
> Reviewed-by: Simon Glass <sjg@chromium.org>
:-) When I have time I will look at changing microblaze not to use it.
But on the other hand Microblaze is not only one arch which uses this.
But probably only one arch which is using DM.
Thanks,
Michal
prev parent reply other threads:[~2015-11-06 9:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-30 14:56 [U-Boot] [PATCH v2 1/3] dm: spi: Add support for all targets which requires MANUAL_RELOC Michal Simek
2015-10-30 14:56 ` [U-Boot] [PATCH v2 2/3] dm: core: Add missing entries for manual relocation Michal Simek
2015-10-30 14:56 ` [U-Boot] [PATCH v2 3/3] dm: sf: Add support for all targets which requires MANUAL_RELOC Michal Simek
2015-11-06 3:15 ` Simon Glass
2015-11-06 9:01 ` Michal Simek [this message]
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=563C6C61.6020707@xilinx.com \
--to=michal.simek@xilinx.com \
--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