From: Jens Scharsig <esw@bus-elektronik.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC] i2c_reloc_fixup fails on m68k
Date: Mon, 14 Oct 2013 09:50:08 +0200 [thread overview]
Message-ID: <525BA230.7090801@bus-elektronik.de> (raw)
In-Reply-To: <525B8656.80703@denx.de>
Hello Heiko,
Am 2013-10-14 07:51, schrieb Heiko Schocher:
> Hello Jens,
>
> Am 24.09.2013 09:41, schrieb Jens Scharsig:
>> Hello Heiko,
>>> Hello Jens,
>>>> I have a access violation problem with i2c_reloc_fixup on coldfire
>>>> m68k systems.
>>>>
>>>> I found out, the i2c_reloc_fixup tries to relocate the adapter itself,
>>>> but at this time i2c_adap_p is already relocated.
>>>
>>> Which toolchain?
>>
>> m68k-elf-gcc (Sourcery CodeBench Lite 2011.09-21) 4.6.1
>> Copyright (C) 2011 Free Software Foundation, Inc.
>> This is free software; see the source for copying conditions. There is NO
>> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
>>
>>>
>>>> Can anybody confirm this?
>>>
>>> Added Mike Frysinger, Sonic Zhang (for blackfin) Jason Jin (for m68k)
>>> and Macpaul Lin (for nds32) to Cc ...
>>>
>>>> I think also m68k, backfin and nds32 systems are affected
>>>
>>> Sorry, I have no such system ... maybe you are the first who stepped
>>> in it ...
>>
>> I have only a m68k system, but only this tree arch's call i2c_reloc_fixup
>> in this way.
>
> Any news here?
No, silence anywhere
>
> @Jens: I want to add this patch in the new merge window, could you send
> a correct patch please, thanks!
I will do this soon.
Regards Jens
next prev parent reply other threads:[~2013-10-14 7:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-23 13:50 [U-Boot] [RFC] i2c_reloc_fixup fails on m68k Jens Scharsig
2013-09-24 6:33 ` Heiko Schocher
2013-09-24 7:41 ` Jens Scharsig
2013-10-14 5:51 ` Heiko Schocher
2013-10-14 7:50 ` Jens Scharsig [this message]
2013-10-14 17:40 ` Mike Frysinger
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=525BA230.7090801@bus-elektronik.de \
--to=esw@bus-elektronik.de \
--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