From: Dale Farnsworth <dale@farnsworth.org>
To: Lennert Buytenhek <buytenh@wantstofly.org>
Cc: netdev@vger.kernel.org, Nicolas Pitre <nico@cam.org>
Subject: Re: [PATCH 5/5] mv643xx_eth: inter-mv643xx SMI port sharing
Date: Mon, 28 Apr 2008 11:24:50 -0700 [thread overview]
Message-ID: <20080428182450.GF2691@farnsworth.org> (raw)
In-Reply-To: <20080423232959.GG17159@xi.wantstofly.org>
On Thu, Apr 24, 2008 at 01:29:59AM +0200, Lennert Buytenhek wrote:
> There exist chips with up to four mv643xx_eth silicon blocks but
> only one external SMI (MII management) interface -- the SMI logic
> of the first block is shared by all the blocks.
>
> Handle this by allowing a per-port override of which
> mv643xx_eth_shared's SMI registers (and spinlock) to use.
>
> Signed-off-by: Lennert Buytenhek <buytenh@marvell.com>
> Acked-by: Nicolas Pitre <nico@marvell.com>
Acked-by: Dale Farnsworth <dale@farnsworth.org>
prev parent reply other threads:[~2008-04-28 18:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-23 23:29 [PATCH 5/5] mv643xx_eth: inter-mv643xx SMI port sharing Lennert Buytenhek
2008-04-28 18:24 ` Dale Farnsworth [this message]
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=20080428182450.GF2691@farnsworth.org \
--to=dale@farnsworth.org \
--cc=buytenh@wantstofly.org \
--cc=netdev@vger.kernel.org \
--cc=nico@cam.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).