From: Axel Belinfante <Axel.Belinfante@cs.utwente.nl>
To: 9fans@cse.psu.edu
Subject: [9fans] recent bitsy kernel deployment?
Date: Thu, 31 Aug 2006 23:15:32 +0200 [thread overview]
Message-ID: <200608312115.k7VLFWx02413@demeter.cs.utwente.nl> (raw)
just wondering if the bitsy code has been exercised recently.
it has been a while since I last updated the bitsy, and I only
recently used it again after a long period of non-usage.
unfortunately I 'stored' mine switched on (don't do that!!) which harmed
its battery (now replaced) and probably also the sleeve battery.
it looks like /dev/battery could be made to report slightly more about
the battery status e.g. about the sleeve one, but to add that I need
to rebuild the kernel and probably the apps too (to keep them in sync).
since uploading over the wavelan is much easier than via the cradle,
I would feel slighly more confortable knowing that these things
still work. (of course they do, and yeah, I can just try, but still...)
Axel.
next reply other threads:[~2006-08-31 21:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-31 21:15 Axel Belinfante [this message]
2006-08-31 21:19 ` Francisco J Ballesteros
2006-08-31 22:05 ` Gorka guardiola
2006-09-02 12:54 ` Axel Belinfante
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=200608312115.k7VLFWx02413@demeter.cs.utwente.nl \
--to=axel.belinfante@cs.utwente.nl \
--cc=9fans@cse.psu.edu \
/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;
as well as URLs for NNTP newsgroup(s).