diff for duplicates of <20150220164753.GC22752@roeck-us.net> diff --git a/a/1.txt b/N1/1.txt index 7ffd4c3..5ad0dd3 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,17 +1,17 @@ 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: @@ -32,10 +32,10 @@ On Fri, Feb 20, 2015 at 09:21:38AM -0500, Peter Hurley 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 @@ -64,8 +64,8 @@ On Fri, Feb 20, 2015 at 09:21:38AM -0500, Peter Hurley 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 @@ -76,7 +76,7 @@ On Fri, Feb 20, 2015 at 09:21:38AM -0500, Peter Hurley 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 > > >>>> @@ -91,7 +91,7 @@ On Fri, Feb 20, 2015 at 09:21:38AM -0500, Peter Hurley 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 @@ -99,7 +99,7 @@ On Fri, Feb 20, 2015 at 09:21:38AM -0500, Peter Hurley 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 @@ -111,7 +111,7 @@ On Fri, Feb 20, 2015 at 09:21:38AM -0500, Peter Hurley 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. @@ -123,9 +123,9 @@ On Fri, Feb 20, 2015 at 09:21:38AM -0500, Peter Hurley 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 :) > @@ -168,3 +168,7 @@ mechanism and, if not, how it can be improved. Thanks, Guenter +-- +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 1bf9f7f..e848924 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -8,26 +8,39 @@ "ref\054E61DD2.3060002@gmail.com\0" "ref\053F2F94C-0C43-4A54-B8CD-EEC454A0AC19@konsulko.com\0" "ref\054E742F2.80506@hurleysoftware.com\0" - "From\0linux@roeck-us.net (Guenter Roeck)\0" - "Subject\0[PATCH 2/4] of: DT quirks infrastructure\0" + "ref\054E742F2.80506-WaGBZJeGNqdsbIuE7sb01tBPR1lH4CV8@public.gmane.org\0" + "From\0Guenter Roeck <linux-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>\0" + "Subject\0Re: [PATCH 2/4] of: DT quirks infrastructure\0" "Date\0Fri, 20 Feb 2015 08:47:53 -0800\0" - "To\0linux-arm-kernel@lists.infradead.org\0" + "To\0Peter Hurley <peter-WaGBZJeGNqdsbIuE7sb01tBPR1lH4CV8@public.gmane.org>\0" + "Cc\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> + Ludovic Desroches <ludovic.desroches-AIFe0yeh4nAAvxtiuMwx3w@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>\0" "\00:1\0" "b\0" "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" @@ -48,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" @@ -80,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" @@ -92,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" @@ -107,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" @@ -115,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" @@ -127,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" @@ -139,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,6 +196,10 @@ "mechanism and, if not, how it can be improved.\n" "\n" "Thanks,\n" - Guenter + "Guenter\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 -d1f97acc52b6315563c964644841bc9923768645eda4ff30b3434d81881e34c4 +da14c91d143b19b5f09d1380ea08947eb76bf286b336cfaceec40859d89ca222
diff --git a/a/1.txt b/N2/1.txt index 7ffd4c3..b07cc7d 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -32,10 +32,10 @@ On Fri, Feb 20, 2015 at 09:21:38AM -0500, Peter Hurley 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 @@ -64,8 +64,8 @@ On Fri, Feb 20, 2015 at 09:21:38AM -0500, Peter Hurley 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 @@ -76,7 +76,7 @@ On Fri, Feb 20, 2015 at 09:21:38AM -0500, Peter Hurley 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 > > >>>> @@ -91,7 +91,7 @@ On Fri, Feb 20, 2015 at 09:21:38AM -0500, Peter Hurley 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 @@ -99,7 +99,7 @@ On Fri, Feb 20, 2015 at 09:21:38AM -0500, Peter Hurley 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 @@ -111,7 +111,7 @@ On Fri, Feb 20, 2015 at 09:21:38AM -0500, Peter Hurley 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. @@ -123,9 +123,9 @@ On Fri, Feb 20, 2015 at 09:21:38AM -0500, Peter Hurley 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 1bf9f7f..a8ec016 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -8,10 +8,22 @@ "ref\054E61DD2.3060002@gmail.com\0" "ref\053F2F94C-0C43-4A54-B8CD-EEC454A0AC19@konsulko.com\0" "ref\054E742F2.80506@hurleysoftware.com\0" - "From\0linux@roeck-us.net (Guenter Roeck)\0" - "Subject\0[PATCH 2/4] of: DT quirks infrastructure\0" + "From\0Guenter Roeck <linux@roeck-us.net>\0" + "Subject\0Re: [PATCH 2/4] of: DT quirks infrastructure\0" "Date\0Fri, 20 Feb 2015 08:47:53 -0800\0" - "To\0linux-arm-kernel@lists.infradead.org\0" + "To\0Peter Hurley <peter@hurleysoftware.com>\0" + "Cc\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> + Ludovic Desroches <ludovic.desroches@atmel.com> + linux-arm-kernel@lists.infradead.org <linux-arm-kernel@lists.infradead.org> + " Matt Porter <matt.porter@linaro.org>\0" "\00:1\0" "b\0" "On Fri, Feb 20, 2015 at 09:21:38AM -0500, Peter Hurley wrote:\n" @@ -48,10 +60,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" @@ -80,8 +92,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" @@ -92,7 +104,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" @@ -107,7 +119,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" @@ -115,7 +127,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" @@ -127,7 +139,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" @@ -139,9 +151,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" @@ -185,4 +197,4 @@ "Thanks,\n" Guenter -d1f97acc52b6315563c964644841bc9923768645eda4ff30b3434d81881e34c4 +46803c5bcece107c4175b625e5837de714ee9bbc73f8fbb341c7c354d60ed6ad
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.