From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jens Scharsig <esw@bus-elektronik.de>
Date: Mon, 14 Oct 2013 09:50:08 +0200
Subject: [U-Boot] [RFC] i2c_reloc_fixup fails on m68k
In-Reply-To: <525B8656.80703@denx.de>
References: <5240473A.2040208@bus-elektronik.de> <52413253.4020603@denx.de>
	<5241421E.5070400@bus-elektronik.de> <525B8656.80703@denx.de>
Message-ID: <525BA230.7090801@bus-elektronik.de>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.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