Re: Neologics
On Tue, 2007-03-06 at 08:12 -0500, Richard Franks wrote: > I found the section on emergence/Neoforms _very_ interesting - I've > recently been expanding upon this ( > http://www.linuxtogo.org/gowiki/OpenMoko/Ideas/ConceptualFramework ) > from which I've going down similar lines of thought - do you have more > ideas about Neoforms? Yes but would you mind moving this over to wiki.openmoko.org. I would really rather have this kind of information up in a single location. Thanks! Sean ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Neologics
On Wed, 2007-03-07 at 09:11 -0500, Richard Franks wrote: > On 3/7/07, Jon Phillips <[EMAIL PROTECTED]> wrote: > > This is interesting to see the larger ambitions of the project. It might > > also help to expand upon what types of devices could be constructed with > > this logic, in addition to neo1973. I'm thinking remotes, media players, > > watches, etc... > > What if you mated Elite with Yahoo Pipes - instead of RSS feeds, you > have extensible data streams.. and instead of planets you have > conceptual nodes. Instead of trade routes, by clicking on a node you > can see and edit which data streams it imports and exports, and can be > anything from a simple wrapper to the GPS device, to a user, an > application or represent a physical device such as your desktop or > Neo. > > Here's an early demo picture, although the lack of structure makes it > look rather too complex at the moment: > http://www.flickr.com/photos/[EMAIL PROTECTED]/413592619/ > > Instead of adding a security layer later, each node could have its own > private/public key combo from birth, and would (by default) be > authenticated by the node representing the physical device layer. The > user node may use a third-party to authenticate themselves, which > would allow them to travel between devices, or may choose to operate > in a reduced security domain which allows local authentication - > simply drag a new node from your 'parent' user-node, un-check the > security domains you don't want it to access, and allow password > authentication for that 'child' node. > > To set up communication between nodes, the device authentication layer > would handle the swapping of public keys - transparently if requested > between multiple physical devices, but the utility arises from this > ability to dynamically create overlapping security domains (e.g. my > work, friends, family, spouse, etc). > > I think I've failed in the description somewhat, as I'm still in the > early-prototype stages - but I think it could provide access to > conceptual and physical resources as simple building blocks, which is > fundamental for emergence to flourish. Well, please put on the wiki: http://wiki.openmoko.org and flesh it out some more :) Jon > Richard > > ___ > OpenMoko community mailing list > community@lists.openmoko.org > http://lists.openmoko.org/mailman/listinfo/community -- Jon Phillips San Francisco, CA USA PH 510.499.0894 [EMAIL PROTECTED] http://www.rejon.org MSN, AIM, Yahoo Chat: kidproto Jabber Chat: [EMAIL PROTECTED] IRC: [EMAIL PROTECTED] ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Neologics
On 3/7/07, Jon Phillips <[EMAIL PROTECTED]> wrote: This is interesting to see the larger ambitions of the project. It might also help to expand upon what types of devices could be constructed with this logic, in addition to neo1973. I'm thinking remotes, media players, watches, etc... What if you mated Elite with Yahoo Pipes - instead of RSS feeds, you have extensible data streams.. and instead of planets you have conceptual nodes. Instead of trade routes, by clicking on a node you can see and edit which data streams it imports and exports, and can be anything from a simple wrapper to the GPS device, to a user, an application or represent a physical device such as your desktop or Neo. Here's an early demo picture, although the lack of structure makes it look rather too complex at the moment: http://www.flickr.com/photos/[EMAIL PROTECTED]/413592619/ Instead of adding a security layer later, each node could have its own private/public key combo from birth, and would (by default) be authenticated by the node representing the physical device layer. The user node may use a third-party to authenticate themselves, which would allow them to travel between devices, or may choose to operate in a reduced security domain which allows local authentication - simply drag a new node from your 'parent' user-node, un-check the security domains you don't want it to access, and allow password authentication for that 'child' node. To set up communication between nodes, the device authentication layer would handle the swapping of public keys - transparently if requested between multiple physical devices, but the utility arises from this ability to dynamically create overlapping security domains (e.g. my work, friends, family, spouse, etc). I think I've failed in the description somewhat, as I'm still in the early-prototype stages - but I think it could provide access to conceptual and physical resources as simple building blocks, which is fundamental for emergence to flourish. Richard ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Neologics
On Tue, 2007-03-06 at 08:12 -0500, Richard Franks wrote: > I found the section on emergence/Neoforms _very_ interesting - I've > recently been expanding upon this ( > http://www.linuxtogo.org/gowiki/OpenMoko/Ideas/ConceptualFramework ) > from which I've going down similar lines of thought - do you have more > ideas about Neoforms? > > Richard This is interesting to see the larger ambitions of the project. It might also help to expand upon what types of devices could be constructed with this logic, in addition to neo1973. I'm thinking remotes, media players, watches, etc... Jon > > On 3/1/07, Sean Moss-Pultz <[EMAIL PROTECTED]> wrote: > > Dear Community, > > > > For those of you who couldn't make it FOSDEM or Etel, I've posted our > > presentation here: > > > > http://www.openmoko.com/files/OpenMoko_Neologics.pdf > > > > Happy reading! > > > > -Sean > > > > > > ___ > > OpenMoko community mailing list > > community@lists.openmoko.org > > http://lists.openmoko.org/mailman/listinfo/community > > > > ___ > OpenMoko community mailing list > community@lists.openmoko.org > http://lists.openmoko.org/mailman/listinfo/community -- Jon Phillips San Francisco, CA USA PH 510.499.0894 [EMAIL PROTECTED] http://www.rejon.org MSN, AIM, Yahoo Chat: kidproto Jabber Chat: [EMAIL PROTECTED] IRC: [EMAIL PROTECTED] ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Neologics
I found the section on emergence/Neoforms _very_ interesting - I've recently been expanding upon this ( http://www.linuxtogo.org/gowiki/OpenMoko/Ideas/ConceptualFramework ) from which I've going down similar lines of thought - do you have more ideas about Neoforms? Richard On 3/1/07, Sean Moss-Pultz <[EMAIL PROTECTED]> wrote: Dear Community, For those of you who couldn't make it FOSDEM or Etel, I've posted our presentation here: http://www.openmoko.com/files/OpenMoko_Neologics.pdf Happy reading! -Sean ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Neologics
Hello. On Mon, 2007-03-05 at 10:47, Pranav Desai wrote: > On 3/4/07, Stefan Schmidt <[EMAIL PROTECTED]> wrote: > > > >No, it is only needed if you break your bootloader. Everything besides > >this is recoverable with the installed bootloader. > > Will it be possible to add a wiki page specifying how not to break the > bootloader and other things first time developers shouldn't do to make > the hardware unusable ? Everything should be designed to not break the bootloader during normal development and even software upgrades. In the end it's a device for enduser, which means it have to be enduser compatible. :) regards Stefan Schmidt signature.asc Description: Digital signature ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Neologics
On 3/4/07, Stefan Schmidt <[EMAIL PROTECTED]> wrote: Hello. On Sat, 2007-03-03 at 19:18, Pranav Desai wrote: > On 3/1/07, Sean Moss-Pultz <[EMAIL PROTECTED]> wrote: > > In the presentation its mentioned that the debug board will cost an > additional $200. How important is the debug board for phase 1 phones ? > Can we update the firmware drivers and put software, kernel, etc. on > it without the board? No, it is only needed if you break your bootloader. Everything besides this is recoverable with the installed bootloader. Thanks Stefan. Will it be possible to add a wiki page specifying how not to break the bootloader and other things first time developers shouldn't do to make the hardware unusable ? -- Pranav Sometimes it can make life easier as you can do step debugging with the JTAG, but for normal development, even kernel, it is not needed. regards Stefan Schmidt -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: http://www.datenfreihafen.org/contact.html iD8DBQFF6rDXbNSsvd31FmURAmuQAKCM59iT/YJe3YdLCyHFHuenVj8IXQCgrgQC botGrI6368G6BXEsrW/He9Q= =g9zb -END PGP SIGNATURE- ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community -- -- http://pd.dnsalias.org ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Neologics
Hello. On Sat, 2007-03-03 at 19:18, Pranav Desai wrote: > On 3/1/07, Sean Moss-Pultz <[EMAIL PROTECTED]> wrote: > > In the presentation its mentioned that the debug board will cost an > additional $200. How important is the debug board for phase 1 phones ? > Can we update the firmware drivers and put software, kernel, etc. on > it without the board? No, it is only needed if you break your bootloader. Everything besides this is recoverable with the installed bootloader. Sometimes it can make life easier as you can do step debugging with the JTAG, but for normal development, even kernel, it is not needed. regards Stefan Schmidt signature.asc Description: Digital signature ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Neologics
On 3/1/07, Sean Moss-Pultz <[EMAIL PROTECTED]> wrote: Dear Community, For those of you who couldn't make it FOSDEM or Etel, I've posted our presentation here: http://www.openmoko.com/files/OpenMoko_Neologics.pdf Hello Sean, Thanks for the link. In the presentation its mentioned that the debug board will cost an additional $200. How important is the debug board for phase 1 phones ? Can we update the firmware drivers and put software, kernel, etc. on it without the board? For future versions of the phone (phase 2+), is this a necessary piece of hardware for any kind of development work ? Thanks -- Pranav Happy reading! -Sean ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community -- -- http://pd.dnsalias.org ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Neologics
Sean Moss-Pultz schrieb: Dear Community, For those of you who couldn't make it FOSDEM or Etel, I've posted our presentation here: http://www.openmoko.com/files/OpenMoko_Neologics.pdf Happy reading! -Sean ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community That is great. Thank you for that! Regards, Denis ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Neologics
Dear Community, For those of you who couldn't make it FOSDEM or Etel, I've posted our presentation here: http://www.openmoko.com/files/OpenMoko_Neologics.pdf Happy reading! -Sean ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community