linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "John Rigby" <jcrigby@gmail.com>
To: Linuxppc-embedded <Linuxppc-embedded@ozlabs.org>
Subject: Re: Kernel for MPC Lite 5200 will not compile
Date: Thu, 30 Mar 2006 09:29:56 -0700	[thread overview]
Message-ID: <4b73d43f0603300829q7d45a029qdb5d8006ccda7275@mail.gmail.com> (raw)
In-Reply-To: <20060330003419.3FF71353A37@atlas.denx.de>

[-- Attachment #1: Type: text/plain, Size: 3251 bytes --]

Sent this to Wolfgang last night.  Accidently omitted Syvain and the list.

The actual bestcomm "microcode" in Sylvain's tree is the same as the latest
Freescale supported code.  The linux driver code that interfaces with it is
code written by Dale Farnsworth and has Montavista copyright.  I don't know
if it is based on old Freescale (Motorola) code or if it is Dale's creation
(perhaps Dale can comment).

I have just spent some time getting UDMA support into the ATA driver using
the the bestcomm code in Sylvain's tree.  In the process I found some bugs
in the code that may explain some problems people have seen with the FEC
driver.  I'll try to get the patch out tomorrow.

The ATA driver is a port from a version that worked on an older kernel and
used the supported Freescale Bestcomm code.  I did the port because it was
my understanding that attempts to get the supported Freescale code into a
public tree had met with resistance in the past.  (Second hand info, I'm
actually fairly new to the 52xx world).

The pluses for the Freescale version is that several devices are supported
that are not in Sylvain's tree.  The version in Sylvain's kernel has a
generic api plus specific code for FEC.  My upcoming patch fixes some bugs,
adds some missing functionality that I need for ATA and adds the specific
ATA dma driver code.

The biggest minus for the Freescale version is that it is really opaque.
Its implementation makes it hard to figure out what the code is actually
doing.

If there is a chance of getting the Freescale Bestcomm code into Sylvain's
tree (and on up the line to Linus) I would welcome that since I would not
have to port other Bestcomm dependent drivers to the version in Sylvain's
tree.  I would gladly port the current FEC code to the Freescale Bestcomm
code to avoid the work of porting the other drivers.  Also we at Freescale
would prefer to have one version of the Bestcomm code circulating.

So I guess my question for those with an opinion is what version of Bestcomm
should be we use for 5200.

Thanks for your input
John

On 3/29/06, Wolfgang Denk <wd@denx.de> wrote:
>
> In message <442B11E8.7020107@246tNt.com> you wrote:
> >
> > It is ?
>
> I think so.
>
> > I don't know about the 2.6-denx, but the stock 2.6.15 should work just
> fine.
> > What's wrong with it ? (except it misses some drivers ... it should
> compile
> > and boot just fine)
>
> Isn't the current reengineered implementation of  the  BestComm  code
> based  on  an very old Freescale version, which has known limitations
> and problems?
>
> Or has there any action resulted  out  of  the  discussion  with  the
> Freescale engineers, and I have missed it?
>
> Best regards,
>
> Wolfgang Denk
>
> --
> Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
> Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
> In accord with UNIX philosophy, Perl gives you enough  rope  to  hang
> yourself.              - L. Wall & R. L. Schwartz, _Programming Perl_
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>

[-- Attachment #2: Type: text/html, Size: 4093 bytes --]

  parent reply	other threads:[~2006-03-30 16:29 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-28  0:07 Kernel for MPC Lite 5200 will not compile Matthias Fechner
2006-03-28  1:01 ` John Rigby
2006-03-28  9:49   ` Matthias Fechner
2006-03-28 16:15     ` John Rigby
2006-03-28 20:47       ` Sylvain Munaut
2006-03-29 15:32         ` Matthias Fechner
2006-04-01  9:19         ` Matthias Fechner
2006-04-02 17:42           ` Sylvain Munaut
2006-04-02 19:32             ` Matthias Fechner
2006-03-28 22:33       ` Wolfgang Denk
2006-03-29 15:31       ` Matthias Fechner
2006-03-28 22:31 ` Wolfgang Denk
2006-03-29 15:39   ` Matthias Fechner
2006-03-29 20:11     ` Wolfgang Denk
2006-03-29 23:02       ` Sylvain Munaut
2006-03-30  0:34         ` Wolfgang Denk
2006-03-30  6:36           ` Sylvain Munaut
2006-03-30 16:29           ` John Rigby [this message]
2006-03-30 16:39             ` John Rigby
2006-03-30 20:05               ` Dale Farnsworth
2006-03-30 21:51                 ` John Rigby
2006-03-30 19:53             ` 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=4b73d43f0603300829q7d45a029qdb5d8006ccda7275@mail.gmail.com \
    --to=jcrigby@gmail.com \
    --cc=Linuxppc-embedded@ozlabs.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).