From: Pavel Machek <pavel@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] arm: socfpga: Don't redefine CONFIG_PHYLIB
Date: Sat, 5 Dec 2015 19:03:36 +0100 [thread overview]
Message-ID: <20151205180336.GA25245@amd> (raw)
In-Reply-To: <201512051854.01687.marex@denx.de>
On Sat 2015-12-05 18:54:01, Marek Vasut wrote:
> On Saturday, December 05, 2015 at 06:25:19 PM, Pavel Machek wrote:
> > On Sat 2015-12-05 15:04:25, Marek Vasut wrote:
> > > On Saturday, December 05, 2015 at 08:50:39 AM, Pavel Machek wrote:
> > > > CONFIG_PHYLIB is already set by the config system
> > >
> > > Where exactly is it set by the config system ?
> > >
> > > > don't set it again.
> > > > Avoids ton of warnings.
> > >
> > > Sorry, I don't seem to be able to replicate these warnings. Can you
> > > provide more details ?
> >
> > U-boot based on be30dfbabbee12770221f434d2aa08627e712b97 .
> >
> > pavel at duo:~/amp/u-boot$ grep -ri PHYLIB `find . -name "Kconfig"`
> > ./drivers/net/Kconfig:config PHYLIB
> > ./drivers/net/Kconfig: select PHYLIB
> > ./drivers/net/Kconfig: 100Mbit and 1 Gbit operation. You must
> > enable CONFIG_PHYLIB to
> > ./drivers/net/Kconfig: select PHYLIB
> >
> > ALTERA_TSE selects it.
>
> Altera TSE is not selected on any socfpga platform to my knowledge.
> Could it be your patch which is causing the interference ?
Ok, that explains why you don't see it. I have ALTERA_TSE
enabled. ... which is probably useless, but still should not cause ton
of warnings.
Question is: how to solve it properly?
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2015-12-05 18:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-05 7:50 [U-Boot] [PATCH] arm: socfpga: Don't redefine CONFIG_PHYLIB Pavel Machek
2015-12-05 14:04 ` Marek Vasut
2015-12-05 17:25 ` Pavel Machek
2015-12-05 17:54 ` Marek Vasut
2015-12-05 18:03 ` Pavel Machek [this message]
2015-12-05 18:09 ` Marek Vasut
2015-12-06 8:24 ` Thomas Chou
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=20151205180336.GA25245@amd \
--to=pavel@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