From: vb <vb@vsbe.com>
To: "Stefan Roese" <sr@denx.de>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: EMAC2 in ibm_newemac driver
Date: Thu, 2 Oct 2008 21:57:44 -0700 [thread overview]
Message-ID: <f608b67d0810022157q464687e6i8162d8f9f6b319dd@mail.gmail.com> (raw)
In-Reply-To: <200810020751.42821.sr@denx.de>
On Wed, Oct 1, 2008 at 10:51 PM, Stefan Roese <sr@denx.de> wrote:
> On Thursday 02 October 2008, vb wrote:
>>
>
> The ibm_newemac driver in the DENX repository has absolutely no changes to the
> kernel.org version.
>
I am comparing between 2.6.26.5 and your tree, these are the
differences I referred to.
>> I am trying to debug it, but am wondering if anyone had more than two
>> interfaces going on this architecture and if so - what are the
>> gotchas.
>
> The AMCC Glacier 460GT eval board uses all 4 EMAC's with RGMII. IIRC, then you
> need to configure the GPIO multiplexing differently (compared to Canyonlands
> 460EX) to fully support all 4 EMAC's on 460GT. This is done in U-Boot. I
> suggest that you check this configuration first.
>
Stefan, you are a gentleman and a scholar: this is exactly where my
problem was. Thank you for saving me from wasting lots of time trying
to figure out what's 'wrong' with the driver.
Now, comparing glacier GPIO settings with the 460Gx datasheet (rev
1.07 of May 29) it seems that the datasheet is wrong and suggests
using of ALT2 mode for the RGMII2 gpio pins(does not work) as opposed
ALT1 used in glacier (and actually working apart from a problem I
still am seeing with the TX). Do you remember anything about this?
TIA,
vadim
> Best regards,
> Stefan
>
next prev parent reply other threads:[~2008-10-03 4:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-02 4:38 EMAC2 in ibm_newemac driver vb
2008-10-02 5:51 ` Stefan Roese
2008-10-03 4:57 ` vb [this message]
2008-10-03 14:37 ` Stefan Roese
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=f608b67d0810022157q464687e6i8162d8f9f6b319dd@mail.gmail.com \
--to=vb@vsbe.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=sr@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).