[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <BC4BFA45-2CD1-4834-AEFB-58D1133B7F22@freescale.com>
Date: Tue, 3 Jun 2008 13:11:21 -0500
From: Andy Fleming <afleming@...escale.com>
To: Adrian Bunk <bunk@...sta.de>
Cc: Kumar Gala <galak@...nel.crashing.org>,
Scott Wood <scottwood@...escale.com>, netdev@...r.kernel.org,
Jeff Garzik <jeff@...zik.org>, linuxppc-dev@...abs.org
Subject: Re: [RFC] Make board force selection of PHYLIB
On Jun 3, 2008, at 12:00, Adrian Bunk wrote:
> On Tue, Jun 03, 2008 at 09:47:19AM -0500, Kumar Gala wrote:
>> How is this as a fix.
>>
>> - k
>>
>> diff --git a/arch/powerpc/platforms/85xx/Kconfig b/arch/powerpc/
>> platforms/85xx/Kconfig
>> index 7ff29d5..9e5c884 100644
>> --- a/arch/powerpc/platforms/85xx/Kconfig
>> +++ b/arch/powerpc/platforms/85xx/Kconfig
>> @@ -34,6 +34,7 @@ config MPC85xx_MDS
>> bool "Freescale MPC85xx MDS"
>> select DEFAULT_UIMAGE
>> select QUICC_ENGINE
>> + select PHYLIB if GIANFAR=m
>> help
>> This option enables support for the MPC85xx MDS board
>
> The .config you sent me as an example didn't have GIANFAR set, so it
> couldn't help there.
>
> How early do the fixups have to run?
>
> I see two possible solutions:
> - let MPC85xx_MDS unconditionally select PHYLIB or
> - move the fixups to the gianfar driver
Just to reiterate the point: The fixups are not only not gianfar-
specific, they may not involve gianfar at all. The 8568 has *two*
types of built-in ethernet controllers, which use 4 PHYs (of one
type). The fixups are purely PHY-specific for this board.
Andy
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists