Re: [U-Boot] [PATCH] ppc: xilinx: Remove ancient ppc405 and ppc440 platform
Hello Michal and Stefan
Could you provide some context about why are we removing this? Virtex 5 (and V4) are not yet in their end of life.
The plan is to re-factor the code for this platform or just drop all the support?
There are also yocto layers that support ml507 and ml405 http://git.yoctoproject.org/cgit/cgit.cgi/meta-xilinx-community/tree/conf/ma...
The xilinx git tree still supports this boards, will you also remove support there?
Regards!
Hi,
On 05/09/2015 06:24 PM, Ricardo Ribalda Delgado wrote:
Hello Michal and Stefan
Could you provide some context about why are we removing this? Virtex 5 (and V4) are not yet in their end of life.
I was checking this internally and ppc is not supported by tools for several releases (roughly ~2 years). All support from tools was already removed. There is no testing on it done for a long time that's why this platform is obsolete from my point of view.
The plan is to re-factor the code for this platform or just drop all the support?
Platform needs to be moved to generic board support and none from xilinx will do it. If you want to invest your time and support these boards feel free to do it but from my perspective we should just remove it because it is just old and make no sense to waste our time on it.
There are also yocto layers that support ml507 and ml405 http://git.yoctoproject.org/cgit/cgit.cgi/meta-xilinx-community/tree/conf/ma...
I am not yocto guy but from cgit it looks like that it is pretty old too. ppc support 4 years ago, ml507 2 years ago.
The xilinx git tree still supports this boards, will you also remove support there?
I am following mainline. It means removing board in mainline is resulting removing the board in xilinx trees.
Thanks, Michal
Hello Michal
Thanks for your reply
On Mon, May 11, 2015 at 9:11 AM, Michal Simek michal.simek@xilinx.com wrote:
Hi,
On 05/09/2015 06:24 PM, Ricardo Ribalda Delgado wrote:
Hello Michal and Stefan
Could you provide some context about why are we removing this? Virtex 5 (and V4) are not yet in their end of life.
I was checking this internally and ppc is not supported by tools for several releases (roughly ~2 years). All support from tools was already removed.
Virtex5 is only supported by ise/edk, not vivado. This is why the tools from the last two years does not support ppc.
I think that the position from xilinx was to support ise for as long as v5, s6... was on sale.
http://forums.xilinx.com/t5/Implementation/VIrtex-5-and-Vivado-HSL/td-p/2509...
There is no testing on it done for a long time that's why this platform is obsolete from my point of view.
We still use it actively on the fpga family of our productsm and cisco uses quite a lot of virtex5 :)
Also avnet virtex5 boards are still available
http://avnetexpress.avnet.com/store/em/EMController?action=products&cata...
The plan is to re-factor the code for this platform or just drop all the support?
Platform needs to be moved to generic board support and none from xilinx will do it. If you want to invest your time and support these boards feel free to do it but from my perspective we should just remove it because it is just old and make no sense to waste our time on it.
Give me a couple of days and I will be able to answer to that question.
If the patch can wait a bit before it is merged it will be great.
There are also yocto layers that support ml507 and ml405 http://git.yoctoproject.org/cgit/cgit.cgi/meta-xilinx-community/tree/conf/ma...
I am not yocto guy but from cgit it looks like that it is pretty old too. ppc support 4 years ago, ml507 2 years ago.
Last change for virtex5 is from 2014.
Regards!
On Mon, May 11, 2015 at 09:34:24AM +0200, Ricardo Ribalda Delgado wrote:
Hello Michal
Thanks for your reply
On Mon, May 11, 2015 at 9:11 AM, Michal Simek michal.simek@xilinx.com wrote:
[snip]
The plan is to re-factor the code for this platform or just drop all the support?
Platform needs to be moved to generic board support and none from xilinx will do it. If you want to invest your time and support these boards feel free to do it but from my perspective we should just remove it because it is just old and make no sense to waste our time on it.
Give me a couple of days and I will be able to answer to that question.
If the patch can wait a bit before it is merged it will be great.
I will wait to see if you (or someone else) wants to step up and maintain it.
Hi,
On 05/11/2015 09:34 AM, Ricardo Ribalda Delgado wrote:
Hello Michal
Thanks for your reply
On Mon, May 11, 2015 at 9:11 AM, Michal Simek michal.simek@xilinx.com wrote:
Hi,
On 05/09/2015 06:24 PM, Ricardo Ribalda Delgado wrote:
Hello Michal and Stefan
Could you provide some context about why are we removing this? Virtex 5 (and V4) are not yet in their end of life.
I was checking this internally and ppc is not supported by tools for several releases (roughly ~2 years). All support from tools was already removed.
Virtex5 is only supported by ise/edk, not vivado. This is why the tools from the last two years does not support ppc.
It is also about SDK where that support was removed.
I think that the position from xilinx was to support ise for as long as v5, s6... was on sale.
http://forums.xilinx.com/t5/Implementation/VIrtex-5-and-Vivado-HSL/td-p/2509...
One thing was support design tools and the next was to support the latest SW. Anyway this is Virtex5 - ppc440. Any intention to keep ppc405 alive?
There is no testing on it done for a long time that's why this platform is obsolete from my point of view.
We still use it actively on the fpga family of our productsm and cisco uses quite a lot of virtex5 :)
Also avnet virtex5 boards are still available
http://avnetexpress.avnet.com/store/em/EMController?action=products&cata...
ok. I really have no problem to let you support these boards. :-)
The plan is to re-factor the code for this platform or just drop all the support?
Platform needs to be moved to generic board support and none from xilinx will do it. If you want to invest your time and support these boards feel free to do it but from my perspective we should just remove it because it is just old and make no sense to waste our time on it.
Give me a couple of days and I will be able to answer to that question.
If the patch can wait a bit before it is merged it will be great.
Definitely it can wait but it has to be moved and test for generic board support.
There are also yocto layers that support ml507 and ml405 http://git.yoctoproject.org/cgit/cgit.cgi/meta-xilinx-community/tree/conf/ma...
I am not yocto guy but from cgit it looks like that it is pretty old too. ppc support 4 years ago, ml507 2 years ago.
Last change for virtex5 is from 2014.
:-) really just make no sense for me to keep these things alive because we are not testing it at all.
Thanks, Michal
Hello
I have followed doc/README.generic-board and simply adding CONFIG_SYS_GENERIC_BOARD does the trick.
So far it has build with no warnings for:
ml507 ml507_flash xilinx-ppc440-generic v5fx30teval
and I have run it on the ml507 with no issues (is the only hw I have with me this week, but it is VERY similar to the others):
Simply adding CONFIG_SYS_GENERIC_BOARD to the .h file works perfectly As you can see from here:
U-Boot 2015.07-rc1-00091-g698a12bef9e7-dirty (May 12 2015 - 10:14:15)
CPU: IBM PowerPC 440x5 VIRTEX5 at 400 MHz (PLB=100 OPB=8 EBC=67) 32 KiB I-Cache 32 KiB D-Cache DRAM: 256 MiB Flash: 32 MiB *** Warning - bad CRC, using default environment
U-Boot is up and runnining ml507:/#
Regarding xilinx-ppc404 and fx12mm
It also builds ok, but I have no access to an fx12mm. Perhaps Georg can give it a try to confirm that this still works.
Is there any other test that needs to be done after "porting" them to generic board?
Thanks
On Mon, May 11, 2015 at 3:45 PM, Michal Simek michal.simek@xilinx.com wrote:
Hi,
On 05/11/2015 09:34 AM, Ricardo Ribalda Delgado wrote:
Hello Michal
Thanks for your reply
On Mon, May 11, 2015 at 9:11 AM, Michal Simek michal.simek@xilinx.com wrote:
Hi,
On 05/09/2015 06:24 PM, Ricardo Ribalda Delgado wrote:
Hello Michal and Stefan
Could you provide some context about why are we removing this? Virtex 5 (and V4) are not yet in their end of life.
I was checking this internally and ppc is not supported by tools for several releases (roughly ~2 years). All support from tools was already removed.
Virtex5 is only supported by ise/edk, not vivado. This is why the tools from the last two years does not support ppc.
It is also about SDK where that support was removed.
I think that the position from xilinx was to support ise for as long as v5, s6... was on sale.
http://forums.xilinx.com/t5/Implementation/VIrtex-5-and-Vivado-HSL/td-p/2509...
One thing was support design tools and the next was to support the latest SW. Anyway this is Virtex5 - ppc440. Any intention to keep ppc405 alive?
There is no testing on it done for a long time that's why this platform is obsolete from my point of view.
We still use it actively on the fpga family of our productsm and cisco uses quite a lot of virtex5 :)
Also avnet virtex5 boards are still available
http://avnetexpress.avnet.com/store/em/EMController?action=products&cata...
ok. I really have no problem to let you support these boards. :-)
The plan is to re-factor the code for this platform or just drop all the support?
Platform needs to be moved to generic board support and none from xilinx will do it. If you want to invest your time and support these boards feel free to do it but from my perspective we should just remove it because it is just old and make no sense to waste our time on it.
Give me a couple of days and I will be able to answer to that question.
If the patch can wait a bit before it is merged it will be great.
Definitely it can wait but it has to be moved and test for generic board support.
There are also yocto layers that support ml507 and ml405 http://git.yoctoproject.org/cgit/cgit.cgi/meta-xilinx-community/tree/conf/ma...
I am not yocto guy but from cgit it looks like that it is pretty old too. ppc support 4 years ago, ml507 2 years ago.
Last change for virtex5 is from 2014.
:-) really just make no sense for me to keep these things alive because we are not testing it at all.
Thanks, Michal
Hello,
yes, we have still some fx12mm in use and i can try to compile and run the newest u-boot in the next few days.
regards Georg
Am 12.05.2015 um 16:19 schrieb Ricardo Ribalda Delgado:
Hello
I have followed doc/README.generic-board and simply adding CONFIG_SYS_GENERIC_BOARD does the trick.
So far it has build with no warnings for:
ml507 ml507_flash xilinx-ppc440-generic v5fx30teval
and I have run it on the ml507 with no issues (is the only hw I have with me this week, but it is VERY similar to the others):
Simply adding CONFIG_SYS_GENERIC_BOARD to the .h file works perfectly As you can see from here:
U-Boot 2015.07-rc1-00091-g698a12bef9e7-dirty (May 12 2015 - 10:14:15)
CPU: IBM PowerPC 440x5 VIRTEX5 at 400 MHz (PLB=100 OPB=8 EBC=67) 32 KiB I-Cache 32 KiB D-Cache DRAM: 256 MiB Flash: 32 MiB *** Warning - bad CRC, using default environment
U-Boot is up and runnining ml507:/#
Regarding xilinx-ppc404 and fx12mm
It also builds ok, but I have no access to an fx12mm. Perhaps Georg can give it a try to confirm that this still works.
Is there any other test that needs to be done after "porting" them to generic board?
Thanks
On Mon, May 11, 2015 at 3:45 PM, Michal Simek michal.simek@xilinx.com wrote:
Hi,
On 05/11/2015 09:34 AM, Ricardo Ribalda Delgado wrote:
Hello Michal
Thanks for your reply
On Mon, May 11, 2015 at 9:11 AM, Michal Simek michal.simek@xilinx.com wrote:
Hi,
On 05/09/2015 06:24 PM, Ricardo Ribalda Delgado wrote:
Hello Michal and Stefan
Could you provide some context about why are we removing this? Virtex 5 (and V4) are not yet in their end of life.
I was checking this internally and ppc is not supported by tools for several releases (roughly ~2 years). All support from tools was already removed.
Virtex5 is only supported by ise/edk, not vivado. This is why the tools from the last two years does not support ppc.
It is also about SDK where that support was removed.
I think that the position from xilinx was to support ise for as long as v5, s6... was on sale.
http://forums.xilinx.com/t5/Implementation/VIrtex-5-and-Vivado-HSL/td-p/2509...
One thing was support design tools and the next was to support the latest SW. Anyway this is Virtex5 - ppc440. Any intention to keep ppc405 alive?
There is no testing on it done for a long time that's why this platform is obsolete from my point of view.
We still use it actively on the fpga family of our productsm and cisco uses quite a lot of virtex5 :)
Also avnet virtex5 boards are still available
http://avnetexpress.avnet.com/store/em/EMController?action=products&cata...
ok. I really have no problem to let you support these boards. :-)
The plan is to re-factor the code for this platform or just drop all the support?
Platform needs to be moved to generic board support and none from xilinx will do it. If you want to invest your time and support these boards feel free to do it but from my perspective we should just remove it because it is just old and make no sense to waste our time on it.
Give me a couple of days and I will be able to answer to that question.
If the patch can wait a bit before it is merged it will be great.
Definitely it can wait but it has to be moved and test for generic board support.
There are also yocto layers that support ml507 and ml405 http://git.yoctoproject.org/cgit/cgit.cgi/meta-xilinx-community/tree/conf/ma...
I am not yocto guy but from cgit it looks like that it is pretty old too. ppc support 4 years ago, ml507 2 years ago.
Last change for virtex5 is from 2014.
:-) really just make no sense for me to keep these things alive because we are not testing it at all.
Thanks, Michal
Hello Georg
Please make sure this patch is applied:
http://lists.denx.de/pipermail/u-boot/2015-May/214017.html
when you test it.
Thanks!
On Tue, May 12, 2015 at 4:27 PM, Georg Schardt schardt@team-ctech.de wrote:
Hello,
yes, we have still some fx12mm in use and i can try to compile and run the newest u-boot in the next few days.
regards Georg
Am 12.05.2015 um 16:19 schrieb Ricardo Ribalda Delgado:
Hello
I have followed doc/README.generic-board and simply adding CONFIG_SYS_GENERIC_BOARD does the trick.
So far it has build with no warnings for:
ml507 ml507_flash xilinx-ppc440-generic v5fx30teval
and I have run it on the ml507 with no issues (is the only hw I have with me this week, but it is VERY similar to the others):
Simply adding CONFIG_SYS_GENERIC_BOARD to the .h file works perfectly As you can see from here:
U-Boot 2015.07-rc1-00091-g698a12bef9e7-dirty (May 12 2015 - 10:14:15)
CPU: IBM PowerPC 440x5 VIRTEX5 at 400 MHz (PLB=100 OPB=8 EBC=67) 32 KiB I-Cache 32 KiB D-Cache DRAM: 256 MiB Flash: 32 MiB *** Warning - bad CRC, using default environment
U-Boot is up and runnining ml507:/#
Regarding xilinx-ppc404 and fx12mm
It also builds ok, but I have no access to an fx12mm. Perhaps Georg can give it a try to confirm that this still works.
Is there any other test that needs to be done after "porting" them to generic board?
Thanks
On Mon, May 11, 2015 at 3:45 PM, Michal Simek michal.simek@xilinx.com wrote:
Hi,
On 05/11/2015 09:34 AM, Ricardo Ribalda Delgado wrote:
Hello Michal
Thanks for your reply
On Mon, May 11, 2015 at 9:11 AM, Michal Simek michal.simek@xilinx.com wrote:
Hi,
On 05/09/2015 06:24 PM, Ricardo Ribalda Delgado wrote:
Hello Michal and Stefan
Could you provide some context about why are we removing this? Virtex 5 (and V4) are not yet in their end of life.
I was checking this internally and ppc is not supported by tools for several releases (roughly ~2 years). All support from tools was already removed.
Virtex5 is only supported by ise/edk, not vivado. This is why the tools from the last two years does not support ppc.
It is also about SDK where that support was removed.
I think that the position from xilinx was to support ise for as long as v5, s6... was on sale.
http://forums.xilinx.com/t5/Implementation/VIrtex-5-and-Vivado-HSL/td-p/2509...
One thing was support design tools and the next was to support the latest SW. Anyway this is Virtex5 - ppc440. Any intention to keep ppc405 alive?
There is no testing on it done for a long time that's why this platform is obsolete from my point of view.
We still use it actively on the fpga family of our productsm and cisco uses quite a lot of virtex5 :)
Also avnet virtex5 boards are still available
http://avnetexpress.avnet.com/store/em/EMController?action=products&cata...
ok. I really have no problem to let you support these boards. :-)
The plan is to re-factor the code for this platform or just drop all the support?
Platform needs to be moved to generic board support and none from xilinx will do it. If you want to invest your time and support these boards feel free to do it but from my perspective we should just remove it because it is just old and make no sense to waste our time on it.
Give me a couple of days and I will be able to answer to that question.
If the patch can wait a bit before it is merged it will be great.
Definitely it can wait but it has to be moved and test for generic board support.
There are also yocto layers that support ml507 and ml405 http://git.yoctoproject.org/cgit/cgit.cgi/meta-xilinx-community/tree/conf/ma...
I am not yocto guy but from cgit it looks like that it is pretty old too. ppc support 4 years ago, ml507 2 years ago.
Last change for virtex5 is from 2014.
:-) really just make no sense for me to keep these things alive because we are not testing it at all.
Thanks, Michal
On Tue, May 12, 2015 at 04:19:52PM +0200, Ricardo Ribalda Delgado wrote:
Hello
I have followed doc/README.generic-board and simply adding CONFIG_SYS_GENERIC_BOARD does the trick.
So far it has build with no warnings for:
ml507 ml507_flash xilinx-ppc440-generic v5fx30teval
and I have run it on the ml507 with no issues (is the only hw I have with me this week, but it is VERY similar to the others):
Simply adding CONFIG_SYS_GENERIC_BOARD to the .h file works perfectly As you can see from here:
U-Boot 2015.07-rc1-00091-g698a12bef9e7-dirty (May 12 2015 - 10:14:15)
CPU: IBM PowerPC 440x5 VIRTEX5 at 400 MHz (PLB=100 OPB=8 EBC=67) 32 KiB I-Cache 32 KiB D-Cache DRAM: 256 MiB Flash: 32 MiB *** Warning - bad CRC, using default environment
U-Boot is up and runnining ml507:/#
Regarding xilinx-ppc404 and fx12mm
It also builds ok, but I have no access to an fx12mm. Perhaps Georg can give it a try to confirm that this still works.
Is there any other test that needs to be done after "porting" them to generic board?
So I was about to send another email but then I dug a bit further and see you're already listed as the maintainer for all of these platforms. So the question comes back to you, is there anything else you'd want to test before declaring things OK? This particular change is indeed easy but there's other stuff that'll need doing soon enough (device model releated things), so please read up on that. Thanks!
participants (4)
-
Georg Schardt -
Michal Simek -
Ricardo Ribalda Delgado -
Tom Rini