Sent this to Wolfgang last night. Accidently omitted Syvain and the list.<br><br>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).
<br><br>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.
<br><br>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).
<br><br>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.
<br><br>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.<br><br>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.
<br><br>So I guess my question for those with an opinion is what version of Bestcomm should be we use for 5200.<br><br>Thanks for your input<br>John<br><br><div><span class="gmail_quote">On 3/29/06, <b class="gmail_sendername">
Wolfgang Denk</b> <<a href="mailto:wd@denx.de">wd@denx.de</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">In message <
<a href="mailto:442B11E8.7020107@246tNt.com">442B11E8.7020107@246tNt.com</a>> you wrote:<br>><br>> It is ?<br><br>I think so.<br><br>> I don't know about the 2.6-denx, but the stock 2.6.15 should work just fine.
<br>> What's wrong with it ? (except it misses some drivers ... it should compile<br>> and boot just fine)<br><br>Isn't the current reengineered implementation of the BestComm code<br>based on an very old Freescale version, which has known limitations
<br>and problems?<br><br>Or has there any action resulted out of the discussion with the<br>Freescale engineers, and I have missed it?<br><br>Best regards,<br><br>Wolfgang Denk<br><br>--<br>Software Engineering: Embedded and Realtime Systems, Embedded Linux
<br>Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: <a href="mailto:wd@denx.de">wd@denx.de</a><br>In accord with UNIX philosophy, Perl gives you enough rope to hang<br>yourself. - L. Wall & R. L. Schwartz, _Programming Perl_
<br>_______________________________________________<br>Linuxppc-embedded mailing list<br><a href="mailto:Linuxppc-embedded@ozlabs.org">Linuxppc-embedded@ozlabs.org</a><br><a href="https://ozlabs.org/mailman/listinfo/linuxppc-embedded">
https://ozlabs.org/mailman/listinfo/linuxppc-embedded</a><br></blockquote></div><br>