ppc: xilinx: Remove ancient ppc405 and ppc440 platform
PATCH 1/1 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/machine
The xilinx git tree still supports this boards, will you also remove support there?
Regards!
Signature · 1 line
Ricardo Ribalda
PATCH 1/1 ppc: xilinx: Remove ancient ppc405 and ppc440 platform
Hi,
Quoted 4 lines · Ricardo Ribalda Delgado
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.
Quoted 2 lines
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.
Quoted 2 lines
There are also yocto layers that support ml507 and ml405
http://git.yoctoproject.org/cgit/cgit.cgi/meta-xilinx-community/tree/conf/machine
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.
Quoted 2 lines
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
PATCH 1/1 ppc: xilinx: Remove ancient ppc405 and ppc440 platform
Hello Michal
Thanks for your reply
Quoted 11 lines · Michal Simek
Hi,
Quoted 4 lines · Ricardo Ribalda Delgado
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/250930
Quoted 2 lines
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
Quoted 8 lines
Quoted 3 lines
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.
Quoted 6 lines
Quoted 3 lines
There are also yocto layers that support ml507 and ml405
http://git.yoctoproject.org/cgit/cgit.cgi/meta-xilinx-community/tree/conf/machineI 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!
Signature · 1 line
Ricardo Ribalda
PATCH 1/1 ppc: xilinx: Remove ancient ppc405 and ppc440 platform
Quoted 5 lines · Ricardo Ribalda Delgado
Hello Michal
Thanks for your reply
On Mon, May 11, 2015 at 9:11 AM, Michal Simek <[email protected]> wrote:
[snip]
Quoted 11 lines
Quoted 7 lines
Quoted 2 lines
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.
Signature · 8 lines
Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: Digital signature URL: <http://lists.denx.de/pipermail/u-boot/attachments/20150511/61b6fc4f/attachment.sig>
PATCH 1/1 ppc: xilinx: Remove ancient ppc405 and ppc440 platform
In reply to Ricardo Ribalda DelgadoHi,
Quoted 13 lines · Ricardo Ribalda Delgado
Hello Michal
Thanks for your reply
Quoted 8 lines · Michal Simek
Hi,
Quoted 4 lines · Ricardo Ribalda Delgado
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.
Quoted 6 lines
Quoted 3 lines
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.
Quoted 4 lines
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/250930
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?
Quoted 9 lines
Quoted 2 lines
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
ok. I really have no problem to let you support these boards. :-)
Quoted 4 lines
Quoted 4 lines
Quoted 3 lines
The plan is to re-factor the code for this platform or just drop all the support?
Quoted 8 lines
Quoted 4 lines
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.
Quoted 8 lines
Quoted 6 lines
Quoted 3 lines
There are also yocto layers that support ml507 and ml405
http://git.yoctoproject.org/cgit/cgit.cgi/meta-xilinx-community/tree/conf/machineI 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
PATCH 1/1 ppc: xilinx: Remove ancient ppc405 and ppc440 platform
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:
ml507ml507_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
Quoted 77 lines · Michal Simek
Hi,
Quoted 13 lines · Ricardo Ribalda Delgado
Hello Michal
Thanks for your reply
Quoted 8 lines · Michal Simek
Hi,
Quoted 4 lines · Ricardo Ribalda Delgado
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.
Quoted 6 lines
Quoted 3 lines
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.
Quoted 4 lines
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/250930
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?Quoted 9 lines
Quoted 2 lines
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
ok. I really have no problem to let you support these boards. :-)
Quoted 4 lines
Quoted 4 lines
Quoted 3 lines
The plan is to re-factor the code for this platform or just drop all the support?
Quoted 8 lines
Quoted 4 lines
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.
Quoted 8 lines
Quoted 6 lines
Quoted 3 lines
There are also yocto layers that support ml507 and ml405
http://git.yoctoproject.org/cgit/cgit.cgi/meta-xilinx-community/tree/conf/machineI 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
Signature · 1 line
Ricardo Ribalda
PATCH 1/1 ppc: xilinx: Remove ancient ppc405 and ppc440 platform
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:
Quoted 110 lines
Hello
I have followed doc/README.generic-board and simply adding
CONFIG_SYS_GENERIC_BOARDdoes the trick.So far it has build with no warnings for:
ml507
ml507_flash
xilinx-ppc440-generic
v5fx30tevaland 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_BOARDto 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-CacheDRAM: 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
Quoted 63 lines · Michal Simek
Hi,
Quoted 10 lines · Ricardo Ribalda Delgado
Hello Michal
Thanks for your reply
Quoted 5 lines · Michal Simek
Hi,
Quoted 2 lines · Ricardo Ribalda Delgado
Hello Michal and Stefan
Quoted 7 lines
Quoted 5 lines
Quoted 2 lines
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.
Quoted 4 lines
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/250930
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?Quoted 8 lines
Quoted 2 lines
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
ok. I really have no problem to let you support these boards. :-)
Quoted 9 lines
Quoted 6 lines
Quoted 2 lines
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.
Quoted 5 lines
Quoted 4 lines
Quoted 2 lines
There are also yocto layers that support ml507 and ml405
http://git.yoctoproject.org/cgit/cgit.cgi/meta-xilinx-community/tree/conf/machineI 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
PATCH 1/1 ppc: xilinx: Remove ancient ppc405 and ppc440 platform
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!
Quoted 120 lines · Georg Schardt
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
GeorgAm 12.05.2015 um 16:19 schrieb Ricardo Ribalda Delgado:
Quoted 110 lines
Hello
I have followed doc/README.generic-board and simply adding
CONFIG_SYS_GENERIC_BOARDdoes the trick.So far it has build with no warnings for:
ml507
ml507_flash
xilinx-ppc440-generic
v5fx30tevaland 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_BOARDto 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-CacheDRAM: 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
Quoted 63 lines · Michal Simek
Hi,
Quoted 10 lines · Ricardo Ribalda Delgado
Hello Michal
Thanks for your reply
Quoted 5 lines · Michal Simek
Hi,
Quoted 2 lines · Ricardo Ribalda Delgado
Hello Michal and Stefan
Quoted 7 lines
Quoted 5 lines
Quoted 2 lines
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.
Quoted 4 lines
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/250930
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?Quoted 8 lines
Quoted 2 lines
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
ok. I really have no problem to let you support these boards. :-)
Quoted 9 lines
Quoted 6 lines
Quoted 2 lines
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.
Quoted 5 lines
Quoted 4 lines
Quoted 2 lines
There are also yocto layers that support ml507 and ml405
http://git.yoctoproject.org/cgit/cgit.cgi/meta-xilinx-community/tree/conf/machineI 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
Signature · 1 line
Ricardo Ribalda
PATCH 1/1 ppc: xilinx: Remove ancient ppc405 and ppc440 platform
In reply to Ricardo Ribalda DelgadoQuoted 32 lines · Ricardo Ribalda Delgado
Hello
I have followed doc/README.generic-board and simply adding
CONFIG_SYS_GENERIC_BOARDdoes the trick.So far it has build with no warnings for:
ml507
ml507_flash
xilinx-ppc440-generic
v5fx30tevaland 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_BOARDto 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-CacheDRAM: 256 MiB Flash: 32 MiB*** Warning - bad CRC, using default environment
U-Boot is up and runnining
ml507:/#
Quoted 8 lines
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!
Signature · 8 lines
Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: Digital signature URL: <http://lists.denx.de/pipermail/u-boot/attachments/20150512/494a7860/attachment.sig>