diff for duplicates of <54E74BF6.208@hurleysoftware.com> diff --git a/a/1.txt b/N1/1.txt index a120fb4..c21ea16 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -2,17 +2,17 @@ On 02/20/2015 09:35 AM, Ludovic Desroches wrote: > On Fri, Feb 20, 2015 at 09:21:38AM -0500, Peter Hurley wrote: >> On 02/19/2015 12:38 PM, Pantelis Antoniou wrote: >>> ->>>> On Feb 19, 2015, at 19:30 , Frank Rowand <frowand.list@gmail.com> wrote: +>>>> On Feb 19, 2015, at 19:30 , Frank Rowand <frowand.list-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: >>>> >>>> On 2/19/2015 9:00 AM, Pantelis Antoniou wrote: >>>>> Hi Frank, >>>>> ->>>>>> On Feb 19, 2015, at 18:48 , Frank Rowand <frowand.list@gmail.com> wrote: +>>>>>> On Feb 19, 2015, at 18:48 , Frank Rowand <frowand.list-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: >>>>>> >>>>>> On 2/19/2015 6:29 AM, Pantelis Antoniou wrote: >>>>>>> Hi Mark, >>>>>>> ->>>>>>>> On Feb 18, 2015, at 19:31 , Mark Rutland <mark.rutland@arm.com> wrote: +>>>>>>>> On Feb 18, 2015, at 19:31 , Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org> wrote: >>>>>>>> >>>>>>>>>>> +While this may in theory work, in practice it is very cumbersome >>>>>>>>>>> +for the following reasons: @@ -33,10 +33,10 @@ On 02/20/2015 09:35 AM, Ludovic Desroches wrote: >>>>>>>> the FW/bootloader could be common even if the DTB couldn't. >>>>>>>> >>>>>>>> To some extent there must be a DTB that will work across all variants ->>>>>>>> (albeit with limited utility) or the quirk approach wouldn't work? +>>>>>>>> (albeit with limited utility) or the quirk approach wouldn't work… >>>>>>>> >>>>>>> ->>>>>>> That?s not correct; the only part of the DTB that needs to be common +>>>>>>> That’s not correct; the only part of the DTB that needs to be common >>>>>>> is the model property that would allow the quirk detection logic to fire. >>>>>>> >>>>>>> So, there is a base DTB that will work on all variants, but that only means @@ -65,8 +65,8 @@ On 02/20/2015 09:35 AM, Ludovic Desroches wrote: >>>>>>>>>> appended DTB if it's not possible to update the board configuration. >>>>>>>>>> >>>>>>>>> ->>>>>>>>> You?re missing the point. I can?t use the same DTB for each revision of the ->>>>>>>>> board. Each board is similar but it?s not identical. +>>>>>>>>> You’re missing the point. I can’t use the same DTB for each revision of the +>>>>>>>>> board. Each board is similar but it’s not identical. >>>>>>>> >>>>>>>> I think you've misunderstood my point. If you program the board with the >>>>>>>> relevant DTB, or use appended DTB, then you will pass the correct DTB to @@ -77,7 +77,7 @@ On 02/20/2015 09:35 AM, Ludovic Desroches wrote: >>>>>>> >>>>>>> In theory it might work, in practice this does not. Ludovic mentioned that they >>>>>>> have 27 different DTBs in use at the moment. At a relatively common 60k per DTB ->>>>>>> that?s 27x60k = 1.6MB of DTBs, that need to be installed. +>>>>>>> that’s 27x60k = 1.6MB of DTBs, that need to be installed. >>>>>> >>>>>> < snip > >>>>>> @@ -92,7 +92,7 @@ On 02/20/2015 09:35 AM, Ludovic Desroches wrote: >>>>> >>>>> Trust no-one. >>>>> ->>>>> This is one of those things that the kernel community doesn?t understand which makes people +>>>>> This is one of those things that the kernel community doesn’t understand which makes people >>>>> who push product quite mad. >>>>> >>>>> Engineering a product is not only about meeting customer spec, in order to turn a profit @@ -100,7 +100,7 @@ On 02/20/2015 09:35 AM, Ludovic Desroches wrote: >>>>> >>>>> Yes, you can always manually install files in the bootloader. For 1 board no problem. >>>>> For 10 doable. For 100 I guess you can hire an extra guy. For 1 million? Guess what, ->>>>> instead of turning a profit you?re losing money if you only have a few cents of profit +>>>>> instead of turning a profit you’re losing money if you only have a few cents of profit >>>>> per unit. >>>> >>>> I'm not installing physical components manually. Why would I be installing software @@ -112,7 +112,7 @@ On 02/20/2015 09:35 AM, Ludovic Desroches wrote: >>> Having a single binary to flash to every revision of the board makes logistics considerably >>> easier. >>> ->>> Having to boot and tweak the bootloader settings to select the correct dtb (even if it?s present +>>> Having to boot and tweak the bootloader settings to select the correct dtb (even if it’s present >>> on the flash medium) takes time and is error-prone. >>> >>> Factory time == money, errors == money. @@ -124,9 +124,9 @@ On 02/20/2015 09:35 AM, Ludovic Desroches wrote: >>>> And you produce a few million units before testing that the first one off the line works? >>>> >>> ->>> The first one off the line works. The rest will get some burn in and functional testing if you?re +>>> The first one off the line works. The rest will get some burn in and functional testing if you’re >>> lucky. In many cases where the product is very cheap it might make financial sense to just ship ->>> as is and deal with recalls, if you?re reasonably happy after a little bit of statistical sampling. +>>> as is and deal with recalls, if you’re reasonably happy after a little bit of statistical sampling. >>> >>> Hardware is hard :) >> @@ -165,3 +165,8 @@ the i2c driver or mixing DTS fragments for different designs as increased risk >> >> Regards, >> Peter Hurley + +-- +To unsubscribe from this list: send the line "unsubscribe devicetree" in +the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org +More majordomo info at http://vger.kernel.org/majordomo-info.html diff --git a/a/content_digest b/N1/content_digest index 6fb7bbb..a0440ca 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -9,27 +9,39 @@ "ref\053F2F94C-0C43-4A54-B8CD-EEC454A0AC19@konsulko.com\0" "ref\054E742F2.80506@hurleysoftware.com\0" "ref\020150220143533.GA29908@odux.rfo.atmel.com\0" - "From\0peter@hurleysoftware.com (Peter Hurley)\0" - "Subject\0[PATCH 2/4] of: DT quirks infrastructure\0" + "ref\020150220143533.GA29908-FuRPzXQv2LUWBfJKYY8PcdBPR1lH4CV8@public.gmane.org\0" + "From\0Peter Hurley <peter-WaGBZJeGNqdsbIuE7sb01tBPR1lH4CV8@public.gmane.org>\0" + "Subject\0Re: [PATCH 2/4] of: DT quirks infrastructure\0" "Date\0Fri, 20 Feb 2015 10:00:06 -0500\0" - "To\0linux-arm-kernel@lists.infradead.org\0" + "To\0Pantelis Antoniou <pantelis.antoniou-OWPKS81ov/FWk0Htik3J/w@public.gmane.org>" + frowand.list-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org + Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org> + devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org <devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org> + Tony Lindgren <tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org> + Koen Kooi <koen-QLwJDigV5abLmq1fohREcCpxlwaOVQ5f@public.gmane.org> + Nicolas Ferre <nicolas.ferre-AIFe0yeh4nAAvxtiuMwx3w@public.gmane.org> + linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org> + Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org> + linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org <linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org> + Matt Porter <matt.porter-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org> + " Guenter Roeck <linux-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>\0" "\00:1\0" "b\0" "On 02/20/2015 09:35 AM, Ludovic Desroches wrote:\n" "> On Fri, Feb 20, 2015 at 09:21:38AM -0500, Peter Hurley wrote:\n" ">> On 02/19/2015 12:38 PM, Pantelis Antoniou wrote:\n" ">>>\n" - ">>>> On Feb 19, 2015, at 19:30 , Frank Rowand <frowand.list@gmail.com> wrote:\n" + ">>>> On Feb 19, 2015, at 19:30 , Frank Rowand <frowand.list-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:\n" ">>>>\n" ">>>> On 2/19/2015 9:00 AM, Pantelis Antoniou wrote:\n" ">>>>> Hi Frank,\n" ">>>>>\n" - ">>>>>> On Feb 19, 2015, at 18:48 , Frank Rowand <frowand.list@gmail.com> wrote:\n" + ">>>>>> On Feb 19, 2015, at 18:48 , Frank Rowand <frowand.list-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:\n" ">>>>>>\n" ">>>>>> On 2/19/2015 6:29 AM, Pantelis Antoniou wrote:\n" ">>>>>>> Hi Mark,\n" ">>>>>>>\n" - ">>>>>>>> On Feb 18, 2015, at 19:31 , Mark Rutland <mark.rutland@arm.com> wrote:\n" + ">>>>>>>> On Feb 18, 2015, at 19:31 , Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org> wrote:\n" ">>>>>>>>\n" ">>>>>>>>>>> +While this may in theory work, in practice it is very cumbersome\n" ">>>>>>>>>>> +for the following reasons:\n" @@ -50,10 +62,10 @@ ">>>>>>>> the FW/bootloader could be common even if the DTB couldn't.\n" ">>>>>>>>\n" ">>>>>>>> To some extent there must be a DTB that will work across all variants\n" - ">>>>>>>> (albeit with limited utility) or the quirk approach wouldn't work?\n" + ">>>>>>>> (albeit with limited utility) or the quirk approach wouldn't work\342\200\246\n" ">>>>>>>>\n" ">>>>>>>\n" - ">>>>>>> That?s not correct; the only part of the DTB that needs to be common\n" + ">>>>>>> That\342\200\231s not correct; the only part of the DTB that needs to be common\n" ">>>>>>> is the model property that would allow the quirk detection logic to fire.\n" ">>>>>>>\n" ">>>>>>> So, there is a base DTB that will work on all variants, but that only means\n" @@ -82,8 +94,8 @@ ">>>>>>>>>> appended DTB if it's not possible to update the board configuration.\n" ">>>>>>>>>>\n" ">>>>>>>>>\n" - ">>>>>>>>> You?re missing the point. I can?t use the same DTB for each revision of the\n" - ">>>>>>>>> board. Each board is similar but it?s not identical.\n" + ">>>>>>>>> You\342\200\231re missing the point. I can\342\200\231t use the same DTB for each revision of the\n" + ">>>>>>>>> board. Each board is similar but it\342\200\231s not identical.\n" ">>>>>>>>\n" ">>>>>>>> I think you've misunderstood my point. If you program the board with the\n" ">>>>>>>> relevant DTB, or use appended DTB, then you will pass the correct DTB to\n" @@ -94,7 +106,7 @@ ">>>>>>>\n" ">>>>>>> In theory it might work, in practice this does not. Ludovic mentioned that they\n" ">>>>>>> have 27 different DTBs in use at the moment. At a relatively common 60k per DTB\n" - ">>>>>>> that?s 27x60k = 1.6MB of DTBs, that need to be installed.\n" + ">>>>>>> that\342\200\231s 27x60k = 1.6MB of DTBs, that need to be installed.\n" ">>>>>>\n" ">>>>>> < snip >\n" ">>>>>>\n" @@ -109,7 +121,7 @@ ">>>>>\n" ">>>>> Trust no-one.\n" ">>>>>\n" - ">>>>> This is one of those things that the kernel community doesn?t understand which makes people\n" + ">>>>> This is one of those things that the kernel community doesn\342\200\231t understand which makes people\n" ">>>>> who push product quite mad.\n" ">>>>>\n" ">>>>> Engineering a product is not only about meeting customer spec, in order to turn a profit\n" @@ -117,7 +129,7 @@ ">>>>>\n" ">>>>> Yes, you can always manually install files in the bootloader. For 1 board no problem.\n" ">>>>> For 10 doable. For 100 I guess you can hire an extra guy. For 1 million? Guess what,\n" - ">>>>> instead of turning a profit you?re losing money if you only have a few cents of profit\n" + ">>>>> instead of turning a profit you\342\200\231re losing money if you only have a few cents of profit\n" ">>>>> per unit.\n" ">>>>\n" ">>>> I'm not installing physical components manually. Why would I be installing software\n" @@ -129,7 +141,7 @@ ">>> Having a single binary to flash to every revision of the board makes logistics considerably\n" ">>> easier.\n" ">>>\n" - ">>> Having to boot and tweak the bootloader settings to select the correct dtb (even if it?s present\n" + ">>> Having to boot and tweak the bootloader settings to select the correct dtb (even if it\342\200\231s present\n" ">>> on the flash medium) takes time and is error-prone.\n" ">>>\n" ">>> Factory time == money, errors == money.\n" @@ -141,9 +153,9 @@ ">>>> And you produce a few million units before testing that the first one off the line works?\n" ">>>>\n" ">>>\n" - ">>> The first one off the line works. The rest will get some burn in and functional testing if you?re\n" + ">>> The first one off the line works. The rest will get some burn in and functional testing if you\342\200\231re\n" ">>> lucky. In many cases where the product is very cheap it might make financial sense to just ship\n" - ">>> as is and deal with recalls, if you?re reasonably happy after a little bit of statistical sampling.\n" + ">>> as is and deal with recalls, if you\342\200\231re reasonably happy after a little bit of statistical sampling.\n" ">>>\n" ">>> Hardware is hard :)\n" ">>\n" @@ -181,6 +193,11 @@ ">> IOW, your QA process will not change at all == same cost.\n" ">>\n" ">> Regards,\n" - >> Peter Hurley + ">> Peter Hurley\n" + "\n" + "--\n" + "To unsubscribe from this list: send the line \"unsubscribe devicetree\" in\n" + "the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org\n" + More majordomo info at http://vger.kernel.org/majordomo-info.html -f242cee94d2060aa2eae6571dc1e612e20ca1ff221593d2baf94b3b510114575 +8999d17776e7727f42a73d659f47ea92fe97b9ae3707c28699f4b07552ddbd41
diff --git a/a/1.txt b/N2/1.txt index a120fb4..857600e 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -33,10 +33,10 @@ On 02/20/2015 09:35 AM, Ludovic Desroches wrote: >>>>>>>> the FW/bootloader could be common even if the DTB couldn't. >>>>>>>> >>>>>>>> To some extent there must be a DTB that will work across all variants ->>>>>>>> (albeit with limited utility) or the quirk approach wouldn't work? +>>>>>>>> (albeit with limited utility) or the quirk approach wouldn't work… >>>>>>>> >>>>>>> ->>>>>>> That?s not correct; the only part of the DTB that needs to be common +>>>>>>> That’s not correct; the only part of the DTB that needs to be common >>>>>>> is the model property that would allow the quirk detection logic to fire. >>>>>>> >>>>>>> So, there is a base DTB that will work on all variants, but that only means @@ -65,8 +65,8 @@ On 02/20/2015 09:35 AM, Ludovic Desroches wrote: >>>>>>>>>> appended DTB if it's not possible to update the board configuration. >>>>>>>>>> >>>>>>>>> ->>>>>>>>> You?re missing the point. I can?t use the same DTB for each revision of the ->>>>>>>>> board. Each board is similar but it?s not identical. +>>>>>>>>> You’re missing the point. I can’t use the same DTB for each revision of the +>>>>>>>>> board. Each board is similar but it’s not identical. >>>>>>>> >>>>>>>> I think you've misunderstood my point. If you program the board with the >>>>>>>> relevant DTB, or use appended DTB, then you will pass the correct DTB to @@ -77,7 +77,7 @@ On 02/20/2015 09:35 AM, Ludovic Desroches wrote: >>>>>>> >>>>>>> In theory it might work, in practice this does not. Ludovic mentioned that they >>>>>>> have 27 different DTBs in use at the moment. At a relatively common 60k per DTB ->>>>>>> that?s 27x60k = 1.6MB of DTBs, that need to be installed. +>>>>>>> that’s 27x60k = 1.6MB of DTBs, that need to be installed. >>>>>> >>>>>> < snip > >>>>>> @@ -92,7 +92,7 @@ On 02/20/2015 09:35 AM, Ludovic Desroches wrote: >>>>> >>>>> Trust no-one. >>>>> ->>>>> This is one of those things that the kernel community doesn?t understand which makes people +>>>>> This is one of those things that the kernel community doesn’t understand which makes people >>>>> who push product quite mad. >>>>> >>>>> Engineering a product is not only about meeting customer spec, in order to turn a profit @@ -100,7 +100,7 @@ On 02/20/2015 09:35 AM, Ludovic Desroches wrote: >>>>> >>>>> Yes, you can always manually install files in the bootloader. For 1 board no problem. >>>>> For 10 doable. For 100 I guess you can hire an extra guy. For 1 million? Guess what, ->>>>> instead of turning a profit you?re losing money if you only have a few cents of profit +>>>>> instead of turning a profit you’re losing money if you only have a few cents of profit >>>>> per unit. >>>> >>>> I'm not installing physical components manually. Why would I be installing software @@ -112,7 +112,7 @@ On 02/20/2015 09:35 AM, Ludovic Desroches wrote: >>> Having a single binary to flash to every revision of the board makes logistics considerably >>> easier. >>> ->>> Having to boot and tweak the bootloader settings to select the correct dtb (even if it?s present +>>> Having to boot and tweak the bootloader settings to select the correct dtb (even if it’s present >>> on the flash medium) takes time and is error-prone. >>> >>> Factory time == money, errors == money. @@ -124,9 +124,9 @@ On 02/20/2015 09:35 AM, Ludovic Desroches wrote: >>>> And you produce a few million units before testing that the first one off the line works? >>>> >>> ->>> The first one off the line works. The rest will get some burn in and functional testing if you?re +>>> The first one off the line works. The rest will get some burn in and functional testing if you’re >>> lucky. In many cases where the product is very cheap it might make financial sense to just ship ->>> as is and deal with recalls, if you?re reasonably happy after a little bit of statistical sampling. +>>> as is and deal with recalls, if you’re reasonably happy after a little bit of statistical sampling. >>> >>> Hardware is hard :) >> diff --git a/a/content_digest b/N2/content_digest index 6fb7bbb..aad974a 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -9,10 +9,21 @@ "ref\053F2F94C-0C43-4A54-B8CD-EEC454A0AC19@konsulko.com\0" "ref\054E742F2.80506@hurleysoftware.com\0" "ref\020150220143533.GA29908@odux.rfo.atmel.com\0" - "From\0peter@hurleysoftware.com (Peter Hurley)\0" - "Subject\0[PATCH 2/4] of: DT quirks infrastructure\0" + "From\0Peter Hurley <peter@hurleysoftware.com>\0" + "Subject\0Re: [PATCH 2/4] of: DT quirks infrastructure\0" "Date\0Fri, 20 Feb 2015 10:00:06 -0500\0" - "To\0linux-arm-kernel@lists.infradead.org\0" + "To\0Pantelis Antoniou <pantelis.antoniou@konsulko.com>" + frowand.list@gmail.com + Mark Rutland <mark.rutland@arm.com> + devicetree@vger.kernel.org <devicetree@vger.kernel.org> + Tony Lindgren <tony@atomide.com> + Koen Kooi <koen@dominion.thruhere.net> + Nicolas Ferre <nicolas.ferre@atmel.com> + linux-kernel@vger.kernel.org <linux-kernel@vger.kernel.org> + Grant Likely <grant.likely@secretlab.ca> + linux-arm-kernel@lists.infradead.org <linux-arm-kernel@lists.infradead.org> + Matt Porter <matt.porter@linaro.org> + " Guenter Roeck <linux@roeck-us.net>\0" "\00:1\0" "b\0" "On 02/20/2015 09:35 AM, Ludovic Desroches wrote:\n" @@ -50,10 +61,10 @@ ">>>>>>>> the FW/bootloader could be common even if the DTB couldn't.\n" ">>>>>>>>\n" ">>>>>>>> To some extent there must be a DTB that will work across all variants\n" - ">>>>>>>> (albeit with limited utility) or the quirk approach wouldn't work?\n" + ">>>>>>>> (albeit with limited utility) or the quirk approach wouldn't work\342\200\246\n" ">>>>>>>>\n" ">>>>>>>\n" - ">>>>>>> That?s not correct; the only part of the DTB that needs to be common\n" + ">>>>>>> That\342\200\231s not correct; the only part of the DTB that needs to be common\n" ">>>>>>> is the model property that would allow the quirk detection logic to fire.\n" ">>>>>>>\n" ">>>>>>> So, there is a base DTB that will work on all variants, but that only means\n" @@ -82,8 +93,8 @@ ">>>>>>>>>> appended DTB if it's not possible to update the board configuration.\n" ">>>>>>>>>>\n" ">>>>>>>>>\n" - ">>>>>>>>> You?re missing the point. I can?t use the same DTB for each revision of the\n" - ">>>>>>>>> board. Each board is similar but it?s not identical.\n" + ">>>>>>>>> You\342\200\231re missing the point. I can\342\200\231t use the same DTB for each revision of the\n" + ">>>>>>>>> board. Each board is similar but it\342\200\231s not identical.\n" ">>>>>>>>\n" ">>>>>>>> I think you've misunderstood my point. If you program the board with the\n" ">>>>>>>> relevant DTB, or use appended DTB, then you will pass the correct DTB to\n" @@ -94,7 +105,7 @@ ">>>>>>>\n" ">>>>>>> In theory it might work, in practice this does not. Ludovic mentioned that they\n" ">>>>>>> have 27 different DTBs in use at the moment. At a relatively common 60k per DTB\n" - ">>>>>>> that?s 27x60k = 1.6MB of DTBs, that need to be installed.\n" + ">>>>>>> that\342\200\231s 27x60k = 1.6MB of DTBs, that need to be installed.\n" ">>>>>>\n" ">>>>>> < snip >\n" ">>>>>>\n" @@ -109,7 +120,7 @@ ">>>>>\n" ">>>>> Trust no-one.\n" ">>>>>\n" - ">>>>> This is one of those things that the kernel community doesn?t understand which makes people\n" + ">>>>> This is one of those things that the kernel community doesn\342\200\231t understand which makes people\n" ">>>>> who push product quite mad.\n" ">>>>>\n" ">>>>> Engineering a product is not only about meeting customer spec, in order to turn a profit\n" @@ -117,7 +128,7 @@ ">>>>>\n" ">>>>> Yes, you can always manually install files in the bootloader. For 1 board no problem.\n" ">>>>> For 10 doable. For 100 I guess you can hire an extra guy. For 1 million? Guess what,\n" - ">>>>> instead of turning a profit you?re losing money if you only have a few cents of profit\n" + ">>>>> instead of turning a profit you\342\200\231re losing money if you only have a few cents of profit\n" ">>>>> per unit.\n" ">>>>\n" ">>>> I'm not installing physical components manually. Why would I be installing software\n" @@ -129,7 +140,7 @@ ">>> Having a single binary to flash to every revision of the board makes logistics considerably\n" ">>> easier.\n" ">>>\n" - ">>> Having to boot and tweak the bootloader settings to select the correct dtb (even if it?s present\n" + ">>> Having to boot and tweak the bootloader settings to select the correct dtb (even if it\342\200\231s present\n" ">>> on the flash medium) takes time and is error-prone.\n" ">>>\n" ">>> Factory time == money, errors == money.\n" @@ -141,9 +152,9 @@ ">>>> And you produce a few million units before testing that the first one off the line works?\n" ">>>>\n" ">>>\n" - ">>> The first one off the line works. The rest will get some burn in and functional testing if you?re\n" + ">>> The first one off the line works. The rest will get some burn in and functional testing if you\342\200\231re\n" ">>> lucky. In many cases where the product is very cheap it might make financial sense to just ship\n" - ">>> as is and deal with recalls, if you?re reasonably happy after a little bit of statistical sampling.\n" + ">>> as is and deal with recalls, if you\342\200\231re reasonably happy after a little bit of statistical sampling.\n" ">>>\n" ">>> Hardware is hard :)\n" ">>\n" @@ -183,4 +194,4 @@ ">> Regards,\n" >> Peter Hurley -f242cee94d2060aa2eae6571dc1e612e20ca1ff221593d2baf94b3b510114575 +30618e317bfb83cd67e828aeb269c5f0177355f056393df24113bcaf7d78be89
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.