All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC] i2c_reloc_fixup fails on m68k
Date: Mon, 14 Oct 2013 13:40:55 -0400	[thread overview]
Message-ID: <201310141340.58171.vapier@gentoo.org> (raw)
In-Reply-To: <52413253.4020603@denx.de>

On Tuesday 24 September 2013 02:33:55 Heiko Schocher wrote:
> Am 23.09.2013 15:50, schrieb Jens Scharsig:
> > Hello,
> > 
> > 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?
> 
> > 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 ...

Blackfin doesn't do self-relocation like that, so we don't care :)
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20131014/dbe9d9a2/attachment.pgp>

      parent reply	other threads:[~2013-10-14 17:40 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
2013-10-14 17:40   ` Mike Frysinger [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=201310141340.58171.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.