linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: Emmanuel Grumbach <egrumbach@gmail.com>
Cc: Emmanuel Grumbach <emmanuel.grumbach@intel.com>,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v6 2/7] iwlwifi: mei: add the driver to allow cooperation with CSME
Date: Fri, 12 Nov 2021 08:21:34 +0200	[thread overview]
Message-ID: <874k8hnbbl.fsf@codeaurora.org> (raw)
In-Reply-To: <CANUX_P137LnjGus5oO2JYyau-kMsAUOPZPx5JP_UW1jAjUC0ig@mail.gmail.com> (Emmanuel Grumbach's message of "Wed, 10 Nov 2021 11:51:51 +0200")

Emmanuel Grumbach <egrumbach@gmail.com> writes:

> On Wed, Nov 10, 2021 at 11:40 AM Kalle Valo <kvalo@codeaurora.org> wrote:
>>
>> Emmanuel Grumbach <egrumbach@gmail.com> writes:
>>
>> >> So if I'm understanding correctly, enabling CONFIG_IWLMEI will break
>> >> existing iwlwifi setups? Or am I missing something?
>> >
>> > Ok, I'll share more details.
>> > The coexistence between iwlwifi and CSME has never really been taken care
>> > of. CSME is a feature meant for enterprise and those systems typically run
>> > Windows which is why the Windows driver has had this feature for years
>> > but not Linux.
>> > iwlmei will not do anything if you don't have CSME configured to use the
>> > WLAN device. Someone needs to actively configure CSME to use WLAN for
>> > this to happen. Very few systems have this configuration.
>>
>> So in a case when CSME/AMT WLAN (or whatever the feature under
>> discussion is called) is disabled in the BIOS and CONFIG_IWLMEI is
>> enabled in the kernel build, iwlwifi will work as before? This is the
>> most important part for me, we must not break people's network access
>> when they upgrade the kernel.
>
> Yes.

Very good, this is most important for me.

>> > The only way to prevent this situation would be to know what device
>> > the user has from iwlmei in the mei bus enumeration but this is
>> > unfortunately not possible.
>> >
>> > I hope that made things clearer. I know all this is confusing, many
>> > pieces of details that I hoped I wouldn't have to bore you with :)
>>
>> It would have been a lot easier and faster to mention all this in the
>> commit logs from the beginning. Dumping me patches without commit logs
>> and no clear explanation is not really building confidence for me.
>>
>
> I understand. There are loads of details and I didn't really want to bother you
> with all of them, I guess I now know that you are the type of person who want
> the details and I'll be clearer the next time.

It's really comes down to trusting the patches, if I don't even
understand what the patches do I will have a hard time trusting them.

> Practically speaking, I owe you a v8 with the WARNING I mentioned plus
> the bugfix I talked about.
>
> Do you want it now or you want me to wait for more comments?

I'm not planning to review v7 anymore, so please do submit v8.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

  reply	other threads:[~2021-11-12  6:21 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-11 10:55 [PATCH v6 1/7] mei: bus: add client dma interface Emmanuel Grumbach
2021-08-11 10:55 ` [PATCH v6 2/7] iwlwifi: mei: add the driver to allow cooperation with CSME Emmanuel Grumbach
2021-10-18  9:28   ` Kalle Valo
2021-10-18  9:40     ` Emmanuel Grumbach
2021-10-18 11:17       ` Emmanuel Grumbach
2021-10-20  8:21         ` Kalle Valo
2021-10-18 10:56   ` Kalle Valo
2021-10-18 11:03     ` Emmanuel Grumbach
2021-10-20  8:30       ` Kalle Valo
2021-10-20  9:44         ` Emmanuel Grumbach
2021-11-10  9:40           ` Kalle Valo
2021-11-10  9:51             ` Emmanuel Grumbach
2021-11-12  6:21               ` Kalle Valo [this message]
2021-10-18 11:06   ` Kalle Valo
2021-10-18 19:17     ` Emmanuel Grumbach
2021-10-20  5:10       ` Emmanuel Grumbach
2021-08-11 10:55 ` [PATCH v6 3/7] iwlwifi: mei: add debugfs hooks Emmanuel Grumbach
2021-08-11 10:55 ` [PATCH v6 4/7] iwlwifi: integrate with iwlmei Emmanuel Grumbach
2021-10-18 11:03   ` Kalle Valo
2021-08-11 10:55 ` [PATCH v6 5/7] nl80211: vendor-cmd: add Intel vendor commands for iwlmei usage Emmanuel Grumbach
2021-10-18 11:16   ` Kalle Valo
2021-10-18 11:34     ` Emmanuel Grumbach
2021-08-11 10:55 ` [PATCH v6 6/7] iwlwifi: mvm: add vendor commands needed for iwlmei Emmanuel Grumbach
2021-10-18 11:19   ` Kalle Valo
2021-08-11 10:55 ` [PATCH v6 7/7] iwlwifi: mvm: read the rfkill state and feed it to iwlmei Emmanuel Grumbach
2021-10-18 11:20   ` Kalle Valo
2021-10-18 11:23     ` Emmanuel Grumbach

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=874k8hnbbl.fsf@codeaurora.org \
    --to=kvalo@codeaurora.org \
    --cc=egrumbach@gmail.com \
    --cc=emmanuel.grumbach@intel.com \
    --cc=linux-wireless@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;
as well as URLs for NNTP newsgroup(s).