netdev - Re: [RFC PATCH net] Revert "net: phy: Uniform PHY driver access"

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Tue, 14 Sep 2021 19:14:12 +0200
From:   Gerhard Engleder <gerhard@...leder-embedded.com>
To:     Andrew Lunn <andrew@...n.ch>
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?

At least in combination with the board I can see no difference between ASIC
and FPGA. Usually a FPGA bitstream targets a specific board, so the devices
within the FPGA can be treated like devices on the board.

The reference platform is based on off the shelf stuff (Xilinx ZCU104 and Avnet
AES-FMC-NETW1-G). At least I had no problem buying the boards.

Yes, I can provide a bitstream for everybody.

Gerhard