[racket-users] racket on openwrt devices

2015-05-02 Thread Neil Van Dyke
What's the current viability of running Racket on a small OpenWRT 
device?  (Anything new, such as due to the recent modularization of the 
core?)


For example of specs of a popular beefy retail home WiFi router that 
runs OpenWRT well:


Processor: Atheros AR7161 rev 2 680MHz (MIPS arch)
RAM: 64MiB
Flash: 16MiB

Getting that up as high as 128MB RAM and 64MB-128MB flash would probably 
be doable, but fitting Racket on the device within the above specs is 
strongly preferable, for open source projects.


(In the open source application I have in mind, Racket would leave the 
TCP/IP to OpenWRT and the SoC, and spend most of its time doing a 
different kind of protocol through a special USB device.)


Neil V.

--
You received this message because you are subscribed to the Google Groups "Racket 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [racket-users] racket on openwrt devices

2015-05-03 Thread Tony Garnock-Jones
On 2015-05-02 2:29 PM, Neil Van Dyke wrote:
> What's the current viability of running Racket on a small OpenWRT
> device?  (Anything new, such as due to the recent modularization of the
> core?)

Nothing that I know of since 2011ish. The smaller core might make it a
little easier to assemble a minimal set of collections.

> For example of specs of a popular beefy retail home WiFi router that
> runs OpenWRT well:
> Processor: Atheros AR7161 rev 2 680MHz (MIPS arch)
> RAM: 64MiB
> Flash: 16MiB

Nice. Hmm, that amount of nonvolatile storage will be a challenge.
Racket will run in 64MB RAM on a machine of that class, though not well,
if my intuitions from 2011 still hold.

(Last time I ran Racket on OpenWRT, I was using a Netgear WNDR3700v2.)

Tony

-- 
You received this message because you are subscribed to the Google Groups 
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [racket-users] racket on openwrt devices

2015-05-03 Thread Neil Van Dyke

Tony Garnock-Jones wrote on 05/03/2015 12:55 PM:

On 2015-05-02 2:29 PM, Neil Van Dyke wrote:

What's the current viability of running Racket on a small OpenWRT
device?  (Anything new, such as due to the recent modularization of the
core?)

Nothing that I know of since 2011ish. The smaller core might make it a
little easier to assemble a minimal set of collections.


OK, thanks, Tony.  I'll have to give this a try in a week or two.


(Last time I ran Racket on OpenWRT, I was using a Netgear WNDR3700v2.)


I have a collection of these and similar WNDRs (my home office network 
is run by two 3700v2 and a 3800, running OpenWRT).  For Racket, I'll 
probably try a 3700v4 or 4300v1 first, since they're 128 RAM and 128 
NAND flash, albeit with a different SoC with lower CPU clock rate.  I 
don't want to rely on USB Storage for this project.


(Aside: A challenge for an open source project that you want large 
numbers of people to be able to adopt grassroots-style is to find router 
model(s) with sufficient specs, and that run OpenWRT well, and yet are 
still easily available for purchase online and at big-box retailers.  
Additionally, vendors like Netgear and Linksys often replace the product 
guts of a model with very different hardware, without changing the model 
number; so, someone ordering a "WNDR3700" online could be getting any of 
4+ different devices, with widely varying specs, and some of which don't 
run OpenWRT.  Some open source projects can also work on Raspberry Pi 
devices, but sometimes you need the NICs/radios/switch hardware of a 
cheap router anyway, so you might as well do everything in one appliance 
box.  A soho router is more polished and less expensive than a RasPi 
with a bunch of daughterboards and USB hubs and devices hanging off of 
it precariously.)


Neil V.

--
You received this message because you are subscribed to the Google Groups "Racket 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [racket-users] racket on openwrt devices

2015-05-03 Thread Tony Garnock-Jones
On 2015-05-03 2:50 PM, Neil Van Dyke wrote:
> 128 RAM and 128 NAND flash, albeit with a different SoC with lower 
> CPU clock rate.  I don't want to rely on USB Storage for this 
> project.

I should mention also that I couldn't do anything useful with Racket 5.x
(as it was at the time) on the WNDR3700v2 without using a swap file on a
USB stick (!). Simply not enough RAM or storage for Racket.

Tony

-- 
You received this message because you are subscribed to the Google Groups 
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [racket-users] racket on openwrt devices

2015-05-03 Thread Neil Van Dyke



Tony Garnock-Jones wrote on 05/03/2015 03:10 PM:

On 2015-05-03 2:50 PM, Neil Van Dyke wrote:

128 RAM and 128 NAND flash, albeit with a different SoC with lower
CPU clock rate.  I don't want to rely on USB Storage for this
project.

I should mention also that I couldn't do anything useful with Racket 5.x
(as it was at the time) on the WNDR3700v2 without using a swap file on a
USB stick (!). Simply not enough RAM or storage for Racket.


Very good to know.  Guess I'll just target the 128MB RAM devices, and 
not even bother with 64MB.  This weekend I'm writing a (hopefully) 
very-small-footprint HTTP-serving module in pure Racket.


Neil V.

--
You received this message because you are subscribed to the Google Groups "Racket 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.