00:00:00 --- log: started forth/13.08.19 00:03:19 --- join: c00kiemon5ter (~c00kiemon@foss-aueb/coder/c00kiemon5ter) joined #forth 01:32:52 --- quit: Eth|cal (Read error: Connection timed out) 01:33:35 --- join: Eth|cal (~sam@ppp59-167-172-238.static.internode.on.net) joined #forth 01:53:37 --- quit: protist (Ping timeout: 276 seconds) 02:31:12 --- quit: kludge` (Ping timeout: 245 seconds) 02:36:01 --- join: kludge` (~comet@unaffiliated/espiral) joined #forth 02:54:31 --- join: dys (~user@2a01:1e8:e100:8296:21a:4dff:fe4e:273a) joined #forth 03:42:01 --- join: protist (~protist@15.224.69.111.dynamic.snap.net.nz) joined #forth 03:53:56 --- join: tathi (~josh@dsl-216-227-94-110.fairpoint.net) joined #forth 03:53:57 --- mode: ChanServ set +v tathi 03:55:30 bluekelp: Bill Muench has a page at http://www.calcentral.com/~forth/forth/ -- try the EFORTH.X86 on there, it's the Forth source. You can find the primitives by searching for CODE words... 03:58:42 I thought Dr. Ting's changes are also nice: http://offete.com/ 04:00:31 Yeah. I think Bill's Forth source is probably the most readable though... 04:01:34 Hmm...actually, maybe I haven't read Ting's more recent stuff 04:01:35 it is! 04:01:50 but he wrote nice explanations in his newer code too (Ting) 04:08:58 --- join: Nisstyre (~yours@oftn/member/Nisstyre) joined #forth 04:19:55 --- quit: Nisstyre (Ping timeout: 248 seconds) 04:26:19 --- quit: Eth|cal (Ping timeout: 248 seconds) 04:28:51 --- quit: tangentstorm (Quit: WeeChat 0.3.2) 04:43:01 --- join: Eth|cal (~sam@ppp59-167-172-238.static.internode.on.net) joined #forth 04:43:50 --- join: ASau` (~user@p4FF96920.dip0.t-ipconnect.de) joined #forth 04:46:53 --- quit: ASau (Read error: Operation timed out) 04:57:22 --- join: nighty^ (~nighty@lns-bzn-49f-62-147-170-46.adsl.proxad.net) joined #forth 05:08:36 --- quit: nighty^ (Remote host closed the connection) 05:41:47 --- join: nighty^ (~nighty@lns-bzn-49f-62-147-170-46.adsl.proxad.net) joined #forth 05:54:23 --- quit: Bahman (Quit: Leaving.) 06:20:12 --- join: kulp_ (kulp@kulp.ch) joined #forth 06:21:14 --- join: C_Keen (cckeen@pestilenz.org) joined #forth 06:21:56 --- quit: C-Keen (Disconnected by services) 06:22:27 --- quit: dys (*.net *.split) 06:22:28 --- quit: kulp (*.net *.split) 06:24:11 --- nick: C_Keen -> C-Keen 07:00:49 --- join: RodgerTheGreat (~rodger@c-98-202-115-133.hsd1.ut.comcast.net) joined #forth 09:06:08 --- join: Tod-Work (~thansmann@50-202-143-210-static.hfc.comcastbusiness.net) joined #forth 10:17:29 --- join: MalcolmX86 (~chatzilla@108.180.145.19) joined #forth 10:18:52 does anyone know anything about this GA144 chip here ? http://www.greenarraychips.com/home/documents/budget.html - how to build a GA144 system cheaply 10:22:06 arrayForth is used to program the 144 individual computers on one chip - http://www.greenarraychips.com/home/documents/index.html 10:25:51 I know a bit about this chip :) 10:28:39 i would like to connect one to my computer to process streams of data , but it seems that soldering is the first hurdle after purcashing it . 10:29:37 true-grue have you used one before ? 10:29:59 "one" GA144 i mean 10:32:50 I've used its predecessors -- S24/S40. I have g144 dev.board, but don't want to mess with arrayForth. 10:33:16 the schmartboard bundle sucks for me at least. shipping has price tag as the board and chip :( 10:33:43 there was arrayfactor or something similar 10:33:58 if you don't want arrayforth 10:35:17 Have you tried this ArrayFactor by yourself? 10:36:10 Vuokko you say it costs the same to buy GA144-1.20 Evaluation Boards from greenarrays as to buy the solder yourself 88 pin schmartboard ? 10:37:21 I don't know evaluation board but schmartbord's shipping to Finland is big NO for me 10:38:06 and evaluation board has more features than schmartboard bundle 10:39:27 I was happy with simplicity and programmability of VentureForth. It was designed by people with some experience of Chuck's chips programming. 10:40:10 i am in Canada here , in the west north of Nevada where greenarrays is situated . 10:41:25 don't know how well shipping works for GA144 schmartboard here , but eval board looks better for me . 10:42:53 --- quit: protist (Ping timeout: 264 seconds) 10:43:27 i want to find out what Chuck uses to program because it strains my eyes to look at the screen . 10:43:47 I've been thinking (drawing on paper) Arduino compatible GA144 board :) but I have done nothing serious for it yet 10:44:02 I've always had the impression that he generates everything from scratch, including the fonts. 10:44:10 I don't know that as a fact, though. 10:44:19 It's just sort of "between the lines" of the stuff he writes. 10:45:37 keep me posted - be back later , 10:45:46 must eat 11:10:25 how are the forth chips different from standard cpus? other than making stacks faster (not that they're slow on std hardware) i dont' know what the fundamental diff in hardware is 11:13:50 To be honest, I don't consider g144 as a Forth chip in a classic sense :) 11:18:40 true, but i still don't know exactly how the forth chips differ. i've seen some refs to low power and multi-"core"s but that's it 11:19:29 with ARMs running entire linuxes off the 3.3 or 5v that powers a SD card, the latter may be the only niche left soon 11:23:09 It's MPPA (http://en.wikipedia.org/wiki/Massively_parallel_processor_array ) with tiny two-stack machines as a nodes. 11:25:54 Now every ARM can run Linux. There is a niche even for Linux-free embedded programming :) 11:26:21 does each node run its own forth or is it supervised by one with a task manager, etc.? any idea? 11:30:31 There is no Forth, only two circular stacks, some registers and machine code (machineForth, 32 really low-level instuctions, without hardware multiplier). You can think about one node as a simple/tiny18-bit MCU. 11:38:55 bluekelp , each of the 144 nodes on a GA144 has its own CPU , RAM and ROM and is a complete computer 11:52:27 Vuokko , i want to make a data stream processor with a GA144 --- http://en.wikipedia.org/wiki/AMD_FireStream 11:53:23 it says AMD FireStream is PCI-X 11:56:00 I don't know if you can get same troughput with GA144 as FireStream 11:56:42 Especially on a floating point computations :) 12:00:54 "can exceed 3 gigabits per second" http://www.greenarraychips.com/home/documents/greg/PB001-100503-GA144-1-10.pdf 12:02:33 my interest is having 2 extra bits than 16 bit system 12:03:33 I don't see G144 in a role of some kind of accelerator. But this chip is good for a real-time and autonomous control/processing with many sensors etc. 12:06:10 It would be interesting to see it in a "swarm intelligence" projects. 12:10:23 perhaps a bicycle accelerator ? http://endless-sphere.com/forums/viewtopic.php?f=2&t=48099 12:18:41 true-grue , just wondering why you think GA144 is limited for processing a data stream . 12:21:56 thinking more of shoveling data quickly , and non-floating point processing . 12:22:57 It's rather fast for integer-only computations. But you must be aware that even simple transporting of a data word from node to node will costs some time. It also affects on memory access time if you need to have large arrays which are build on several nodes. 12:23:19 --- nick: ASau` -> ASau 12:25:20 The key for successfully programming of this chip is preserving of locality. But it may be really hard for many algorithms. 12:27:11 thinking of doing disclosure control - processing many bytes in parallel possible 12:28:14 --- join: fantazo (~fantazo@213.129.230.10) joined #forth 12:28:18 I call it "multi-pipline processing" :) 12:49:32 want to make a "Y" pipe that i call a fork queue (ie checkerboard sort - read data unit , if black send to black , if white send to white) 12:54:55 the 2 extra bits of the f18 give 4 data 'colour' choices for every 16 bits. 12:58:31 for example , the Freedom Of Information office has special photocopiers they use to censor documents . when certain parts are highlighted with a pink pen and photocopied , those portions are censored . 13:00:20 sometimes they want the text to come up printed in red instead of black . so there are 4 colours for data , black , invisible , red and pink highlight 13:04:11 but using cryptography , a document can contain all of these types of data without all of the data being made available to everyone . 13:21:19 --- quit: nighty^ (Remote host closed the connection) 13:45:59 --- quit: tathi (Ping timeout: 246 seconds) 13:47:04 --- quit: jevin_ (Quit: Textual IRC Client: www.textualapp.com) 13:48:00 --- join: tathi (~josh@dsl-74-209-3-203.fairpoint.net) joined #forth 13:48:01 --- mode: ChanServ set +v tathi 13:53:23 --- join: mark4_ (~mark4@cpe-192-136-213-83.tx.res.rr.com) joined #forth 14:00:28 --- quit: true-grue (Read error: Connection reset by peer) 14:00:57 --- quit: fantazo (Remote host closed the connection) 14:24:35 --- join: jevin (~jevin@72.12.217.220) joined #forth 14:49:00 --- join: Nisstyre (~yours@oftn/member/Nisstyre) joined #forth 14:51:41 --- quit: Nisstyre (Read error: Connection reset by peer) 15:27:16 --- quit: ASau (Quit: fixing X.) 15:27:21 --- quit: mark4_ (Read error: Connection reset by peer) 15:28:02 --- join: ASau (~user@p4FF96920.dip0.t-ipconnect.de) joined #forth 15:52:48 --- join: tangentstorm (~michal@108-218-151-22.lightspeed.rcsntx.sbcglobal.net) joined #forth 16:08:19 --- quit: Tod-Work (Quit: Leaving) 17:07:55 --- quit: tangentstorm (Ping timeout: 248 seconds) 18:06:47 --- join: tangentstorm (~michal@108-218-151-22.lightspeed.rcsntx.sbcglobal.net) joined #forth 18:12:16 --- quit: tangentstorm (Ping timeout: 264 seconds) 18:27:42 --- join: tangentstorm (~michal@108-218-151-22.lightspeed.rcsntx.sbcglobal.net) joined #forth 18:59:22 --- nick: kulp_ -> kulp 18:59:32 --- quit: kulp (Changing host) 18:59:33 --- join: kulp (kulp@unaffiliated/kulp) joined #forth 19:40:09 --- join: Bahman (~Bahman@2.147.83.9) joined #forth 19:43:43 --- quit: kludge` (Ping timeout: 264 seconds) 19:49:21 --- join: kludge` (~comet@unaffiliated/espiral) joined #forth 20:02:10 --- join: Nisstyre (~yours@oftn/member/Nisstyre) joined #forth 20:38:47 --- quit: MalcolmX86 (Remote host closed the connection) 20:52:51 --- join: protist (~protist@8.224.69.111.dynamic.snap.net.nz) joined #forth 22:13:46 --- quit: Nisstyre (Quit: Leaving) 23:07:37 --- join: true-grue (~quassel@95-26-229-87.broadband.corbina.ru) joined #forth 23:13:59 --- quit: RodgerTheGreat (Quit: RodgerTheGreat) 23:44:51 --- quit: c00kiemon5ter (Ping timeout: 246 seconds) 23:46:15 --- join: c00kiemon5ter (~c00kiemon@foss-aueb/coder/c00kiemon5ter) joined #forth 23:59:59 --- log: ended forth/13.08.19