linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Andrey Volkov <avolkov@varma-el.com>
To: Wolfgang Denk <wd@denx.de>
Cc: Sylvain Munaut <tnt@246tNt.com>, linuxppc-embedded@ozlabs.org
Subject: Re: [RFC] MPC5200 BestComm microcode [en]/[de]coding draft
Date: Thu, 01 Sep 2005 16:15:42 +0400	[thread overview]
Message-ID: <4316F0EE.3020001@varma-el.com> (raw)
In-Reply-To: <20050831204627.EAF8C35258E@atlas.denx.de>



Wolfgang Denk wrote:
> Dear Andrey,
> 
> in message <4315D1DC.1000607@varma-el.com> you wrote:
> 
>>Wolfgang, first question to you:
>>May be you are know where I could find (if it exist)
>>BestComm (SmartComm) API for mystic MGT5100?
> 
> 
> We did not test the current code on the Icecube with  the  5100,  but
> previous  versions  used to run fine (well, within the limitations of
> the 5100, that is). So if the current code on our CVS server does not
> run, just check out an oder version. You can search  the  history  of
> changes for example here:
> http://source.denx.net/cgi-bin/gitweb.cgi?p=linuxppc_2_4_devel.git
> like that:
> http://source.denx.net/cgi-bin/gitweb.cgi?p=linuxppc_2_4_devel.git&a=search&s=bestcomm
No, Wolfgang, I'm sorry, but you are don't understand me.
I seek bestcomm u-code for MGT5100 (and only for 5100) exceptionally for
subj. Since in 5100 was implemented EU#1, hence bestcomm u-code
for it have a little differences (in DRD2xx, if be more precesily).
This u-code is partially presented in U-boot (eth RX/TX tasks),
but it is not enough for me.

-- 
Regards
Andrey Volkov

  reply	other threads:[~2005-09-01 12:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-18 18:05 [RFC] MPC5200 BestComm microcode [en]/[de]coding draft Andrey Volkov
2005-08-22 13:31 ` Sylvain Munaut
2005-08-22 13:48   ` Wolfgang Denk
2005-08-31 15:50   ` Andrey Volkov
2005-08-31 20:46     ` Wolfgang Denk
2005-09-01 12:15       ` Andrey Volkov [this message]
2005-09-01 14:25         ` Sylvain Munaut

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=4316F0EE.3020001@varma-el.com \
    --to=avolkov@varma-el.com \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=tnt@246tNt.com \
    --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).