00:00:00 --- log: started forth/21.01.23 00:37:36 --- quit: zolk3ri (Remote host closed the connection) 00:39:54 --- join: zolk3ri joined #forth 00:49:30 --- join: hosewiejacke2 joined #forth 00:49:33 --- quit: hosewiejacke (Read error: Connection reset by peer) 00:56:54 --- join: xek_ joined #forth 01:04:57 --- quit: ovf (*.net *.split) 01:04:57 --- quit: phadthai (*.net *.split) 01:07:01 --- join: ovf joined #forth 01:07:01 --- join: phadthai joined #forth 01:08:51 --- quit: sts-q (Ping timeout: 246 seconds) 01:10:21 --- quit: patrickg (Ping timeout: 240 seconds) 01:10:34 --- quit: jimt[m] (Ping timeout: 243 seconds) 01:10:38 --- quit: siraben (Ping timeout: 246 seconds) 01:19:07 --- join: sts-q joined #forth 01:29:42 --- join: X-Scale` joined #forth 01:29:49 --- quit: X-Scale (Ping timeout: 256 seconds) 01:30:59 --- nick: X-Scale` -> X-Scale 01:32:09 --- quit: dave0 (Quit: dave's not here) 01:35:43 --- quit: hosewiejacke2 (Ping timeout: 265 seconds) 01:40:04 --- join: siraben joined #forth 01:40:48 --- join: jimt[m] joined #forth 01:56:44 --- quit: jimt[m] (Ping timeout: 265 seconds) 01:56:46 --- quit: siraben (Ping timeout: 260 seconds) 02:18:23 --- join: jimt[m] joined #forth 02:26:02 --- join: siraben joined #forth 02:26:02 --- join: patrickg joined #forth 04:12:11 --- join: dave0 joined #forth 04:54:22 --- quit: xek_ (Quit: Leaving) 04:56:26 --- quit: sts-q (Remote host closed the connection) 04:59:44 --- join: sts-q joined #forth 05:54:05 --- quit: dave0 (Quit: dave's not here) 06:51:25 --- quit: _whitelogger (Remote host closed the connection) 06:54:23 --- join: _whitelogger joined #forth 09:45:49 --- quit: cheater (Ping timeout: 265 seconds) 09:56:02 --- join: hosewiejacke2 joined #forth 10:19:58 --- quit: gravicappa (Ping timeout: 240 seconds) 10:20:48 --- join: gravicappa joined #forth 11:00:03 --- join: cheater joined #forth 11:12:14 --- quit: Guest68228 (Ping timeout: 246 seconds) 11:39:26 --- join: Guest68228 joined #forth 11:45:50 --- quit: hosewiejacke2 (Ping timeout: 246 seconds) 12:31:36 --- quit: gravicappa (Ping timeout: 265 seconds) 14:38:28 --- quit: zolk3ri (Quit: leaving) 14:38:53 --- join: zolk3ri joined #forth 15:20:24 anybody tried the RPi Pico? 15:20:29 Sounds like an interesting controller 15:20:35 very well designed peripherals 15:20:38 superb documentation 15:20:49 seems like they thought about everything 15:30:08 --- join: dave0 joined #forth 17:10:40 --- join: lispmacs joined #forth 17:13:18 hi, I am studying into compiler directives and making your own syntax. I was wondering if Forth has a word specifically for "jump execution to the address on the return/control stack" or if that would be implementation specific. The word `again' seems to have this effect... 17:21:42 --- join: Zarutian_HTC joined #forth 17:26:23 FUZxxl: it has some downsides. no hardware floating point, and if you want to use their optimized software floating point support for it it's only free-as-in-beer 17:28:22 the fact that it's a completely open datasheet rather than the usual broadcom behaviour is a step forward of course 17:28:58 --- quit: Zarutian_HTC (Remote host closed the connection) 17:29:14 i'm going to stick to a single cortex-m4 when i need floating point and a single cortex-m0+ when i don't 17:30:08 putting two cortex m0+ in a single package is frankly kinda weird, i don't really know what their imagined use case is that that's the optimal solution 17:30:38 --- join: Zarutian_HTC joined #forth 17:54:32 floatcomplex: huch? Isn't the firmware open source, too? 17:54:56 afaik the idea is to have one processor for your main code and the other for short running low latency stuff 17:55:30 and the M0+ is so small, it's not much effort to put a second one in 17:55:45 there's lots of useful stuff to learn from having a multi processor system 18:34:52 --- join: boru` joined #forth 18:34:54 --- quit: boru (Disconnected by services) 18:34:57 --- nick: boru` -> boru 18:42:16 * Zarutian_HTC hands FUZxxl a Sega Genesis, bucketfull of transputers, GreenArray chips, a reference to FlowBasedProgramming, and an IBM manual on hetroarch computing 18:48:09 oh and that PlayStation thing with SPUs 19:02:05 FUZxxl: i'm trying to find where in the actual code the offending license is, they may have removed it. their website still has objectionable text on it though 19:02:24 "As Cortex-M0+ lacks a floating-point unit, we have commissioned optimised floating-point functions from Mark Owen, author of the popular Qfplib libraries; these are substantially faster than their GCC library equivalents, and are licensed for use on any RP2040-based product." 19:06:00 * Zarutian_HTC thought RISCV was all the rage now 19:27:42 --- join: Croran joined #forth 19:41:11 --- quit: actuallybatman (Quit: Lost terminal) 19:59:20 --- quit: Zarutian_HTC (Ping timeout: 256 seconds) 20:07:27 --- join: Zarutian_HTC joined #forth 20:20:46 --- join: actuallybatman joined #forth 20:33:52 --- quit: dave0 (Quit: dave's not here) 20:38:18 --- quit: sts-q (Ping timeout: 240 seconds) 20:46:06 --- join: proteus-guy joined #forth 20:48:38 --- join: sts-q joined #forth 21:35:50 --- quit: Lord_Nightmare (Ping timeout: 265 seconds) 21:36:55 --- quit: Croran (Quit: Croran) 22:01:57 it's their first custom hardware design, so it makes sense not to change too many variables 22:02:32 Once they're more familiar with spinning out MCUs maybe they'll consider using some RISC-V core 22:03:03 patrickg: change not too many variables from...what exactly? 22:04:00 from shipping an ARM SoC on a custom board to shipping a custom ARM MCU 22:04:40 patrickg: cortex m0+ has very little to do with cortex a anything 22:05:39 i happen to agree with you that riscv would have been a risc too far, but i don't think "we want to use arm because we did before" is the reason 22:05:46 they can still lean-in on existing channels, the tooling for verification etc is probably similar 22:06:39 if anything, aarch64 and riscv64 asm look more similar than aarch64 and cortex-m asm do 22:07:01 even going from cortex-whatever (that is, arm ltd design to plug in) to some custom ARM design would be folly when you're also dealing with creating your own chip for the first time 22:07:37 get the custom chip made, then look at customizing more parts or changing partners for parts 22:37:19 --- join: gravicappa joined #forth 22:54:05 --- join: Lord_Nightmare joined #forth 23:15:01 --- quit: dysprosaic (Read error: Connection reset by peer) 23:15:52 --- join: dysprosaic joined #forth 23:18:43 --- join: dave0 joined #forth 23:35:45 --- quit: dysprosaic (Ping timeout: 256 seconds) 23:36:47 --- join: dysprosaic joined #forth 23:53:51 --- quit: phadthai (Ping timeout: 258 seconds) 23:59:59 --- log: ended forth/21.01.23