00:00:00 --- log: started forth/13.06.03 00:12:19 --- quit: Eth|cal (Read error: Connection timed out) 00:12:52 --- join: Eth|cal (~sam@ppp59-167-172-238.static.internode.on.net) joined #forth 00:22:22 --- join: obobo (~obobo@dyn-76-75-122-56.nexicom.net) joined #forth 00:34:03 --- quit: Eth|cal (Read error: Connection timed out) 00:34:54 --- join: Eth|cal (~sam@ppp59-167-172-238.static.internode.on.net) joined #forth 00:44:53 --- quit: overdamped (Ping timeout: 264 seconds) 00:53:51 --- quit: Nisstyre-laptop (Quit: Leaving) 00:54:24 --- quit: Eth|cal (Read error: Connection timed out) 00:54:56 --- join: Eth|cal (~sam@ppp59-167-172-238.static.internode.on.net) joined #forth 01:05:45 --- quit: ttmrichter (Quit: Quit) 01:05:47 --- join: ttmrichter_ (~ttmrichte@gertm.eu) joined #forth 01:06:25 --- nick: ttmrichter_ -> ttmrichter 01:07:14 --- join: nighty^ (~nighty@tin51-1-82-226-147-104.fbx.proxad.net) joined #forth 01:15:15 --- quit: Eth|cal (Read error: Connection timed out) 01:15:57 --- join: Eth|cal (~sam@ppp59-167-172-238.static.internode.on.net) joined #forth 01:36:52 --- quit: Eth|cal (Read error: Connection timed out) 01:37:29 --- join: Eth|cal (~sam@ppp59-167-172-238.static.internode.on.net) joined #forth 01:37:52 --- join: epicmonkey (~epicmonke@host-224-51.dataart.net) joined #forth 02:08:05 --- quit: Eth|cal (Read error: Operation timed out) 02:49:53 is there really anyone using forth as their os 02:50:03 for daily using 02:50:17 Probably not. 02:50:52 then what about chunk? 02:51:17 I'm sure there's lots of embedded systems that use a Forth-based OS (or at least RMX), however. 02:51:44 i hope mobile app could use this 02:52:28 like when the app launched, it would load a forth kernel, do some initialization jobs and then do the logic part 02:55:39 --- join: rixard_ (~rixard@81-235-139-119-no63.tbcn.telia.com) joined #forth 03:02:26 --- quit: rixard (Read error: Connection reset by peer) 03:02:26 --- nick: rixard_ -> rixard 03:02:26 --- quit: epicmonkey (Ping timeout: 276 seconds) 03:03:47 --- join: epicmonkey (~epicmonke@host-224-51.dataart.net) joined #forth 04:09:17 --- join: Eth|cal (~sam@ppp59-167-172-238.static.internode.on.net) joined #forth 04:53:13 --- join: Nisstyre (~yours@oftn/member/Nisstyre) joined #forth 05:57:56 --- quit: proteusguy (Ping timeout: 260 seconds) 06:10:31 --- join: proteusguy (~proteusgu@ppp-58-8-87-132.revip2.asianet.co.th) joined #forth 06:20:18 I'm working on a system that I hope eventually becomes "my os." Awfully long way to go, though. 06:20:41 Main problem at the moment is that I'm greedy - I want something that an function well as an os but also will serve well in very lean embedded applications. 06:21:05 I've done some work in the past on an FPGA-based stack processor, and I'm looking for a high degree of compatibility between the two things. 06:25:00 KipIngram: Would you mind sharing your FPGA work? 06:25:08 * ttmrichter just got an FPGA devkit. 06:25:27 My first serious project (as opposed to just exercising the FPGA to learn its capabilities) is a stack processor so... 06:27:55 I'd prefer to keep it proprietary, just in case I want to commercialize it at some point. But I would be happy to kick around ideas - I've thought a lot about how to get the best out of FPGA fabrics. What brand FPGA do you have? 06:29:30 I can offer you the most insight about Xilinx Spartan 6. 06:44:20 I have a Cyclone IV. :( 06:44:30 (The smallest one, both in capabilities and in form factor.:D) 06:44:38 Well, ok. 06:44:46 It still might be useful to you for us to chat. 06:45:02 I just won't be able to give as much advice about the fabric details. 06:45:21 If you're interested in more why don't you pm me so we don't clog up the channel. 06:46:01 --- join: RodgerTheGreat (~rodger@50-198-177-185-static.hfc.comcastbusiness.net) joined #forth 07:40:33 but I have a spartan 6 too :( 07:40:39 maybe you could go in ##fpga and talk at me :) 07:41:39 --- nick: kulp_ -> kulp 07:41:56 --- quit: kulp (Changing host) 07:41:56 --- join: kulp (~kulp@unaffiliated/kulp) joined #forth 08:22:54 --- quit: Nisstyre (Read error: Connection reset by peer) 08:24:59 --- join: Nisstyre (~yours@oftn/member/Nisstyre) joined #forth 08:48:30 --- join: mtm (~mtm@c-76-102-52-34.hsd1.ca.comcast.net) joined #forth 08:56:31 --- quit: epicmonkey (Ping timeout: 264 seconds) 09:07:56 --- join: epicmonkey (~epicmonke@host-224-58.dataart.net) joined #forth 09:15:13 --- quit: jyf (Ping timeout: 256 seconds) 09:17:06 --- quit: epicmonkey (Ping timeout: 252 seconds) 09:27:42 --- join: jyf (~root@42.96.194.66) joined #forth 09:32:16 --- join: ncv (~quassel@79.114.118.238) joined #forth 09:32:16 --- quit: ncv (Changing host) 09:32:16 --- join: ncv (~quassel@unaffiliated/neceve) joined #forth 10:11:50 --- nick: Adeon -> Adeonicorn 10:19:43 --- join: Tod-Work (~thansmann@50-202-143-210-static.hfc.comcastbusiness.net) joined #forth 10:26:19 --- join: epicmonkey (~epicmonke@188.134.41.113) joined #forth 11:28:01 --- join: dto (~user@pool-96-252-62-13.bstnma.fios.verizon.net) joined #forth 11:35:10 For you FPGA experimenters: Have you tried C.H. Ting's eP32 processor? 11:41:06 --- quit: proteusguy (Ping timeout: 260 seconds) 12:10:27 --- quit: dto (Remote host closed the connection) 12:40:26 --- quit: ncv (Remote host closed the connection) 12:48:50 --- join: Onionnion (~ryan@adsl-68-254-173-217.dsl.milwwi.ameritech.net) joined #forth 13:00:06 --- join: dto (~user@pool-96-252-62-13.bstnma.fios.verizon.net) joined #forth 13:21:56 --- quit: Onionnion (Read error: Operation timed out) 13:28:37 --- join: ASau` (~user@p5797F121.dip0.t-ipconnect.de) joined #forth 13:32:10 --- quit: ASau (Ping timeout: 276 seconds) 13:35:51 --- nick: ASau` -> ASau 13:51:59 --- quit: dto (Remote host closed the connection) 14:29:47 --- join: Onionnion (~ryan@adsl-68-254-171-150.dsl.milwwi.ameritech.net) joined #forth 14:41:01 --- quit: nighty^ (Remote host closed the connection) 15:04:26 --- join: dto (~user@pool-96-252-62-13.bstnma.fios.verizon.net) joined #forth 15:39:51 --- quit: Nisstyre (Quit: Leaving) 15:42:08 --- quit: Tod-Work (Quit: Leaving) 15:56:14 --- quit: epicmonkey (Ping timeout: 256 seconds) 16:01:37 --- join: epicmonkey (~epicmonke@188.134.41.113) joined #forth 16:09:56 --- quit: epicmonkey (Ping timeout: 264 seconds) 16:12:49 --- quit: dto (Remote host closed the connection) 16:28:17 --- quit: mtm (Quit: Leaving...) 17:11:37 Backer: Have you got a link for that Ting paper? 18:10:36 --- quit: Onionnion (Read error: Connection reset by peer) 18:12:22 http://home.vianetworks.nl/users/mhx/Forth_EP32.pdf 18:41:37 --- join: dto (~user@pool-96-252-62-13.bstnma.fios.verizon.net) joined #forth 19:20:56 --- quit: dto (Remote host closed the connection) 19:35:07 --- join: mtm (~mtm@c-24-130-130-44.hsd1.ca.comcast.net) joined #forth 19:58:14 --- join: proteusguy (~proteusgu@ppp-58-8-87-132.revip2.asianet.co.th) joined #forth 20:15:34 --- join: protist (~protist@236.172.69.111.dynamic.snap.net.nz) joined #forth 20:21:59 Backer: eforth? 20:22:56 any thoughts? :D http://ideone.com/gfa1rl 20:23:07 `does>' is not functional yet 20:27:49 what a coincidence ! neither is mine ! 20:28:55 kulp: hey i'll get it, i've done it before! :D 20:30:57 I haven't :( 20:30:58 hehe 20:31:06 protist: you did it in x86 first right ? 20:31:17 kulp: yep :) 20:34:04 why so many people using x86 asm for impl forth since x86 is not popular in embed domain 20:34:35 jyf: i did it to learn 20:34:38 jyf: Because people have x86 machines. 20:34:46 ^ exactly :) 20:34:47 Not a lot of people collect eval boards like I do. :) 20:34:50 ttmrichter: that's reasonable 20:35:01 * ttmrichter is up to five eval boards obtained in the past three months or so. :) 20:35:38 hmm 20:35:59 protist: then do you have any modern x86 asm quick intro for me? 20:36:15 i dont need those old ibm pc tutorials 20:36:29 jyf: i read just enough Moving Forth to not ruin any surprises...then jumped head first 20:36:29 and i know interupt binary endians 20:36:39 protist: oop 20:36:52 jyf: i'de have to admit that while functional, my implementation was quirky 20:36:56 --- quit: proteusguy (Remote host closed the connection) 20:36:57 protist: but moving forth not use x86 asm isnt it 20:37:13 jyf: i just read the page about threaded code lol 20:37:18 ok 20:37:23 jyf: i read a book on x86 separately 20:39:08 --- join: proteusguy (~proteusgu@ppp-58-8-87-132.revip2.asianet.co.th) joined #forth 20:51:16 I read the old Byte book "Threaded Interpreted Languages" for my first Forth-like. 20:59:22 My favorite Forth book was "Forth Fundamentals" by McCabe. 20:59:36 For implementation - for philosophy it was Brodie's "Thinking Forth." 21:09:53 ttmrichter: what's the date when you read that book 21:10:53 Oh, God. Sometime in the '80s? 21:11:03 I want to say '83, but it might have been a bit later. 21:13:52 i wasnt born at that time 21:14:02 and my father didnt met my mother :] 21:17:37 * ttmrichter could say something cruel about not yet even being a twinkle in the mailman's eye, but won't. 21:18:29 loll 21:18:43 Waitwhat?! Jilin? 21:39:46 --- quit: RodgerTheGreat (Quit: RodgerTheGreat) 21:53:27 --- quit: proteusguy (Remote host closed the connection) 22:09:48 --- join: proteusguy (~proteusgu@180.183.48.210) joined #forth 22:29:38 --- quit: mtm (Quit: Leaving...) 23:03:37 --- quit: ASau (Ping timeout: 252 seconds) 23:03:47 --- quit: protist (Read error: Connection reset by peer) 23:59:59 --- log: ended forth/13.06.03