[prev in list] [next in list] [prev in thread] [next in thread] 

List:       devicetree
Subject:    Re: [PATCH] arm64: Add support for cisco craw64 ARMv8 SoCs
From:       Arnd Bergmann <arnd () arndb ! de>
Date:       2021-03-31 20:18:22
Message-ID: CAK8P3a2ANBD5q-J+Mr0up+wFBdWJG3Z2ceUP=aB29G7WMq1Z3Q () mail ! gmail ! com
[Download RAW message or body]

On Wed, Mar 31, 2021 at 7:57 PM Daniel Walker <danielwa@cisco.com> wrote:
> 
> On Wed, Mar 31, 2021 at 09:04:15AM +0200, Arnd Bergmann wrote:
> > On Wed, Mar 31, 2021 at 3:46 AM Daniel Walker <danielwa@cisco.com> wrote:
> > > From: Ofer Licht <olicht@cisco.com>
> > 
> > Thanks for the submission, it's always nice to see a new platform
> 
> 
> > > Define craw64 config, dts and Makefile for Cisco
> > > SoCs known as Craw.
> > 
> > I'd like some more information about the platform, e.g. the target
> > market and maybe a link to the product information.
> 
> Our SoC is produced as an internal product. So SoC specifications aren't
> widely available.
> 
> Here is an example of a Cisco product which uses this SoC,
> 
> https://www.cisco.com/c/en/us/products/collateral/switches/catalyst-9200-series-switches/nb-06-cat9200-ser-data-sheet-cte-en.html
>  
> I suspect that's not really what your looking for tho.

No, that's pretty much exactly what I was looking for. Just put this one
sentence and the link into the patch description and it will be fine.

> > 
> > The memory size is usually filled by the boot loader, just put an
> > empty node into the .dtsi file
> 
> Arnd, I must regretfully inform you that Cisco has a deep dark addiction to
> bootloaders which, are, um, how do I say this diplomatically, um , brain dead.
> 
> You have some other comments below related to moving things into the bootloader,
> and I can look into it, but bootloader inflexibility is wide spread inside
> Cisco.

Ok, no worries. If the bootloader can do it right, you should do it, but
this part is not essential.

        Arnd


[prev in list] [next in list] [prev in thread] [next in thread]