From: "Oliver Fuchs" <olivers.lists@gmx.net>
To: LinuxPPC <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: MPC82xx enet on SCC3
Date: Mon, 16 Aug 2004 16:00:32 +0200 [thread overview]
Message-ID: <4120DA20.2984.1BD2DC2@localhost> (raw)
In-Reply-To: <66FD1720-EC80-11D8-8A46-003065F9B7DC@embeddededge.com>
From: Dan Malek <dan@embeddededge.com>
Subject: Re: MPC82xx enet on SCC3
> > as far as I understand, my kernel (2.4.24 from ELDK3.0) is not
> > prepared for Ethernet on SCC3 of the MPC82xx.
>
> An #ifdef and two lines of #defines should be all you need,
> unless you have some special BSCR or other set up needed.
>
Ok, it was a little bit more, but I have it.
I have modified arch/ppc/config.in and arch/ppc/8260_io/enet.c so
that it fits to SCC1-4 w/o further modifications there.
I would contribute this, if anyone wants to use it.
But as Wolfgang has mentioned frequently, it only makes sense to
contribute a patch that aplies to the latest CVS version.
Is there any chance to get the latest CVS version by HTTP or FTP?
Oliver
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-08-16 14:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-12 14:29 MPC82xx enet on SCC3 Oliver Fuchs
2004-08-12 16:55 ` Dan Malek
2004-08-16 14:00 ` Oliver Fuchs [this message]
2004-08-16 16:21 ` Wolfgang Denk
2004-08-16 17:40 ` Ralph Siemsen
2004-08-17 9:49 ` Oliver Fuchs
2004-08-26 10:08 ` Cramfs Limitations Song Sam
2004-08-26 15:12 ` Wolfgang Denk
2004-08-27 1:35 ` Song Sam
2004-08-27 7:38 ` Wolfgang Denk
2004-08-27 8:33 ` Song Sam
2004-08-26 10:10 ` Does ext2 based on MTD acceptable for Embedded Development? Song Sam
2004-08-27 7:08 ` Oliver Fuchs
2004-08-27 7:39 ` Wolfgang Denk
2004-08-27 10:05 ` Oliver Fuchs
2004-08-27 14:24 ` Wolfgang Denk
2004-08-16 18:18 ` MPC82xx enet on SCC3 Dan Malek
2004-08-17 9:49 ` Oliver Fuchs
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=4120DA20.2984.1BD2DC2@localhost \
--to=olivers.lists@gmx.net \
--cc=linuxppc-embedded@lists.linuxppc.org \
/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).