netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ondrej Zary <linux@rainbow-software.org>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	romieu@fr.zoreil.com
Subject: Re: [RFC, RFT PATCH 1/2] dl2k: Add support for IP1000A-based cards
Date: Fri, 4 Sep 2015 20:11:24 +0200	[thread overview]
Message-ID: <201509042011.25311.linux@rainbow-software.org> (raw)
In-Reply-To: <201508252326.13784.linux@rainbow-software.org>

On Tuesday 25 August 2015 23:26:13 Ondrej Zary wrote:
> On Tuesday 25 August 2015 23:04:30 David Miller wrote:
> > From: Ondrej Zary <linux@rainbow-software.org>
> > Date: Sun, 23 Aug 2015 23:06:27 +0200
> >
> > > Add support for IP1000A chips to dl2k driver.
> > > IP1000A chip looks like a TC9020 with integrated PHY.
> > >
> > > Tested with Asus NX1101.
> >
> > You're saying the PHY support is incomplete, so gigabit isn't even
> > detected for these chips.
> >
> > So in a way this is a regression of sorts.
> >
> > Come back with these proposed changes once you have the PHY support
> > situation sorted out.
> >
> > Thanks.
>
> Actually, gigabit works with this patch. The "PHY magic" part contains
> mii_write(9, 0x0700) which makes gigabit work.
>
> BTW. D-Link DGE-550T is on the way so I'll test that too.

Just got the DGE-550T (vendor 0x1186, device 0x4000) and it works with the 
modified driver.

-- 
Ondrej Zary

      parent reply	other threads:[~2015-09-04 18:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-23 21:06 [RFC, RFT PATCH 1/2] dl2k: Add support for IP1000A-based cards Ondrej Zary
2015-08-23 21:06 ` [RFC, RFT PATCH 2/2] ipg: Remove ipg driver Ondrej Zary
2015-08-25 21:04 ` [RFC, RFT PATCH 1/2] dl2k: Add support for IP1000A-based cards David Miller
2015-08-25 21:26   ` Ondrej Zary
2015-08-25 23:08     ` Francois Romieu
2015-09-04 18:11     ` Ondrej Zary [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=201509042011.25311.linux@rainbow-software.org \
    --to=linux@rainbow-software.org \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=romieu@fr.zoreil.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;
as well as URLs for NNTP newsgroup(s).