___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
Dear all,
Can you kindly let me know how to install Python Mega Widgets on XO?
Thanks a lot in advance,
Sung-Hyuck
p.s. Please ignore the previous empty e-mail. Sorry for that.
___
Devel mailing list
Devel@lists.laptop.org
Hey folks, crazy news:
On Saturday 29.12.07, there was a successful 'entanglement based quantum
key distribution' between two xo-laptops!!
QKD is a quantum-cryptographic scheme to securely distribute correlated
random numbers between the communicating parties.
At the 24C3, we (sj and aaron,
On Mon, 2007-12-31 at 18:10 +, David Woodhouse wrote:
An interesting goal would be cleaning up CONFIG_OLPC so that
it could be enabled in stock kernels of standard Linux distros.
I actually see that as a prerequisite for getting the thing upstream.
And the first step along that path
There has, in the past few months, been a surge of interest in health and
telehealth applications for the XO.
My own efforts have been focused on telehealth hardware and software
intended for use in scenarios where medical facilities are available but man
hours to manually screen individuals is
David Woodhouse wrote:
So here's an untested patch to make the reboot fixups slightly more
generic, so that we can easily add our own 'fixup' for the XO in a
fashion which will actually be mergeable upstream.
It would be slightly nicer and generic if we had
void (*mach_reboot_fixup)(void
I'm not sure about some of the kernel configuration options. A few
minor things stick out in my mind; I don't know the rationale behind
some of these things and am curious about developer decisions and
thoughts on how to build the kernel.
* CONFIG_NO_HZ + CONFIG_HZ=100?
* SLAB vs SLUB
*
I can't speak for the OLPC kernel folks, but here's a few thoughts:
First off I noticed CONFIG_NO_HZ=y and CONFIG_HZ=100; is this a quirk of
the kernel's general configuration? As I understand, these options
should be mutually exclusive because CONFIG_HZ is a parameter of a
scheduler
Steve Lewis wrote:
I have gotten sugar running under windows with QEMU -
no I have lots of questions
1) If I make changes in the emulated system are those changes remembered
between runs?
Yes.
2) Can I have the emulator point at a part of the windows file system -
allowing my tools to work
John Richard Moser wrote:
I'm also noticing some things like KALLSYMS and BUG(), BSD process
accounting, and the like. KALLSYMS, BUG(), and printk() are useful; on
a true embedded device I'd say remove 'em but I can't justify it here...
BSD process accounting and auditd support though?
On Jan 1, 2008 9:36 AM, Ian Daniher [EMAIL PROTECTED] wrote:
There has, in the past few months, been a surge of interest in health and
telehealth applications for the XO.
Glad to hear it. I have been talking up the idea for several years but
evidently not to the right people. %-[
There is a
Hi all,
As Ian said i'm working in a EKG prototype with the assistance of a
professor and alumni of my uni,
The process has been stoped due to intersemestral vacations but we have a
working prototype, although we still need a lot of improvements.
So i guess in two weeks or so we will
Hi all,
Just an update: Pascals has an 'alpha' version of Hesperian WTND Chapter one
up online here http://pascal.scheffers.net/Outputs/chapter%201.html. This
is to be compared to the PDF version
herehttp://www.hesperian.org/assets/wtnd/WTND_Chapter_1_pdf.php
.
Best wishes,
Ian
On Jan 1, 2008
From a security standpoint, there is an advantage to building in
everything. The main kernel is verified with a crypto signature before
it is executed. Loading a module without first verifying a
similarly-strong signature weakens the security.
Modules are a good idea for kernels that are
Mitch Bradley wrote:
From a security standpoint, there is an advantage to building in
everything. The main kernel is verified with a crypto signature before
it is executed. Loading a module without first verifying a
similarly-strong signature weakens the security.
Modules are a good
There is a telemedicine kit from India for about $200, and there are
other possibilities. I have been encouraged by developments in blood
chemistry measurements that do not require a needle stick. The first
such product is likely to be a diabetic blood sugar meter, but the
process applies
On Dec 30, 2007 10:20 AM, C. Scott Ananian [EMAIL PROTECTED] wrote:
I have run the python documentation tool 'epydoc' on the contents of
the joyride-1477 release. The results are here:
http://dev.laptop.org/~cscott/joyride-1477-api/
Thanks. I was wishing for that. Can you do the other
Sorry. It got away from me.
On Jan 1, 2008 2:11 PM, Edward Cherlin [EMAIL PROTECTED] wrote:
On Dec 30, 2007 10:20 AM, C. Scott Ananian [EMAIL PROTECTED] wrote:
I have run the python documentation tool 'epydoc' on the contents of
the joyride-1477 release. The results are here:
Mitch Bradley wrote:
From a security standpoint, there is an advantage to building in
everything. The main kernel is verified with a crypto signature before
it is executed. Loading a module without first verifying a
similarly-strong signature weakens the security.
Modules are a good
John Richard Moser wrote:
I'm not sure about some of the kernel configuration options. A few
minor things stick out in my mind; I don't know the rationale behind
some of these things and am curious about developer decisions and
thoughts on how to build the kernel.
* CONFIG_NO_HZ +
Edward Cherlin wrote:
Does anybody know of a documentation tool for Open Firmware, or for
FORTH more generally? Exploring using 'words' and 'see'
Are you looking for automated documentation generation, or FORTH coding
and documentation standards? I don't know about the former, but there is
a
From: Edward Cherlin [EMAIL PROTECTED]
And what about Smalltalk/Etoys?
Not sure what level of doc you're seeking. If I misunderstood you, I
apologize.
Smalltalk's libraries are to a certain extent self-documenting in its
browser, which is good because they vary depending on whatever you've
Edward Cherlin wrote:
Does anybody know of a documentation tool for Open Firmware, or for
FORTH more generally? Exploring using 'words' and 'see'
is fun up to a point if you're learning FORTH, but really doesn't cut
it for supporting documentation.
I presume that you have seen
I was trying a modification of the Hello World tutorial to package an
application with a bunch of additional files (essentially the python
acts as a launcher at the moment). In any case, when I follow the
hello world tutorial instructions to create the MANIFEST and run
setup.py, it complains
Hi all!
From now on, the channel #olpc-groups is open with the ambition to
connect local communities from everywhere! I can imagine a lot of
potential for collaborations, projects, problem solving and
not-reinventing-the-wheel :) !
SJ and I have talked about the current status of the
Chris Hager wrote:
Hi all!
From now on, the channel #olpc-groups is open with the ambition to
connect local communities from everywhere! I can imagine a lot of
potential for collaborations, projects, problem solving and
not-reinventing-the-wheel :) !
SJ and I have talked about the
Bernardo Innocenti wrote:
John Richard Moser wrote:
I'm not sure about some of the kernel configuration options. A few
minor things stick out in my mind; I don't know the rationale behind
some of these things and am curious about developer decisions and
thoughts on how to build the
Mitch Bradley wrote:
From a security standpoint, there is an advantage to building in
everything. The main kernel is verified with a crypto signature before
it is executed. Loading a module without first verifying a
similarly-strong signature weakens the security.
Loadable kernel
On Jan 1, 2008 7:03 PM, Kent Loobey [EMAIL PROTECTED] wrote:
On Tuesday 01 January 2008 15:57:17 you wrote:
I was trying a modification of the Hello World tutorial
What is the URL to the Hello World tutorial of which you speak?
Thanks.
Started with:
John Richard Moser wrote:
Please, build a kernel with the changes you consider useful,
and make it available somewhere, along with your proposed
config patch. Please make sure that the resulting kernel
also still works on QEMU and VMware.
The base hardware drivers built in supports qemu
Bernardo Innocenti wrote:
John Richard Moser wrote:
Please, build a kernel with the changes you consider useful,
and make it available somewhere, along with your proposed
config patch. Please make sure that the resulting kernel
also still works on QEMU and VMware.
The base hardware
Bernardo Innocenti wrote:
I'd keep the debug symbols (which shouldn't cost any memory
at runtime).
Possibly not. The kernel runs inside one giant huge page doesn't it?
4MiB read-write-execute...
Not on the Geode: we don't have MTRRs, so I guess the kernel
is being mapped by 4KB pages.
Tom Sylla wrote:
Not on the Geode: we don't have MTRRs, so I guess the kernel
is being mapped by 4KB pages.
4MB page support is unrelated to MTRR support. (one is related to linear
addresses, the other physical addresses; please see the Intel or AMD
documentation on paging and caching)
On Jan 1, 2008 9:50 PM, Bernardo Innocenti [EMAIL PROTECTED] wrote:
So I wonder why we couldn't use these to speed up access
to the framebuffer in the amd_drv X driver.
I don't understand, this was always taken care of.
On Jan 1, 2008 5:10 PM, Arjun Sarwal [EMAIL PROTECTED] wrote:
There is a telemedicine kit from India for about $200, and there are
other possibilities. I have been encouraged by developments in blood
chemistry measurements that do not require a needle stick. The first
such product is
35 matches
Mail list logo
