From: Dan Malek <dan@embeddededge.com>
To: "Robert P. J. Day" <rpjday@mindspring.com>
Cc: Embedded Linux PPC list <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: fix to enet.c to enable networking when booting from flash
Date: Tue, 13 Jul 2004 14:39:36 -0400 [thread overview]
Message-ID: <FDAC0433-D4FB-11D8-8CEC-003065F9B7DC@embeddededge.com> (raw)
In-Reply-To: <Pine.LNX.4.60.0407131328290.19248@dell.enoriver.com>
On Jul 13, 2004, at 1:34 PM, Robert P. J. Day wrote:
> #if defined(CONFIG_RPXLITE) || defined(CONFIG_RPXCLASSIC) ||
> defined(CONFIG_EP8xx) || defined(CONFIG_EP852)
> /* And while we are here, set the configuration to enable
> ethernet.
> */
> *((volatile uint *)RPX_CSR_ADDR) &= ~BCSR0_ETHLPBK;
> *((volatile uint *)RPX_CSR_ADDR) |=
> (BCSR0_ETHEN | BCSR0_COLTESTDIS | BCSR0_FULLDPLXDIS);
>> *((volatile uint *)RPX_CSR_ADDR) |=0x00100000; <-- add this
> //1:ethernet,0:SPI
> #endif
In newer drivers, this would be done in a board specific file. As you
can tell, this code enables the Ethernet PHY. I don't understand
why that extra 'add this' is necessary. That does some PCMCIA signal
routing to IP_B5, which should not have any effect on the Ethernet.
What revision of board is this? I have RPXLite's that I boot from
flash all of the time without trouble.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
** This list is shutting down 7/24/2004.
next prev parent reply other threads:[~2004-07-13 18:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-13 17:34 fix to enet.c to enable networking when booting from flash Robert P. J. Day
2004-07-13 18:39 ` Dan Malek [this message]
2004-07-13 18:46 ` Robert P. J. Day
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=FDAC0433-D4FB-11D8-8CEC-003065F9B7DC@embeddededge.com \
--to=dan@embeddededge.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=rpjday@mindspring.com \
/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).