netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Halasa <khc@pm.waw.pl>
To: Hendrik Sattler <post@hendrik-sattler.de>
Cc: netdev@vger.kernel.org
Subject: Re: IXP4xx networking and phylib
Date: Mon, 12 Jan 2009 18:36:44 +0100	[thread overview]
Message-ID: <m3wsd0a0k3.fsf@maximus.localdomain> (raw)
In-Reply-To: <200901121705.07966.post@hendrik-sattler.de> (Hendrik Sattler's message of "Mon\, 12 Jan 2009 17\:05\:07 +0100")

Hi,

Added CC: netdev.

Hendrik Sattler <post@hendrik-sattler.de> writes:

> My IXP465 MII port is connected to a Marvell switch (port 5). This port 
> is "always on" and has no PHY registers. It is configured in hardware. The 
> switch ports 1-4 have phy registers but that's not the matter.
> The problem is that there is no standard way in the platform info to tell the 
> driver (now phylib) that there are _no_ PHY registers.
>
> Is there a standard way to say: enable the ethernet interface and be done with 
> it?
> I currently do this by patching the driver. The PHYLIB patch makes that even 
> easier but it would be better to not need patching at all (at least one 
> driver less to patch).
>
> Maybe something like:
>   if (phyid < 0)
>      /* only enable the interface but there are no PHY registers */
-- 
Krzysztof Halasa

       reply	other threads:[~2009-01-12 17:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200901121705.07966.post@hendrik-sattler.de>
2009-01-12 17:36 ` Krzysztof Halasa [this message]
2009-02-04 23:15   ` IXP4xx networking and phylib Andy Fleming
2009-02-05  9:11     ` Hendrik Sattler

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=m3wsd0a0k3.fsf@maximus.localdomain \
    --to=khc@pm.waw.pl \
    --cc=netdev@vger.kernel.org \
    --cc=post@hendrik-sattler.de \
    /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).