Linux on ARM based TI OMAP SoCs
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@sunsite.dk>
To: Richard Cochran <richardcochran@gmail.com>
Cc: Mugunthan V N <mugunthanvnm@ti.com>,
	Ben Hutchings <bhutchings@solarflare.com>,
	netdev@vger.kernel.org, davem@davemloft.net,
	devicetree-discuss@lists.ozlabs.org, linux-omap@vger.kernel.org,
	b-cousson@ti.com, paul@pwsan.com
Subject: Re: [PATCH 1/3] driver: net: ethernet: cpsw: implement ethtool get/set phy setting
Date: Sat, 09 Mar 2013 11:49:24 +0100	[thread overview]
Message-ID: <87ehfo4zm3.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20130309065106.GA2588@netboy.at.omicron.at> (Richard Cochran's message of "Sat, 9 Mar 2013 07:51:06 +0100")

>>>>> "Richard" == Richard Cochran <richardcochran@gmail.com> writes:

Hi,

 >> As Peter Korsgaard mentioned we need to have infrastructure to
 >> handle CPSW kind of hardware.

 Richard> This will be a big job, I think, but I agree that it is worth doing.

 Richard> I can think of one other switch-with-host-port device. Maybe
 Richard> we should start off by making a list of actual products and
 Richard> their capabilities, in order to get an overall idea of what we
 Richard> would need to develop.

Next to the dsa stuff with external switches, I can think of 3 other
devices off the top of my head:

Freescale imx287:
http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=i.MX287

Freescale T1022:
http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=T1020

Ralink RT3502:
http://www.netcheif.com/Reviews/VigorFly200/PDF/RT3052-product%20brief.pdf

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2013-03-09 10:49 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-07 12:30 [PATCH 0/3] cpsw interrupt pacing and get/set phy setting implementation Mugunthan V N
2013-03-07 12:30 ` [PATCH 1/3] driver: net: ethernet: cpsw: implement ethtool get/set phy setting Mugunthan V N
2013-03-07 13:24   ` Peter Korsgaard
     [not found]     ` <8762135on4.fsf-D6SC8u56vOOJDPpyT6T3/w@public.gmane.org>
2013-03-07 17:13       ` Mugunthan V N
2013-03-07 18:49         ` Peter Korsgaard
2013-03-07 19:59     ` Ben Hutchings
2013-03-08  7:23       ` Mugunthan V N
2013-03-08 14:53         ` Ben Hutchings
2013-03-08 15:04           ` Peter Korsgaard
     [not found]             ` <87ip523pc3.fsf-D6SC8u56vOOJDPpyT6T3/w@public.gmane.org>
2013-03-08 15:08               ` Mugunthan V N
     [not found]           ` <1362754401.3248.8.camel-/LGg1Z1CJKReKY3V0RtoKmatzQS1i7+A3tAM5lWOD0I@public.gmane.org>
2013-03-08 15:07             ` Mugunthan V N
     [not found]               ` <5139FE94.6090004-l0cyMroinI0@public.gmane.org>
2013-03-09  6:51                 ` Richard Cochran
2013-03-09 10:49                   ` Peter Korsgaard [this message]
     [not found] ` <1362659421-11884-1-git-send-email-mugunthanvnm-l0cyMroinI0@public.gmane.org>
2013-03-07 12:30   ` [PATCH 2/3] arm: dts: am33xx: add default ethtool slave to cpsw node Mugunthan V N
2013-03-07 16:13     ` Tony Lindgren
2013-03-07 17:13       ` Mugunthan V N
2013-03-07 12:30   ` [PATCH 3/3] driver: net: ethernet: cpsw: implement interrupt pacing via ethtool Mugunthan V N

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=87ehfo4zm3.fsf@dell.be.48ers.dk \
    --to=jacmet@sunsite.dk \
    --cc=b-cousson@ti.com \
    --cc=bhutchings@solarflare.com \
    --cc=davem@davemloft.net \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=mugunthanvnm@ti.com \
    --cc=netdev@vger.kernel.org \
    --cc=paul@pwsan.com \
    --cc=richardcochran@gmail.com \
    /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