All of lore.kernel.org
 help / color / mirror / Atom feed
From: Georg Schardt <schardt@team-ctech.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] ppc: xilinx: Remove ancient ppc405 and ppc440 platform
Date: Tue, 12 May 2015 16:27:16 +0200	[thread overview]
Message-ID: <55520DC4.7080205@team-ctech.de> (raw)
In-Reply-To: <CAPybu_2+6NXGmNeCxihfby0CoFym-2jnp7p_qkMy5c03fxyWTw@mail.gmail.com>

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/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?
>>
>>
>>>> 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&catalogId=500201&storeId=500201&N=0&langId=-1&slnk=b&term=AES-XLX-V5LX-EVL110-G&hrf=http%3A%2F%2Fwww.em.avnet.com%2Fen-us%2Fdesign%2Fdrc%2FPages%2FXilinx-Virtex-5-LX-Evaluation-Kit.aspx&intcmp=EMA-BUY-AES-XLX-V5LX-EVL110-G
>> 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/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.
>>> 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
>
>

  reply	other threads:[~2015-05-12 14:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-09 16:24 [U-Boot] [PATCH] ppc: xilinx: Remove ancient ppc405 and ppc440 platform Ricardo Ribalda Delgado
2015-05-11  7:11 ` Michal Simek
2015-05-11  7:34   ` Ricardo Ribalda Delgado
2015-05-11 12:10     ` Tom Rini
2015-05-11 13:45     ` Michal Simek
2015-05-12 14:19       ` Ricardo Ribalda Delgado
2015-05-12 14:27         ` Georg Schardt [this message]
2015-05-12 14:31           ` Ricardo Ribalda Delgado
2015-05-12 15:07         ` Tom Rini

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=55520DC4.7080205@team-ctech.de \
    --to=schardt@team-ctech.de \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.