On Sep 14, 2011, at 12:13 PM, Kumar Gala wrote:
> The SoC configuration may have more ports enabled than a given board
> actually can utilize. Add a routinue that allows the board code to
> disable a port that it knows isn't being used.
>
> fm_disable_port() needs to be called before cpu_eth_in
On Sep 15, 2011, at 12:11 AM, Wolfgang Denk wrote:
> Dear Kumar Gala,
>
> In message you
> wrote:
>>
>> Now you could say that we should deal with this via #defines. Which is
>> true, however our reference boards allow for running in hundreds if not
>> thousands of various possible HW config
Dear Kumar Gala,
In message you wrote:
>
> Now you could say that we should deal with this via #defines. Which is
> true, however our reference boards allow for running in hundreds if not
> thousands of various possible HW configurations and we've tried to avoid
> having different builds for su
On Sep 14, 2011, at 3:13 PM, Wolfgang Denk wrote:
> Dear Kumar Gala,
>
> In message <1316020387-6252-1-git-send-email-ga...@kernel.crashing.org> you
> wrote:
>> The SoC configuration may have more ports enabled than a given board
>> actually can utilize. Add a routinue that allows the board co
Dear Kumar Gala,
In message <1316020387-6252-1-git-send-email-ga...@kernel.crashing.org> you
wrote:
> The SoC configuration may have more ports enabled than a given board
> actually can utilize. Add a routinue that allows the board code to
> disable a port that it knows isn't being used.
I don'
5 matches
Mail list logo