From: Sander Vermin <sander@vermin.nl>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] AT91SAM9260EK with KS8721 PHY
Date: Tue, 08 Apr 2008 09:58:19 +0200 [thread overview]
Message-ID: <47FB259B.8040703@vermin.nl> (raw)
In-Reply-To: <47FA8A34.8080603@free.fr>
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
next prev parent reply other threads:[~2008-04-08 7:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-07 13:16 [U-Boot-Users] AT91SAM9260EK with KS8721 PHY Sander Vermin
2008-04-07 13:49 ` Stelian Pop
2008-04-07 13:54 ` Eric BENARD
2008-04-07 14:14 ` Sander Vermin
2008-04-07 20:00 ` Stelian Pop
2008-04-07 20:23 ` Eric BENARD
2008-04-07 20:49 ` Stelian Pop
2008-04-07 20:55 ` Eric BENARD
2008-04-08 7:58 ` Sander Vermin [this message]
2008-04-08 8:36 ` Eric BENARD
2008-04-08 9:09 ` Sander Vermin
2008-04-08 9:09 ` michael
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=47FB259B.8040703@vermin.nl \
--to=sander@vermin.nl \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.