netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: RaghuramChary.Jallipalli@microchip.com
Cc: davem@davemloft.net, netdev@vger.kernel.org,
	UNGLinuxDriver@microchip.com, Woojung.Huh@microchip.com
Subject: Re: [PATCH net 3/3] lan78xx: Lan7801 Support for Fixed PHY
Date: Tue, 10 Apr 2018 04:49:43 +0200	[thread overview]
Message-ID: <20180410024943.GA11777@lunn.ch> (raw)
In-Reply-To: <0573C9D4B793EF43BF95221F2F4CC851533633@CHN-SV-EXMX06.mchp-main.com>

On Tue, Apr 10, 2018 at 02:23:23AM +0000, RaghuramChary.Jallipalli@microchip.com wrote:
> > 
> > What do you expect is connected to the MAC if there is no PHY?
> > 
> Hi Andrew,
> We connect the Ethernet switch to this MAC.

Ah, cool. I was thinking you were going to say an SFP cage.

What switch is it? Does it have a DSA driver?

     Andrew

  reply	other threads:[~2018-04-10  2:49 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-06  6:12 [PATCH net 0/3] lan78xx: Fixes and enhancements Raghuram Chary J
2018-04-06  6:12 ` [PATCH net 1/3] lan78xx: PHY DSP registers initialization to address EEE link drop issues with long cables Raghuram Chary J
2018-04-06 14:43   ` Andrew Lunn
2018-04-06 15:21     ` David Miller
2018-04-10  2:27       ` RaghuramChary.Jallipalli
2018-04-10 13:50   ` Sasha Levin
2018-04-06  6:12 ` [PATCH net 2/3] lan78xx: Add support to dump lan78xx registers Raghuram Chary J
2018-04-06 14:40   ` Andrew Lunn
2018-04-10  2:25     ` RaghuramChary.Jallipalli
2018-04-10 13:50   ` Sasha Levin
2018-04-06  6:12 ` [PATCH net 3/3] lan78xx: Lan7801 Support for Fixed PHY Raghuram Chary J
2018-04-06 14:35   ` Andrew Lunn
2018-04-10  2:23     ` RaghuramChary.Jallipalli
2018-04-10  2:49       ` Andrew Lunn [this message]
2018-04-10  4:02         ` RaghuramChary.Jallipalli
2018-04-10 13:50   ` Sasha Levin
2018-04-10 13:50 ` [PATCH net 0/3] lan78xx: Fixes and enhancements Sasha Levin

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=20180410024943.GA11777@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=RaghuramChary.Jallipalli@microchip.com \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=Woojung.Huh@microchip.com \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.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).