diff for duplicates of <00a501c3e541$c214e4d0$2987110a@lsd.css.fujitsu.com> diff --git a/a/1.txt b/N1/1.txt index 8e21402..a8bbca8 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -50,7 +50,7 @@ Our Plan: - The device will find a parity error. When the device find a parity error, it reports the error in the PCI status - register as "Detected Parity Error = 1". + register as "Detected Parity Error == 1". After the driver did some PIO writes, the driver can notice the error by reading the PCI staus register. @@ -64,7 +64,7 @@ Our Plan: - The device will find a parity error. When the device detected a data parity error, - it set the "Detected Parity Error = 1". + it set the "Detected Parity Error == 1". After a while, the driver check the PCI status register, and knows that there was a data parity error. @@ -79,7 +79,7 @@ Our Plan: and assert PERR signal on the bus. Then the device will notice the error and report it in PCI status register as - "Master Data Parity error = 1". + "Master Data Parity error == 1". - Because the driver can't decide which I/O failed precisely, the recovery method will be reseting the HW and restarting the I/O if possible. diff --git a/a/content_digest b/N1/content_digest index 809464f..77769f1 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -1,6 +1,6 @@ "From\0Hironobu Ishii <ishii.hironobu@jp.fujitsu.com>\0" "Subject\0[RFC/PATCH, 4/4] readX_check() performance evaluation\0" - "Date\0Wed, 28 Jan 2004 01:54:46 +0000\0" + "Date\0Wed, 28 Jan 2004 10:54:46 +0900\0" "To\0linux-kernel <linux-kernel@vger.kernel.org>" " linux-ia64 <linux-ia64@vger.kernel.org>\0" "\00:1\0" @@ -57,7 +57,7 @@ " - The device will find a parity error.\n" " When the device find a parity error, \n" " it reports the error in the PCI status \n" - " register as \"Detected Parity Error = 1\".\n" + " register as \"Detected Parity Error == 1\".\n" " After the driver did some PIO writes,\n" " the driver can notice the error by reading\n" " the PCI staus register.\n" @@ -71,7 +71,7 @@ "\n" " - The device will find a parity error.\n" " When the device detected a data parity error,\n" - " it set the \"Detected Parity Error = 1\".\n" + " it set the \"Detected Parity Error == 1\".\n" "\n" " After a while, the driver check the PCI status\n" " register, and knows that there was a data parity error.\n" @@ -86,7 +86,7 @@ " and assert PERR signal on the bus.\n" " Then the device will notice the error and \n" " report it in PCI status register as \n" - " \"Master Data Parity error = 1\".\n" + " \"Master Data Parity error == 1\".\n" " - Because the driver can't decide which I/O failed\n" " precisely, the recovery method will be reseting the HW\n" " and restarting the I/O if possible.\n" @@ -98,4 +98,4 @@ "Thanks,\n" Hironobu Ishii -8e037f54e942216aae570bbd77be63d27eaa060fc87bc59c653f07952893d532 +ae50e68bf8563d1159702dfc6322d7724a6f606d2aac65034963ab589342c4f2
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.