From: Andrew Lunn <andrew@lunn.ch>
To: Gerhard Engleder <gerhard@engleder-embedded.com>
Cc: Vladimir Oltean <vladimir.oltean@nxp.com>,
Vladimir Oltean <olteanv@gmail.com>,
netdev <netdev@vger.kernel.org>,
Heiner Kallweit <hkallweit1@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Russell King <linux@armlinux.org.uk>,
Jakub Kicinski <kuba@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH net] Revert "net: phy: Uniform PHY driver access"
Date: Tue, 14 Sep 2021 18:29:55 +0200 [thread overview]
Message-ID: <YUDOA9SKfCliXlTx@lunn.ch> (raw)
In-Reply-To: <CANr-f5zNnywpNxMAmNDv60otqXo2oGKiQpT2BL3VraOZftGc4w@mail.gmail.com>
> 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
next prev parent reply other threads:[~2021-09-14 16:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-12 19:28 [RFC PATCH net] Revert "net: phy: Uniform PHY driver access" Vladimir Oltean
2021-09-12 20:49 ` Gerhard Engleder
2021-09-12 21:38 ` Vladimir Oltean
2021-09-13 18:49 ` Andrew Lunn
2021-09-14 12:06 ` Vladimir Oltean
2021-09-14 14:33 ` Andrew Lunn
2021-09-14 15:15 ` Vladimir Oltean
2021-09-14 16:17 ` Gerhard Engleder
2021-09-14 16:29 ` Andrew Lunn [this message]
2021-09-14 17:14 ` Gerhard Engleder
2021-09-14 17:44 ` Vladimir Oltean
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=YUDOA9SKfCliXlTx@lunn.ch \
--to=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=gerhard@engleder-embedded.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=vladimir.oltean@nxp.com \
/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.