diff for duplicates of <48A19788.6050502@harris.com>

diff --git a/a/1.1.hdr b/a/1.1.hdr
deleted file mode 100644
index 325c5b0..0000000
--- a/a/1.1.hdr
+++ /dev/null
@@ -1,2 +0,0 @@
-Content-Type: text/plain; charset=UTF-8
-Content-Transfer-Encoding: 7bit
diff --git a/a/1.2.hdr b/a/1.2.hdr
deleted file mode 100644
index 6a9de1e..0000000
--- a/a/1.2.hdr
+++ /dev/null
@@ -1,2 +0,0 @@
-Content-Type: text/html; charset=UTF-8
-Content-Transfer-Encoding: quoted-printable
diff --git a/a/1.1.txt b/N1/1.txt
similarity index 100%
rename from a/1.1.txt
rename to N1/1.txt
diff --git a/a/1.2.bin b/N1/2.bin
similarity index 100%
rename from a/1.2.bin
rename to N1/2.bin
diff --git a/a/2.hdr b/N1/2.hdr
index 4b86001..e9e8314 100644
--- a/a/2.hdr
+++ b/N1/2.hdr
@@ -1,4 +1,2 @@
-Content-Type: text/plain; charset="us-ascii"
-MIME-Version: 1.0
-Content-Transfer-Encoding: 7bit
-Content-Disposition: inline
+Content-Type: text/html; charset=UTF-8
+Content-Transfer-Encoding: 8bit
diff --git a/a/2.txt b/a/2.txt
deleted file mode 100644
index 2e03888..0000000
--- a/a/2.txt
+++ /dev/null
@@ -1,4 +0,0 @@
-_______________________________________________
-Linuxppc-dev mailing list
-Linuxppc-dev@ozlabs.org
-https://ozlabs.org/mailman/listinfo/linuxppc-dev
diff --git a/a/content_digest b/N1/content_digest
index e700999..5b14731 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -12,7 +12,7 @@
   Sparks
   Sam <SSparks@aclaratech.com>
  " linux-ide@vger.kernel.org\0"
- "\02:1.1\0"
+ "\01:1\0"
  "b\0"
  "Benjamin Herrenschmidt wrote:\n"
  ">   \n"
@@ -64,82 +64,76 @@
  "correct - byte lanes, read/write signaling, timing, etc.  Curious.\n"
  "\n"
      Steve
- "\02:1.2\0"
- "b\0"
- "<!DOCTYPE html PUBLIC \"-//W3C//DTD HTML 4.01 Transitional//EN\">\r\n"
- "<html>\r\n"
- "<head>\r\n"
- "  <meta content=\"text/html;charset=UTF-8\" http-equiv=\"Content-Type\">\r\n"
- "</head>\r\n"
- "<body bgcolor=\"#ffffff\" text=\"#000000\">\r\n"
- "Benjamin Herrenschmidt wrote:\r\n"
- "<blockquote cite=\"mid:1218492032.8041.11.camel@pasglop\" type=\"cite\">\r\n"
- "  <pre wrap=\"\">\r\n"
- "  </pre>\r\n"
- "  <blockquote type=\"cite\">\r\n"
- "    <pre wrap=\"\">1. IDE status read does not work. (But am I understand correctly\r\n"
- "   that IDE works well if IRQ is unspecified? Then this is hardly\r\n"
- "   an issue.)\r\n"
- "2. IDE interrupt comes when it should not. I'd recommend to use\r\n"
- "   oscilloscope to find out what is happening there, that is, if\r\n"
- "   the drive actually deasserts its irq line after status read.\r\n"
- "   If so, than this could be a PIC problem.\r\n"
- "\r\n"
- "What is the platform on which you're observing the issue, btw?\r\n"
- "    </pre>\r\n"
- "  </blockquote>\r\n"
- "  <pre wrap=\"\"><!---->\r\n"
- "Another possibility is that you got the wrong interrupt number\r\n"
- "in the device-tree...\r\n"
- "\r\n"
- "Ben.\r\n"
- "  </pre>\r\n"
- "</blockquote>\r\n"
- "<br>\r\n"
- "<tt>The platform is the AMCC Sequoia board.\302\240 We've built a little\r\n"
- "adapter to connect a compact flash card to the processor bus.\302\240 I\r\n"
- "believe the interrupt selection in the device tree is correct, and I've\r\n"
- "checked over the u-boot settings for the IRQ line (active high, level\r\n"
- "sensitive).\302\240 I've also tried edge-sensitive but it doesn't make a\r\n"
- "difference.<br>\r\n"
- "<br>\r\n"
- "When u-boot queries the CF card, we see the IRQ pulse as expected, but\r\n"
- "when the kernel runs, we see the IRQ go high and stay there, which the\r\n"
- "kernel naturally treats as a stuck interrupt.\302\240 The other oddity is that\r\n"
- "we see a single diagnostic failure on startup:<br>\r\n"
- "<br>\r\n"
- "</tt>\r\n"
- "<blockquote><tt>ata1.00: Drive reports diagnostics failure. This may\r\n"
- "indicate a drive</tt><br>\r\n"
- "  <tt>ata1.00: fault or invalid emulation. Contact drive vendor for\r\n"
- "information.</tt><br>\r\n"
- "</blockquote>\r\n"
- "<tt><br>\r\n"
- "That is strange, because if we manually do the soft reset from u-boot,\r\n"
- "we see the ATA \"feature byte\" return 0x01, which means success.\302\240 When\r\n"
- "the kernel does the soft reset, we see a 0x00, which means failure.\302\240\r\n"
- "You would think it is timing related, but a logic analyzer trace shows\r\n"
- "reasonable timing.\302\240 We need to wire up a better test rig, so I don't\r\n"
- "want folks on this list to waste any time on it.\302\240 I'll report back if I\r\n"
- "learn anything of general interest.<br>\r\n"
- "<br>\r\n"
- "With the interrupt disabled in the device tree, and ignoring the\r\n"
- "diagnostics failure, the drive actually works.\302\240 I'm able to mount a\r\n"
- "filesystem, read files from it, etc.\302\240 So, the drive is fully\r\n"
- "functional, just without using interrupts.\302\240 Therefore, I believe most\r\n"
- "everything is correct - byte lanes, read/write signaling, timing, etc.\302\240\r\n"
- "Curious.<br>\r\n"
- "<br>\r\n"
- "\302\240\302\240\302\240 Steve<br>\r\n"
- "<br>\r\n"
- "</tt>\r\n"
- "</body>\r\n"
- "</html>\r\n"
  "\01:2\0"
  "b\0"
