From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [Bug] IXP425 and e1000 network driver
Date: Tue, 28 Apr 2009 00:05:33 +0200 [thread overview]
Message-ID: <20090427220533.ACAD483420E8@gemini.denx.de> (raw)
In-Reply-To: <49D68311.4090807@gmail.com>
Dear Ben,
In message <49D68311.4090807@gmail.com> you wrote:
> Wolfgang Denk wrote:
> > Dear Ben,
> >
> > In message <gijdmd$vhk$1@ger.gmane.org> Stefan Althoefer wrote:
> >
> >> Hi,
> >>
> >> I found that IXP425 (big endian ARM) did not work with e1000 network
> >> driver. The reason is broken access to controller registers.
> >>
> >> I get it working with this patch:
> >>
> >> --------
> >> --- a/drivers/net/e1000.c
> >> +++ b/drivers/net/e1000.c
> >> @@ -105,12 +105,15 @@ static void e1000_phy_hw_reset(struct e1000_hw *hw);
> >> static int e1000_phy_reset(struct e1000_hw *hw);
> >> static int e1000_detect_gig_phy(struct e1000_hw *hw);
> >>
> >> -#define E1000_WRITE_REG(a, reg, value) (writel((value), ((a)->hw_addr + E1000_##reg)))
> >> -#define E1000_READ_REG(a, reg) (readl((a)->hw_addr + E1000_##reg))
> >> -#define E1000_WRITE_REG_ARRAY(a, reg, offset, value) (\
> >> - writel((value), ((a)->hw_addr + E1000_##reg + ((offset) << 2))))
> >> -#define E1000_READ_REG_ARRAY(a, reg, offset) ( \
> >> - readl((a)->hw_addr + E1000_##reg + ((offset) << 2)))
> >> +#define E1000_WRITE_REG(a, reg, value) \
> >> + (writel(cpu_to_le32(value), ((a)->hw_addr + E1000_##reg)))
> >> +#define E1000_READ_REG(a, reg) \
> >> + (le32_to_cpu(readl((a)->hw_addr + E1000_##reg)))
> >> +#define E1000_WRITE_REG_ARRAY(a, reg, offset, value) \
> >> + (writel(cpu_to_le32(value),\
> >> + ((a)->hw_addr + E1000_##reg + ((offset) << 2))))
> >> +#define E1000_READ_REG_ARRAY(a, reg, offset) \
> >> + (le32_to_cpu(readl((a)->hw_addr + E1000_##reg + ((offset) << 2))))
> >> #define E1000_WRITE_FLUSH(a) {uint32_t x; x = E1000_READ_REG(a, STATUS);}
> >>
> >> #ifndef CONFIG_AP1000 /* remove for warnings */
> >> ---------
> >>
> >> However, I'm not sure it this is the correct fix.
> >>
> >> Is readl supposed to read raw data?
> >>
> >> Is le32_to_cpu/cpu_to_le32 a function or a macro? In the later case the
> >> code is not save or slow due to multiple argument expansion.
> >>
> >> -- Stefan
> >>
> >
> > I have never seen any comments on this. Could you please have a look
> > at it?
> >
> > Best regards,
> >
> > Wolfgang Denk
> >
> >
> Sure thing.
And what was the result of you having a look at thispatch?
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
In the beginning there was nothing.
And the Lord said "Let There Be Light!"
And still there was nothing, but at least now you could see it.
next prev parent reply other threads:[~2009-04-27 22:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-20 18:31 [U-Boot] [Bug] IXP425 and e1000 network driver Stefan Althoefer
2009-04-03 21:18 ` Wolfgang Denk
2009-04-03 21:43 ` Ben Warren
2009-04-27 22:05 ` Wolfgang Denk [this message]
2009-08-05 20:26 ` Wolfgang Denk
2009-08-10 5:50 ` Ben Warren
2009-08-10 7:44 ` Wolfgang Denk
2009-05-02 11:56 ` Jean-Christophe PLAGNIOL-VILLARD
2009-05-03 2:56 ` Ben Warren
2009-06-03 21:36 ` Wolfgang Denk
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=20090427220533.ACAD483420E8@gemini.denx.de \
--to=wd@denx.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