From: Vitaly Bordug <vitb@kernel.crashing.org>
To: cbou@mail.ru
Cc: linuxppc-dev@ozlabs.org, netdev@vger.kernel.org,
Jeff Garzik <jeff@garzik.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] [NET] phy/fixed.c: rework to not duplicate PHY layer functionality
Date: Sun, 2 Dec 2007 01:22:35 +0300 [thread overview]
Message-ID: <20071202012235.4ad9abc3@kernel.crashing.org> (raw)
In-Reply-To: <20071201213403.GA2350@zarina>
On Sun, 2 Dec 2007 00:34:03 +0300
Anton Vorontsov wrote:
> > If i understand your code correctly, you seem to rely on the fact
> > that fixed_phy_add() is called before the fixed MDIO bus is scanned
> > for devices.
>
> Yes, indeed. The other name of "fixed phys" are "platform phys"
> or "platform MDIO bus" on which virtual PHYs are placed.
>
> That is, these phys supposed to be created by the platform setup
> code (arch/). The rationale here is: we do hardware emulation, thus
> to make drivers actually see that "hardware", we have to create it
> early.
well that was the intention but... The point is - as device is emulated, (nearly) everything is doable,
and the only tradeoff to consider, is how far will we go with that emulation. IOW, PHYlib could be tricked
to "do the right thing", and I thought about adding module flexibility...
But thinking more about it, it seems that BSP-code-phy-creation just sucks less and is clear enough yet flexible.
--
Sincerely, Vitaly
next prev parent reply other threads:[~2007-12-01 22:22 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-26 14:29 [PATCH 1/3] [NET] phy/fixed.c: rework to not duplicate PHY layer functionality Vitaly Bordug
2007-11-26 14:29 ` [PATCH 2/3] [POWERPC] fsl_soc: add support for gianfar for fixed-link property Vitaly Bordug
2007-11-26 15:04 ` Joakim Tjernlund
2007-11-27 11:39 ` Anton Vorontsov
2007-11-27 13:17 ` Joakim Tjernlund
2007-11-27 13:59 ` Anton Vorontsov
2007-11-27 14:01 ` Joakim Tjernlund
2007-11-26 14:29 ` [PATCH 3/3] [POWERPC] MPC8349E-mITX: Vitesse 7385 PHY is not connected to the MDIO bus Vitaly Bordug
2007-12-01 13:48 ` [PATCH 1/3] [NET] phy/fixed.c: rework to not duplicate PHY layer functionality Jochen Friedrich
2007-12-01 19:07 ` Vitaly Bordug
2007-12-01 21:34 ` Anton Vorontsov
2007-12-01 22:22 ` Vitaly Bordug [this message]
2007-12-01 23:27 ` Stephen Rothwell
2007-12-02 11:54 ` [PATCH 1/3] [NET] phy/fixed.c: rework to not duplicate PHYlayer functionality Joakim Tjernlund
2007-12-02 12:13 ` Anton Vorontsov
2007-12-01 21:59 ` [PATCH 1/3] [NET] phy/fixed.c: rework to not duplicate PHY layer functionality Jeff Garzik
2007-12-01 22:16 ` Vitaly Bordug
2007-12-04 20:07 ` Jeff Garzik
2007-12-05 1:22 ` Vitaly Bordug
-- strict thread matches above, loose matches on Subject: below --
2007-12-06 22:51 Vitaly Bordug
2008-01-18 6:45 ` Kumar Gala
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=20071202012235.4ad9abc3@kernel.crashing.org \
--to=vitb@kernel.crashing.org \
--cc=cbou@mail.ru \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--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).