From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/2] net: add ICPlus PHY driver
Date: Thu, 29 Nov 2012 15:29:06 +0100 [thread overview]
Message-ID: <201211291529.07010.marex@denx.de> (raw)
In-Reply-To: <CAGm1_ktOvEiw7yD6G-hFc4zOEbWrKtzi8ARYfNxzNR_0tgsdfQ@mail.gmail.com>
Dear Yegor Yefremov,
> On Thu, Nov 29, 2012 at 1:55 PM, Marek Vasut <marex@denx.de> wrote:
> > Dear Yegor Yefremov,
> >
> >> On Thu, Nov 29, 2012 at 8:53 AM, Henrik Nordstr?m
> >>
> >> <henrik@henriknordstrom.net> wrote:
> >> > tor 2012-11-29 klockan 07:27 +0100 skrev Marek Vasut:
> >> >> Dear yegorslists at googlemail.com,
> >> >>
> >> >> > From: Yegor Yefremov <yegorslists@googlemail.com>
> >> >> >
> >> >> > The driver code was taken from Linux kernel source:
> >> >> > drivers/net/phy/icplus.c
> >> >> >
> >> >> > Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com>
> >> >>
> >> >> [...]
> >> >>
> >> >> Is there any user for this PHY please?
> >> >
> >> > I don't have one, but know at least one user having one in an A10
> >> > based "netbook".
> >> >
> >> > http://linux-sunxi.org/File:H6-netbook-mainboard.jpg
> >>
> >> I found these boards in kernel:
> >>
> >> arch/mips/configs/malta_defconfig:CONFIG_ICPLUS_PHY=m
> >> arch/mips/configs/bcm47xx_defconfig:CONFIG_ICPLUS_PHY=m
> >> arch/mips/configs/ip27_defconfig:CONFIG_ICPLUS_PHY=m
> >> arch/mips/configs/sead3_defconfig:CONFIG_ICPLUS_PHY=y
> >> arch/powerpc/configs/mpc512x_defconfig:CONFIG_ICPLUS_PHY=y
> >> arch/powerpc/configs/52xx/motionpro_defconfig:CONFIG_ICPLUS_PHY=y
> >> arch/powerpc/configs/83xx/mpc832x_rdb_defconfig:CONFIG_ICPLUS_PHY=y
> >> arch/powerpc/configs/mpc83xx_defconfig:CONFIG_ICPLUS_PHY=y
> >> arch/powerpc/configs/ppc6xx_defconfig:CONFIG_ICPLUS_PHY=m
> >
> > Sure, but the question/point is ... won't this be dead code in u-boot? It
> > won't once you add at least one board that actually uses it ... adding
> > it only so it's there will only cause it to bitrot and it'll actually
> > only add more burden to maintainers.
>
> It won't be dead code, because we will use it :-) Our board is
> derivative of BeagleBone & Co, so the whole support stuff is already
> in u-boot.
You need to enable it for that board though ;-)
> I can also image that some system didn't require network
> support in u-boot and didn't bother with implementing the phy driver.
> x86 systems are likely to have this phy too. And the driver is really
> small and uses mostly generic routines.
>
> Yegor
Best regards,
Marek Vasut
next prev parent reply other threads:[~2012-11-29 14:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-28 10:15 [U-Boot] [PATCH 1/2] phy: export genphy_parse_link() yegorslists at googlemail.com
2012-11-28 10:15 ` [U-Boot] [PATCH 2/2] net: add ICPlus PHY driver yegorslists at googlemail.com
2012-11-29 6:27 ` Marek Vasut
2012-11-29 7:32 ` Yegor Yefremov
2012-11-29 7:43 ` Marek Vasut
2012-11-29 7:53 ` Henrik Nordström
2012-11-29 8:07 ` Yegor Yefremov
2012-11-29 12:55 ` Marek Vasut
2012-11-29 13:13 ` Yegor Yefremov
2012-11-29 14:29 ` Marek Vasut [this message]
2012-11-29 14:40 ` Yegor Yefremov
2012-11-29 14:51 ` Marek Vasut
2012-11-29 14:59 ` Yegor Yefremov
2013-07-08 15:47 ` Joe Hershberger
2013-01-15 10:41 ` [U-Boot] [PATCH 1/2] phy: export genphy_parse_link() Yegor Yefremov
2013-07-08 15:45 ` Joe Hershberger
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=201211291529.07010.marex@denx.de \
--to=marex@denx.de \
--cc=u-boot@lists.denx.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