9front - general discussion about 9front
 help / color / mirror / Atom feed
From: kemal <kemalinanc8@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] driver for intel wireless 7260?
Date: Fri, 6 Aug 2021 14:07:03 +0000	[thread overview]
Message-ID: <CABO6shecLcNLhMP+RepGJ_ps4vYCNg0Nw5sZ0zvCbn_967W5zA@mail.gmail.com> (raw)
In-Reply-To: <08503B0AE53DF93EF8C1913E3E6EB190@wopr.sciops.net>

[-- Attachment #1: Type: text/plain, Size: 1007 bytes --]

2021-08-06 4:43 GMT, qwx <qwx@sciops.net>:
> The patch unfortunately doesn't work for me after a quick test on
> a x240 (did=0x08b2), I have to change Type7260 to 20, not 30, and
> it just dies with a firmware error (with 6.9 firmware).
>
> I can't test more than that right now, but I'll try again later.

when you try it again, would you please mail the whole error
message here, so i can debug it? here is an example error
message:

#l1: firmware: iwm-7260-17, rev 11, build 3216344376, size [3]
14000+2c000 + [3] 14000+2c000 + 0
#l1: fatal firmware error
lastcmd: 136 (0x88)
error: id 65, trm_hw_status 000002f0 00000000,
branchlink2 0000099a, interruptlink 0000d340 0000b8ca,
errordata 00000000 00000200 02030000
#l1: cmd 136: flushq: broken
readnvmsect: flushq: broken
#l1: cmd 152: qcmd: broken
#l1: qcmd: broken

also apparently i'm not supposed to do the niclock/nicunlock
dance for tx commands, so check if qid == 4 so that we know
it was sent by cmd(). perhaps might solve things? diff attached.

[-- Attachment #2: diff.txt --]
[-- Type: text/plain, Size: 643 bytes --]

--- /sys/src/9/pc/etheriwl.c
+++ /sys/src/9/pc/etheriwl.c
@@ -3452,7 +3452,7 @@
 		return "qcmd: broken";
 	}
 	/* wake up the nic (just needed for 7k) */
-	if(ctlr->family == 7000 && q->n == 0)
+	if(ctlr->family == 7000 && qid == 4 && q->n == 0)
 		if(niclock(ctlr) != nil){
 			iunlock(ctlr);
 			return "qcmd: busy";
@@ -4283,8 +4283,8 @@
 		if(tx != nil && tx->n > 0){
 			tx->n--;
 			wakeup(tx);
-			/* unlock 7k family nics as all commands are done */
-			if(ctlr->family == 7000 && tx->n == 0)
+			/* unlock 7k family nics as the command is done */
+			if(ctlr->family == 7000 && qid == 4 && tx->n == 0)
 				nicunlock(ctlr);
 		}
 	}

  parent reply	other threads:[~2021-08-06 14:11 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-06  4:43 qwx
2021-08-06  4:57 ` Skylar Bleed
2021-08-06 10:06 ` cinap_lenrek
2021-08-06 17:56   ` Skylar Bleed
2021-08-06 23:48     ` cinap_lenrek
2021-08-07  2:59       ` Skylar Bleed
2021-08-07 11:16         ` cinap_lenrek
2021-08-07 14:39           ` Skylar Bleed
2021-08-07 22:14             ` kemal
2021-08-08 14:35               ` Skylar Bleed
2021-08-09 12:05               ` kemal
2021-08-10 15:11                 ` Skylar Bleed
2021-08-12 21:03                   ` kemal
2021-08-13 19:49                     ` Skylar Bleed
2021-08-14 13:26                       ` kemal
2021-08-13 23:41                     ` kemal
2021-08-14 17:25                       ` cinap_lenrek
2021-08-14 17:50                       ` kemal
2021-08-07 22:27             ` ori
2021-08-07 10:30     ` kemal
2021-08-06 14:07 ` kemal [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-07-26 16:30 Skylar Bleed
2021-07-26 19:29 ` cinap_lenrek
2021-07-27  7:21   ` Aw: " Eckard Brauer
2021-08-04 20:50     ` kemal
2021-08-05  0:32       ` kemal
2021-08-05  7:52         ` cinap_lenrek
2021-08-05 12:41           ` kemal
2021-08-05 21:19             ` Eckard Brauer
2021-08-05 22:33             ` cinap_lenrek

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=CABO6shecLcNLhMP+RepGJ_ps4vYCNg0Nw5sZ0zvCbn_967W5zA@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).