netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Vadym Kochan <vadym.kochan@plvision.eu>
Cc: netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
	Oleksandr Mazur <oleksandr.mazur@plvision.eu>,
	Serhiy Boiko <serhiy.boiko@plvision.eu>,
	Serhiy Pshyk <serhiy.pshyk@plvision.eu>,
	Volodymyr Mytnyk <volodymyr.mytnyk@plvision.eu>,
	Taras Chornyi <taras.chornyi@plvision.eu>,
	Andrii Savka <andrii.savka@plvision.eu>,
	Jiri Pirko <jiri@mellanox.com>,
	Ido Schimmel <idosch@mellanox.com>,
	Chris Packham <Chris.Packham@alliedtelesis.co.nz>
Subject: Re: [RFC next-next v2 2/5] net: marvell: prestera: Add PCI interface support
Date: Fri, 1 May 2020 15:25:24 +0200	[thread overview]
Message-ID: <20200501132524.GB128166@lunn.ch> (raw)
In-Reply-To: <20200501062223.GA15217@plvision.eu>

> > Hi Vadym
> > 
> > What are the plans for getting the firmware into linux-firmware git
> > repo?
> > 
> > 	Andrew
> 
> Well, what is the procedure ? I was thinking that probably after
> conceptual part will be approved and I will send official PATCH series
> along with the firmware image to the linux-firmware ?

Hi Vadym

I just wanted to ensure you actually were going to send the
firmware. For the Marvell 10G PHYs, you need to signed an NDA with
Marvell to get the firmware, and you probably cannot distribute
it. Marvell seems to have no interest in making the firmware
available. So we NACKed support for loading the firmware a runtime.

If you have all the legal mumbo jumbo in place to make the firmware
available, great. You can post it for merging to linux-firmware now.

Thanks
	   Andrew


  reply	other threads:[~2020-05-01 14:01 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-30 23:20 [RFC next-next v2 0/5] net: marvell: prestera: Add Switchdev driver for Prestera family ASIC device 98DX326x (AC3x) Vadym Kochan
2020-04-30 23:20 ` [RFC next-next v2 1/5] net: marvell: prestera: Add driver for Prestera family ASIC devices Vadym Kochan
2020-05-11 10:32   ` Jiri Pirko
2020-05-11 11:11     ` Vadym Kochan
2020-05-11 11:29       ` Jiri Pirko
2020-05-11 12:42         ` Andrew Lunn
2020-05-11 13:02           ` Vadym Kochan
2020-05-11 13:53             ` Andrew Lunn
2020-05-11 14:11               ` Vadym Kochan
2020-05-11 15:32                 ` Jiri Pirko
2020-05-11 16:43                   ` Andrew Lunn
2020-05-11 17:24                     ` Jiri Pirko
2020-05-12 14:53     ` Vadym Kochan
2020-05-12 15:03       ` Jiri Pirko
2020-05-12 15:07         ` Vadym Kochan
2020-05-12 15:21           ` Jiri Pirko
2020-05-11 12:57   ` Jiri Pirko
2020-05-11 19:24     ` Vadym Kochan
2020-05-12  5:55       ` Jiri Pirko
2020-05-12  7:15         ` Vadym Kochan
2020-05-12 11:13           ` Jiri Pirko
2020-05-12 14:50     ` Vadym Kochan
2020-05-12 15:02       ` Jiri Pirko
2020-04-30 23:20 ` [RFC next-next v2 2/5] net: marvell: prestera: Add PCI interface support Vadym Kochan
2020-05-01  0:00   ` Andrew Lunn
2020-05-01  6:22     ` Vadym Kochan
2020-05-01 13:25       ` Andrew Lunn [this message]
2020-05-11 11:23   ` Jiri Pirko
2020-05-26 16:26     ` Vadym Kochan
2020-05-27  5:53       ` Jiri Pirko
2020-05-27  8:55         ` Vadym Kochan
2020-05-27 12:01           ` Mickey Rachamim
2020-05-28 10:29             ` Jiri Pirko
2020-04-30 23:20 ` [RFC next-next v2 3/5] net: marvell: prestera: Add ethtool " Vadym Kochan
2020-05-11 17:31   ` Jiri Pirko
2020-04-30 23:20 ` [RFC next-next v2 4/5] net: marvell: prestera: Add Switchdev driver implementation Vadym Kochan
2020-04-30 23:20 ` [RFC next-next v2 5/5] dt-bindings: marvell,prestera: Add address mapping for Prestera Switchdev PCIe driver Vadym Kochan
2020-05-01  0:01   ` Andrew Lunn

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=20200501132524.GB128166@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=Chris.Packham@alliedtelesis.co.nz \
    --cc=andrii.savka@plvision.eu \
    --cc=davem@davemloft.net \
    --cc=idosch@mellanox.com \
    --cc=jiri@mellanox.com \
    --cc=netdev@vger.kernel.org \
    --cc=oleksandr.mazur@plvision.eu \
    --cc=serhiy.boiko@plvision.eu \
    --cc=serhiy.pshyk@plvision.eu \
    --cc=taras.chornyi@plvision.eu \
    --cc=vadym.kochan@plvision.eu \
    --cc=volodymyr.mytnyk@plvision.eu \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).