public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Peter Tyser <ptyser@xes-inc.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC PATCH 2/3] net: add phylib implementation
Date: Thu, 27 Aug 2009 10:56:20 -0500	[thread overview]
Message-ID: <1251388580.885.1505.camel@localhost.localdomain> (raw)
In-Reply-To: <20090827153807.GA4581@b07421-ec1.am.freescale.net>

On Thu, 2009-08-27 at 10:38 -0500, Scott Wood wrote:
> On Thu, Aug 27, 2009 at 01:54:47AM -0400, Mike Frysinger wrote:
> > On Thursday 27 August 2009 01:11:32 Stefan Roese wrote:
> > > On Thursday 27 August 2009 03:55:57 Mike Frysinger wrote:
> > > > > +int phy_init(void)
> > > > > +{
> > > > > +	/* Initialize the list */
> > > > > +	INIT_LIST_HEAD(&phy_drvs.list);
> > > >
> > > > does it really need to be dynamic ?  arent there static initializers so
> > > > this can be done in .data ?
> > >
> > > Using static initializers fails on PPC because of the somewhat broken
> > > relocation. So this dynamic implementation is the preferred version, at
> > > least for PPC people.
> > 
> > so the ppc port cant use the .data section at all ?  that doesnt sound correct 
> > to me.
> 
> We can't have initialized pointers in .data without manual runtime fixup. 
> Only .text has relocation information.
> 
> Someone tried to get proper relocation working a while ago, but ran into
> toolchain bugs.  Maybe current toolchains are better...

X-ES's board's in U-Boot fully relocate to SDRAM with the
CONFIG_RELOC_FIXUP_WORKS define and -mrelocatable compiler flag.  This
feature has worked with gcc-4.3.1/binutils-2.18.90 and
gcc-4.2.2/binutils-2.17.50.

Does anyone have a specific example of a toolchain that doesn't work?
It'd be great to get the issue figured out and get rid of all those
gd->reloc_off references that currently litter the code...

Peter

  reply	other threads:[~2009-08-27 15:56 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-25  7:02 [U-Boot] Phy lib again Michal Simek
2009-08-25  7:08 ` Stefan Roese
2009-08-25  7:14   ` Michal Simek
2009-08-25 16:48     ` Ben Warren
2009-08-26  7:27       ` Michal Simek
2009-08-25  9:23   ` Jean-Christophe PLAGNIOL-VILLARD
2009-08-26 20:13 ` [U-Boot] [RFC PATCH 1/3] net: rework the mii support Jean-Christophe PLAGNIOL-VILLARD
2009-08-26 20:13   ` [U-Boot] [RFC PATCH 2/3] net: add phylib implementation Jean-Christophe PLAGNIOL-VILLARD
2009-08-26 20:13     ` [U-Boot] [RFC PATCH 3/3] phylib: add generic phy driver Jean-Christophe PLAGNIOL-VILLARD
2009-08-27  1:58       ` Mike Frysinger
2009-08-27  1:55     ` [U-Boot] [RFC PATCH 2/3] net: add phylib implementation Mike Frysinger
2009-08-27  5:11       ` Stefan Roese
2009-08-27  5:54         ` Mike Frysinger
2009-08-27 15:38           ` Scott Wood
2009-08-27 15:56             ` Peter Tyser [this message]
2009-08-27 17:49               ` [U-Boot] PowerPC -mrelocatable Scott Wood
2009-08-27 19:36                 ` Joakim Tjernlund
2009-09-08 16:16                 ` Peter Tyser
2009-09-08 17:29                   ` Mike Frysinger
2009-09-08 18:20                   ` Wolfgang Denk
2009-09-09  8:04                     ` Joakim Tjernlund
2009-09-11 22:52                     ` Peter Tyser
2009-08-27 19:13             ` [U-Boot] [RFC PATCH 2/3] net: add phylib implementation Mike Frysinger
2009-08-27 19:16               ` Scott Wood
2009-08-27  1:16   ` [U-Boot] [RFC PATCH 1/3] net: rework the mii support Mike Frysinger
2009-08-27 15:44   ` Ben Warren

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=1251388580.885.1505.camel@localhost.localdomain \
    --to=ptyser@xes-inc.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