[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YUDOA9SKfCliXlTx@lunn.ch>
Date: Tue, 14 Sep 2021 18:29:55 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Gerhard Engleder <gerhard@...leder-embedded.com>
Cc: Vladimir Oltean <vladimir.oltean@....com>,
Vladimir Oltean <olteanv@...il.com>,
netdev <netdev@...r.kernel.org>,
Heiner Kallweit <hkallweit1@...il.com>,
"David S. Miller" <davem@...emloft.net>,
Russell King <linux@...linux.org.uk>,
Jakub Kicinski <kuba@...nel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [RFC PATCH net] Revert "net: phy: Uniform PHY driver access"
> I submitted it, but Michal Simek argumented that dts files of FPGA
> logic shall not be part of mainline. I suggested that at least one
> reference platform for every FPGA based IP core should be allowed,
> but he said that no one is able to test it. So it seems that you
> will never see any dts file which contains FPGA logic in mainline. I
> will try to submit it again if anyone will support me?
My opinion: If there is a real product out in the field using this,
the DT for the product can be in mainline.
Reference Design Kits for ASICs are well supported in mainline. So the
question is, is an FPGA sufficiently different to an ASIC that is
should be treated differently? Do you have an off the shelf platform
or something custom? How easy is it to get the platform which is used
as an RDK? Can you make a bitstream available for anybody to use?
Andrew
Powered by blists - more mailing lists