- "_______________________________________________\n"
- "Linuxppc-dev mailing list\n"
- "Linuxppc-dev@ozlabs.org\n"
- https://ozlabs.org/mailman/listinfo/linuxppc-dev
+ "<!DOCTYPE html PUBLIC \"-//W3C//DTD HTML 4.01 Transitional//EN\">\n"
+ "<html>\n"
+ "<head>\n"
+ "  <meta content=\"text/html;charset=UTF-8\" http-equiv=\"Content-Type\">\n"
+ "</head>\n"
+ "<body bgcolor=\"#ffffff\" text=\"#000000\">\n"
+ "Benjamin Herrenschmidt wrote:\n"
+ "<blockquote cite=\"mid:1218492032.8041.11.camel@pasglop\" type=\"cite\">\n"
+ "  <pre wrap=\"\">\n"
+ "  </pre>\n"
+ "  <blockquote type=\"cite\">\n"
+ "    <pre wrap=\"\">1. IDE status read does not work. (But am I understand correctly\n"
+ "   that IDE works well if IRQ is unspecified? Then this is hardly\n"
+ "   an issue.)\n"
+ "2. IDE interrupt comes when it should not. I'd recommend to use\n"
+ "   oscilloscope to find out what is happening there, that is, if\n"
+ "   the drive actually deasserts its irq line after status read.\n"
+ "   If so, than this could be a PIC problem.\n"
+ "\n"
+ "What is the platform on which you're observing the issue, btw?\n"
+ "    </pre>\n"
+ "  </blockquote>\n"
+ "  <pre wrap=\"\"><!---->\n"
+ "Another possibility is that you got the wrong interrupt number\n"
+ "in the device-tree...\n"
+ "\n"
+ "Ben.\n"
+ "  </pre>\n"
+ "</blockquote>\n"
+ "<br>\n"
+ "<tt>The platform is the AMCC Sequoia board.\302\240 We've built a little\n"
+ "adapter to connect a compact flash card to the processor bus.\302\240 I\n"
+ "believe the interrupt selection in the device tree is correct, and I've\n"
+ "checked over the u-boot settings for the IRQ line (active high, level\n"
+ "sensitive).\302\240 I've also tried edge-sensitive but it doesn't make a\n"
+ "difference.<br>\n"
+ "<br>\n"
+ "When u-boot queries the CF card, we see the IRQ pulse as expected, but\n"
+ "when the kernel runs, we see the IRQ go high and stay there, which the\n"
+ "kernel naturally treats as a stuck interrupt.\302\240 The other oddity is that\n"
+ "we see a single diagnostic failure on startup:<br>\n"
+ "<br>\n"
+ "</tt>\n"
+ "<blockquote><tt>ata1.00: Drive reports diagnostics failure. This may\n"
+ "indicate a drive</tt><br>\n"
+ "  <tt>ata1.00: fault or invalid emulation. Contact drive vendor for\n"
+ "information.</tt><br>\n"
+ "</blockquote>\n"
+ "<tt><br>\n"
+ "That is strange, because if we manually do the soft reset from u-boot,\n"
+ "we see the ATA \"feature byte\" return 0x01, which means success.\302\240 When\n"
+ "the kernel does the soft reset, we see a 0x00, which means failure.\302\240\n"
+ "You would think it is timing related, but a logic analyzer trace shows\n"
+ "reasonable timing.\302\240 We need to wire up a better test rig, so I don't\n"
+ "want folks on this list to waste any time on it.\302\240 I'll report back if I\n"
+ "learn anything of general interest.<br>\n"
+ "<br>\n"
+ "With the interrupt disabled in the device tree, and ignoring the\n"
+ "diagnostics failure, the drive actually works.\302\240 I'm able to mount a\n"
+ "filesystem, read files from it, etc.\302\240 So, the drive is fully\n"
+ "functional, just without using interrupts.\302\240 Therefore, I believe most\n"
+ "everything is correct - byte lanes, read/write signaling, timing, etc.\302\240\n"
+ "Curious.<br>\n"
+ "<br>\n"
+ "\302\240\302\240\302\240 Steve<br>\n"
+ "<br>\n"
+ "</tt>\n"
+ "</body>\n"
+ "</html>\n"
 
-218f125eed9479a181570c19a752010afe2e50ecacd481e40561d2b6ee1d141a
+a619090619589c20c24559cfed7aba738a71d036f53fb08eadfe6cca340dee07
