From: David Miller <davem@davemloft.net>
To: alobakin@marvell.com
Cc: kai.heng.feng@canonical.com, anthony.wong@canonical.com,
irusskikh@marvell.com, kuba@kernel.org, ndanilov@marvell.com,
mstarovoitov@marvell.com, dmitry.bezrukov@marvell.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: atlantic: Add support for firmware v4
Date: Tue, 07 Jul 2020 12:56:24 -0700 (PDT) [thread overview]
Message-ID: <20200707.125624.2030141794702878802.davem@davemloft.net> (raw)
In-Reply-To: <20200707084657.205-1-alobakin@marvell.com>
From: Alexander Lobakin <alobakin@marvell.com>
Date: Tue, 7 Jul 2020 11:46:57 +0300
> From: Kai-Heng Feng <kai.heng.feng@canonical.com>
> Date: Tue, 7 Jul 2020 14:38:28 +0800
>
>> We have a new ethernet card that is supported by the atlantic driver:
>> 01:00.0 Ethernet controller [0200]: Aquantia Corp. AQC107 NBase-T/IEEE 802.3bz Ethernet Controller [AQtion] [1d6a:07b1] (rev 02)
>>
>> But the driver failed to probe the device:
>> kernel: atlantic: Bad FW version detected: 400001e
>> kernel: atlantic: probe of 0000:01:00.0 failed with error -95
>>
>> As a pure guesswork, simply adding the firmware version to the driver
>
> Please don't send "pure guessworks" to net-fixes tree. You should have
> reported this as a bug to LKML and/or atlantic team, so we could issue
> it.
Production hardware is shipping to customers and the driver
maintainers didn't add support for this ID yet? What is that
"atlantic team" waiting for?
Honestly I don't blame someone for posting a patch like this to get it
to work.
next prev parent reply other threads:[~2020-07-07 19:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-07 6:38 Kai-Heng Feng
2020-07-07 8:46 ` Alexander Lobakin
2020-07-07 10:02 ` Kai-Heng Feng
2020-07-07 19:56 ` David Miller [this message]
2020-07-15 15:34 ` [EXT] " Igor Russkikh
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=20200707.125624.2030141794702878802.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=alobakin@marvell.com \
--cc=anthony.wong@canonical.com \
--cc=dmitry.bezrukov@marvell.com \
--cc=irusskikh@marvell.com \
--cc=kai.heng.feng@canonical.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mstarovoitov@marvell.com \
--cc=ndanilov@marvell.com \
--cc=netdev@vger.kernel.org \
/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
all inboxes | Powered by JetHome®