00:00:00 --- log: started forth/17.10.10 00:06:19 --- quit: ZombieChicken (*.net *.split) 00:12:50 --- join: ZombieChicken (~weechat@gateway/tor-sasl/forgottenwizard) joined #forth 00:26:03 --- join: proteus-guy (~proteusgu@183.88.65.145) joined #forth 00:40:05 ..? 00:47:27 --- quit: jedb (Ping timeout: 240 seconds) 01:05:04 --- join: jedb (~jedb@123.100.45.84) joined #forth 01:17:50 --- quit: rtmanpages (Ping timeout: 240 seconds) 01:51:02 --- join: proteusguy (~proteus-g@183.88.65.145) joined #forth 01:51:02 --- mode: ChanServ set +v proteusguy 01:57:19 --- quit: proteusguy (Ping timeout: 260 seconds) 02:01:29 --- quit: jedb (Ping timeout: 258 seconds) 02:01:46 --- join: jedb (~jedb@199.66.90.113) joined #forth 02:22:04 --- join: smokeink (~smoke@221.7.252.119) joined #forth 02:51:15 --- quit: wa5qjh_ (Remote host closed the connection) 02:52:51 --- join: wa5qjh_ (~Thunderbi@freebsd/user/wa5qjh) joined #forth 02:56:02 --- quit: wa5qjh_ (Remote host closed the connection) 02:58:44 --- join: wa5qjh_ (~Thunderbi@freebsd/user/wa5qjh) joined #forth 03:07:39 --- join: mnemnion (~mnemnion@c-73-34-61-146.hsd1.co.comcast.net) joined #forth 03:11:43 --- quit: mnemnion (Ping timeout: 240 seconds) 03:24:23 --- quit: zy]x[yz (Ping timeout: 248 seconds) 03:26:01 --- join: rtmanpages (~rtmanpage@56.sub-174-204-9.myvzw.com) joined #forth 03:29:14 --- quit: wa5qjh_ (Remote host closed the connection) 04:09:11 --- join: zy]x[yz (~corey@unaffiliated/cmtptr) joined #forth 04:21:59 --- quit: nighty- (Quit: Disappears in a puff of smoke) 04:33:01 --- join: proteusguy (~proteusgu@180.183.142.238) joined #forth 04:33:01 --- mode: ChanServ set +v proteusguy 04:34:45 --- quit: proteus-guy (Ping timeout: 248 seconds) 04:37:15 --- quit: proteusguy (Read error: Connection reset by peer) 04:37:36 --- join: proteusguy (~proteusgu@14.207.87.124) joined #forth 04:37:36 --- mode: ChanServ set +v proteusguy 05:04:49 --- join: nighty- (~nighty@s229123.ppp.asahi-net.or.jp) joined #forth 05:05:27 --- quit: zy]x[yz (Ping timeout: 240 seconds) 05:23:18 --- join: zy]x[yz (~corey@unaffiliated/cmtptr) joined #forth 05:41:38 --- quit: wa5qjh (Read error: Connection reset by peer) 05:50:54 --- join: wa5qjh (~Thunderbi@freebsd/user/wa5qjh) joined #forth 05:52:04 --- quit: wa5qjh (Read error: Connection reset by peer) 05:53:17 Is there more than one integer divide/mod instruction? Is there a symmetric divide and symmetric mod? 05:53:18 --- join: wa5qjh (~Thunderbi@freebsd/user/wa5qjh) joined #forth 05:53:38 --- join: leaverite (~quassel@175.158.225.198) joined #forth 05:53:38 --- quit: leaverite (Changing host) 05:53:38 --- join: leaverite (~quassel@freebsd/user/wa5qjh) joined #forth 05:54:07 --- nick: leaverite -> wa5qjh_ 05:59:19 --- quit: wa5qjh (Remote host closed the connection) 05:59:19 --- quit: wa5qjh_ (Remote host closed the connection) 06:20:40 --- join: rprimus (~micro@178.79.128.27) joined #forth 06:27:48 --- join: proteus-guy (~proteus-g@14.207.87.124) joined #forth 06:54:27 --- quit: proteus-guy (Ping timeout: 255 seconds) 07:02:45 --- quit: smokeink (Quit: leaving) 07:09:45 --- quit: proteusguy (Ping timeout: 255 seconds) 07:16:17 --- join: mnemnion (~mnemnion@c-73-34-61-146.hsd1.co.comcast.net) joined #forth 07:17:20 --- quit: mnemnion (Remote host closed the connection) 07:19:09 --- join: mnemnion (~mnemnion@c-73-34-61-146.hsd1.co.comcast.net) joined #forth 07:24:24 --- quit: mnemnion (Ping timeout: 246 seconds) 07:40:21 ANS specifies a few variations. 07:40:28 6.1.1561 FM/MOD "f-m-slash-mod" CORE 07:40:28 ( d1 n1 -- n2 n3 ) 07:40:28 Divide d1 by n1, giving the floored quotient n3 and the remainder n2. 07:40:28 Input and output stack arguments are signed. An ambiguous condition 07:40:28 exists if n1 is zero or if the quotient lies outside the range of a 07:40:28 single-cell signed integer. 07:40:28 6.1.2214 SM/REM "s-m-slash-rem" CORE 07:40:29 ( d1 n1 -- n2 n3 ) 07:40:29 Divide d1 by n1, giving the symmetric quotient n3 and the remainder n2. 07:40:30 Input and output stack arguments are signed. An ambiguous condition 07:40:30 exists if n1 is zero or if the quotient lies outside the range of a 07:40:31 single-cell signed integer. 07:40:59 --- join: mnemnion (~mnemnion@c-73-34-61-146.hsd1.co.comcast.net) joined #forth 07:43:25 Also UM/MOD (6.1.2370) for unsigned integers 07:45:23 --- quit: mnemnion (Ping timeout: 240 seconds) 08:02:45 --- quit: jedb (Read error: Connection reset by peer) 08:21:16 --- join: jedb (~jedb@123.100.45.84) joined #forth 08:29:24 --- quit: jedb (Ping timeout: 255 seconds) 08:29:43 --- join: jedb (jedb@gateway/vpn/mullvad/x-ipakypsiklesfpfz) joined #forth 08:44:22 --- join: mnemnion (~mnemnion@c-73-34-61-146.hsd1.co.comcast.net) joined #forth 08:49:09 --- quit: mnemnion (Ping timeout: 260 seconds) 08:54:56 --- join: dys (~dys@2a01:598:9903:42de:226:5eff:fee9:68d2) joined #forth 09:00:16 --- join: mnemnion (~mnemnion@c-73-34-61-146.hsd1.co.comcast.net) joined #forth 09:04:57 --- quit: mnemnion (Ping timeout: 255 seconds) 09:16:03 --- join: mnemnion (~mnemnion@c-73-34-61-146.hsd1.co.comcast.net) joined #forth 09:20:39 --- quit: mnemnion (Ping timeout: 260 seconds) 09:30:42 --- quit: MrBusiness3 (Read error: Connection reset by peer) 09:31:51 --- join: mnemnion (~mnemnion@c-73-34-61-146.hsd1.co.comcast.net) joined #forth 09:32:05 --- join: MrBusiness3 (~ArcMrBism@2602:306:8325:a300:c801:d7f:77e1:92be) joined #forth 09:36:07 --- quit: mnemnion (Ping timeout: 248 seconds) 09:46:32 --- join: mnemnion (~mnemnion@c-73-34-61-146.hsd1.co.comcast.net) joined #forth 09:46:33 --- quit: mnemnion (Remote host closed the connection) 09:46:49 --- join: mnemnion (~mnemnion@c-73-34-61-146.hsd1.co.comcast.net) joined #forth 10:10:16 --- join: Mat4 (~david@ip5b409eae.dynamic.kabel-deutschland.de) joined #forth 10:21:03 --- join: rixard (~rixard@h-103-65.A444.priv.bahnhof.se) joined #forth 10:23:23 --- quit: rixard (Client Quit) 10:23:46 --- quit: Mat4 (Quit: leaving) 10:32:24 --- join: proteusguy (~proteus-g@2405:9800:bc10:1ca:6194:7d6f:75f1:d62c) joined #forth 10:32:24 --- mode: ChanServ set +v proteusguy 10:36:28 --- quit: rprimus (Quit: leaving) 10:42:11 --- join: rprimus (~micro@a9.lence.net) joined #forth 10:48:36 --- quit: mnemnion (Remote host closed the connection) 10:49:09 --- join: mnemnion (~mnemnion@c-73-34-61-146.hsd1.co.comcast.net) joined #forth 10:53:23 --- quit: mnemnion (Ping timeout: 240 seconds) 11:04:44 --- join: mnemnion (~mnemnion@c-73-34-61-146.hsd1.co.comcast.net) joined #forth 11:09:03 --- quit: mnemnion (Ping timeout: 255 seconds) 11:13:59 --- join: mnemnion (~mnemnion@c-73-34-61-146.hsd1.co.comcast.net) joined #forth 11:15:17 --- quit: mnemnion (Remote host closed the connection) 11:15:51 --- join: mnemnion (~mnemnion@c-73-34-61-146.hsd1.co.comcast.net) joined #forth 11:20:24 --- quit: mnemnion (Ping timeout: 255 seconds) 12:06:26 so I wonder.. 12:06:33 any people very familiar with fig forth? 12:06:49 I still wonder whether I like forth or find it to be a piece of trash 12:06:59 zy]x[yz: why's that? 12:07:22 because when I think about the idea of forth, I love it 12:07:32 but when I sit down and actually try to use it, I keep finding myself just frustrated 12:07:40 :) 12:10:15 --- quit: proteusguy (Remote host closed the connection) 12:11:26 --- join: proteusguy (~proteus-g@2405:9800:bc10:1ca:d135:4226:9c98:ebab) joined #forth 12:11:26 --- mode: ChanServ set +v proteusguy 12:13:29 FatalNIX: yes. You don't want to learn it. 12:13:40 Why is that 12:13:48 FatalNIX: and yes, Forth is a piece of trash in general. 12:13:57 fig-Forth is quite special kind of trash. 12:14:34 What are my best options besides writing my own for running Forth on a 6502? For some reason, my porting attempts didn't seem to work right for fig forth.. 12:14:59 (I'd say that you don't want to run 6502 at all...) 12:15:14 If eForth doesn't work there... 12:15:18 Now that's just unproductive 12:15:31 Using Forth is what is unproductive. 12:20:50 There's a C64 Forth called durexforth. 12:21:04 And one for the PET called pettil. 12:26:19 volksForth has a 6502 variant: https://sourceforge.net/projects/volksforth/files/ 12:29:54 IIRC, I have seen it, and it is even trashier than figForth. 12:36:29 I have no experience with it, my limited knowledge of it is that it was at least partially the basis for bigForth and gForth 12:39:52 I think I might just write my own 12:40:06 figforth did something that actually seemed quite amazing 12:40:15 it placed the TIB in stack space 12:40:28 that's actually a really cool idea 12:46:16 seems like a bad idea to me; why would you want a user input area in a place that can overwrite your stacks? 12:46:49 Yeah, boundary checks are no-no in Forth. :D 12:56:27 * crc wonders which fig-forth does this; the 6502 listing at http://forth.org/fig-forth/fig-forth_6502.pdf has TIB at 0x100, and the stack ending at 0x9E 12:56:30 uh 12:56:36 you're dealing with limited flat memory here 12:56:40 there's no boundry checks ANYWHERE 12:56:53 nothing stops you from making the computer go crazy 12:57:16 I see why they did it now and it makes a hell of a lot of sense 12:58:07 so, the 6502 has one stack. What happens is that for the data stack they store it somewhere else, then use the systems stack as a return stack. however, the return stack of 256 bytes is a waste of space, and the remainder of that extra is used for the tib 12:58:18 this provides performance beneifts 12:58:50 benefits* 13:01:19 crc: irrespectively of that, I don't remember boundary checks in EXPECT. 13:03:33 huh 13:03:40 WORD apparently calls BLOCK in figforth 13:03:41 wut 13:04:29 Not in figForth only. 13:04:36 It must call BLOCK anyway. 13:05:08 is BLOCK not analogous to BLK? 13:05:20 Absolutely not. 13:06:24 because I noticed in this fig forth it BLOCK calls RLSW and BLOCK is called by WORD 13:06:36 but that's a problem; RLSW access storage sector data 13:06:44 I can't have that one bit 13:07:04 It calls R/W, which has asm label RSLW. 13:07:33 ah so that's what RLSW is 13:07:38 RSLW* 13:10:14 xek: this system has no storage 13:10:33 woops 13:10:38 why did xek get thrown in there 13:12:23 * DGASAU shrugs. 13:12:58 I'll just have to remove this feature 13:13:30 Good luck learning weirdness of ENCLOSE and deviation of blocks subsystem from all popular texts. 13:14:06 I warned you, but you seem to be smarter. :) 13:15:01 I'm not too worried about it. I may implement some stuff on my TRS-80 to handle block data though 13:15:07 it'l just be slow and annoying 13:15:13 (I only have audio cassette tapes) 13:15:24 but that's a different platform 13:15:45 Well... 13:15:54 ENCLOSE part still applies. 13:16:15 And good luck implementing your own way of storing program source. :D 13:16:23 Including text editor. :D 13:18:36 I'm starting to lean toward just writing my own implementation for this 6502 machine 13:18:42 I will have to for my trs-80 anyways 13:18:45 as well 13:39:19 --- quit: rtmanpages (Ping timeout: 248 seconds) 13:41:28 (Why not just leave the museum piece rest in peace and move on instead?..) 13:54:50 because new computers suck 13:55:31 * DGASAU shrugs. 14:00:48 so here's my idea. I can store the return stack on the actual stack. in the very beginning of the zero page, I can place some important forth 'system' registers as needed, but I only need very few. the rest of the zero page is packed with both the TIB and the parameter stack. this way, both TIB and parameter stack operations can be handled using the X register. The other choice is to put the TIB in upper memory. in this machine the program 14:00:48 is loader at $200 and goes up to $9FFF 14:00:57 after that IO memory exists 14:01:41 I should be able to store the PAD right at the end of memory under $A000 and if I have an upper memory TIB, put the TIB there too 14:01:53 but I see no need to have a parameter stack size that is almost 256, it feels like a waste of memory 14:02:19 For toy problems you don't need stack at all. :) 14:02:28 (PDP-8...) 14:02:39 lol 14:02:48 I would love to have a PDP-11 or something right now 14:02:55 in my office 14:03:10 it would be an interesting change from my color computer 14:04:00 I figure since the 6502 has a stasck might as well use it 14:04:18 i don't like having holes of memory 14:04:59 this is why my 6502 SBC design has an MMU that lets you remap every block anywhere you want, to help with hardware memory maps giving you little holes everywhere 14:06:36 Sure, it is so important not to have memory holes. :D 14:17:08 --- quit: MrBusiness3 (Quit: https://www.youtube.com/watch?v=xIIqYqtR1lY -- Suicide is Painless - Johnny Mandel) 14:17:53 --- join: rtmanpages (~rtmanpage@111.sub-174-204-4.myvzw.com) joined #forth 14:28:02 --- join: MrBusiness (~ArcMrBism@2602:306:8325:a300:89dc:5656:5379:b9ce) joined #forth 14:50:09 --- join: wa5qjh (~Thunderbi@freebsd/user/wa5qjh) joined #forth 14:54:40 --- quit: wa5qjh (Ping timeout: 258 seconds) 14:55:35 --- join: wa5qjh (~Thunderbi@freebsd/user/wa5qjh) joined #forth 14:58:42 --- join: wa5qjh_ (~Thunderbi@freebsd/user/wa5qjh) joined #forth 15:00:02 --- quit: wa5qjh (Ping timeout: 258 seconds) 15:02:57 --- quit: wa5qjh_ (Ping timeout: 240 seconds) 15:04:41 --- join: wa5qjh (~Thunderbi@freebsd/user/wa5qjh) joined #forth 15:08:57 --- quit: wa5qjh (Ping timeout: 240 seconds) 15:10:18 --- join: wa5qjh (~Thunderbi@freebsd/user/wa5qjh) joined #forth 15:13:41 --- join: wa5qjh_ (~Thunderbi@freebsd/user/wa5qjh) joined #forth 15:14:44 --- quit: wa5qjh (Ping timeout: 260 seconds) 15:14:45 --- nick: wa5qjh_ -> wa5qjh 15:24:36 --- join: wa5qjh_ (~Thunderbi@freebsd/user/wa5qjh) joined #forth 15:25:27 --- quit: wa5qjh (Ping timeout: 248 seconds) 15:25:27 --- nick: wa5qjh_ -> wa5qjh 15:29:43 --- quit: wa5qjh (Ping timeout: 248 seconds) 15:30:35 --- join: wa5qjh (~Thunderbi@freebsd/user/wa5qjh) joined #forth 15:35:46 --- join: wa5qjh_ (~Thunderbi@freebsd/user/wa5qjh) joined #forth 15:37:11 --- quit: wa5qjh (Ping timeout: 248 seconds) 15:37:11 --- nick: wa5qjh_ -> wa5qjh 15:41:27 --- quit: wa5qjh (Ping timeout: 248 seconds) 15:41:36 --- join: wa5qjh_ (~Thunderbi@freebsd/user/wa5qjh) joined #forth 15:47:06 --- join: wa5qjh_1 (~Thunderbi@freebsd/user/wa5qjh) joined #forth 15:48:23 --- quit: wa5qjh_ (Ping timeout: 248 seconds) 15:48:23 --- nick: wa5qjh_1 -> wa5qjh_ 15:52:39 --- quit: wa5qjh_ (Ping timeout: 248 seconds) 15:52:51 --- join: wa5qjh_ (~Thunderbi@freebsd/user/wa5qjh) joined #forth 15:57:35 --- join: wa5qjh_1 (~Thunderbi@freebsd/user/wa5qjh) joined #forth 15:59:03 --- quit: wa5qjh_ (Ping timeout: 248 seconds) 15:59:04 --- nick: wa5qjh_1 -> wa5qjh_ 16:03:27 --- quit: wa5qjh_ (Ping timeout: 255 seconds) 16:45:40 --- quit: nighty- (Quit: Disappears in a puff of smoke) 16:47:41 --- join: wa5qjh_ (~Thunderbi@freebsd/user/wa5qjh) joined #forth 16:48:02 --- join: wa5qjh (~quassel@freebsd/user/wa5qjh) joined #forth 16:48:41 ? 16:49:27 * irc #forth @ . * 16:51:50 has anybody seen a Forth running in an ARM7 device such asan R-pi or beagelboneBlack without another OS to support it ? 16:52:09 you mean ARMv7? 16:52:13 os like linux or freeBSD ? 16:52:20 yeah 16:53:03 * jn__ hasn't seen one, but for lack of looking 16:53:28 Forth is supposed to be an OS too. yeah, me too. 16:54:56 I've seen forth running in several micro-controllers but all like msp430, 6809 etc. etc. 16:57:09 there's pbforth for, among others, the 'Mindstorm' toys, I dont know if the Arduino has any kind opf serial port or other means to 'talk' to a 'host' of some kind. 16:59:18 I'd kinda like to put forth on a R-Pi by itself, sans linux etc. Thinking more of the Pi-Zero tho. 17:00:29 so, like tht, it would have to be able to work in blocks/screens tho, I'd think 17:06:10 at the moment tho, it sounds like a pie-in-the-sky sort of idea. I dont think there's be any way to talk to it except a rs232/tty connection. It would Have to have host os support to do wifi at the moment as far as I can tell. 17:24:40 ==well, anyway, just a thought :) 17:38:34 forth on the VideoCore4 (the boot that boots first on the RasPi) would be an interesting exercise too 17:47:13 Wasn't Forth used for a Sun BIOS already? 17:52:52 OpenFirmware, yes 17:53:34 (not just Sun used OF, but also IBM, and probably others) 17:53:49 Does anyone use it anymore? 17:56:16 OF-derived "device trees" are commonly used in all kinds of ARM devices, but i don't think real OF is used anymore in new products 18:04:20 --- quit: dys (Ping timeout: 264 seconds) 18:07:09 --- join: wa5qjh_1 (~Thunderbi@freebsd/user/wa5qjh) joined #forth 18:07:23 --- quit: wa5qjh_ (Ping timeout: 240 seconds) 18:07:24 --- nick: wa5qjh_1 -> wa5qjh_ 18:09:00 --- quit: wa5qjh (Ping timeout: 255 seconds) 18:09:15 --- join: wa5qjh (~quassel@175.158.225.198) joined #forth 18:09:15 --- quit: wa5qjh (Changing host) 18:09:15 --- join: wa5qjh (~quassel@freebsd/user/wa5qjh) joined #forth 18:12:44 --- join: wa5qjh_1 (~Thunderbi@freebsd/user/wa5qjh) joined #forth 18:13:30 --- quit: wa5qjh_ (Ping timeout: 240 seconds) 18:13:31 --- nick: wa5qjh_1 -> wa5qjh_ 18:16:54 --- join: wa5qjh_1 (~Thunderbi@freebsd/user/wa5qjh) joined #forth 18:17:50 --- quit: wa5qjh_ (Ping timeout: 240 seconds) 18:17:51 --- nick: wa5qjh_1 -> wa5qjh_ 18:22:19 --- quit: wa5qjh_ (Ping timeout: 240 seconds) 18:22:20 --- join: wa5qjh_1 (~Thunderbi@freebsd/user/wa5qjh) joined #forth 18:25:39 FreeBSD uses pfe forth to boot the os. 18:26:19 --- quit: wa5qjh_1 (Ping timeout: 240 seconds) 18:28:15 --- join: wa5qjh_ (~Thunderbi@freebsd/user/wa5qjh) joined #forth 18:30:54 is ther any ssh or sshd support for Forth in any version? I installed gforth on an old android device last night and it said something about getting to port 4444 to talk to it., but not sure if it was ssh in forth or not. 18:31:03 --- join: wa5qjh_1 (~Thunderbi@freebsd/user/wa5qjh) joined #forth 18:32:19 --- quit: wa5qjh_ (Ping timeout: 240 seconds) 18:32:20 --- nick: wa5qjh_1 -> wa5qjh_ 18:32:48 Dunno, but I think it would be quite a task to get a real useable 'native' forth onto a pi or any other ARMv7 device. 18:33:21 far beyond my meager abilities. 18:37:05 but being a sort of robotic or 'play with the hardware' kind of platform forth would be a natural.. really, the only 'natural' 18:38:23 --- join: wa5qjh_1 (~Thunderbi@freebsd/user/wa5qjh) joined #forth 18:39:09 There was a 7-segment scrolling message badge made for the Vintage Computer Festival Midwest using a 6502 microprocessor. It has a serial port so you can hook it up to a terminal or terminal program and use it. This would make a nice forth computer. 18:39:15 Badge: http://www.sunrise-ev.com/6502.htm 18:39:35 --- quit: wa5qjh_ (Ping timeout: 248 seconds) 18:39:35 --- nick: wa5qjh_1 -> wa5qjh_ 18:39:36 Badge: http://www.sunrise-ev.com/photos/6502/manual-rev5dr.pdf 18:40:48 maybe some sort of 'minimallinux or bsd OS to be booted from videoCore4 with hooks from forth into the OS for some basic resources like ssh usb, and maybe ascii file support to be used alongside blks. ( I'm guessing) . 18:40:55 I am hoping that someone will make a badge / single board computer using the 6809/6309. 18:42:30 6809, as much as I love that old thing, is getting old. the 6812 implements all or most of the same instructions but I dont think it's binary compatible 18:43:19 At work I am using a HCS08 (68HC08) for a new project. 18:43:31 --- join: nighty- (~nighty@kyotolabs.asahinet.com) joined #forth 18:43:45 in a datasheet for it, they said it implememnted al l the addressing modes of the 6809 with a few 'enhancements' to a couple of them. 18:44:17 The 6812 is likely the better then the 6808. 18:44:18 have you got a good forth for it? how much memory does it take ? 18:44:39 and maybe a little easier to get, too. 18:45:13 I've got a few HC08's myself. including the qt4 18:45:29 hc08qt4 18:45:41 One of the 6808 has 60k of ROM and 4k of RAM. You can add more RAM to the 6808 using a I2C or SPI port. 18:46:07 used to have a bag of them but lotta stuff lost since I moved here. 18:47:04 I think they have a HCS08 with 128kB but the index registers 16-bits. 18:47:16 I think they have a HCS08 with 128kB ROM but the index registers 16-bits. 18:48:03 index register and in only one index register. 18:48:21 Hey!! think I've got one of those still says MOTOROLA on it MC68DEMO908GB60 18:48:59 actually manufactoired by AXIOM 18:49:07 The NXP HCS08 can run at 20MHz bus clock. 18:49:54 But no documentation on the board any more, dern it!1 18:50:24 and I think it's hc908QT4's 18:50:25 The Pi 3 has 4 cores so you could run multitasking forth. 18:52:05 The 6502 can use self-modifying code. 18:52:38 If running out of RAM. 18:53:55 Yeah, and I want one too!! very hard to get my hands on out here in backwoods of Philippines. ! 18:54:28 The 6809 can be emulated in a FPGA and run at 25 MHz. 18:55:41 rather use one of the 2 HC12's on hand since like the pi-3b I'd never get my hands on a fpga 6809. :) 18:56:40 The HC12 should be fine. 18:56:59 --- quit: wa5qjh_ (Remote host closed the connection) 18:57:15 --- join: wa5qjh_ (~Thunderbi@freebsd/user/wa5qjh) joined #forth 18:57:52 6809 can support moveable code even. meaning move the binary from one place in memory to another and it still works. totally re-locateable/. 18:58:16 --- quit: karswell_ (Read error: Connection reset by peer) 18:58:33 so, do you have a forth for that 60K HC08 ? 19:02:38 --- join: wa5qjh_1 (~Thunderbi@freebsd/user/wa5qjh) joined #forth 19:03:33 --- quit: wa5qjh_ (Ping timeout: 248 seconds) 19:03:34 --- nick: wa5qjh_1 -> wa5qjh_ 19:06:26 (I really like bold false statements like "FreeBSD uses pfe forth to boot the os". They don't leave doubts in Forth experts' level.) 19:07:51 --- quit: wa5qjh_ (Ping timeout: 248 seconds) 19:08:08 --- join: wa5qjh_ (~Thunderbi@freebsd/user/wa5qjh) joined #forth 19:09:06 DGASAU. dont unbderstand. what you mean ? 19:10:01 what is it you're contesting ? 19:10:03 I mean that the statement "FreeBSD uses pfe forth to boot the os" is so obviously false that it makes think that you haven't seen at least one of things mentioned. 19:11:05 I've got the whole set of textfiles it uses in /boot it doent use grub. 19:11:19 So what? 19:11:32 How does that make the statement true? 19:11:53 so, what part of my statement dont you believe ? 19:13:39 what part of it are you claiming to be false ? 19:13:48 No I do not have forth for the hc08. 19:15:28 I think code for the 6805 can be assembled to run on a 6808. 19:15:53 This part is false: "FreeBSD uses pfe forth to boot the os". 19:16:19 You must have never seen either PFE Forth, or FreeBSD boot loader. 19:16:48 Or both. 19:19:45 --- join: wa5qjh_1 (~Thunderbi@freebsd/user/wa5qjh) joined #forth 19:20:16 why you say that? what are you using for your OS/ windoze ? ubuntu? 19:20:39 Why does the latter matter even? 19:20:56 The statement that is false is this one of yours: "FreeBSD uses pfe forth to boot the os". 19:21:11 --- quit: wa5qjh_ (Ping timeout: 248 seconds) 19:21:12 --- nick: wa5qjh_1 -> wa5qjh_ 19:23:14 What is d compared to an s in 20 s>d. 19:23:18 I'M Running FreeBSD11-RELEASE and have both gforth and PFE installed here. and have copied the additional files pfe uses in th boot process. Som, yeah, it does matter since you're calling me a liar 19:23:37 Yes, you are a liar. 19:23:48 Single to double? 19:24:03 Whether you have gforth or PFE installed doesn't matter, since those are user-level programs. 19:24:11 They don't even belong to base system. 19:24:31 You would be pretty much aware of that were you actually using FreeBSD. 19:25:34 no, they dont. I chose to add the 'user level pfe forth specifically because FreeBSD is using pfe for the loader. it's used Forth as it's loader probalbyly all the way back to 2.2 19:25:38 (At least, normally FreeBSD users are aware of the distinction between kernel code, base system code, and the rest.) 19:26:00 FreeBSD has never used PFE for loader. 19:26:14 And it doesn't use it either still. ;) 19:26:20 I've been using FreeBSD since before Jordan Hubbard left to goto work for Apple. 19:26:34 * crc is pretty sure freebsd has used ficl, not pfe 19:26:45 Given that you insist on this, you lack skills just to check what FreeBSD uses. ;) 19:27:16 that would be about FreeBSD 2.2 or before. was even on subscription to it with Walnut Creek for a long time! 19:27:59 OK, this discussion is over. go back to your hidey hole and troll somebody else. 19:28:36 Note that the time you're using FreeBSD (if that is true) still doesn't make your statement true. 19:28:53 FreeBSD doesn't use PFE. 19:29:01 Nethier in base system, nor in kernel, nor in loader. 19:29:30 (Hell, you're not even aware of licensing terms of PFE!) 19:32:13 wa5qjh: definitely ficl, not pfe: https://svnweb.freebsd.org/base/head/sys/boot/ 19:34:00 --- join: wa5qjh_1 (~Thunderbi@freebsd/user/wa5qjh) joined #forth 19:34:30 --- quit: wa5qjh_ (Ping timeout: 255 seconds) 19:34:30 --- nick: wa5qjh_1 -> wa5qjh_ 19:38:11 -20 s>d 7 sm/rem . . -2 -6 ok 19:38:12 -20 s>d 7 fm/mod . . -3 1 ok 19:38:12 -20 7 mod -20 7 / . . -3 1 ok 19:38:12 20 s>d 7 um/mod . . 2 6 ok 19:38:53 crc, ok, guess I was mistaken about pfe but it's still forth 19:39:00 --- quit: wa5qjh_ (Ping timeout: 255 seconds) 19:39:16 * DGASAU shrugs. 19:39:49 --- join: wa5qjh_ (~Thunderbi@freebsd/user/wa5qjh) joined #forth 19:39:50 ("Competent" FreeBSD users cannot even look into /usr/src...) 19:43:50 crc I cant remember I'd even seen ficl as a name of forth before. Thanks. installing it now. 19:44:24 --- quit: wa5qjh_ (Ping timeout: 255 seconds) 19:45:50 --- join: wa5qjh_ (~Thunderbi@freebsd/user/wa5qjh) joined #forth 19:46:17 Which proves my point that you have never seen FreeBSD loader before. :D 19:47:55 nice looking wordset too. and 'words' laid out much more readable than gforth. 19:48:54 Except that some fundamental constructs don't work. 19:49:40 And unlikely to start working ever. 19:53:03 --- join: wa5qjh_1 (~Thunderbi@freebsd/user/wa5qjh) joined #forth 19:54:45 --- quit: wa5qjh_ (Ping timeout: 255 seconds) 19:57:27 --- quit: wa5qjh_1 (Ping timeout: 240 seconds) 19:59:02 --- join: wa5qjh_ (~Thunderbi@freebsd/user/wa5qjh) joined #forth 20:01:52 --- join: wa5qjh_1 (~Thunderbi@freebsd/user/wa5qjh) joined #forth 20:02:57 --- quit: wa5qjh_ (Ping timeout: 240 seconds) 20:02:58 --- nick: wa5qjh_1 -> wa5qjh_ 20:07:27 --- join: wa5qjh_1 (~Thunderbi@freebsd/user/wa5qjh) joined #forth 20:07:35 --- quit: wa5qjh_ (Ping timeout: 248 seconds) 20:07:35 --- nick: wa5qjh_1 -> wa5qjh_ 20:11:51 --- quit: wa5qjh_ (Ping timeout: 248 seconds) 20:13:31 --- join: wa5qjh_ (~Thunderbi@freebsd/user/wa5qjh) joined #forth 20:17:43 --- quit: wa5qjh_ (Ping timeout: 248 seconds) 20:19:31 --- join: wa5qjh_ (~Thunderbi@freebsd/user/wa5qjh) joined #forth 20:23:35 --- quit: wa5qjh_ (Ping timeout: 248 seconds) 20:25:26 --- join: wa5qjh_ (~Thunderbi@freebsd/user/wa5qjh) joined #forth 20:30:42 --- join: wa5qjh_1 (~Thunderbi@freebsd/user/wa5qjh) joined #forth 20:32:07 --- quit: wa5qjh_ (Ping timeout: 248 seconds) 20:32:07 --- nick: wa5qjh_1 -> wa5qjh_ 20:35:11 --- join: wa5qjh_1 (~Thunderbi@freebsd/user/wa5qjh) joined #forth 20:36:23 --- quit: wa5qjh_ (Ping timeout: 248 seconds) 20:36:25 --- nick: wa5qjh_1 -> wa5qjh_ 20:40:37 --- quit: wa5qjh_ (Ping timeout: 248 seconds) 20:40:50 --- join: wa5qjh_ (~Thunderbi@freebsd/user/wa5qjh) joined #forth 20:44:53 --- quit: wa5qjh_ (Ping timeout: 248 seconds) 20:46:05 --- join: wa5qjh_ (~Thunderbi@freebsd/user/wa5qjh) joined #forth 20:48:56 --- join: wa5qjh_1 (~Thunderbi@freebsd/user/wa5qjh) joined #forth 20:50:13 --- quit: wa5qjh_ (Ping timeout: 248 seconds) 20:50:14 --- nick: wa5qjh_1 -> wa5qjh_ 20:52:21 --- quit: rtmanpages (Ping timeout: 255 seconds) 20:55:21 --- join: wa5qjh_1 (~Thunderbi@freebsd/user/wa5qjh) joined #forth 20:56:43 --- quit: wa5qjh_ (Ping timeout: 240 seconds) 20:56:43 --- nick: wa5qjh_1 -> wa5qjh_ 21:01:03 --- quit: wa5qjh_ (Ping timeout: 240 seconds) 21:01:11 --- join: wa5qjh_1 (~Thunderbi@freebsd/user/wa5qjh) joined #forth 21:03:57 --- join: wa5qjh_ (~Thunderbi@freebsd/user/wa5qjh) joined #forth 21:05:23 --- quit: wa5qjh_1 (Ping timeout: 240 seconds) 21:08:21 --- quit: wa5qjh_ (Ping timeout: 248 seconds) 21:09:52 --- join: wa5qjh_ (~Thunderbi@freebsd/user/wa5qjh) joined #forth 21:15:03 --- join: wa5qjh_1 (~Thunderbi@freebsd/user/wa5qjh) joined #forth 21:16:21 --- quit: wa5qjh_ (Ping timeout: 248 seconds) 21:16:22 --- nick: wa5qjh_1 -> wa5qjh_ 21:19:15 --- join: wa5qjh_1 (~Thunderbi@freebsd/user/wa5qjh) joined #forth 21:20:37 --- quit: wa5qjh_ (Ping timeout: 248 seconds) 21:20:38 --- nick: wa5qjh_1 -> wa5qjh_ 21:24:57 --- quit: wa5qjh_ (Ping timeout: 240 seconds) 21:25:03 --- join: wa5qjh_1 (~Thunderbi@freebsd/user/wa5qjh) joined #forth 21:29:27 --- quit: wa5qjh_1 (Ping timeout: 240 seconds) 21:31:02 --- join: wa5qjh_ (~Thunderbi@freebsd/user/wa5qjh) joined #forth 21:33:51 --- join: wa5qjh_1 (~Thunderbi@freebsd/user/wa5qjh) joined #forth 21:34:57 --- quit: wa5qjh_ (Ping timeout: 240 seconds) 21:34:58 --- nick: wa5qjh_1 -> wa5qjh_ 21:39:19 --- quit: wa5qjh_ (Ping timeout: 248 seconds) 21:39:26 --- join: wa5qjh_1 (~Thunderbi@freebsd/user/wa5qjh) joined #forth 21:43:35 --- quit: wa5qjh_1 (Ping timeout: 248 seconds) 21:45:25 --- join: wa5qjh_ (~Thunderbi@freebsd/user/wa5qjh) joined #forth 21:48:13 --- join: wa5qjh_1 (~Thunderbi@freebsd/user/wa5qjh) joined #forth 21:49:59 --- quit: wa5qjh_ (Ping timeout: 248 seconds) 21:51:14 --- join: wa5qjh_ (~Thunderbi@freebsd/user/wa5qjh) joined #forth 21:52:34 --- quit: wa5qjh_1 (Ping timeout: 260 seconds) 21:55:27 --- quit: wa5qjh_ (Ping timeout: 240 seconds) 21:57:14 --- join: wa5qjh_ (~Thunderbi@freebsd/user/wa5qjh) joined #forth 22:01:27 --- quit: wa5qjh_ (Ping timeout: 240 seconds) 22:03:09 --- join: wa5qjh_ (~Thunderbi@freebsd/user/wa5qjh) joined #forth 22:07:27 --- quit: wa5qjh_ (Ping timeout: 240 seconds) 22:08:24 --- join: wa5qjh_ (~Thunderbi@freebsd/user/wa5qjh) joined #forth 22:12:05 --- quit: proteusguy (Remote host closed the connection) 22:12:27 --- quit: wa5qjh_ (Ping timeout: 240 seconds) 22:13:29 --- join: wa5qjh_ (~Thunderbi@freebsd/user/wa5qjh) joined #forth 22:17:27 --- quit: wa5qjh_ (Ping timeout: 240 seconds) 22:19:25 --- join: wa5qjh_ (~Thunderbi@freebsd/user/wa5qjh) joined #forth 22:21:52 --- quit: ecraven (Remote host closed the connection) 22:23:35 --- quit: wa5qjh_ (Ping timeout: 248 seconds) 22:25:25 --- join: wa5qjh_ (~Thunderbi@freebsd/user/wa5qjh) joined #forth 22:31:01 --- join: wa5qjh_1 (~Thunderbi@freebsd/user/wa5qjh) joined #forth 22:31:03 --- quit: wa5qjh_ (Ping timeout: 248 seconds) 22:31:03 --- nick: wa5qjh_1 -> wa5qjh_ 22:33:24 --- join: proteusguy (~proteus-g@183.89.209.32) joined #forth 22:33:24 --- mode: ChanServ set +v proteusguy 22:38:10 --- join: wa5qjh_1 (~Thunderbi@freebsd/user/wa5qjh) joined #forth 22:39:35 --- quit: wa5qjh_ (Ping timeout: 248 seconds) 22:39:36 --- nick: wa5qjh_1 -> wa5qjh_ 22:43:50 --- quit: wa5qjh_ (Ping timeout: 240 seconds) 22:44:04 --- join: wa5qjh_ (~Thunderbi@freebsd/user/wa5qjh) joined #forth 22:45:57 --- quit: reepca (Ping timeout: 240 seconds) 22:48:10 --- quit: wa5qjh_ (Ping timeout: 240 seconds) 22:49:10 --- join: wa5qjh_ (~Thunderbi@freebsd/user/wa5qjh) joined #forth 22:52:00 --- join: wa5qjh_1 (~Thunderbi@freebsd/user/wa5qjh) joined #forth 22:53:10 --- quit: wa5qjh_ (Ping timeout: 240 seconds) 22:53:10 --- nick: wa5qjh_1 -> wa5qjh_ 22:57:40 --- join: wa5qjh_1 (~Thunderbi@freebsd/user/wa5qjh) joined #forth 22:57:43 --- quit: wa5qjh_ (Ping timeout: 248 seconds) 22:57:43 --- nick: wa5qjh_1 -> wa5qjh_ 23:01:59 --- quit: wa5qjh_ (Ping timeout: 248 seconds) 23:03:39 --- join: wa5qjh_ (~Thunderbi@freebsd/user/wa5qjh) joined #forth 23:06:30 --- join: wa5qjh_1 (~Thunderbi@freebsd/user/wa5qjh) joined #forth 23:07:51 --- quit: wa5qjh_ (Ping timeout: 248 seconds) 23:07:52 --- nick: wa5qjh_1 -> wa5qjh_ 23:13:55 --- join: wa5qjh_1 (~Thunderbi@freebsd/user/wa5qjh) joined #forth 23:14:33 --- quit: wa5qjh_ (Ping timeout: 255 seconds) 23:14:33 --- nick: wa5qjh_1 -> wa5qjh_ 23:19:36 --- join: wa5qjh_1 (~Thunderbi@freebsd/user/wa5qjh) joined #forth 23:21:17 --- quit: wa5qjh_ (Ping timeout: 255 seconds) 23:23:50 --- quit: wa5qjh_1 (Ping timeout: 240 seconds) 23:25:35 --- join: wa5qjh_ (~Thunderbi@freebsd/user/wa5qjh) joined #forth 23:29:16 johnmark, wonder if Freescale sold it's 68 series cpu's to NXP? or if something happened like why AMD is making x86 like cpu's now 23:29:30 --- quit: wa5qjh_ (Ping timeout: 240 seconds) 23:29:55 I was downloading some pdf's while ago and noticed that NXP label on some of it. 23:31:36 --- join: wa5qjh_ (~Thunderbi@freebsd/user/wa5qjh) joined #forth 23:33:47 --- join: MrBismuth (~ArcMrBism@2602:306:8325:a300:89dc:5656:5379:b9ce) joined #forth 23:35:10 --- join: wa5qjh_1 (~Thunderbi@freebsd/user/wa5qjh) joined #forth 23:35:21 --- quit: nighty- (Quit: Disappears in a puff of smoke) 23:35:50 --- quit: wa5qjh_ (Ping timeout: 240 seconds) 23:35:51 --- nick: wa5qjh_1 -> wa5qjh_ 23:36:30 --- quit: MrBusiness (Ping timeout: 255 seconds) 23:36:56 --- join: nighty- (~nighty@kyotolabs.asahinet.com) joined #forth 23:37:27 --- join: ecraven (~ecraven@www.nexoid.at) joined #forth 23:40:48 --- join: wa5qjh_1 (~Thunderbi@freebsd/user/wa5qjh) joined #forth 23:42:27 --- quit: wa5qjh_ (Ping timeout: 240 seconds) 23:42:41 johnmark, I have seen that that M68MOD912C32 and the M68DEMO908GB60 are both still available. I saw the 08 on ebay for $15 & $19 just while ago. but the TI MSP430??2553 launchpad is too and it's got lots of rom and ram space. and some gpio space too, i think. 23:43:28 and they're pretty cheap too. 23:44:57 --- quit: wa5qjh_1 (Ping timeout: 240 seconds) 23:46:47 --- join: wa5qjh_ (~Thunderbi@freebsd/user/wa5qjh) joined #forth 23:55:19 --- join: wa5qjh_1 (~Thunderbi@freebsd/user/wa5qjh) joined #forth 23:55:57 --- quit: wa5qjh_ (Ping timeout: 240 seconds) 23:55:58 --- nick: wa5qjh_1 -> wa5qjh_ 23:56:49 Both of those M68x boards I mentioned have lots of breadboarding space too. 23:57:52 and lots of pins to connect to. R-pi/ eat your heart out :) 23:59:59 --- log: ended forth/17.10.10