All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <4252844.GfFuvxr01B@debian64>

diff --git a/a/1.txt b/N1/1.txt
index 329ad50..a85ccde 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -4,22 +4,28 @@ On Saturday, April 23, 2016 11:44:09 AM Julian Margetson wrote:
 > >> On Friday, April 22, 2016 06:50:44 AM Julian Margetson wrote:
 > >>> On 4/21/2016 4:25 PM, Christian Lamparter wrote:
 > >>>> On Thursday, April 21, 2016 09:15:21 PM Andy Shevchenko wrote:
-> >>>>> The last approach in the commit 8b3444852a2b ("sata_dwc_460ex: 
+> >>>>> The last approach in the commit 8b3444852a2b ("sata_dwc_460ex:=20=
+
 > >>>>> move to generic
-> >>>>> DMA driver") to switch to generic DMA engine API wasn't tested on 
+> >>>>> DMA driver") to switch to generic DMA engine API wasn't tested =
+on=20
 > >>>>> bare metal.
-> >>>>> Besides that we expecting new board support coming with the same 
+> >>>>> Besides that we expecting new board support coming with the sam=
+e=20
 > >>>>> SATA IP but
 > >>>>> with different DMA.
 > >>>>>
-> >>>>> The driver has been tested myself on Sam460ex and WD MyBookLive 
+> >>>>> The driver has been tested myself on Sam460ex and WD MyBookLive=
+=20
 > >>>>> (apollo3g)
-> >>>>> boards. In any case I ask Christian, Måns, and Julian to 
+> >>>>> boards. In any case I ask Christian, M=E5ns, and Julian to=20
 > >>>>> independently test and
 > >>>>> provide Tested-by tag or error report.
-> >>>> I did a test run on my WD MyBook Live. I applied all the patches in
+> >>>> I did a test run on my WD MyBook Live. I applied all the patches=
+ in
 > >>>> this series on top of the topic/dw branch of Vinod Koul:
-> >>>> <https://git.kernel.org/cgit/linux/kernel/git/vkoul/slave-dma.git/>
+> >>>> <https://git.kernel.org/cgit/linux/kernel/git/vkoul/slave-dma.gi=
+t/>
 > >>>>
 > >>>> Tested-by: Christian Lamparter<chunkeey@googlemail.com>
 > >>>> ---
@@ -28,7 +34,8 @@ On Saturday, April 23, 2016 11:44:09 AM Julian Margetson wrote:
 > >>>> # hdparm -t /dev/sda
 > >>>>
 > >>>> /dev/sda:
-> >>>>    Timing buffered disk reads: 204 MB in  3.02 seconds = 67.51 MB/sec
+> >>>>    Timing buffered disk reads: 204 MB in  3.02 seconds =3D 67.51=
+ MB/sec
 > >>>>
 > >>>> # bonnie++ -u mbl
 > >>>> Using uid:1000, gid:1000.
@@ -44,27 +51,38 @@ On Saturday, April 23, 2016 11:44:09 AM Julian Margetson wrote:
 > >>>> Create files in random order...done.
 > >>>> Stat files in random order...done.
 > >>>> Delete files in random order...done.
-> >>>> Version  1.97       ------Sequential Output------ --Sequential 
+> >>>> Version  1.97       ------Sequential Output------ --Sequential=20=
+
 > >>>> Input- --Random-
-> >>>> Concurrency   1     -Per Chr- --Block-- -Rewrite- -Per Chr- 
+> >>>> Concurrency   1     -Per Chr- --Block-- -Rewrite- -Per Chr-=20
 > >>>> --Block-- --Seeks--
-> >>>> Machine        Size K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec 
+> >>>> Machine        Size K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/se=
+c=20
 > >>>> %CP  /sec %CP
-> >>>> mbl            496M    98  99 26011  21 17589  20   538  99 80138  
+> >>>> mbl            496M    98  99 26011  21 17589  20   538  99 8013=
+8 =20
 > >>>> 39 208.9   8
-> >>>> Latency             95267us    1409ms     295ms   26947us 9644us    
+> >>>> Latency             95267us    1409ms     295ms   26947us 9644us=
+   =20
 > >>>> 1787ms
-> >>>> Version  1.97       ------Sequential Create------ --------Random 
+> >>>> Version  1.97       ------Sequential Create------ --------Random=
+=20
 > >>>> Create--------
-> >>>> mbl                 -Create-- --Read--- -Delete-- -Create-- 
+> >>>> mbl                 -Create-- --Read--- -Delete-- -Create--=20
 > >>>> --Read--- -Delete--
-> >>>>                 files  /sec %CP  /sec %CP  /sec %CP  /sec %CP  /sec 
+> >>>>                 files  /sec %CP  /sec %CP  /sec %CP  /sec %CP  /=
+sec=20
 > >>>> %CP  /sec %CP
-> >>>>                    16  6959  78 +++++ +++  5197  40  7250 79 +++++ 
+> >>>>                    16  6959  78 +++++ +++  5197  40  7250 79 +++=
+++=20
 > >>>> +++  4718  37
-> >>>> Latency               149ms    6742us     212ms 177ms     767us     
+> >>>> Latency               149ms    6742us     212ms 177ms     767us =
+   =20
 > >>>> 217ms
-> >>>> 1.97,1.97,mbl,1,1461269771,496M,,98,99,26011,21,17589,20,538,99,80138,39,208.9,8,16,,,,,6959,78,+++++,+++,5197,40,7250,79,+++++,+++,4718,37,95267us,1409ms,295ms,26947us,9644us,1787ms,149ms,6742us,212ms,177ms,767us,217ms 
+> >>>> 1.97,1.97,mbl,1,1461269771,496M,,98,99,26011,21,17589,20,538,99,=
+80138,39,208.9,8,16,,,,,6959,78,+++++,+++,5197,40,7250,79,+++++,+++,471=
+8,37,95267us,1409ms,295ms,26947us,9644us,1787ms,149ms,6742us,212ms,177m=
+s,767us,217ms=20
 > >>>>
 > >>>>
 > >>> Again on copy partitions .
@@ -73,52 +91,67 @@ On Saturday, April 23, 2016 11:44:09 AM Julian Margetson wrote:
 > >> Well, a unrelated driver "m41t80" caused a crash:
 > >> [   12.912739] Oops: Kernel access of bad area, sig: 11 [#3]
 > >> [   12.912743] PREEMPT Canyonlands
-> >> [   12.912753] CPU: 0 PID: 1413 Comm: irq/45-m41t80 Tainted: G      
+> >> [   12.912753] CPU: 0 PID: 1413 Comm: irq/45-m41t80 Tainted: G    =
+ =20
 > >> D         4.6.0-rc4-next-20160421-sam460ex-jm #1
 > >> [   12.912757] task: ea9834e0 ti: eea6c000 task.ti: eea6c000
 > >> [   12.912760] NIP: c0224480 LR: c0023494 CTR: c0042508
-> >> [   12.912764] REGS: eea6daf0 TRAP: 0300   Tainted: G D          
+> >> [   12.912764] REGS: eea6daf0 TRAP: 0300   Tainted: G D         =20=
+
 > >> (4.6.0-rc4-next-20160421-sam460ex-jm)
-> >> [   12.912774] MSR: 00029000 <CE,EE,ME>  CR: 24008282 XER: 00000000
+> >> [   12.912774] MSR: 00029000 <CE,EE,ME>  CR: 24008282 XER: 0000000=
+0
 > >> [   12.912825] DEAR: 00000008 ESR: 00000000
 > >> [...]
 > >> [   12.912927] --- interrupt: 300 at mutex_lock+0x0/0x1c
-> >> [   12.912927]     LR = m41t80_handle_irq+0x28/0xac
+> >> [   12.912927]     LR =3D m41t80_handle_irq+0x28/0xac
 > >> [   12.912932] [eea6de40] [00000000]   (null) (unreliable)
 > >> [   12.912938] [eea6de60] [c004ffac] irq_thread_fn+0x2c/0x48
 > >> [   12.912944] [eea6de80] [c00501cc] irq_thread+0xc4/0x160
 > >> [   12.912951] [eea6ded0] [c003a3f8] kthread+0xc8/0xcc
-> >> [   12.912957] [eea6df40] [c000aee8] ret_from_kernel_thread+0x5c/0x64
+> >> [   12.912957] [eea6df40] [c000aee8] ret_from_kernel_thread+0x5c/0=
+x64
 > >> [   12.912960] Instruction dump:
-> >> [   12.912974] 80010014 7fc3f378 bbc10008 7c0803a6 38210010 4be24ca8 
+> >> [   12.912974] 80010014 7fc3f378 bbc10008 7c0803a6 38210010 4be24c=
+a8=20
 > >> 9421ffd0 7c0802a6
-> >> [   12.912987] bf210014 90010034 3b4302d8 812302ec <83890008> 
+> >> [   12.912987] bf210014 90010034 3b4302d8 812302ec <83890008>=20
 > >> 812302d8 7f9a4840 419e011c
 > >> [   12.912995] Fixing recursive fault but reboot is needed!
 > >>                   ^^^ "reboot is needed!"
 > >>
-> >> Another thing that came to my mind: Have you checked if your hard drive
-> >> and the cables are ok? Are there any pending sectors or suspicious smart
+> >> Another thing that came to my mind: Have you checked if your hard =
+drive
+> >> and the cables are ok? Are there any pending sectors or suspicious=
+ smart
 > >> values? Has the drive passed the extended offline test?
-> >>   Otherwise, I can't reproduce the error with my MyBook system. I've 
+> >>   Otherwise, I can't reproduce the error with my MyBook system. I'=
+ve=20
 > >> tested
-> >> your kernel and it worked on the device without crashing. (I 
+> >> your kernel and it worked on the device without crashing. (I=20
 > >> copied/dd'ed
-> >> 80GB from and back to the hard-drive. It was long and boring, but I 
+> >> 80GB from and back to the hard-drive. It was long and boring, but =
+I=20
 > >> didn't
 > >> encounter any issues and the crc32 matched).
 > >>
-> >> Sorry, but I can't help you if I can't reproduce it... And short of 
+> >> Sorry, but I can't help you if I can't reproduce it... And short o=
+f=20
 > >> sending
-> >> your box to test, I see no efficient way to debug it. However, what I 
+> >> your box to test, I see no efficient way to debug it. However, wha=
+t I=20
 > >> can
-> >> do, if you are interested: I have a few "build your own" My Book Live 
+> >> do, if you are interested: I have a few "build your own" My Book L=
+ive=20
 > >> kits.
-> >> It just needs a 3.5" hard-drive and 12v power adapter. If you are 
+> >> It just needs a 3.5" hard-drive and 12v power adapter. If you are=20=
+
 > >> interested
-> >> PM me off-list, this way you can verify that the kernels you build do 
+> >> PM me off-list, this way you can verify that the kernels you build=
+ do=20
 > >> work,
-> >> just in case this error is due to a hardware issue (zapped controller,
+> >> just in case this error is due to a hardware issue (zapped control=
+ler,
 > >> bad ram/drive/cable?) with your sam460ex box.
 > >>
 > >> Regards,
@@ -126,10 +159,12 @@ On Saturday, April 23, 2016 11:44:09 AM Julian Margetson wrote:
 > >>
 > >>
 > > My Hardware seems ok.
-> > I have swapped cables and drives between the SII3512 pci controller 
+> > I have swapped cables and drives between the SII3512 pci controller=
+=20
 > > and the DWC controller.
 > > No issues when connected to the SII3512 pci controller .
-> > The DWC controller works ok under AmigaOS 4.1FE so that does not 
+> > The DWC controller works ok under AmigaOS 4.1FE so that does not=20=
+
 > > appear to be a problem.
 > >
 > > Regards
@@ -141,16 +176,17 @@ On Saturday, April 23, 2016 11:44:09 AM Julian Margetson wrote:
 > >
 > >
 > Test with kernel compiled with no other sata controllers included.
-> Freshly formatted harddrive  with one ntfs partition. MS-DOs partition 
+> Freshly formatted harddrive  with one ntfs partition. MS-DOs partitio=
+n=20
 > table.
 > Booted from USB thumb drive.
 > Keyboard and mouse freeze as soon as gparted is run.
-> 
+>=20
 
 Well, then. Have you checked for any errata for the sam460ex?
 There's a known errata for the 460EX, with the CPU lockup upon
 high AHB traffic:
-<http://lists.denx.de/pipermail/u-boot/2008-June/036078.html> 
+<http://lists.denx.de/pipermail/u-boot/2008-June/036078.html>=20
 
 "This patch implements a fix provided by AMCC so that the lockup upon
 simultanious traffic on AHB USB OTG, USB 2.0 and SATA doesn't occur
@@ -158,8 +194,8 @@ anymore:..."
 
 This should be fixed by u-boot. However, there's no telling if
 there's more to this workaround in the dma engine. You could try
-to do the testing without anything connected to the USB ports 
+to do the testing without anything connected to the USB ports=20
 and disable/remove all usb hcds modules. As for fixing this:
-I did a quick search but couldn't find any public information. 
+I did a quick search but couldn't find any public information.=20
 There's always support@apm.com (contact them!), or maybe someone
 from the Amiga community knows more?
diff --git a/a/content_digest b/N1/content_digest
index 4ee0652..a919d79 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -20,22 +20,28 @@
  "> >> On Friday, April 22, 2016 06:50:44 AM Julian Margetson wrote:\n"
  "> >>> On 4/21/2016 4:25 PM, Christian Lamparter wrote:\n"
  "> >>>> On Thursday, April 21, 2016 09:15:21 PM Andy Shevchenko wrote:\n"
- "> >>>>> The last approach in the commit 8b3444852a2b (\"sata_dwc_460ex: \n"
+ "> >>>>> The last approach in the commit 8b3444852a2b (\"sata_dwc_460ex:=20=\n"
+ "\n"
  "> >>>>> move to generic\n"
- "> >>>>> DMA driver\") to switch to generic DMA engine API wasn't tested on \n"
+ "> >>>>> DMA driver\") to switch to generic DMA engine API wasn't tested =\n"
+ "on=20\n"
  "> >>>>> bare metal.\n"
- "> >>>>> Besides that we expecting new board support coming with the same \n"
+ "> >>>>> Besides that we expecting new board support coming with the sam=\n"
+ "e=20\n"
  "> >>>>> SATA IP but\n"
  "> >>>>> with different DMA.\n"
  "> >>>>>\n"
- "> >>>>> The driver has been tested myself on Sam460ex and WD MyBookLive \n"
+ "> >>>>> The driver has been tested myself on Sam460ex and WD MyBookLive=\n"
+ "=20\n"
  "> >>>>> (apollo3g)\n"
- "> >>>>> boards. In any case I ask Christian, M\303\245ns, and Julian to \n"
+ "> >>>>> boards. In any case I ask Christian, M=E5ns, and Julian to=20\n"
  "> >>>>> independently test and\n"
  "> >>>>> provide Tested-by tag or error report.\n"
- "> >>>> I did a test run on my WD MyBook Live. I applied all the patches in\n"
+ "> >>>> I did a test run on my WD MyBook Live. I applied all the patches=\n"
+ " in\n"
  "> >>>> this series on top of the topic/dw branch of Vinod Koul:\n"
- "> >>>> <https://git.kernel.org/cgit/linux/kernel/git/vkoul/slave-dma.git/>\n"
+ "> >>>> <https://git.kernel.org/cgit/linux/kernel/git/vkoul/slave-dma.gi=\n"
+ "t/>\n"
  "> >>>>\n"
  "> >>>> Tested-by: Christian Lamparter<chunkeey@googlemail.com>\n"
  "> >>>> ---\n"
@@ -44,7 +50,8 @@
  "> >>>> # hdparm -t /dev/sda\n"
  "> >>>>\n"
  "> >>>> /dev/sda:\n"
- "> >>>>    Timing buffered disk reads: 204 MB in  3.02 seconds = 67.51 MB/sec\n"
+ "> >>>>    Timing buffered disk reads: 204 MB in  3.02 seconds =3D 67.51=\n"
+ " MB/sec\n"
  "> >>>>\n"
  "> >>>> # bonnie++ -u mbl\n"
  "> >>>> Using uid:1000, gid:1000.\n"
@@ -60,27 +67,38 @@
  "> >>>> Create files in random order...done.\n"
  "> >>>> Stat files in random order...done.\n"
  "> >>>> Delete files in random order...done.\n"
- "> >>>> Version  1.97       ------Sequential Output------ --Sequential \n"
+ "> >>>> Version  1.97       ------Sequential Output------ --Sequential=20=\n"
+ "\n"
  "> >>>> Input- --Random-\n"
- "> >>>> Concurrency   1     -Per Chr- --Block-- -Rewrite- -Per Chr- \n"
+ "> >>>> Concurrency   1     -Per Chr- --Block-- -Rewrite- -Per Chr-=20\n"
  "> >>>> --Block-- --Seeks--\n"
- "> >>>> Machine        Size K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec \n"
+ "> >>>> Machine        Size K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/se=\n"
+ "c=20\n"
  "> >>>> %CP  /sec %CP\n"
- "> >>>> mbl            496M    98  99 26011  21 17589  20   538  99 80138  \n"
+ "> >>>> mbl            496M    98  99 26011  21 17589  20   538  99 8013=\n"
+ "8 =20\n"
  "> >>>> 39 208.9   8\n"
- "> >>>> Latency             95267us    1409ms     295ms   26947us 9644us    \n"
+ "> >>>> Latency             95267us    1409ms     295ms   26947us 9644us=\n"
+ "   =20\n"
  "> >>>> 1787ms\n"
- "> >>>> Version  1.97       ------Sequential Create------ --------Random \n"
+ "> >>>> Version  1.97       ------Sequential Create------ --------Random=\n"
+ "=20\n"
  "> >>>> Create--------\n"
- "> >>>> mbl                 -Create-- --Read--- -Delete-- -Create-- \n"
+ "> >>>> mbl                 -Create-- --Read--- -Delete-- -Create--=20\n"
  "> >>>> --Read--- -Delete--\n"
- "> >>>>                 files  /sec %CP  /sec %CP  /sec %CP  /sec %CP  /sec \n"
+ "> >>>>                 files  /sec %CP  /sec %CP  /sec %CP  /sec %CP  /=\n"
+ "sec=20\n"
  "> >>>> %CP  /sec %CP\n"
- "> >>>>                    16  6959  78 +++++ +++  5197  40  7250 79 +++++ \n"
+ "> >>>>                    16  6959  78 +++++ +++  5197  40  7250 79 +++=\n"
+ "++=20\n"
  "> >>>> +++  4718  37\n"
- "> >>>> Latency               149ms    6742us     212ms 177ms     767us     \n"
+ "> >>>> Latency               149ms    6742us     212ms 177ms     767us =\n"
+ "   =20\n"
  "> >>>> 217ms\n"
- "> >>>> 1.97,1.97,mbl,1,1461269771,496M,,98,99,26011,21,17589,20,538,99,80138,39,208.9,8,16,,,,,6959,78,+++++,+++,5197,40,7250,79,+++++,+++,4718,37,95267us,1409ms,295ms,26947us,9644us,1787ms,149ms,6742us,212ms,177ms,767us,217ms \n"
+ "> >>>> 1.97,1.97,mbl,1,1461269771,496M,,98,99,26011,21,17589,20,538,99,=\n"
+ "80138,39,208.9,8,16,,,,,6959,78,+++++,+++,5197,40,7250,79,+++++,+++,471=\n"
+ "8,37,95267us,1409ms,295ms,26947us,9644us,1787ms,149ms,6742us,212ms,177m=\n"
+ "s,767us,217ms=20\n"
  "> >>>>\n"
  "> >>>>\n"
  "> >>> Again on copy partitions .\n"
@@ -89,52 +107,67 @@
  "> >> Well, a unrelated driver \"m41t80\" caused a crash:\n"
  "> >> [   12.912739] Oops: Kernel access of bad area, sig: 11 [#3]\n"
  "> >> [   12.912743] PREEMPT Canyonlands\n"
- "> >> [   12.912753] CPU: 0 PID: 1413 Comm: irq/45-m41t80 Tainted: G      \n"
+ "> >> [   12.912753] CPU: 0 PID: 1413 Comm: irq/45-m41t80 Tainted: G    =\n"
+ " =20\n"
  "> >> D         4.6.0-rc4-next-20160421-sam460ex-jm #1\n"
  "> >> [   12.912757] task: ea9834e0 ti: eea6c000 task.ti: eea6c000\n"
  "> >> [   12.912760] NIP: c0224480 LR: c0023494 CTR: c0042508\n"
- "> >> [   12.912764] REGS: eea6daf0 TRAP: 0300   Tainted: G D          \n"
+ "> >> [   12.912764] REGS: eea6daf0 TRAP: 0300   Tainted: G D         =20=\n"
+ "\n"
  "> >> (4.6.0-rc4-next-20160421-sam460ex-jm)\n"
- "> >> [   12.912774] MSR: 00029000 <CE,EE,ME>  CR: 24008282 XER: 00000000\n"
+ "> >> [   12.912774] MSR: 00029000 <CE,EE,ME>  CR: 24008282 XER: 0000000=\n"
+ "0\n"
  "> >> [   12.912825] DEAR: 00000008 ESR: 00000000\n"
  "> >> [...]\n"
  "> >> [   12.912927] --- interrupt: 300 at mutex_lock+0x0/0x1c\n"
- "> >> [   12.912927]     LR = m41t80_handle_irq+0x28/0xac\n"
+ "> >> [   12.912927]     LR =3D m41t80_handle_irq+0x28/0xac\n"
  "> >> [   12.912932] [eea6de40] [00000000]   (null) (unreliable)\n"
  "> >> [   12.912938] [eea6de60] [c004ffac] irq_thread_fn+0x2c/0x48\n"
  "> >> [   12.912944] [eea6de80] [c00501cc] irq_thread+0xc4/0x160\n"
  "> >> [   12.912951] [eea6ded0] [c003a3f8] kthread+0xc8/0xcc\n"
- "> >> [   12.912957] [eea6df40] [c000aee8] ret_from_kernel_thread+0x5c/0x64\n"
+ "> >> [   12.912957] [eea6df40] [c000aee8] ret_from_kernel_thread+0x5c/0=\n"
+ "x64\n"
  "> >> [   12.912960] Instruction dump:\n"
- "> >> [   12.912974] 80010014 7fc3f378 bbc10008 7c0803a6 38210010 4be24ca8 \n"
+ "> >> [   12.912974] 80010014 7fc3f378 bbc10008 7c0803a6 38210010 4be24c=\n"
+ "a8=20\n"
  "> >> 9421ffd0 7c0802a6\n"
- "> >> [   12.912987] bf210014 90010034 3b4302d8 812302ec <83890008> \n"
+ "> >> [   12.912987] bf210014 90010034 3b4302d8 812302ec <83890008>=20\n"
  "> >> 812302d8 7f9a4840 419e011c\n"
  "> >> [   12.912995] Fixing recursive fault but reboot is needed!\n"
  "> >>                   ^^^ \"reboot is needed!\"\n"
  "> >>\n"
- "> >> Another thing that came to my mind: Have you checked if your hard drive\n"
- "> >> and the cables are ok? Are there any pending sectors or suspicious smart\n"
+ "> >> Another thing that came to my mind: Have you checked if your hard =\n"
+ "drive\n"
+ "> >> and the cables are ok? Are there any pending sectors or suspicious=\n"
+ " smart\n"
  "> >> values? Has the drive passed the extended offline test?\n"
- "> >>   Otherwise, I can't reproduce the error with my MyBook system. I've \n"
+ "> >>   Otherwise, I can't reproduce the error with my MyBook system. I'=\n"
+ "ve=20\n"
  "> >> tested\n"
- "> >> your kernel and it worked on the device without crashing. (I \n"
+ "> >> your kernel and it worked on the device without crashing. (I=20\n"
  "> >> copied/dd'ed\n"
- "> >> 80GB from and back to the hard-drive. It was long and boring, but I \n"
+ "> >> 80GB from and back to the hard-drive. It was long and boring, but =\n"
+ "I=20\n"
  "> >> didn't\n"
  "> >> encounter any issues and the crc32 matched).\n"
  "> >>\n"
- "> >> Sorry, but I can't help you if I can't reproduce it... And short of \n"
+ "> >> Sorry, but I can't help you if I can't reproduce it... And short o=\n"
+ "f=20\n"
  "> >> sending\n"
- "> >> your box to test, I see no efficient way to debug it. However, what I \n"
+ "> >> your box to test, I see no efficient way to debug it. However, wha=\n"
+ "t I=20\n"
  "> >> can\n"
- "> >> do, if you are interested: I have a few \"build your own\" My Book Live \n"
+ "> >> do, if you are interested: I have a few \"build your own\" My Book L=\n"
+ "ive=20\n"
  "> >> kits.\n"
- "> >> It just needs a 3.5\" hard-drive and 12v power adapter. If you are \n"
+ "> >> It just needs a 3.5\" hard-drive and 12v power adapter. If you are=20=\n"
+ "\n"
  "> >> interested\n"
- "> >> PM me off-list, this way you can verify that the kernels you build do \n"
+ "> >> PM me off-list, this way you can verify that the kernels you build=\n"
+ " do=20\n"
  "> >> work,\n"
- "> >> just in case this error is due to a hardware issue (zapped controller,\n"
+ "> >> just in case this error is due to a hardware issue (zapped control=\n"
+ "ler,\n"
  "> >> bad ram/drive/cable?) with your sam460ex box.\n"
  "> >>\n"
  "> >> Regards,\n"
@@ -142,10 +175,12 @@
  "> >>\n"
  "> >>\n"
  "> > My Hardware seems ok.\n"
- "> > I have swapped cables and drives between the SII3512 pci controller \n"
+ "> > I have swapped cables and drives between the SII3512 pci controller=\n"
+ "=20\n"
  "> > and the DWC controller.\n"
  "> > No issues when connected to the SII3512 pci controller .\n"
- "> > The DWC controller works ok under AmigaOS 4.1FE so that does not \n"
+ "> > The DWC controller works ok under AmigaOS 4.1FE so that does not=20=\n"
+ "\n"
  "> > appear to be a problem.\n"
  "> >\n"
  "> > Regards\n"
@@ -157,16 +192,17 @@
  "> >\n"
  "> >\n"
  "> Test with kernel compiled with no other sata controllers included.\n"
- "> Freshly formatted harddrive  with one ntfs partition. MS-DOs partition \n"
+ "> Freshly formatted harddrive  with one ntfs partition. MS-DOs partitio=\n"
+ "n=20\n"
  "> table.\n"
  "> Booted from USB thumb drive.\n"
  "> Keyboard and mouse freeze as soon as gparted is run.\n"
- "> \n"
+ ">=20\n"
  "\n"
  "Well, then. Have you checked for any errata for the sam460ex?\n"
  "There's a known errata for the 460EX, with the CPU lockup upon\n"
  "high AHB traffic:\n"
- "<http://lists.denx.de/pipermail/u-boot/2008-June/036078.html> \n"
+ "<http://lists.denx.de/pipermail/u-boot/2008-June/036078.html>=20\n"
  "\n"
  "\"This patch implements a fix provided by AMCC so that the lockup upon\n"
  "simultanious traffic on AHB USB OTG, USB 2.0 and SATA doesn't occur\n"
@@ -174,10 +210,10 @@
  "\n"
  "This should be fixed by u-boot. However, there's no telling if\n"
  "there's more to this workaround in the dma engine. You could try\n"
- "to do the testing without anything connected to the USB ports \n"
+ "to do the testing without anything connected to the USB ports=20\n"
  "and disable/remove all usb hcds modules. As for fixing this:\n"
- "I did a quick search but couldn't find any public information. \n"
+ "I did a quick search but couldn't find any public information.=20\n"
  "There's always support@apm.com (contact them!), or maybe someone\n"
  from the Amiga community knows more?
 
-a1bb89af8c569c2c2ec84467f092de33bfebbbea7bd9c4dc4a1ed61984920abd
+f3f46283f9caac4acec951fe2a59b11e3e48ccd4e7f00f2d15eec958950f4c0b

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.