public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed

From: "Albrecht Dreß" <albrecht.dress@arcor•de>
To: linuxppc-dev@lists•ozlabs.org
Subject: Re: MPC5200/BestComm functions question
Date: Sun, 13 Sep 2009 18:13:53 +0200	[thread overview]
Message-ID: <1252858433.3337.2@antares> (raw)
In-Reply-To: <fa686aa40909120701k4c4faa8ev78ac556f0b1f88ed@mail.gmail.com> (from grant.likely@secretlab.ca on Sat Sep 12 16:01:35 2009)

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

Am 12.09.09 16:01 schrieb(en) Grant Likely:

> I've actually got a better driver which exports an API for doing  
> local plus bus FIFO transfers.  It's been posted to the mailing list  
> a couple of times.  I'll cc: you the next time I post it (real soon  
> now).

Thanks a lot, that will be really helpful! :-)

> Bestcomm can do that, but Freescale has not publically released the  
> bestcomm documentation, and they do not support writing custom  
> bestcomm tasks.  From what I understand there are a number of hidden  
> bugs in the bestcomm engine which you could run into if you deviate  
> from the provided tasks.  You're very much on your own if you go down  
> that route.  :-(

I see - that's a pity, shifting those tasks to a "coprocessor" sounds  
like an attractive idea!

BTW, I didn't forget about the 5200 GPT/WDT issue, I just didn't have  
the time yet to implement it.  The old work vs. what I would like to do  
conflict, but I will try to find a reasonable solution.

Thanks, Albrecht.

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

     prev parent reply	other threads:[~2009-09-13 16:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-12 12:36 MPC5200/BestComm functions question Albrecht Dreß
2009-09-12 14:01 ` Grant Likely
2009-09-13 16:13   ` Albrecht Dreß [this message]

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=1252858433.3337.2@antares \
    --to=albrecht.dress@arcor$(echo .)de \
    --cc=linuxppc-dev@lists$(echo .)ozlabs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox