From: "Dale Farnsworth" <dale@farnsworth.org>
To: Wolfgang Denk <wd@denx.de>,
linuxppc-dev@lists.linuxppc.org,
Tom Rini <trini@kernel.crashing.org>
Subject: Re: MPC5200 Patches
Date: Mon, 10 Nov 2003 12:02:07 -0700 [thread overview]
Message-ID: <20031110190207.GA12163@zenos.farnsworth.org> (raw)
In-Reply-To: <20031107222025.3181CC5F59@atlas.denx.de>
On Fri, Nov 07, 2003 at 10:20:20PM +0000, Wolfgang Denk wrote:
> The code is actually identical the the later version where Motorola
> replaced the headers with GPL preambles. I sent a tarball with the GPL
> bestcomm code to Tom Rini.
I just thought that applying a patch that had "Motorola Confidential
Proprietary" all over it wasn't a good idea. :-)
> > I did not publish the port because the ethernet support relies on
> > a Motorola-written DMA subsystem with a proprietary license that
> > doesn't permit redistribution. A month ago, Motorola finally sent
> > me an updated, GPLed version of the DMA controller code. I merged
> > the new version, but the DMA API has changed and I've been busy with
> > other things
>
> The main problem with the FEC code is that it does NOT use the offical
> bestcomm API but (for efficiency reasons?) meddles directly with
> internal bestcomm data. This is why the code breaks with each new
> release of the bestcomm code.
I think you're referring to the way the fec code accesses the ring
buffers. Motorola supports direct access to the ring buffer and this
is the only release of the bestcomm that broke that access. Previous
breakages were due to other changes in bestcomm API.
> The code I submitted contains some things; some code was developed by
> BenH, some by DENX. It would be sad if this stuff was just ignored.
> How about merging our code and your new stuff?
I have merged your code, benh's and mine and placed it at
ftp://source.mvista.com/pub/linuxppc/mpc5200/linuxppc_2_4_devel.mpc5200.patch
This patch doesn't require uboot. I retained the uboot code and added
CONFIG_UBOOT, but haven't tested with it.
I would appreciate it if you could take some time to test it with your
hardware. I find that USB and PCI are not working here, but they also
fail with your patch, so it may be my icecube hardware.
I haven't tested this merged code on the MGT5100, and in fact, I removed
the MGT5100 FEC support because the #ifdefs in fec.c were just too ugly.
I'll insert a compatibility layer to support the MGT5100 FEC if there
is sufficient interest. Is anyone still using the MGT5100?
> For me the main issue is that MPC5200 support makes it into the
> official kernel trees as fast as possible.
Agreed, with reasonable quality.
Thanks,
-Dale
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-11-10 19:02 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-01 9:36 MPC5200 Patches Wolfgang Denk
2003-11-03 23:31 ` Dale Farnsworth
2003-11-07 22:20 ` Wolfgang Denk
2003-11-10 19:02 ` Dale Farnsworth [this message]
2003-11-10 20:46 ` Wolfgang Denk
2003-11-10 21:00 ` Tom Rini
2003-11-12 0:34 ` Wolfgang Denk
2003-11-12 4:50 ` Dale Farnsworth
2003-11-12 9:30 ` Geert Uytterhoeven
2003-11-12 9:49 ` Wolfgang Denk
2003-11-12 9:59 ` Geert Uytterhoeven
2003-11-12 11:41 ` Gabriel Paubert
2003-11-12 11:51 ` Geert Uytterhoeven
2003-11-12 14:47 ` Wolfgang Denk
2003-11-12 14:45 ` Wolfgang Denk
2003-11-12 17:43 ` Gabriel Paubert
2003-11-12 19:41 ` Geert Uytterhoeven
2003-11-14 6:11 ` Kumar Gala
2003-11-14 15:20 ` Tom Rini
2003-11-12 15:18 ` Tom Rini
2003-11-12 15:49 ` Gary Thomas
2003-11-12 15:53 ` Tom Rini
2003-11-16 20:33 ` Wolfgang Denk
2003-11-17 6:07 ` Dale Farnsworth
2003-11-17 8:35 ` Wolfgang Denk
2003-11-17 15:19 ` Tom Rini
2003-11-17 16:02 ` Wolfgang Denk
2003-11-17 16:25 ` Tom Rini
2003-11-18 14:52 ` Dale Farnsworth
2003-11-20 11:53 ` Christoph Hellwig
2003-11-20 12:10 ` Wolfgang Denk
2003-11-20 12:17 ` Christoph Hellwig
2003-11-21 1:04 ` Paul Mackerras
2003-11-18 0:43 ` Benjamin Herrenschmidt
2003-11-18 0:44 ` Benjamin Herrenschmidt
2003-11-18 14:45 ` Wolfgang Denk
2003-11-18 15:00 ` Wolfgang Denk
2003-11-17 18:50 ` Tom Rini
2003-12-03 18:28 ` Dale Farnsworth
[not found] ` <20031203185310.19A48C5F5F@atlas.denx.de>
2003-12-04 0:35 ` Dale Farnsworth
[not found] ` <20031110162536.GC8584@ip68-0-152-218.tc.ph.cox.net>
2003-11-10 19:09 ` Dale Farnsworth
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=20031110190207.GA12163@zenos.farnsworth.org \
--to=dale@farnsworth.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=trini@kernel.crashing.org \
--cc=wd@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).