From: Chris Kuethe <chris.kuethe@gmail.com>
To: "Ron Frazier (NTP)" <timekeepingntplist@c3energy.com>
Cc: thumbgps-devel@lists.bufferbloat.net
Subject: Re: [Thumbgps-devel] Build vs. modify vs. what should we be doing anyway?
Date: Mon, 12 Mar 2012 19:42:54 -0700 [thread overview]
Message-ID: <CAGHP0pKroaNWx648wRHZuXO77varEnfsWQqx70vRbCGsXVS-sA@mail.gmail.com> (raw)
In-Reply-To: <4F5EB328.5050301@c3energy.com>
On Mon, Mar 12, 2012 at 19:38, Ron Frazier (NTP)
<timekeepingntplist@c3energy.com> wrote:
> I think configuration data should be stored in flash. That way extended
> power off periods are not a problem.
>
> My BU-353 has a supercap. That's better than a battery that I might have to
> replace, or possibly couldn't replace. But I don't like knowing that, if I
> unplug it for a week, I'm going to have to reprogram it.
See, I wouldn't mind losing the config after a few hours without
power. At least that way you have a way to reset the serial port when
it gets hopelessly confused - a situation known to gpsd as the
bluetooth problem.
>
> Sincerely,
>
> Ron
>
>
> On 3/12/2012 7:01 PM, Dave Taht wrote:
>>
>> I like the supercap idea more than the battery idea. I imagine (and I
>> may be wrong) - that that will have a longer field lifetime than a
>> battery could.
>>
>>
>
>
> --
>
> (PS - If you email me and don't get a quick response, don't be concerned.
> I get about 300 emails per day from alternate energy mailing lists and
> such. I don't always see new messages very quickly. If you need a
> reply and have not heard from me in 1 - 2 weeks, send your message again.)
>
> Ron Frazier
> timekeepingdude AT c3energy.com
>
> _______________________________________________
> Thumbgps-devel mailing list
> Thumbgps-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/thumbgps-devel
--
GDB has a 'break' feature; why doesn't it have 'fix' too?
next prev parent reply other threads:[~2012-03-13 2:43 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-10 18:02 Patrick Maupin
2012-03-12 21:03 ` Eric S. Raymond
2012-03-12 21:18 ` tz
2012-03-12 21:26 ` Eric S. Raymond
2012-03-12 21:28 ` Patrick Maupin
2012-03-12 21:39 ` Eric S. Raymond
2012-03-12 22:10 ` Patrick Maupin
2012-03-12 22:23 ` tz
2012-03-12 22:33 ` Patrick Maupin
2012-03-13 2:29 ` Ron Frazier (NTP)
2012-03-13 2:39 ` Chris Kuethe
2012-03-12 22:45 ` Eric S. Raymond
2012-03-12 23:01 ` Dave Taht
2012-03-13 1:43 ` Eric S. Raymond
2012-03-13 2:04 ` Chris Kuethe
2012-03-13 2:13 ` Eric S. Raymond
2012-03-13 2:40 ` Dave Taht
2012-03-13 2:53 ` Chris Kuethe
2012-03-13 4:54 ` Eric S. Raymond
2012-03-13 13:23 ` Dave Taht
2012-03-13 14:35 ` tz
2012-03-13 16:04 ` Eric S. Raymond
2012-03-13 16:22 ` tz
2012-03-13 2:38 ` Ron Frazier (NTP)
2012-03-13 2:42 ` Chris Kuethe [this message]
2012-03-13 3:00 ` Ron Frazier (NTP)
2012-03-13 3:04 ` Dave Taht
2012-03-13 3:06 ` Chris Kuethe
2012-03-13 3:16 ` Dave Taht
2012-03-13 3:31 ` Chris Kuethe
2012-03-13 4:49 ` Dave Taht
2012-03-13 4:55 ` Eric S. Raymond
2012-03-13 4:16 ` Eric S. Raymond
2012-03-12 21:40 ` tz
2012-03-12 21:27 ` Patrick Maupin
2012-03-12 21:22 ` Patrick Maupin
2012-03-12 21:37 ` Eric S. Raymond
2012-03-12 21:45 ` Patrick Maupin
2012-03-12 22:02 ` Eric S. Raymond
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAGHP0pKroaNWx648wRHZuXO77varEnfsWQqx70vRbCGsXVS-sA@mail.gmail.com \
--to=chris.kuethe@gmail.com \
--cc=thumbgps-devel@lists.bufferbloat.net \
--cc=timekeepingntplist@c3energy.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox