00:00:00 --- log: started forth/20.01.14
00:10:46 --- join: mtsd joined #forth
00:22:32 --- join: gravicappa joined #forth
00:37:36 --- join: proteus-guy joined #forth
00:43:48 --- quit: jsoft (Ping timeout: 268 seconds)
00:45:13 --- quit: proteus-guy (Ping timeout: 240 seconds)
01:02:01 --- join: proteus-guy joined #forth
01:09:14 --- join: xek joined #forth
01:10:48 --- join: dys joined #forth
02:24:14 --- quit: smokeink (Remote host closed the connection)
02:25:56 --- join: smokeink joined #forth
02:25:57 --- quit: smokeink (Remote host closed the connection)
02:46:40 --- quit: Robert (Quit: reboot)
02:53:14 --- quit: WickedShell (Remote host closed the connection)
02:53:19 --- join: iyzsong joined #forth
03:15:47 --- join: dddddd joined #forth
03:34:52 --- quit: jedb (Remote host closed the connection)
03:39:23 --- join: jedb joined #forth
03:56:46 --- quit: cartwright (Ping timeout: 240 seconds)
04:00:12 --- join: cartwright joined #forth
04:01:33 --- quit: proteus-guy (Ping timeout: 268 seconds)
04:06:47 --- quit: rdrop-exit (Quit: Lost terminal)
05:15:54 --- quit: iyzsong (Ping timeout: 260 seconds)
05:29:28 <dddddd> https://fosdem.org/2020/schedule/event/riscv_luajit/ includes "Deviation (side project) Yet another Forth and yet another assembler"
05:29:57 <tpbsd> g'day dddddd :)
05:30:12 <dddddd> oh, rdrop is offline (wrt risc-v)
05:30:22 <dddddd> Hello tpbsd!
05:30:26 <tpbsd> lua is a deviant on embedded!
05:31:03 <tpbsd> yeah rdrop-exit isnt always here
05:31:17 <tpbsd> maybe his volcano caused a power outage ?
05:32:17 <tpbsd> dddddd I have Forth (Mecrisp-Stellaris) running on a RISC-V in the form of a GD32VF103 mcu
05:37:07 <dddddd> I guess it's just dinner time there, let's hope it's just that.
05:39:36 <tpbsd> actually he may be asleep as it's 22:30 there
05:40:02 <tpbsd> oops 21:30
05:40:19 <tpbsd> well one or the other
05:40:31 <tpbsd> hes in Manila
05:43:50 --- join: ryke joined #forth
06:00:29 --- quit: WilhelmVonWeiner (Ping timeout: 258 seconds)
06:04:12 --- join: Labu joined #forth
06:06:06 --- join: X-Scale` joined #forth
06:07:13 --- quit: X-Scale (Ping timeout: 240 seconds)
06:07:13 --- nick: X-Scale` -> X-Scale
06:13:04 --- quit: dave0 (Quit: dave's not here)
06:30:01 --- quit: mtsd (Quit: Leaving)
06:36:06 --- quit: ryke (Ping timeout: 260 seconds)
07:02:20 --- join: `presiden joined #forth
07:03:08 --- quit: `presiden (Client Quit)
08:07:16 --- join: `presiden joined #forth
09:15:55 --- join: jsoft joined #forth
09:34:50 --- quit: dys (Ping timeout: 245 seconds)
10:02:08 --- join: proteus-guy joined #forth
11:15:21 * crc continues work on documentation; I added sections on scripting and loops
11:44:36 --- join: X-Scale` joined #forth
11:47:45 --- quit: X-Scale (Ping timeout: 268 seconds)
11:47:46 --- nick: X-Scale` -> X-Scale
12:48:34 --- quit: gravicappa (Ping timeout: 260 seconds)
14:18:02 --- join: jedb_ joined #forth
14:21:01 --- quit: jedb (Ping timeout: 260 seconds)
14:33:46 --- quit: xek (Ping timeout: 258 seconds)
14:45:22 --- join: WickedShell joined #forth
15:21:54 --- join: dave0 joined #forth
15:29:05 <tpbsd> :~/projects/retro% fossil update
15:29:05 <tpbsd> Autosync:  http://forthworks.com:8000
15:29:05 <tpbsd> Round-trips: 2   Artifacts sent: 0  received: 25
15:29:05 <tpbsd> Pull done, sent: 1567  received: 7904
15:29:07 <tpbsd> :)
16:02:59 --- join: jedb__ joined #forth
16:05:54 --- quit: jedb_ (Ping timeout: 265 seconds)
16:58:04 --- join: WilhelmVonWeiner joined #forth
16:58:29 --- nick: WilhelmVonWeiner -> Guest50399
17:07:07 --- quit: MrMobius (Quit:  HydraIRC -> http://www.hydrairc.com <- The alternative IRC client)
17:09:04 <crc> tpbsd: if there's anything in the docs you'd like to see added or improved on please let me know
17:10:16 <tpbsd> crc, lol, I'm admiring how excellent they are and urging myself to try and improve my docs to your standards!
17:12:34 <tpbsd> one thing I have is labels and references as I use py.sphinx which is just a simple markup language, no python programming involved so creating the doc is easy, but like all "helpful" apps it has a few presets that are annoying and I dont yet understand
17:14:27 <tpbsd> this is my front page, apologies if you have seen it already
17:14:30 <tpbsd> https://mecrisp-stellaris-folkdoc.sourceforge.io/index.html
17:14:58 <tpbsd> because it's all open source, I host it for free on Sourceforge :)
17:15:57 <tpbsd> I paid for a cloud server for years then one day I realised I was wasting money as the content was all open source
17:40:22 --- join: karswell joined #forth
17:46:34 --- join: tabemann joined #forth
18:02:04 --- quit: tabemann (Ping timeout: 268 seconds)
18:12:43 --- join: ryke joined #forth
18:16:15 --- quit: proteus-guy (Ping timeout: 268 seconds)
18:24:04 --- quit: dave0 (Quit: dave's not here)
18:27:45 --- join: MrMobius joined #forth
18:28:03 --- join: proteus-guy joined #forth
18:38:15 --- quit: proteus-guy (Ping timeout: 272 seconds)
18:40:04 --- quit: MrMobius (Quit:  HydraIRC -> http://www.hydrairc.com <- *I* use it, so it must be good!)
18:53:06 --- quit: dddddd (Remote host closed the connection)
18:55:05 <crc> I moved the other way, starting with source forge and now running servers I control
18:56:07 <tpbsd> aha, interesting
19:01:11 <crc> I have five servers currently; one running slackware, one running freebsd, two running openbsd, and one straggler running debian (the only one using apache rather than servers I've written in retro)
19:01:49 <tpbsd> virtual or hardware servers ?
19:02:23 <tpbsd> I'm thinking hardware as you had hardware issues recently with one of them ?
19:02:37 <crc> Virtual; I don't have the budget to run my own hardware yet
19:03:07 <crc> One of the openbsd servers lost the ability to use the network
19:03:14 <tpbsd> oh, ok
19:03:59 <tpbsd> running your own hardware can be pretty expensive anyway, apart from the cost of the hardware
19:04:37 <tpbsd> here in AU electricity is about the most or near to the most expensive in the world, so a 24/7 server electricity cost really adds up
19:04:48 <crc> I'll be shutting that one down soon, still probing it to try to find out why it failed
19:44:52 --- join: smokeink joined #forth
19:55:27 --- quit: karswell (Remote host closed the connection)
19:55:52 --- join: karswell_ joined #forth
19:56:09 --- quit: ryke (Ping timeout: 272 seconds)
20:08:11 --- quit: Labu (Ping timeout: 272 seconds)
20:13:09 --- nick: karswell_ -> karswell
20:32:19 --- quit: remexre (Quit: WeeChat 2.6)
20:37:16 --- quit: proteusguy (Ping timeout: 260 seconds)
20:37:49 --- join: gravicappa joined #forth
20:49:43 --- join: proteusguy joined #forth
20:49:43 --- mode: ChanServ set +v proteusguy
20:57:35 --- join: rdrop-exit joined #forth
20:58:14 <rdrop-exit> c[] howdy Forth wranglers
21:48:23 <jsoft> Gidday there
21:48:36 <rdrop-exit> hi jsoft!
21:48:41 <jsoft> You don't happen to know much about lorawan do you ?
21:49:05 <rdrop-exit> nope, sorry
21:49:22 <jsoft> Hmm.
21:49:24 <jsoft> What about now?
21:49:34 <rdrop-exit> sounds interesting though
21:49:48 <jsoft> Nah I am just curious. 
21:50:03 <jsoft> I am getting irritated by a lot of the lorawan modules
21:50:24 <jsoft> And 90% of the modules use the same chip, and often use stm32's to drive them
21:50:27 <jsoft> But are in C
21:50:39 <jsoft> I was half entertaining the idea of writing a lorawan stack 
21:50:47 <rdrop-exit> cool
21:50:50 <jsoft> It would be a bit of a mission though
21:51:13 <rdrop-exit> I bet
21:52:20 <rdrop-exit> Who controls the spec?
21:52:45 <jsoft> There is some lorawan alliance weirdo situation
21:52:52 <jsoft> But there are open source code bases and such
21:52:58 <rdrop-exit> aha
21:53:12 <jsoft> I have not looked proper, but I think its all in the open mostly.
21:54:02 <rdrop-exit> the wikipedia page on it isn't very informative
21:54:37 <jsoft> I actually find most wikipedia pages on technical things uninformative
21:55:11 <rdrop-exit> I always read the associated talk page to see what they;re fighting over
21:55:28 <rdrop-exit> https://en.wikipedia.org/wiki/Talk:LPWAN
21:55:34 --- quit: karswell (Remote host closed the connection)
21:57:02 --- join: karswell joined #forth
21:59:00 <rdrop-exit> good luck with it, keep us posted
21:59:42 <jsoft> Hey now, I've not commited to it yet! :D
21:59:53 <rdrop-exit> :)) No worries
22:00:07 <jsoft> rdrop-exit, what have you been tinkering with though ?
22:00:38 <rdrop-exit> RISC-V specs
22:01:16 <rdrop-exit> I plan on tethering to RISC-V targets via JTAG
22:02:45 <jsoft> What is RISK-V again?
22:02:50 <rdrop-exit> Writing up the Debug-Mode registers and trying to grok them, also writing a RISC-V assembler for 32-bit targets
22:02:50 <jsoft> RISC-V even?
22:03:19 <jsoft> I'm such a chump :D
22:03:47 <rdrop-exit> An open-source hardware ISA
22:04:20 <rdrop-exit> Competition for ARM 
22:04:27 <rdrop-exit> https://en.wikipedia.org/wiki/RISC-V
22:05:05 <rdrop-exit> According to tpbsd it may possibly take over the world in the long run
22:07:39 <jsoft> hehe
22:07:45 <jsoft> So there are working chips out there?
22:07:56 <rdrop-exit> yes
22:08:06 <jsoft> Are they uC's or CPU's?
22:09:25 <WickedShell> both
22:09:44 <jsoft> Hmm ok
22:09:46 <jsoft> What company?
22:10:19 <rdrop-exit> here's a list
22:10:20 <rdrop-exit> https://en.wikipedia.org/wiki/RISC-V#Implementations
22:10:20 <jsoft> Like you know how stm32 is the semi jellybean arm vendor
22:10:40 <jsoft> Alibaba group, interesting
22:10:49 <jsoft> 2.5Ghz, farking hell
22:10:54 <WickedShell> SiFive and some chinese company I've forgotten about are the main ones I see people using
22:10:57 <WickedShell> Outside of FPGA cores
22:11:03 <WickedShell> Which are also really popular...
22:11:44 <jsoft> Hmm
22:12:21 <rdrop-exit> tpbsd has a Chinese RISC-V board he's been comparing to a similar ARM board
22:13:41 <rdrop-exit> https://mecrisp-stellaris-folkdoc.sourceforge.io/gd32vf103.html
22:14:18 <WickedShell> I think this is the one I've seen a lot of people playing with: https://www.seeedstudio.com/blog/2019/09/12/get-started-with-k210-hardware-and-programming-environment/
22:14:25 <WickedShell> (that chip in various forms)
22:15:33 <rdrop-exit> That one seems to be 64-bit dual core
22:16:11 <WickedShell> Yeah. I haven't used it personally I've just been seeing it make the rounds on Hackaday and elsewhere :P But that's not necessarily an endorsement :P
22:16:16 <rdrop-exit> I'm focusing only on 32-bit integer RV32IMC
22:16:31 <WickedShell> I have a HiFive 1 I've done a bit with, but it didn't have enough peripherals for pretty much anything I wanted to seriously chase
22:18:01 <rdrop-exit> I may get a HiFive or something similar to test my tether and cross-assembler
22:18:55 <WickedShell> Rev B is a bit better for extra peripherals :)
22:19:38 <rdrop-exit> It's still early days for me, and this is only a limited-spare time project for me
22:20:54 <rdrop-exit> I won't worry about peripherals until I have a specific application in mind, for the moment I'm just developping the toolset
22:21:34 <rdrop-exit> to control and program the RISC-V via a tether
22:28:27 <yunfan> rdrop-exit:which board of this riscv named?
22:29:28 <rdrop-exit> yunfan, are you asking about the one tpbsd has?
22:30:24 <rdrop-exit> He has the Longan-Nano board
22:30:33 <rdrop-exit> https://mecrisp-stellaris-folkdoc.sourceforge.io/gd32vf103.html
22:31:14 <rdrop-exit> "Longan Nano is a development board based on GD32VF103CBT6 MCU with RISC-V 32-bit core of GigaDevice.
22:31:17 <rdrop-exit> "
22:31:35 <yunfan> rdrop-exit:thanks, aha, this is the one i want to buy
22:31:39 <yunfan> its cheap :D
22:31:59 <rdrop-exit> This is the one I'm looking at for now:
22:32:22 <rdrop-exit> https://www.sifive.com/boards/hifive1-rev-b
22:32:32 <yunfan> it even has a oled screen
22:49:49 --- quit: karswell (Read error: Connection reset by peer)
23:59:59 --- log: ended forth/20.01.14