9front - general discussion about 9front
 help / color / mirror / Atom feed
From: kemal <kemalinanc8@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] Free Carrots #6: Tools For Fighting WiFi Inequality
Date: Sun, 23 Jul 2023 00:30:49 +0300	[thread overview]
Message-ID: <CABO6shcKGEpB3C2v-Qp7wfTv2svs5JDUgjQkj0-s+c_5aE7zHA@mail.gmail.com> (raw)
In-Reply-To: <CABO6shcb9bWrLL8zVXXGecv5_c+pz5N64LEd6UAD-xtRebJe=g@mail.gmail.com>

2023-07-22 22:53 GMT+03:00, kemal <kemalinanc8@gmail.com>:
>> > i'm 99% sure it's coincidence, the pcie version or connector shape
>> > shouldn't matter.
> it both does and doesn't
> intel changed the firmware significantly in the 7000 series, which
> coincides with intel's mpcie->m2 switch in wifi cards
> there are both 6000 series m2 cards as you mentioned and 7000 series
> mpcie cards (7260-7265 have mpcie versions to my knowledge)
> so this problem is about 7000+ series of cards
> (3000 series are 1x1 versions of 7000)
>
> because of this a different code path exists for initialization,
> there's probably
> some bug in it. i checked the latest patch i prepared a long time ago
> for 7260 support and i realized there was a change i made that i forgot
> about (maybe i didn't send that patch at all, i don't remember...)
> the calibration commands in the main firmware initialization doesn't
> include
> type+length in the command itself and simply sends the calibration block
> it may have caused the firmware to ignore calibration commands, which
> would result in botched calibration+slow speeds.
> (although if this was the case i'd expect the firmware returning a error
> to the driver, so i'm not sure on this)
> i prepared a patch to include this change
>
> i also cleaned up fw capability checking and added pci ids for 3165-3168
> as those should work out of the box with the current code
>
> i can't test this patch, so i will attach it for those who want to test
>
> it can get pushed if it works
>

my mail didn't end up in /n/lists/9front, so the mail server may have
ate my mail. i'm going to reply to my original message and upload
my patch to okturing instead of attaching it, hoping that it will get
sent
http://okturing.com/src/16441/body

  reply	other threads:[~2023-07-22 23:24 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-04  2:51 sl
2023-06-04 13:39 ` hiro
2023-06-04 16:48   ` sl
2023-06-04 19:32     ` hiro
2023-06-05  5:04       ` Stanley Lieber
2023-06-05  7:56         ` hiro
2023-07-08  2:38           ` sl
2023-07-22 19:53             ` kemal
2023-07-22 21:30               ` kemal [this message]
2023-07-22 21:49                 ` kemal
2023-07-22 22:22                   ` qwx
2023-07-22 22:57                   ` Stanley Lieber
2023-07-23  0:24                     ` kemal
2023-07-24  2:35                 ` ori
2023-07-24  9:58                   ` kemal
2023-07-24 11:55                     ` kemal
2023-07-24 12:08                       ` Steve simon
2023-07-24 12:40                         ` kemal
2023-06-10 12:21 ` mkf9
2023-06-10 23:01   ` sl

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=CABO6shcKGEpB3C2v-Qp7wfTv2svs5JDUgjQkj0-s+c_5aE7zHA@mail.gmail.com \
    --to=kemalinanc8@gmail.com \
    --cc=9front@9front.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).