linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: maxime.ripard@free-electrons.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/3] ARM: sunxi: enable big-endian
Date: Fri, 29 Jul 2016 18:39:07 +0200	[thread overview]
Message-ID: <20160729163907.GD6215@lukather> (raw)
In-Reply-To: <20160729075923.GE415@weiser.dinsnail.net>

Hi,

On Fri, Jul 29, 2016 at 09:59:23AM +0200, Michael Weiser wrote:
> Hi ChenYu,
> 
> On Wed, Jul 27, 2016 at 09:55:11AM +0800, Chen-Yu Tsai wrote:
> > > As far as I gather, the Cubieboard2 does not route the EMAC pins anywhere.
> > > So I can't connect a PHY to it for testing.
> > The EMAC pins are muxed with the GMAC pins. All you need to do is disable
> > the GMAC, enable the EMAC, and use emac_pins_a for the pinctrl.
> 
> Okay, I've done that by copying the relevant dts sections from
> sun4i-a10-cubieboard.dts. It initialises and transmits packets fine. But
> it doesn't seem to accept incoming packets. I suspect that programming
> of its own MAC address (which the driver chooses randomly) suffers from
> an endianness issue. I'm somewhat stumped as to what is causing it since
> all accesses use {read,write}l. Interrupt handling is another possible
> culprit. I'm still digging.

Maybe a good way to confirm that would be to generate outgoing
traffic, dump that and see what the mac address is? If it's not
programmed properly, you should see it in the packets.

Maxime

-- 
Maxime Ripard, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20160729/ba256feb/attachment-0001.sig>

  reply	other threads:[~2016-07-29 16:39 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-21 18:23 [PATCH 0/3 v2] Fixes for running a big-endian kernel on Cubieboard2 Michael Weiser
2016-07-21 18:23 ` [PATCH 1/3] mmc: sunxi-mmc: change idma descriptor to __le32 Michael Weiser
2016-07-22  8:59   ` Maxime Ripard
2016-07-21 18:23 ` [PATCH 2/3] stmmac: change dma descriptors " Michael Weiser
2016-07-26 12:13   ` Giuseppe CAVALLARO
2016-07-29  7:53     ` Michael Weiser
2016-07-29  8:26       ` Giuseppe CAVALLARO
2016-07-21 18:23 ` [PATCH 3/3] ARM: sunxi: enable big-endian Michael Weiser
2016-07-22  9:01   ` Maxime Ripard
2016-07-22 13:56     ` Michael Weiser
2016-07-25 12:25       ` Maxime Ripard
2016-07-26 19:26         ` Michael Weiser
2016-07-27  1:55           ` Chen-Yu Tsai
2016-07-29  7:59             ` Michael Weiser
2016-07-29 16:39               ` Maxime Ripard [this message]
2016-07-29 18:55                 ` Michael Weiser
  -- strict thread matches above, loose matches on Subject: below --
2016-07-18 16:23 [PATCH 0/3] Fixes for running a big-endian kernel on Cubieboard2 Michael Weiser
2016-07-18 16:23 ` [PATCH 3/3] ARM: sunxi: enable big-endian Michael Weiser

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=20160729163907.GD6215@lukather \
    --to=maxime.ripard@free-electrons.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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;
as well as URLs for NNTP newsgroup(s).