Hi there,
the Ruckus R610 AP is end of life. I got one for doing "things" with it, so I started to do the following:
Getting root access to the device:
Flashed an older unleashed firmware from ruckus (R610_200.6.10.1.312.bl7).
Got root access with https://ms264556.net/ruckus/UnleashedAddRootShell
got mtd layout because u-boot bootdelay=0:
ruckus$ cat /proc/mtd
dev: size erasesize name
mtd0: 06000000 00020000 "rcks_wlan.main"
mtd1: 06000000 00020000 "rcks_wlan.bkup"
mtd2: 04000000 00020000 "datafs"
mtd3: 00020000 00010000 "SBL1"
mtd4: 00020000 00010000 "MIBIB"
mtd5: 00040000 00010000 "SBL2"
mtd6: 00080000 00010000 "SBL3"
mtd7: 00010000 00010000 "DDRCONFIG"
mtd8: 00010000 00010000 "SSD"
mtd9: 00080000 00010000 "TZ"
mtd10: 00080000 00010000 "RPM"
mtd11: 00080000 00010000 "APPSBL"
mtd12: 00040000 00010000 "APPSBLENV"
mtd13: 00040000 00010000 "ART"
mtd14: 00010000 00010000 "Board Data"
mtd15: 00260000 0001f000 "kernel"
mtd16: 0157cffc 0001f000 "ubi_rootfs"
mtd17: 002c0000 0001f000 "kernel"
mtd18: 01a80c5d 0001f000 "ubi_rootfs"
mtd19: 03811000 0001f000 "data"
u-boot env is at mtd12 
dd the mtd12 to a file, copied it via scp to an external host, edited the file with hexedit and set bootdelay to 1.
There is no mtd command, so i had to dd if=env.bin of=/dev/mtdblock12
It worked. The bootdelay is 2 now (whatever), so I can ctrl-c into the u-boot.
The cpu:
ruckus$ cat /proc/cpuinfo
processor : 0
model name : ARMv7 Processor rev 0 (v7l)
BogoMIPS : 1476.60
Features : swp half thumb fastmult vfp edsp neon tls vfpv4 idiva idivt
CPU implementer : 0x51
CPU architecture: 7
CPU variant : 0x2
CPU part : 0x04d
CPU revision : 0
processor : 1
model name : ARMv7 Processor rev 0 (v7l)
BogoMIPS : 1635.20
Features : swp half thumb fastmult vfp edsp neon tls vfpv4 idiva idivt
CPU implementer : 0x51
CPU architecture: 7
CPU variant : 0x2
CPU part : 0x04d
CPU revision : 0
Hardware : Ruckus Wireless R710/T710/R610 Access Point
Revision : 0000
Serial : 0000000000000000
It seems to have an ath79k wifi hardware.
The fcc ID is S9GR610 , the internal photos are detailed without the metal covers, so we can see the chipsets.
If anyone is interested to get this thing supported, what's the next step? When we brick it - It dowsn't matter, I didn't had to pay for it. Also, there are some more R610 
For now, I don't have a build environment, I only have a small vm to build the images with preselected packages like firmwareselector does...