From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Tom Psyborg <pozega.tomislav@gmail.com>
Cc: linux-wireless@vger.kernel.org,
Daniel Golle <daniel@makrotopia.org>,
Mathias Kresin <dev@kresin.me>, Felix Fietkau <nbd@nbd.name>
Subject: Re: [PATCH v4 4/8] rt2800: fix registers init for MT7620
Date: Tue, 16 Oct 2018 17:49:58 +0200 [thread overview]
Message-ID: <20181016154957.GA8730@redhat.com> (raw)
In-Reply-To: <CAKR_QVJ9T3EOhMoWPUv3x7-+NS54Y7cCRafM34pqve_4eV-zJQ@mail.gmail.com>
Hello
On Tue, Oct 16, 2018 at 01:32:18PM +0200, Tom Psyborg wrote:
> I am sending you two builds privately so please check if there are any
> differences between the two builds and report back. Thanks.
I extracted rt2800lib.ko module from provided images, did disassembly via:
./staging_dir/toolchain-mipsel_24kc_gcc-7.3.0_musl/bin/mipsel-openwrt-linux-objdump \
-d -r --prefix-addresses ~/rt2800lib-BUILDn.ko > ~/BUILDn.dump.txt
command and compered disassembled code. Here is difference:
$ diff -up BUILD1.dump.txt BUILD2.dump.txt
--- BUILD1.dump.txt 2018-10-16 16:40:34.834220838 +0200
+++ BUILD2.dump.txt 2018-10-16 16:40:40.187219211 +0200
@@ -1,5 +1,5 @@
-/home/stasiu/rt2800lib-BUILD1.ko: file format elf32-tradlittlemips
+/home/stasiu/rt2800lib-BUILD2.ko: file format elf32-tradlittlemips
Disassembly of section .text:
@@ -9374,7 +9374,7 @@ Disassembly of section .text:
00007f80 <rt2800_clear_beacon+0x224> jalr v0
00007f84 <rt2800_clear_beacon+0x228> move a0,s0
00007f88 <rt2800_clear_beacon+0x22c> lhu v1,732(s0)
-00007f8c <rt2800_clear_beacon+0x230> li v0,21392
+00007f8c <rt2800_clear_beacon+0x230> li v0,25426
00007f90 <rt2800_clear_beacon+0x234> bne v1,v0,0000810c <rt2800_clear_beacon+0x3b0>
00007f94 <rt2800_clear_beacon+0x238> li a2,1025
00007f98 <rt2800_clear_beacon+0x23c> lw v0,4(s0)
There is no difference in init_registers (which is inlined in
rt2800_enable_radio). The only difference is in some number
rt2800_clear_beacon() function.
Regards
Stanislaw
next prev parent reply other threads:[~2018-10-16 15:50 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-12 8:56 [PATCH v4 0/8] rt2800: register programing tweaks and clean ups Stanislaw Gruszka
2018-10-12 8:56 ` [PATCH v4 1/8] rt2x00: remove unneeded check Stanislaw Gruszka
2018-10-12 8:56 ` [PATCH v4 2/8] rt2x00: remove confusing AGC register Stanislaw Gruszka
2018-10-12 8:56 ` [PATCH v4 3/8] rt2x00: update TX_SW_CFG2 value Stanislaw Gruszka
2018-10-12 8:56 ` [PATCH v4 4/8] rt2800: fix registers init for MT7620 Stanislaw Gruszka
2018-10-12 10:48 ` Tom Psyborg
2018-10-12 11:36 ` Stanislaw Gruszka
2018-10-12 11:51 ` Tom Psyborg
2018-10-12 12:03 ` Stanislaw Gruszka
2018-10-12 12:20 ` Tom Psyborg
2018-10-12 12:26 ` Stanislaw Gruszka
2018-10-12 12:41 ` Tom Psyborg
2018-10-16 8:09 ` Stanislaw Gruszka
2018-10-16 11:19 ` Felix Fietkau
2018-10-16 11:21 ` Stanislaw Gruszka
2018-10-16 11:25 ` Felix Fietkau
2018-10-16 11:32 ` Tom Psyborg
2018-10-16 15:49 ` Stanislaw Gruszka [this message]
2018-10-17 13:25 ` Tom Psyborg
2018-10-19 9:00 ` Stanislaw Gruszka
2018-10-19 14:21 ` Tom Psyborg
2018-10-20 9:44 ` Stanislaw Gruszka
2018-10-18 15:51 ` Tom Psyborg
2018-10-16 8:11 ` Stanislaw Gruszka
2018-10-16 10:38 ` Daniel Golle
2018-11-02 2:07 ` [PATCH] mips: ralink: add accessors for MT7620 chipver and pkg Daniel Golle
2018-11-05 18:36 ` Paul Burton
2018-11-05 20:19 ` Daniel Golle
2018-11-05 23:05 ` Paul Burton
2018-11-05 23:27 ` Tom Psyborg
2018-10-13 9:46 ` [PATCH v4 4/8] rt2800: fix registers init for MT7620 Kalle Valo
2018-10-16 8:02 ` Stanislaw Gruszka
2018-10-12 8:56 ` [PATCH v4 5/8] rt2800: enable TX_PIN_CFG_LNA_PE_ bits per band Stanislaw Gruszka
2018-10-12 8:56 ` [PATCH v4 6/8] rt2800: enable TX_PIN_CFG_RFRX_EN only for MT7620 Stanislaw Gruszka
2018-10-12 10:52 ` Tom Psyborg
2018-10-12 11:38 ` Stanislaw Gruszka
2018-10-12 8:56 ` [PATCH v4 7/8] rt2800: remove unneeded RT6352 check Stanislaw Gruszka
2018-10-12 8:56 ` [PATCH v4 8/8] rt2800: comment and simplify AGC init for RT6352 Stanislaw Gruszka
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=20181016154957.GA8730@redhat.com \
--to=sgruszka@redhat.com \
--cc=daniel@makrotopia.org \
--cc=dev@kresin.me \
--cc=linux-wireless@vger.kernel.org \
--cc=nbd@nbd.name \
--cc=pozega.tomislav@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.