Neo1973 + PSP == wifi proxy?

[Alex Savvutin]

Hi,

PSP is not an open platform (Sony SDK costs $10000), but there is the "homebrew" SDK (http://ps2dev.org/psp), it's kind of hacking but it is possible sometimes to get the "homebrew" apps to run on the PSP. So wifi proxy can be implemented in C++ (PSP 2.7/8/+ firmware also supports Flash).

I think it's interesting to make a more abstract project, I mean unified wifi/bluetooth/etc proxy for various platforms. Just another example: Neo1973 <=> Bluetooth <=> Desktop PC <=> Internet. And so on.

Best wishes,
Alex


-----Original Message-----
From: "Richard Franks" <spontificus at gmail.com>
To: OpenMoko <community at lists.openmoko.org>
Date: Mon, 11 Dec 2006 10:08:02 -0500
Subject: Neo1973 + PSP == wifi proxy?

> 
> I dropped the original idea below because of its limited utility, and
> this follow-up has even less utility.. however, since there is some
> javascript support in the PSP browser.. and the PSP would export its
> file-system to the Neo.. it should be technically possible. I wouldn't
> like to guess at the approximate bandwidth though ;-)
> 
> Richard
> 
> 
> On 11/29/06, Richard Franks <spontificus at gmail.com> wrote:
> > On 11/29/06, Richard Franks <spontificus at gmail.com> wrote:
> > > Oh wait. You mean hosting the HTML file(s) on the Neo? By pointing the
> > > PC browser to the HTML file on the Neo's memory, you could in effect
> > > set up a meta-refresh every second or so, or use AJAX to read files
> > > (requests) from the Neo's memory, and pass them on to the external
> > > Server as subsequent requests.
> > >
> > > GWT has a nice feature whereby it regards return requests as asyncronous events.
> > >
> > > All it would require is javascript support.
> >
> > Hey! This is the first project idea which we (the community) could
> > start today and complete even before the first Neo1973 ships, without
> > access to the SDK or any other data. Booya.
> >
> > There would be three components:
> >
> > 1) A small utility (cpp? Preferences?) which:
> > * Runs on the Neo and opens up a localhost port - the Neo would connect to this.
> > * Sets up a ring-buffer (implemented by files: request1.html ....
> > request10.html)
> > * Forwards results it receives back from the server (via the browser)
> > to the localhost client
> >
> > 2) The AJAX part which handles the PC end of the bridge
> >
> > 3) The server utility which speaks to the PC and understands the
> > Neo1973 requests it receives... or just passes it on in the case of an
> > SSH tunnel.
> >
> > There is actually a disconnect on the AJAX-Neo side - not sure of the
> > best way to get the return data from the browser back onto the Neo's
> > filesystem for dissemination, without invoking the file-download
> > dialog. Streaming is one way, but would require kernel hacking to
> > implement a file as a ring-buffer? If it's not a ring-buffer then you
> > run out of storage space.
> >
> > Oh wait, the file the PC browser writes to on the USB stick, can be
> > implemented as a symlink by the Neo.. to a device instantiated by the
> > app (1).
> >
> > Ok, good - did I miss anything? Who wants to help develop this?
> >
> > Richard
> >
> 
> _______________________________________________
> OpenMoko community mailing list
> community at lists.openmoko.org
> http://lists.openmoko.org/mailman/listinfo/community
>