MPC5200 BestComm microcode [en]/[de]coding draft
RFC 1/1 MPC5200 BestComm microcode [en]/[de]coding draft
Hello Sylvain,
This a draft of Documentation/powerpc/bestcomm.txt, it was born since I couldn't find DRD/LCD description and "... graphical task builder are currently in development" (quotation from AN2604) :(, so I try write doco by myself. Here result of my reverse engineering.
If you or somebody have more information or found some bugs, please, fix/expand my text, especially places marked by "?".
Signature · 2 lines
Regards Andrey Volkov
Draft
---
commit 8a3ea9eb0933e43b8fad1f50ef566b6145202e25
tree 7d9356ec710b68c159c8ad95c49ea1c2439beb74
parent 825f973a6a6e12ff0c9d5bc10a74b4cae3687db5
author Andrey Volkov <[email protected]> Thu, 18 Aug 2005 21:58:24 +0400 committer Andrey Volkov <[email protected]> Thu, 18 Aug 2005 21:58:24 +0400
Documentation/powerpc/bestcomm.txt | 143 ++++++++++++++++++++++++++++++++++++ 1 files changed, 143 insertions(+), 0 deletions(-)
Documentation/powerpc/bestcomm.txt new file +143 -0
@@ -0,0 +1,143 @@ + Microcode description of MPC5200 Bestcomm DMA +===================================================================== + +Please mail me (Andrey Volkov, [email protected]) if you have +questions, comments or corrections. + +All instructions of Bestcomm microcode are divided on +two main types: LCD (Loop Control Descriptor) and +DRD (Data Routing Descriptor). Any Task must started from +LCD[EX] instruction and finished by DRD instruction (usually NOP). +Each of instruction types, in one's turn, are divided on two +and three subtypes accordingly, which are described below: + +1) DRD1A - load/store data, and, optionally, made some operation +on it (depend on what loaded to FDT). Here is fields description +of this DRD: + +Bits num. Name Desc. +[31:29] Reserved, must be 0 +[28:28] MORE ?????, if set then idx/var + dst/src fields are changed. I.e. + [16:10] contain SOURCE, + and [09:03] contain DESTINATION. +[27:27] TFD Transfer Frame Done. Assert frame + done Transfer Frame Done line of + selected (in INIT field) periphery. +[26:26] INT Interrupt. If set to 1, + then generate core interrupt +[25:21] INIT Initiator (aka requestor) number. +[20:19] RS Read Size (0 - 32bit word, 1 - byte, + 2 - 16 bit word, 3 - dynamic/reserved?? + (masked in real time?)) +[18:17] WS Write Size (see above) +[16:16] ?????????????? +[15:15] Destination index prefix, + if set (i.e. =1), then bitfield [13:10] + contain index number, and [14:14] have + meaning of indirect addressing flag. + If this field cleared then field + [14:10] contain index of VARIABLE. +[14:14] Indirect addressing by idx, + (and only by idx) flag, or high bit of + variable index. +[13:10] index of DESTINATION/SOURCE idx/var. + +[09:09] ???? For some cases 1, for another 0.???? + +[08:08] Same as in [14:10], but for source. +[07:03] Same as in [14:10], but for source. +[02:00] EU3 Number of function, which will execute + on EU#3. +Note: For DRD1A exist special case, aka NOP, which act as +task terminator. Fields, in this case, have next meanings: + +[31:28] Reserved must be 0. +[27:27] TFD Transfer Frame Done. +[26:26] INT Interrupt. +[25:21] INIT Initiator (aka requestor) number. Usually 0, + or ALWAYS INITIATOR. +[16:00] NOP code Must be 0x1f8 + +Ex. Please, pay attention to first two lines: since MORE is set, +codes for idx2 and var13 are in different fields, then for case +where MORE is not set (var4 = var2).: + 0x10601010 -- DRD1A: var4 = var2; FN=0 MORE init=3 WS=0 RS=0 + 0x00008868 -- DRD1A: idx2 = var13; FN=0 init=0 WS=0 RS=0 + 0x0404c999 -- DRD1A: *idx2 = EU3(); FN=1 INT init=0 WS=2 RS=0 + 0x000001f8 -- DRD1A: NOP + 0x040001f8 -- DRD1A: INT init=0 + +Next two DRDs are ALWAYS coupled, i.e it is impossible to using +DRD2B1 without preceded DRD2A, but any (?fixme?) number DRD2B1 +may followed by DRD2A. + +2) DRD2A - setup bestcomm Execution Unit (EU) +Bitfields encodings: + +Bits num. Name Desc +[31:31] MORE ????????? +[30:29] EXT must be always initialized + by 3 (binary 11) +[27:27] TFD Transfer Frame Done. +[26:21] INIT Initiator number. +[20:19] RS Read Size +[18:17] WS Write Size +[16:04] reserved, must be 0 +[03:00] EU3 Number of function, which will execute + on EU#3 at DRD2B1 time. +Ex: + 0x60140002 -- DRD2A: EU3=2 EXT init=0 WS=2 RS=2 + +3) DRD2B1 - execute function and store result of it. + +Bits num. Name Desc +[31:28] Reserved must be 0. + +[27:22] DST Result destination (var/idx/*idx). + See description of field [15:10] of DRD1A + section. +[21:20] WS ?? Write Size for dst ?? +[19:18] EU# Since MPC5200 have only EU#3, this filed + always must contain 3 +[17:12] ???? (Reserved, must be 0x0f), + may be encoded operands sizes???? +[11:06] OP1 operand 1 of EU#3 + See description of field [15:10] in DRD1A + section. +[05:00] OP2 operand 2 of EU#3 + See description of field [15:10] in DRD1A + section, or, if for EU#3 function needed + only one operand (like CRC), then this field + must contain 0x1f + +Ex: + 0x0d0cf247 -- DRD2B1: *idx4 = EU3(); EU3(var9,var7) + 0x0c8cfc5f -- DRD2B1: *idx2 = EU3(); EU3(*idx1) + +4) LCD - run followed loop microcode, or may be used for checking +some conditions. LCD may be nested (only two levels are supported). + +Bits num. Name Desc +[31:31] LOOP Loop prefix, always 1 +[30:30] ??????????????????? +[29:23] INIT1 ???Initializition part of first init expression.??? +[22:11] ??????????????????? +[10:06] CMP_VAR Variable to which idx compared. Part of + Termination control. +[05:03] INC1 increment1 +[02:00] INC2 increment2, if unsused may be any value + +5) LCDEXT - If in yours loop used more then 2 indexes, then +this record MUST PRECEDED LCD. Also loop end condition MAY pointed HERE, +then it not pointed in LCD. + +Bits num. Name Desc +[31:31] LOOP Loop prefix, always 1 +[30:30] ??????????????????? +[29:23] INIT1 ???Initializition part of first init expression.??? +[22:11] ??????????????????? +[10:06] CMP_VAR Variable to which idx compared. Part of + Termination control. +[05:03] INC1 increment1 +[02:00] INC2 increment2, if unsused may be any value
Hi Andrey,
Quoted 10 lines · Andrey Volkov
Hello Sylvain,
This a draft of
Documentation/powerpc/bestcomm.txt, it was born since I couldn't find DRD/LCD description and "... graphical task builder are currently in development" (quotation from AN2604) :(, so I try write doco by myself. Here result of my reverse engineering.If you or somebody have more information or found some bugs, please, fix/expand my text, especially places marked by "?".
First, yes, it's definitly a good idea to work on some documentation on how to write microcode.
But I'm not sure including that into the Documentation/ directory is such a good idea. Changing documentation that's there requires sending patch to Linus and get it processed etc ... And since It's mostly reverse engineering, it's probably going to change often as we get a better understanding.
We could publish it as a Wiki (that's a tendency these days ;) so that everyone can contribute easily and post code examples etc ... What do you think ?
See comments below for the "real" comments ;)
Documentation/powerpc/bestcomm.txt line 19
Quoted 13 lines
Documentation/powerpc/bestcomm.txt new file +13
-0+All instructions of Bestcomm microcode are divided on +two main types: LCD (Loop Control Descriptor) and +DRD (Data Routing Descriptor). Any Task must started from +LCD[EX] instruction and finished by DRD instruction (usually NOP). +Each of instruction types, in one's turn, are divided on two +and three subtypes accordingly, which are described below: + +1) DRD1A - load/store data, and, optionally, made some operation +on it (depend on what loaded to FDT). Here is fields description +of this DRD: + +Bits num. Name Desc. +[31:29] Reserved, must be 0
Well yes, the 3 first bits indicate what type of descriptor it is ;-
Documentation/powerpc/bestcomm.txt line 23
Quoted 4 lines
+[28:28] MORE ?????, if set then idx/var
Documentation/powerpc/bestcomm.txt new file +3
-0+ dst/src fields are changed. I.e. + [16:10] contain SOURCE, + and [09:03] contain DESTINATION.
What I got for this bit is that if it's set that means the next DRD is in the same LCD context, if not, it goes one LCD context before (like a closing brace for a for loop } ).
Documentation/powerpc/bestcomm.txt line 28
Quoted 5 lines
+[27:27] TFD Transfer Frame Done. Assert frame
Documentation/powerpc/bestcomm.txt new file +4
-0+ done Transfer Frame Done line of + selected (in INIT field) periphery. +[26:26] INT Interrupt. If set to 1, + then generate core interrupt
Generate the core interrupt when the bestcomm engine exits the current LCD. Don't know why it's part of the DRD descriptors and from what a Freescale engineer told me, he doesn't know either ;)
Documentation/powerpc/bestcomm.txt line 32
Quoted 4 lines
+[25:21] INIT Initiator (aka requestor) number.
+[20:19] RS Read Size (0 - 32bit word, 1 - byte,Documentation/powerpc/bestcomm.txt new file +2
-0+ 2 - 16 bit word, 3 - dynamic/reserved?? + (masked in real time?))
IIRC, there is a field in the SDMA registers to specify what 3 means. However, the bestcomm api replace all the 3 with the correct size in the ucode itself. That functionnality may not work or just isn't practical. Best to have the correct size specified when running the task anyway.
Quoted 9 lines
+[18:17] WS Write Size (see above)
+[16:16] ??????????????
+[15:15] Destination index prefix,Documentation/powerpc/bestcomm.txt new file +6
-0+ if set (i.e. =1), then bitfield [13:10] + contain index number, and [14:14] have + meaning of indirect addressing flag. + If this field cleared then field + [14:10] contain index of VARIABLE. +[14:14] Indirect addressing by idx,
Documentation/powerpc/bestcomm.txt line 51
Quoted 10 lines
Documentation/powerpc/bestcomm.txt new file +10
-0+ (and only by idx) flag, or high bit of + variable index. +[13:10] index of DESTINATION/SOURCE idx/var. + +[09:09] ???? For some cases 1, for another 0.???? + +[08:08] Same as in [14:10], but for source. +[07:03] Same as in [14:10], but for source. +[02:00] EU3 Number of function, which will execute + on EU#3.
[2:0] is FN but what do you exactly mean it is. The only thing I notice is that if it =1 then the source is "EU3()" ... whatever that means.
Also, I'm not sure it has something to do with the FDT since there is only 3 bits.
Documentation/powerpc/bestcomm.txt line 60
Quoted 9 lines
Documentation/powerpc/bestcomm.txt new file +9
-0+Note: For DRD1A exist special case, aka NOP, which act as +task terminator. Fields, in this case, have next meanings: + +[31:28] Reserved must be 0. +[27:27] TFD Transfer Frame Done. +[26:26] INT Interrupt. +[25:21] INIT Initiator (aka requestor) number. Usually 0, + or ALWAYS INITIATOR. +[16:00] NOP code Must be 0x1f8
Where did you see that that you could use theses bit in NOP ?
Documentation/powerpc/bestcomm.txt line 73
Quoted 12 lines
Documentation/powerpc/bestcomm.txt new file +12
-0+Ex. Please, pay attention to first two lines: since MORE is set, +codes for idx2 and var13 are in different fields, then for case +where MORE is not set (var4 = var2).: + 0x10601010 -- DRD1A: var4 = var2; FN=0 MORE init=3 WS=0 RS=0 + 0x00008868 -- DRD1A: idx2 = var13; FN=0 init=0 WS=0 RS=0 + 0x0404c999 -- DRD1A: *idx2 = EU3(); FN=1 INT init=0 WS=2 RS=0 + 0x000001f8 -- DRD1A: NOP + 0x040001f8 -- DRD1A: INT init=0 + +Next two DRDs are ALWAYS coupled, i.e it is impossible to using +DRD2B1 without preceded DRD2A, but any (?fixme?) number DRD2B1 +may followed by DRD2A.
? AFAIU it's either
DRD2A, DRD2B1
or
DRD2A, DRDF2B2
Documentation/powerpc/bestcomm.txt line 81
Quoted 7 lines
+2) DRD2A - setup bestcomm Execution Unit (EU)
Documentation/powerpc/bestcomm.txt new file +6
-0+Bitfields encodings: + +Bits num. Name Desc +[31:31] MORE ????????? +[30:29] EXT must be always initialized + by 3 (binary 11)
What I have is that
[31:29] Always 011 - Indicates a DRD2A.
[28:28] MORE - Same meaning as before. Just tells if the following (here that's the one that is after the corresponding DRD2B{1,2}) DRD is in the same loop or if it's in the previous loop level ?
Quoted 5 lines
+[27:27] TFD Transfer Frame Done. +[26:21] INIT Initiator number. +[20:19] RS Read Size +[18:17] WS Write Size+[16:04] reserved, must be 0
They are the function number to use in EU#{0,1,2} but in MPC5200, only EU3 is implemented.
Documentation/powerpc/bestcomm.txt line 92
Quoted 6 lines
+[03:00] EU3 Number of function, which will execute
Documentation/powerpc/bestcomm.txt new file +5
-0+ on EU#3 at DRD2B1 time. +Ex: + 0x60140002 -- DRD2A: EU3=2 EXT init=0 WS=2 RS=2 + +3) DRD2B1 - execute function and store result of it.
Can't find the piece if paper where I wrote about DRD2B1 ... For DRD2B2 there is only 1 example I know of, so quite hard to deduce anything.
Quoted 2 lines
+4) LCD - run followed loop microcode, or may be used for checking +some conditions. LCD may be nested (only two levels are supported).
Two levels ? Didn't know that but sure there is no example with 3 levels.
Documentation/powerpc/bestcomm.txt line 129
Quoted 10 lines
Documentation/powerpc/bestcomm.txt new file +10
-0+ +Bits num. Name Desc +[31:31] LOOP Loop prefix, always 1 +[30:30] ??????????????????? +[29:23] INIT1 ???Initializition part of first init expression.??? +[22:11] ??????????????????? +[10:06] CMP_VAR Variable to which idx compared. Part of + Termination control. +[05:03] INC1 increment1 +[02:00] INC2 increment2, if unsused may be any value
What I got :
bits[31:30] : 10 - identify a LCD
bit [29 ] : d - Whether to dereferentiate init_a or not. idx_a =
deref ? *(init_a) : init_a
bits[28:27] : ta - Type of init_a : 00 -> var
11 -> idx
bits[26:23] : ia - init_a : Where to find initial value for idx_a bits[22:21] : ?? - Unknow
bits[20:19] : tb - Type of init_b
bits[18:15] : ib - init_b
bits[14:13] : cc - condition_choice : 00 - use idx_a
01 - use idx_b
11 - no condition
bits[12:11] : ?? - Unknow always 00
bits[10: 6] : ca - condition_arg : What to do the comparaison against bits[ 5: 3] : sa - step_a : What inc[] to use to increment idx_a (and also where to look for the condition code)
bits[ 2: 0] : sb - step_b
Condition codes (first 4 bits of the increments)
Quoted 2 lines
= c
4
once 0
!= 6 <= a < 2
Documentation/powerpc/bestcomm.txt line 143
Quoted 13 lines
+5) LCDEXT - If in yours loop used more then 2 indexes, then
Documentation/powerpc/bestcomm.txt new file +12
-0+this record MUST PRECEDED LCD. Also loop end condition MAY pointed HERE, +then it not pointed in LCD. + +Bits num. Name Desc +[31:31] LOOP Loop prefix, always 1 +[30:30] ??????????????????? +[29:23] INIT1 ???Initializition part of first init expression.??? +[22:11] ??????????????????? +[10:06] CMP_VAR Variable to which idx compared. Part of + Termination control. +[05:03] INC1 increment1 +[02:00] INC2 increment2, if unsused may be any value
similar to LCD
Sylvain
Quoted 6 lines · In message <[email protected]> you wrote:
But I'm not sure including that into the
Documentation/directory is such a good idea. Changing documentation that's there requires sending patch to Linus and get it processed etc ... And since It's mostly reverse engineering, it's probably going to change often as we get a better understanding.
Documentation/ is the first place to look for Linux kernel
documentation, so it seems the best place for such stuff to me.
Quoted 3 lines
We could publish it as a Wiki (that's a tendency these days ;) so that everyone can contribute easily and post code examples etc ... What do you think ?
This is a good idea for collecting the information, but IMHO the document itself should go (too) to Documentation/
Just my $ 0.02
Best regards,
Wolfgang Denk
Signature · 5 lines
Software Engineering: Embedded and Realtime Systems, Embedded Linux Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: [email protected] Programmer's Lament: (Shakespeare, Macbeth, Act I, Scene vii) "That we but teach bloody instructions, which, being taught, return to plague the inventor..."
Hello Sylvain, Wolfgang
Sorry for silence, I was out of office last week.
(And will be absent at next two weeks too).
Wolfgang, first question to you:
May be you are know where I could find (if it exist) BestComm (SmartComm) API for mystic MGT5100?
Quoted 6 lines · Sylvain Munaut
But I'm not sure including that into the
Documentation/directory is such a good idea. Changing documentation that's there requires sending patch to Linus and get it processed etc ... And since It's mostly reverse engineering, it's probably going to change often as we get a better understanding.
I agree with Wolfgang's opinion: when I seek description of some kernel part, I'm firstly check Documentation/, next grepping kernel tree. In any case, when doco will be completed it will not changed often.
Quoted 4 lines
We could publish it as a Wiki (that's a tendency these days ;) so that everyone can contribute easily and post code examples etc ... What do you think ?
Agree, good think. Wolfgang, is it appropriately to use WIKI of denx.de?
Quoted 27 lines
See comments below for the "real" comments ;)
Quoted 9 lines
+[18:17] WS Write Size (see above)
+[16:16] ??????????????
+[15:15] Destination index prefix,Documentation/powerpc/bestcomm.txt new file +6
-0+ if set (i.e. =1), then bitfield [13:10] + contain index number, and [14:14] have + meaning of indirect addressing flag. + If this field cleared then field + [14:10] contain index of VARIABLE. +[14:14] Indirect addressing by idx,Documentation/powerpc/bestcomm.txt line 51
Quoted 10 lines
Documentation/powerpc/bestcomm.txt new file +10
-0+ (and only by idx) flag, or high bit of + variable index. +[13:10] index of DESTINATION/SOURCE idx/var. + +[09:09] ???? For some cases 1, for another 0.???? + +[08:08] Same as in [14:10], but for source. +[07:03] Same as in [14:10], but for source. +[02:00] EU3 Number of function, which will execute + on EU#3.[2:0] is FN but what do you exactly mean it is. The only thing I notice is that if it =1 then the source is "
EU3()" ... whatever that means.
Quoted 2 lines
Also, I'm not sure it has something to do with the FDT since there is only 3 bits.
With first 7 functions, as I understand. In theory it may be any function (depend on functions arrangement in FDT).
Quoted 4 lines
Quoted 4 lines
Documentation/powerpc/bestcomm.txt new file +4
-0+Note: For DRD1A exist special case, aka NOP, which act as +task terminator. Fields, in this case, have next meanings: + +[31:28] Reserved must be 0.
Quoted 8 lines
Documentation/powerpc/bestcomm.txt line 60
Quoted 5 lines
+[27:27] TFD Transfer Frame Done. +[26:26] INT Interrupt. +[25:21] INIT Initiator (aka requestor) number. Usually 0,Documentation/powerpc/bestcomm.txt new file +2
-0+ or ALWAYS INITIATOR. +[16:00] NOP code Must be 0x1f8Where did you see that that you could use theses bit in NOP ?
INT - was used in image_rtos1/TASK_PCI_TX for example. INIT,TFD - my assumption, not sure certainly.
Quoted 9 lines
Quoted 9 lines
Documentation/powerpc/bestcomm.txt new file +9
-0+Ex. Please, pay attention to first two lines: since MORE is set, +codes for idx2 and var13 are in different fields, then for case +where MORE is not set (var4 = var2).: + 0x10601010 -- DRD1A: var4 = var2; FN=0 MORE init=3 WS=0 RS=0 + 0x00008868 -- DRD1A: idx2 = var13; FN=0 init=0 WS=0 RS=0 + 0x0404c999 -- DRD1A: *idx2 = EU3(); FN=1 INT init=0 WS=2 RS=0 + 0x000001f8 -- DRD1A: NOP + 0x040001f8 -- DRD1A: INT init=0 +
Quoted 8 lines
Documentation/powerpc/bestcomm.txt line 73
Quoted 3 lines
Documentation/powerpc/bestcomm.txt new file +3
-0+Next two DRDs are ALWAYS coupled, i.e it is impossible to using +DRD2B1 without preceded DRD2A, but any (?fixme?) number DRD2B1 +may followed by DRD2A.? AFAIU it's either
DRD2A, DRD2B1
or
DRD2A, DRDF2B2
Oops, I miss DRD2B2, but then situation become more clean:
DRD2B2 - load accumulator of execution unit.
Then 0x1f code in DRD2B1 OP2 (and may be in OP1) mean EU accumulator.
Quoted 15 lines
Documentation/powerpc/bestcomm.txt line 81
Quoted 7 lines
+2) DRD2A - setup bestcomm Execution Unit (EU)
Documentation/powerpc/bestcomm.txt new file +6
-0+Bitfields encodings: + +Bits num. Name Desc +[31:31] MORE ????????? +[30:29] EXT must be always initialized + by 3 (binary 11)What I have is that
[31:29] Always 011 - Indicates a DRD2A.
[28:28] MORE - Same meaning as before. Just tells if the following (here that's the one that is after the corresponding DRD2B{1,2}) DRD is in the same loop or if it's in the previous loop level ?
Quoted 8 lines
Quoted 5 lines
+[27:27] TFD Transfer Frame Done. +[26:21] INIT Initiator number. +[20:19] RS Read Size +[18:17] WS Write Size+[16:04] reserved, must be 0
They are the function number to use in EU#{0,1,2} but in MPC5200, only EU3 is implemented.
I extend description.
Quoted 11 lines
Documentation/powerpc/bestcomm.txt line 92
Quoted 6 lines
+[03:00] EU3 Number of function, which will execute
Documentation/powerpc/bestcomm.txt new file +5
-0+ on EU#3 at DRD2B1 time. +Ex: + 0x60140002 -- DRD2A: EU3=2 EXT init=0 WS=2 RS=2 + +3) DRD2B1 - execute function and store result of it.Can't find the piece if paper where I wrote about DRD2B1 ... For DRD2B2 there is only 1 example I know of, so quite hard to deduce anything.
Two if be more precisely :), both in CRC16 u-code.
Quoted 4 lines
Quoted 2 lines
+4) LCD - run followed loop microcode, or may be used for checking +some conditions. LCD may be nested (only two levels are supported).
Two levels ? Didn't know that but sure there is no example with 3 levels.
Ok, I remove this sentence, it was born, because I doesn't found how loops are terminated (as you point, it was absence of bit in DRD :) ).
Signature · 2 lines
Regards Andrey Volkov
Dear Andrey,
Quoted 4 lines · in message <[email protected]> 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
Quoted 1 line
Agree, good think. Wolfgang, is it appropriately to use WIKI of denx.de?
Yes, of course. Just let me know what you want and we can create a new web (I don't see any good existing place where this fits).
Best regards,
Wolfgang Denk
Signature · 4 lines
Software Engineering: Embedded and Realtime Systems, Embedded Linux Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: [email protected] "The number of Unix installations has grown to 10, with more expected." - The Unix Programmer's Manual, 2nd Edition, June, 1972
Quoted 9 lines · Wolfgang Denk
Dear Andrey,
Quoted 3 lines · in message <[email protected]> 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?
Quoted 8 lines
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.
Signature · 2 lines
Regards Andrey Volkov
Quoted 22 lines · Andrey Volkov
Quoted 10 lines · Wolfgang Denk
Dear Andrey,
Quoted 3 lines · in message <[email protected]> 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?Quoted 8 lines
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
Quoted 7 lines
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.
Do you have a MGT5100 ?
Frankly I'm not sure it's of much interest since even Freescale is not seeking to have linux on 5100 and I'm not even sure you can buy some ...
Sylvain