From owner-freebsd-wireless@freebsd.org Mon Jan 28 07:25:00 2019 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A3C9914A9469 for ; Mon, 28 Jan 2019 07:25:00 +0000 (UTC) (envelope-from blockk2000@gmail.com) Received: from mail-oi1-f180.google.com (mail-oi1-f180.google.com [209.85.167.180]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B5A93752EB for ; Mon, 28 Jan 2019 07:24:58 +0000 (UTC) (envelope-from blockk2000@gmail.com) Received: by mail-oi1-f180.google.com with SMTP id c206so12271403oib.0 for ; Sun, 27 Jan 2019 23:24:58 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=bP8NPlG+BvtDrpgviwmvZqmIJZJvjvPbIyAgekjnoM0=; b=Kt2Kl+XJPvhEmx6R4/l0NeGL5Knv5o/tAlM72ANT1J632/mstKj3AqqBKm77MgfbwD GRLNjTZeGtAKLTk3jPKOPsTetmaIqMKRHOPG+qjGNmfscorhnyaz4mQOw0QNc3C5hUm4 h51GAjsNfEgBq9gSi5eGvPBk+/hqK+9kUJFxElTovwzKS7KexlaXGg0LBzmwxyE6e1CA prhDowzgTTA1vlY3JUFudEZMRU5nYtAFD3q3eHoVBOYoMvWFXTngkJtefcgKBXUV6Dhb VNHCq1N9oQDFnEdVJVW+HLi6JQUZSFliB58B/ablOz0hz8/orJZElQXf/gFY8rEZKCah JUsQ== X-Gm-Message-State: AHQUAuYv21FjKZm8x8LFnEyPCIpd5uDmJC6pdqKCoJeE+jcWyywQzkTN dl4YCK0P2x9bMEHDLpNzuJcAxKGQjM88u0ufZOs= X-Google-Smtp-Source: ALg8bN4QKsGB9aaFcQCYOnL37Q2JTWxLOVpQ892wssXsNlYSXd4WE/1+nX5wKFwkArqEWpADij5tvGQuZffLupJsM60= X-Received: by 2002:aca:eb0f:: with SMTP id j15mr5474770oih.110.1548660292317; Sun, 27 Jan 2019 23:24:52 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Wen-Jun Guo Date: Mon, 28 Jan 2019 15:24:41 +0800 Message-ID: Subject: Re: failed to initialize Intel 9560 wifi driver To: waddlesplash Cc: freebsd-wireless@freebsd.org X-Rspamd-Queue-Id: B5A93752EB X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; spf=pass (mx1.freebsd.org: domain of blockk2000@gmail.com designates 209.85.167.180 as permitted sender) smtp.mailfrom=blockk2000@gmail.com X-Spamd-Result: default: False [-3.38 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-wireless@freebsd.org]; DMARC_NA(0.00)[nctu.edu.tw]; MIME_TRACE(0.00)[0:+,1:+]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MX_GOOD(-0.01)[cached: alt3.gmail-smtp-in.l.google.com]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[180.167.85.209.list.dnswl.org : 127.0.5.0]; NEURAL_HAM_SHORT(-0.22)[-0.225,0]; RCVD_TLS_LAST(0.00)[]; FORGED_SENDER(0.30)[wjguo@cs.nctu.edu.tw,blockk2000@gmail.com]; FREEMAIL_TO(0.00)[gmail.com]; R_DKIM_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; FROM_NEQ_ENVFROM(0.00)[wjguo@cs.nctu.edu.tw,blockk2000@gmail.com]; IP_SCORE(-1.15)[ipnet: 209.85.128.0/17(-3.72), asn: 15169(-1.95), country: US(-0.08)]; RCVD_COUNT_TWO(0.00)[2] Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jan 2019 07:25:00 -0000 After rebase, the firmware still doesn't work. It returned the statux 0xdead on the ALIVE packet. We don't know how to diagnose since we don't have the datasheet for the chi= p . I checked: 1. The current iwm's init code before waiting alive packet is similar to linux's iwl driver. I don't know if there is a necessary register we should set. 2. I see the version 34 of the loaded ucode from TLV field. That means the system doesn't load an empty file. But, I am not able to confirm if each byte is correct. The current work I have posted on github https://github.com/wjguo/freebsd/pull/1 It is welcome to give ideas of how to make the firmware running successfully. Thanks. Wen-Jun Guo =E6=96=BC 2019=E5=B9=B41=E6=9C=8824=E6= =97=A5 =E9=80=B1=E5=9B=9B =E4=B8=8B=E5=8D=882:31=E5=AF=AB=E9=81=93=EF=BC=9A > Yes. I am checking the difference and fixing the model-specific code for > the new family 9000. > Still, the firmware still responds 0xdead. I saw your work makes iwm > driver more consistent to Linux's iwl. > I will rebase to it and continue my work. > > waddlesplash =E6=96=BC 2019=E5=B9=B41=E6=9C=8824= =E6=97=A5 =E9=80=B1=E5=9B=9B =E4=B8=8B=E5=8D=8812:15=E5=AF=AB=E9=81=93=EF= =BC=9A > >> On Sun, Jan 20, 2019 at 6:52 AM Wen-Chun KUO >> wrote: >> > lwhsu and I are trying to add intel 9560 to iwm(4), the preliminary >> patch >> > adds 9000 series firmware module and skeleton is here: >> >> Hi, >> >> I just submitted and kevans91 just merged a rather large (18 >> individual commits) changeset of DragonFlyBSD changes (ivadasz' work, >> not mine) which refactor quite a bit of iwm's firmware and device >> state tracking code, and bring a lot of it closer to Linux's behavior. >> This might be relevant to your work? >> >> -waddlesplash >> > > > -- > Wen-Jun Guo > > --=20 Wen-Jun Guo