From mboxrd@z Thu Jan  1 00:00:00 1970
From: Sander Vermin <sander@vermin.nl>
Date: Tue, 08 Apr 2008 09:58:19 +0200
Subject: [U-Boot-Users] AT91SAM9260EK with KS8721 PHY
In-Reply-To: <47FA8A34.8080603@free.fr>
References: <47FA1E97.50706@vermin.nl>
	<1207576185.6290.4.camel@galileo>	<47FA2C30.7050609@vermin.nl>
	<1207598435.5709.14.camel@galileo>	<47FA82C3.70002@free.fr>
	<1207601357.5709.25.camel@galileo> <47FA8A34.8080603@free.fr>
Message-ID: <47FB259B.8040703@vermin.nl>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

Eric BENARD schreef:
> Stelian Pop a ?crit :
>> Hmm, if I sed:
>>     s/KS8721/DM9161/g
>> and
>>     s/ks8721/dm9161/g
>>
>> on your files I find almost no change with regard to the original
>> version, except:
>>
>> #define PHY_ADDRESS (1<<5)
>>
>> and a #if 0 commenting out a bit of the initialisation sequence...
>>
> yes, goal was to make a clean driver starting from dm9161 with 
> PHY_ADDRESS in the config file ... but I didn't had time to progress 
> on it :-(
> Isolate problem can happen depending on the pullup/down configuration 
> I think (I didn't check in tthe datasheet, but I once met the problem).
>
>> This makes me think it may only be a PHY_ADDRESS issue: what happens if
>> you change in cpu/arm926ejs/at91sam9/ether.c :
>>
>> macb_eth_initialize(0, (void *)AT91_BASE_EMAC, 0x00);
>>
>> to
>>
>> macb_eth_initialize(0, (void *)AT91_BASE_EMAC, 1<<5);
>>
> It's not running on a 9260 so I can't test but it should work (and 
> this may be the problem Sander have).
>
> Eric
I did a new build with:

macb_eth_initialize(0, (void *)AT91_BASE_EMAC, 1<<5);

in stead of:

macb_eth_initialize(0, (void *)AT91_BASE_EMAC, 0x00);

But still no PHY detected :-(

The files that Eric send were for a AT91RM9200? and don't work on my 
AT91SAM9260?

Sander