public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2] net: ne2000: Divided a function of NE2000 driver
Date: Thu, 2 Oct 2008 16:45:15 +0200	[thread overview]
Message-ID: <20081002144515.GD15561@game.jcrosoft.org> (raw)
In-Reply-To: <48E4652F.7010005@gmail.com>

On 23:07 Wed 01 Oct     , Ben Warren wrote:
> Hi Nobuhiro-san,
> 
> Nobuhiro Iwamatsu wrote:
> > get_prom function was used __attriute__ , but it is not enable.
> > ax88796.o does not do link besides ne2000.o. When ld is carried
> > out, get_prom function of ax88796.c is ignored.
> > This problem is a thing by specifications of ld.
> > I checked and test this patch on SuperH and MIPS.
> >   
> You're seeing a common problem with weak functions - namely that they
> don't always get overridden. If there was a single function in ax88796.c
> that had strong static linkage there wouldn't be a problem. Using the
> weak attribute for get_prom() is an elegant solution that improves code
> re-use, so I'm wondering if there's a way it can be made to work.
> 
> If nobody has any suggestions over the next couple of days, I'll pull in
> this patch.
> 
> This get_prom() function was set as weak in commit
> 2ef7503a593c77a80c2a054011970227c4b62774, labeled " NE2000: Fix
> regresssion introduced by e710185aae90 on non AX88796" by
> Jean-Christophe PLAGNIOL-VILLARD. It's a shame that this was done
> without testing...
The NE2000 is tested every modification and Release on qemu_mips by myself

And I've no problem on this board.

Best Regards,
J.

  reply	other threads:[~2008-10-02 14:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-30  6:02 [U-Boot] [PATCH v2] net: ne2000: Divided a function of NE2000 driver Nobuhiro Iwamatsu
2008-10-02  6:07 ` Ben Warren
2008-10-02 14:45   ` Jean-Christophe PLAGNIOL-VILLARD [this message]
2008-10-02 16:45     ` Ben Warren
2008-10-03  4:39       ` Nobuhiro Iwamatsu
2008-10-03 14:14         ` 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=20081002144515.GD15561@game.jcrosoft.org \
    --to=plagnioj@jcrosoft.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