jacklsw has quit [Remote host closed the connection]
jacklsw has joined #riscv
netmonk has quit [Quit: WeeChat 4.6.0]
hwspeedy has quit [Read error: Connection reset by peer]
ldevulder has joined #riscv
jacklsw has quit [Quit: Back to the real world]
coldfeet has joined #riscv
ldevulder has quit [Ping timeout: 276 seconds]
jmabsd48 has joined #riscv
jmabsd48 has left #riscv [#riscv]
jmabsd has joined #riscv
<jmabsd>
Hi all, what is the cheapest RISCV64 board with an M.2 PCI connector, ability to hook it to Power over Ethernet, and maybe 4GB or 2GB RAM? Also same Q but for ARM64
<jmabsd>
Also what are good channels to ask this question
<la_mettrie>
this may be good enough, now wait patiently
<jmabsd>
Nice ok.
<jmabsd>
About the Power over Ethernet part, I think a separate module can solve it. So just a RISCV64 board with an M.2 22x80mm PCI connector and 4GB or 2GB RAM.
<jmabsd>
The PoE module will feed electricity via USB PD.
raym has quit [Quit: kernel update, rebooting...]
<jmabsd>
Relatively low watt consumption when idling if possible.
<mps>
jmabsd: banapi-f3 mybe
<jmabsd>
By the way, if you skip the PCI requiremenet and only demand two USB3 connections and 4GB or 2GB RAM, what's the cheapest SBC then?
jbe has quit [Ping timeout: 252 seconds]
jbe has joined #riscv
ldevulder has joined #riscv
hwspeedy has joined #riscv
agent314 has quit [Ping timeout: 276 seconds]
ldevulder has quit [Ping timeout: 245 seconds]
ungeskriptet has quit [Remote host closed the connection]
<kepstin>
basically treat it as a proprietary connector
<jmabsd>
OK.
<jmabsd>
Regarding the speed of the K1, should it be roughly like a BCM2711 (that's the SoC on the Raspberry Pi 4)?
<kepstin>
I haven't used a pi 4 myself, but i'd bet the k1 feels significantly slower for many tasks
<jmabsd>
Or more like half or more like double or 5x or 10x
<Tenkawa>
Depends on the workload
<jmabsd>
OK. For some simple NAT, VPN, it should be excellent shouldn't it?
<jmabsd>
the PCI will take 2.5gbps or even faster ethernet
<Tenkawa>
I've found some things on the BPI-F3 to be nice asd swift...some... not so much
<Tenkawa>
er and
<kepstin>
not so much excellent as much as "sufficient"; make sure you're using stuff that parallelizes well
<kepstin>
e.g. use wireguard, not openvpn :)
<jmabsd>
Oh. Hm.
<jmabsd>
Oh. Maybe an ARM would be safer bet?
<Tenkawa>
The bus IO needs a fair bit of tunning in my opinion
<Tenkawa>
er tuning
<jmabsd>
Like an RK3588
<kepstin>
i mean, i'm sure it'll be fine. but i wouldn't bet on nat at 2.5gbit line speed :)
<jmabsd>
Tenkawa: You mean in drivers/software?
<Tenkawa>
Jmabsd: yes
<jmabsd>
Oh I see. It could be a bottleneck.
<Tenkawa>
kepstin: indeed... I've had a hard time getting full speed out of a single link
<kepstin>
i've got a milkv jupiter board with the slightly faster m1 chip, but I haven't really done any testing of network speed. mostly been using it as a developer platform, and one thing it's particularly slow at is compilation workloads :(
<jmabsd>
OK. The Out of Order Execution RISCV chips are just around the corner aren't they
<Tenkawa>
kepstin: I have a few JH7110's and the BPI-F3 K1... the JH7110's definitely have made more progress in support... unfortunately as we know... just ot as robust performance.
<Tenkawa>
s/ot/not
<kepstin>
as far as i know, the sg2380 is more or less dead due global politics (sophgo might be blocked from using tsmc for chip production)
<jmabsd>
Hm. Someone says the K1's speed should be enough for 400mbps NAT/VPN type use anyhow
<Tenkawa>
speed has nothing to do with its io capsvity
<Tenkawa>
er capacity
<Tenkawa>
the rpi 4 cpu is plenty fast enough for its ethernet however it cannot get near saturating it....