netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: akpm@osdl.org
Cc: netdev@vger.kernel.org, broonie@sirena.org.uk, jgarzik@pobox.com,
	thockin@hockin.org
Subject: Re: [patch 3/9] natsemi: Add support for using MII port with no PHY
Date: Thu, 27 Apr 2006 05:54:58 -0400	[thread overview]
Message-ID: <445094F2.1060807@garzik.org> (raw)
In-Reply-To: <200604270932.k3R9W5lK025315@shell0.pdx.osdl.net>

akpm@osdl.org wrote:
> From: Mark Brown <broonie@sirena.org.uk>
> 
> Provide a module option which configures the natsemi driver to use the
> external MII port on the chip but ignore any PHYs that may be attached to it. 
> The link state will be left as it was when the driver started and can be
> configured via ethtool.  Any PHYs that are present can be accessed via the MII
> ioctl()s.
> 
> This is useful for systems where the device is connected without a PHY or
> where either information or actions outside the scope of the driver are
> required in order to use the PHYs.
> 
> Signed-off-by: Mark Brown <broonie@sirena.org.uk>
> Cc: Tim Hockin <thockin@hockin.org>
> Cc: Jeff Garzik <jgarzik@pobox.com>
> Signed-off-by: Andrew Morton <akpm@osdl.org>

NAK.

The proper way to do this is via the force_media boolean flag found in 
several net drivers.

In general I agree with the motivation to do something like this...

	Jeff




  reply	other threads:[~2006-04-27  9:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-27  9:30 [patch 3/9] natsemi: Add support for using MII port with no PHY akpm
2006-04-27  9:54 ` Jeff Garzik [this message]
2006-04-28 13:01   ` Mark Brown
2006-05-03 11:07     ` Jeff Garzik

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=445094F2.1060807@garzik.org \
    --to=jeff@garzik.org \
    --cc=akpm@osdl.org \
    --cc=broonie@sirena.org.uk \
    --cc=jgarzik@pobox.com \
    --cc=netdev@vger.kernel.org \
    --cc=thockin@hockin.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).