diff for duplicates of <3143301.IOZImBPhRt@debian64>

diff --git a/a/1.txt b/N1/1.txt
index 8c8633e..12dd39c 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -1,23 +1,24 @@
 On Friday, March 24, 2017 11:09:03 AM CET Sebastian Gottschall wrote:
-> i have a r7800 running. consider to use the board.bin file which is 
+> i have a r7800 running. consider to use the board.bin file which is=20
 > stored in flash memory of the r7800.
-Well, this is a bit beside the point. But what makes you think that 
-what is stored in the flash memory of R7800 is the "board.bin"? 
+Well, this is a bit beside the point. But what makes you think that=20
+what is stored in the flash memory of R7800 is the "board.bin"?=20
 I know that Netgear provided a myriad of different board data files
 with in there GPL drop:
 
 Here's a link:
-<https://github.com/paul-chambers/netgear-r7800/tree/master/git_home/madwifi-11n.git/halphy_tools/host/eepromUtil/release_qca9984/hw1>
+<https://github.com/paul-chambers/netgear-r7800/tree/master/git_home/madwif=
+i-11n.git/halphy_tools/host/eepromUtil/release_qca9984/hw1>
 
 So, does the data in your flash matches any of those files 1:1 or not?
 
-(Note: From what I know, it's the caldata that's in the flash. 
-caldata ≈ cal+board. But I'm asking why ath10k's bmi identification
+(Note: From what I know, it's the caldata that's in the flash.=20
+caldata =E2=89=88 cal+board. But I'm asking why ath10k's bmi identification
 isn't working for those chips right now. And judging from your logs,
-you are using probably a similar WA to the 
+you are using probably a similar WA to the=20
 936-ath10k_skip_otp_check.patch out of necessity as well.)
 
-> there are 2 stored for both cards. you need to patch ath10k to use 
+> there are 2 stored for both cards. you need to patch ath10k to use=20
 > different board.bin files for each card.
 Exactly. Why do you (or anyone for that matter) need to patch ath10k?
 The driver is supposed to support the QCA9984 out of the box, right?
@@ -26,38 +27,45 @@ And I know, that the bmi identification is supposed to work, as
 somebody posted the following log:
 <http://lists.infradead.org/pipermail/lede-dev/2016-December/004987.html>
 
-[  379.392210] ath10k_pci 0002:01:00.0: boot upload otp to 0x1234 len 9000 for board id
-[  379.399945] ath10k_pci 0002:01:00.0: bmi fast download address 0x1234 buffer 0xe1676038 length 9000
+[  379.392210] ath10k_pci 0002:01:00.0: boot upload otp to 0x1234 len 9000 =
+for board id
+[  379.399945] ath10k_pci 0002:01:00.0: bmi fast download address 0x1234 bu=
+ffer 0xe1676038 length 9000
 [  379.408977] ath10k_pci 0002:01:00.0: bmi lz stream start address 0x1234
-[  379.415603] ath10k_pci 0002:01:00.0: bmi lz data buffer 0xe1676038 length 9000
+[  379.415603] ath10k_pci 0002:01:00.0: bmi lz data buffer 0xe1676038 lengt=
+h 9000
 [  379.451626] ath10k_pci 0002:01:00.0: bmi lz stream start address 0x0
-[  379.457985] ath10k_pci 0002:01:00.0: bmi execute address 0x1234 param 0x10
+[  379.457985] ath10k_pci 0002:01:00.0: bmi execute address 0x1234 param 0x=
+10
 [  380.857006] ath10k_pci 0002:01:00.0: bmi execute result 0x400
-[  380.862749] ath10k_pci 0002:01:00.0: boot get otp board id result 0x00000400 board_id 1 chip_id 0
-[  380.871603] ath10k_pci 0002:01:00.0: boot using board name 'bus=pci,bmi-chip-id=0,bmi-board-id=1'
+[  380.862749] ath10k_pci 0002:01:00.0: boot get otp board id result 0x0000=
+0400 board_id 1 chip_id 0
+[  380.871603] ath10k_pci 0002:01:00.0: boot using board name 'bus=3Dpci,bm=
+i-chip-id=3D0,bmi-board-id=3D1'
 [  380.880468] ath10k_pci 0002:01:00.0: board name
-[  380.884999] ath10k_pci 0002:01:00.0: 00000000: 62 75 73 3d 70 63 69 2c 62 6d 69 2d 63 68 69 70  bus=pci,bmi-chip
-[  380.895159] ath10k_pci 0002:01:00.0: 00000010: 2d 69 64 3d 30 2c 62 6d 69 2d 62 6f 61 72 64 2d  -id=0,bmi-board-
-[  380.905317] ath10k_pci 0002:01:00.0: 00000020: 69 64 3d 31                                      id=1
-[  380.914436] ath10k_pci 0002:01:00.0: boot found match for name 'bus=pci,bmi-chip-id=0,bmi-board-id=1'
-[  380.923640] ath10k_pci 0002:01:00.0: boot found board data for 'bus=pci,bmi-chip-id=0,bmi-board-id=1'
+[  380.884999] ath10k_pci 0002:01:00.0: 00000000: 62 75 73 3d 70 63 69 2c 6=
+2 6d 69 2d 63 68 69 70  bus=3Dpci,bmi-chip
+[  380.895159] ath10k_pci 0002:01:00.0: 00000010: 2d 69 64 3d 30 2c 62 6d 6=
+9 2d 62 6f 61 72 64 2d  -id=3D0,bmi-board-
+[  380.905317] ath10k_pci 0002:01:00.0: 00000020: 69 64 3d 31              =
+                        id=3D1
+[  380.914436] ath10k_pci 0002:01:00.0: boot found match for name 'bus=3Dpc=
+i,bmi-chip-id=3D0,bmi-board-id=3D1'
+[  380.923640] ath10k_pci 0002:01:00.0: boot found board data for 'bus=3Dpc=
+i,bmi-chip-id=3D0,bmi-board-id=3D1'
 [  380.932845] ath10k_pci 0002:01:00.0: using board api 2
-...
+=2E..
 
 The board name for the QCA9984 is supposed to look like
-"'bus=pci,bmi-chip-id=0,bmi-board-id=1'"
+"'bus=3Dpci,bmi-chip-id=3D0,bmi-board-id=3D1'"
 
 and not like (from your log):
-> bus=pci,vendor=168c,device=0046,subsystem-vendor=168c,subsystem-device=cafe 
+> bus=3Dpci,vendor=3D168c,device=3D0046,subsystem-vendor=3D168c,subsystem-d=
+evice=3Dcafe=20
 > from ath10k/QCA9984/hw1.0/board-2.bin
 
-> the failed to fetch board data error is normal. 
+> the failed to fetch board data error is normal.=20
 I don't think it is. I think it's a regression.
 
 Thanks,
 Christian
-
-_______________________________________________
-ath10k mailing list
-ath10k@lists.infradead.org
-http://lists.infradead.org/mailman/listinfo/ath10k
diff --git a/a/content_digest b/N1/content_digest
index 3fb2f3b..6d2856b 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -4,36 +4,37 @@
  "Subject\0Re: QCA9984 bmi identification failure\0"
  "Date\0Fri, 24 Mar 2017 16:01:42 +0100\0"
  "To\0Sebastian Gottschall <s.gottschall@dd-wrt.com>\0"
- "Cc\0Adrian Chadd <adrian@freebsd.org>"
-  linux-wireless (linux-wireless@vger.kernel.org) <linux-wireless@vger.kernel.org>
-  ath10k@lists.infradead.org
+ "Cc\0ath10k@lists.infradead.org"
   ath10k-devel <ath10k-devel@qca.qualcomm.com>
+  Michal Kazior <michal.kazior@tieto.com>
   Valo
   Kalle <kvalo@qca.qualcomm.com>
+  linux-wireless (linux-wireless@vger.kernel.org) <linux-wireless@vger.kernel.org>
   hannu.nyman@iki.fi
- " Michal Kazior <michal.kazior@tieto.com>\0"
+ " Adrian Chadd <adrian@freebsd.org>\0"
  "\00:1\0"
  "b\0"
  "On Friday, March 24, 2017 11:09:03 AM CET Sebastian Gottschall wrote:\n"
- "> i have a r7800 running. consider to use the board.bin file which is \n"
+ "> i have a r7800 running. consider to use the board.bin file which is=20\n"
  "> stored in flash memory of the r7800.\n"
- "Well, this is a bit beside the point. But what makes you think that \n"
- "what is stored in the flash memory of R7800 is the \"board.bin\"? \n"
+ "Well, this is a bit beside the point. But what makes you think that=20\n"
+ "what is stored in the flash memory of R7800 is the \"board.bin\"?=20\n"
  "I know that Netgear provided a myriad of different board data files\n"
  "with in there GPL drop:\n"
  "\n"
  "Here's a link:\n"
- "<https://github.com/paul-chambers/netgear-r7800/tree/master/git_home/madwifi-11n.git/halphy_tools/host/eepromUtil/release_qca9984/hw1>\n"
+ "<https://github.com/paul-chambers/netgear-r7800/tree/master/git_home/madwif=\n"
+ "i-11n.git/halphy_tools/host/eepromUtil/release_qca9984/hw1>\n"
  "\n"
  "So, does the data in your flash matches any of those files 1:1 or not?\n"
  "\n"
- "(Note: From what I know, it's the caldata that's in the flash. \n"
- "caldata \342\211\210 cal+board. But I'm asking why ath10k's bmi identification\n"
+ "(Note: From what I know, it's the caldata that's in the flash.=20\n"
+ "caldata =E2=89=88 cal+board. But I'm asking why ath10k's bmi identification\n"
  "isn't working for those chips right now. And judging from your logs,\n"
- "you are using probably a similar WA to the \n"
+ "you are using probably a similar WA to the=20\n"
  "936-ath10k_skip_otp_check.patch out of necessity as well.)\n"
  "\n"
- "> there are 2 stored for both cards. you need to patch ath10k to use \n"
+ "> there are 2 stored for both cards. you need to patch ath10k to use=20\n"
  "> different board.bin files for each card.\n"
  "Exactly. Why do you (or anyone for that matter) need to patch ath10k?\n"
  "The driver is supposed to support the QCA9984 out of the box, right?\n"
@@ -42,40 +43,47 @@
  "somebody posted the following log:\n"
  "<http://lists.infradead.org/pipermail/lede-dev/2016-December/004987.html>\n"
  "\n"
- "[  379.392210] ath10k_pci 0002:01:00.0: boot upload otp to 0x1234 len 9000 for board id\n"
- "[  379.399945] ath10k_pci 0002:01:00.0: bmi fast download address 0x1234 buffer 0xe1676038 length 9000\n"
+ "[  379.392210] ath10k_pci 0002:01:00.0: boot upload otp to 0x1234 len 9000 =\n"
+ "for board id\n"
+ "[  379.399945] ath10k_pci 0002:01:00.0: bmi fast download address 0x1234 bu=\n"
+ "ffer 0xe1676038 length 9000\n"
  "[  379.408977] ath10k_pci 0002:01:00.0: bmi lz stream start address 0x1234\n"
- "[  379.415603] ath10k_pci 0002:01:00.0: bmi lz data buffer 0xe1676038 length 9000\n"
+ "[  379.415603] ath10k_pci 0002:01:00.0: bmi lz data buffer 0xe1676038 lengt=\n"
+ "h 9000\n"
  "[  379.451626] ath10k_pci 0002:01:00.0: bmi lz stream start address 0x0\n"
- "[  379.457985] ath10k_pci 0002:01:00.0: bmi execute address 0x1234 param 0x10\n"
+ "[  379.457985] ath10k_pci 0002:01:00.0: bmi execute address 0x1234 param 0x=\n"
+ "10\n"
  "[  380.857006] ath10k_pci 0002:01:00.0: bmi execute result 0x400\n"
- "[  380.862749] ath10k_pci 0002:01:00.0: boot get otp board id result 0x00000400 board_id 1 chip_id 0\n"
- "[  380.871603] ath10k_pci 0002:01:00.0: boot using board name 'bus=pci,bmi-chip-id=0,bmi-board-id=1'\n"
+ "[  380.862749] ath10k_pci 0002:01:00.0: boot get otp board id result 0x0000=\n"
+ "0400 board_id 1 chip_id 0\n"
+ "[  380.871603] ath10k_pci 0002:01:00.0: boot using board name 'bus=3Dpci,bm=\n"
+ "i-chip-id=3D0,bmi-board-id=3D1'\n"
  "[  380.880468] ath10k_pci 0002:01:00.0: board name\n"
- "[  380.884999] ath10k_pci 0002:01:00.0: 00000000: 62 75 73 3d 70 63 69 2c 62 6d 69 2d 63 68 69 70  bus=pci,bmi-chip\n"
- "[  380.895159] ath10k_pci 0002:01:00.0: 00000010: 2d 69 64 3d 30 2c 62 6d 69 2d 62 6f 61 72 64 2d  -id=0,bmi-board-\n"
- "[  380.905317] ath10k_pci 0002:01:00.0: 00000020: 69 64 3d 31                                      id=1\n"
- "[  380.914436] ath10k_pci 0002:01:00.0: boot found match for name 'bus=pci,bmi-chip-id=0,bmi-board-id=1'\n"
- "[  380.923640] ath10k_pci 0002:01:00.0: boot found board data for 'bus=pci,bmi-chip-id=0,bmi-board-id=1'\n"
+ "[  380.884999] ath10k_pci 0002:01:00.0: 00000000: 62 75 73 3d 70 63 69 2c 6=\n"
+ "2 6d 69 2d 63 68 69 70  bus=3Dpci,bmi-chip\n"
+ "[  380.895159] ath10k_pci 0002:01:00.0: 00000010: 2d 69 64 3d 30 2c 62 6d 6=\n"
+ "9 2d 62 6f 61 72 64 2d  -id=3D0,bmi-board-\n"
+ "[  380.905317] ath10k_pci 0002:01:00.0: 00000020: 69 64 3d 31              =\n"
+ "                        id=3D1\n"
+ "[  380.914436] ath10k_pci 0002:01:00.0: boot found match for name 'bus=3Dpc=\n"
+ "i,bmi-chip-id=3D0,bmi-board-id=3D1'\n"
+ "[  380.923640] ath10k_pci 0002:01:00.0: boot found board data for 'bus=3Dpc=\n"
+ "i,bmi-chip-id=3D0,bmi-board-id=3D1'\n"
  "[  380.932845] ath10k_pci 0002:01:00.0: using board api 2\n"
- "...\n"
+ "=2E..\n"
  "\n"
  "The board name for the QCA9984 is supposed to look like\n"
- "\"'bus=pci,bmi-chip-id=0,bmi-board-id=1'\"\n"
+ "\"'bus=3Dpci,bmi-chip-id=3D0,bmi-board-id=3D1'\"\n"
  "\n"
  "and not like (from your log):\n"
- "> bus=pci,vendor=168c,device=0046,subsystem-vendor=168c,subsystem-device=cafe \n"
+ "> bus=3Dpci,vendor=3D168c,device=3D0046,subsystem-vendor=3D168c,subsystem-d=\n"
+ "evice=3Dcafe=20\n"
  "> from ath10k/QCA9984/hw1.0/board-2.bin\n"
  "\n"
- "> the failed to fetch board data error is normal. \n"
+ "> the failed to fetch board data error is normal.=20\n"
  "I don't think it is. I think it's a regression.\n"
  "\n"
  "Thanks,\n"
- "Christian\n"
- "\n"
- "_______________________________________________\n"
- "ath10k mailing list\n"
- "ath10k@lists.infradead.org\n"
- http://lists.infradead.org/mailman/listinfo/ath10k
+ Christian
 
-f612af229970f986e3b77a30472738ffffe058e69bb82b5e6ef56505946b2dfc
+333b96e22ff1ce7b3c25058f729ba7dae5d4dcaba93f261b26fc8771e18c4910
