[Avila] Fwd: ixp400_eth.c has to be patched?

[John Carter]

Chris,

Do you know if there are plans to support this PHY in upcoming BSP's?

What are the limitations when running the current BSP withhout the  
support?

Thanks,

John Carter

On May 12, 2006, at 12:40 PM, Chris Lang wrote:

> Gianluca,
>    The issue that you are facing is actually due to the fact that  
> the phy on the 2345 does not currently have any support in the 0.6  
> BSP. However, as you have seen, it can work without the phy being  
> supported. Also, the IAL that is being used in the 0.6 BSP is 2.0.  
> The phy that is on the board I believe is a National DP83848.
>    So, basicly the IAL would need to be patched to support this phy.
>
> Thanks,
> Chris Lang
>
>
>
>
>
> ----- Original Message ----- From: "Gianluca Mando'"  
> <mando at airspot.it>
> To: <avila at lists.unixstudios.net>
> Sent: Friday, May 12, 2006 6:02 AM
> Subject: [Avila] Fwd: ixp400_eth.c has to be patched?
>
>
>> Hi all,
>> the board support package 0.6 (kernel 2.6) seems to me not  
>> supporting correctly
>> the Media Indipendent Interface (MII) part of the ethernet driver.
>> It does not generate any explicit message on command line but  
>> services such as
>> SNMP agent does not function properly when interfacing the  
>> ethernet NIC.
>>
>> Any idea on how to solve this problem? has to be applied patch IAL  
>> 1.5.1 from
>> Intel site? It seems to address a similar or the same problem.
>>
>> Gianluca
>>
>> ----- Messaggio inoltrato da Gianluca Mando' <mando at airspot.it> -----
>>    Data: Wed, 10 May 2006 20:05:27 +0200
>>    Da: Gianluca Mando' <mando at airspot.it>
>> Rispondi-A: Gianluca Mando' <mando at airspot.it>
>> Oggetto: ixp400_eth.c has to be patched?
>>      A: avila at lists.unixstudios.net
>>
>>
>> Hi all,
>>
>> loading my GW2345 with BSP 0.6 I can find the following in /var/ 
>> log/message:
>>
>> <12>Feb  3 14:02:35 kernel: ixp400_eth: ixEthMiiLinkStatus failed  
>> on PHY0.
>> <12>Feb  3 14:02:35 kernel: ^ICan't determine
>> <12>Feb  3 14:02:35 kernel: the auto negotiated parameters. Using  
>> default
>> values.
>>
>> Furthermore when I launch the following net-snmp command from a host:
>>
>> snmpwalk -v1 -c wmrtetra 192.168.3.2 interface
>>
>> or also simply starting snmpd on target, the target does not  
>> answer and I can
>> find in /var/log/messages:
>>
>> <11>Feb  3 15:35:34 kernel: ixp400_eth: Error reading MII reg 0 on  
>> phy 0
>> <11>Feb  3 15:35:34 kernel: ixp400_eth: Error reading MII reg 1 on  
>> phy 0
>> <11>Feb  3 15:35:34 kernel: ixp400_eth: Error reading MII reg 2 on  
>> phy 0
>> <11>Feb  3 15:35:34 kernel: ixp400_eth: Error reading MII reg 3 on  
>> phy 0
>> <11>Feb  3 15:35:34 kernel: ixp400_eth: Error reading MII reg 4 on  
>> phy 0
>> <11>Feb  3 15:35:34 kernel: ixp400_eth: Error reading MII reg 5 on  
>> phy 0
>> <11>Feb  3 15:35:34 kernel: ixp400_eth: Error reading MII reg 6 on  
>> phy 0
>> <11>Feb  3 15:35:34 kernel: ixp400_eth: Error reading MII reg 7 on  
>> phy 0
>>
>> I think the problem could be in the following block of code in file
>> ixp400_eth.c:
>>
>>
>>        res = ixEthMiiLinkStatus(phyNum,
>>                                 &linkUp,
>>                                 &speed100,
>>                                 &newDuplex,
>>                                 &autonegotiate);
>>        /* release the MII register access mutex */
>>        up(&miiAccessMutex);
>>
>> #if defined(CONFIG_LEDMAN)
>> ledman_cmd((linkUp ? LEDMAN_CMD_ON : LEDMAN_CMD_OFF),
>> (priv->port_id ? LEDMAN_LAN2_LINK : LEDMAN_LAN1_LINK));
>> #endif
>>
>>        if (res != IX_ETH_ACC_SUCCESS)
>>        {
>> #if defined(CONFIG_LEDMAN)
>>     goto out;
>> #else
>>            P_WARN("ixEthMiiLinkStatus failed on PHY%d.\n"
>>                   "\tCan't determine\nthe auto negotiated  
>> parameters. "
>>                   "Using default values.\n",
>>                   phyNum);
>>
>>            /* this shouldn't happen. exit the thread if it does */
>>     return -1;
>> #endif
>>        }
>>
>> ....
>>
>> In particular, googling I found that the problem could be the  
>> comparison:
>>
>>        if (res != IX_ETH_ACC_SUCCESS)
>>
>> This patch from Intel  
>> "GPL_ixp400LinuxEthernetDriverPatch-1_5_1.zip" substitute
>> privious istruction with
>>
>>  if (res != IX_SUCCESS)
>>
>> ----------------------------------------------------------------
>> This message was sent using IMP, the Internet Messaging Program.
>>
>> ----- Fine messaggio inoltrato -----
>>
>>
>>
>>
>> ----------------------------------------------------------------
>> This message was sent using IMP, the Internet Messaging Program.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: avila-unsubscribe at lists.unixstudios.net
>> For additional commands, e-mail: avila-help at lists.unixstudios.net
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: avila-unsubscribe at lists.unixstudios.net
> For additional commands, e-mail: avila-help at lists.unixstudios.net
>