* [U-Boot-Users] [PATCH] Major overhaul for Xilinx ML300 board support
@ 2005-09-28 8:55 Peter Ryser
2005-09-29 23:54 ` Keith J Outwater
0 siblings, 1 reply; 2+ messages in thread
From: Peter Ryser @ 2005-09-28 8:55 UTC (permalink / raw)
To: u-boot
Attached the CHANGELOG entry for a larger patch that overhauls the ML300
support in U-Boot. The patch is needed as a bug fix for several items
around IIC, System ACE CF, and Ethernet MAC that did not work or did not
work properly. It is also a preparatory and required patch for
additional patches that I plan to submit shortly to add support for more
Xilinx boards around Virtex-II Pro and Virtex-4 FX FPGAs. All
modifications in this patch affect the board/xilinx sub-directory and
include/configs/ml300.h only.
The patch itself is too large to submit to the list (70k). It can be
found at
ftp://customer:xilinx at ftp.xilinx.com/upload/ml300.2005-09-27.patch.txt.gz
This area is cleaned out on a regular basis. If the patch should no
longer be available from this area send me an email and I will upload it
again.
The patch applies cleanly against the current CVS tree. It also does not
generate any warnings during compilation and passes the "MAKEALL ppc"
test (there are errors, e.g. cpci5200, but I cannot see how they could
be caused by this patch).
While most parts adhere to the coding style there are some pieces in the
patch that do not comply 100%. These pieces are mostly in comments or in
include files. I tried to clean this up over the past few days but
constantly broke something more important (i.e. code and compilation). I
hope this patch can be applied to the CVS tree as is. If so, I plan to
submit one or multiple follow-up patches that will fix coding style issues.
After the patch is applied, board/xilinx/ml300/sw_services with all its
files and sub-directories should be removed from the CVS tree. This
directory has been moved up to board/xilinx/sw_services as it is not
specific to the ML300 board and will be reused for other Xilinx boards.
Attached is a second small patch (cm.patch) with changes to the
MAINTAINERS and CREDITS file. I hope that's okay.
- Peter
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: CHANGELOG
Url: http://lists.denx.de/pipermail/u-boot/attachments/20050928/127cf032/attachment.txt
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: cm.patch
Url: http://lists.denx.de/pipermail/u-boot/attachments/20050928/127cf032/attachment-0001.txt
^ permalink raw reply [flat|nested] 2+ messages in thread
* [U-Boot-Users] [PATCH] Major overhaul for Xilinx ML300 board support
2005-09-28 8:55 [U-Boot-Users] [PATCH] Major overhaul for Xilinx ML300 board support Peter Ryser
@ 2005-09-29 23:54 ` Keith J Outwater
0 siblings, 0 replies; 2+ messages in thread
From: Keith J Outwater @ 2005-09-29 23:54 UTC (permalink / raw)
To: u-boot
Peter -
I considered using the Xilinx/ml300 infrastructure in U-Boot to assist my
port to a custom VirtexIIPro board,
but I was concerned about maintaining synchronization between hardware IP
and IP software driver versions.
In the end I took the driver source code generated in EDK and placed it
locally in my board-specific
directory. Somehow, there should be a way for a particular Xilinx FPGA
processor based board to
select the correct driver versions based on the hardware IP versions used.
Any ideas? I would really
prefer to reference driver code in a common library rather than using a
local copy.
Keith
u-boot-users-admin at lists.sourceforge.net wrote on 09/28/2005 01:55:15 AM:
> Attached the CHANGELOG entry for a larger patch that overhauls the ML300
> support in U-Boot.
>
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2005-09-29 23:54 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-09-28 8:55 [U-Boot-Users] [PATCH] Major overhaul for Xilinx ML300 board support Peter Ryser
2005-09-29 23:54 ` Keith J Outwater
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox