From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni)
To: linux-arm-kernel@lists.infradead.org
Subject: SATA working on 370/XP, Ethernet next...
Date: Fri, 20 Jul 2012 17:52:37 +0200 [thread overview]
Message-ID: <20120720175237.6a10eb83@skate> (raw)
In-Reply-To: <20120720144133.GA15606@lunn.ch>
Le Fri, 20 Jul 2012 16:41:33 +0200,
Andrew Lunn <andrew@lunn.ch> a ?crit :
> I'm interested in Ethernet. I assume it uses
> drivers/net/ethernet/marvell/mv643xx_eth.c?
No, the network IP in the A370 and AXP is totally different and Marvell
engineers think it needs a new driver, and I have been making internal
reviews of their driver, but it needs more work before being ready for
submission.
A while ago, we had a discussion with Ben Dooks (from CodeThink) on
whether a new driver was needed or not. Ben will correct me if I'm
wrong, but he was suggesting that a new driver was not needed, but both
Marvell engineers and my comparison of the datasheets between A370/AXP
and older Marvell EBU SoCs clearly show that this IP has changed
dramatically, and is even not the same IP as before.
If needed, I can post the network driver code in a RFC state, but it is
clearly not yet ready for inclusion.
I would of course be happy to test SATA patches for the Armada XP. Ian,
did you reuse the plat-orion/addr-map.c code to do the window setup?
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-07-20 15:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-20 14:41 SATA working on 370/XP, Ethernet next Andrew Lunn
2012-07-20 15:35 ` Ian Molton
2012-07-20 15:52 ` Thomas Petazzoni [this message]
2012-07-20 16:05 ` Ian Molton
2012-07-20 16:12 ` Thomas Petazzoni
2012-07-20 16:25 ` Ian Molton
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=20120720175237.6a10eb83@skate \
--to=thomas.petazzoni@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).