00:00:00 --- log: started forth/07.02.15 00:00:23 --- quit: Zarutian (Read error: 110 (Connection timed out)) 00:11:54 --- join: Raystm2- (n=NanRay@adsl-68-95-253-147.dsl.rcsntx.swbell.net) joined #forth 00:15:32 --- join: ecraven (n=nex@eutyche.swe.uni-linz.ac.at) joined #forth 00:20:09 --- quit: Raystm2 (Read error: 145 (Connection timed out)) 00:24:50 --- join: Zarutian (n=Zarutian@194-144-84-110.du.xdsl.is) joined #forth 00:30:15 --- quit: grub_booter (Read error: 104 (Connection reset by peer)) 00:36:23 --- part: omg-bunny left #forth 00:53:23 --- join: crest_ (n=crest@p54897196.dip.t-dialin.net) joined #forth 01:02:07 --- quit: Crest (Read error: 110 (Connection timed out)) 01:04:05 --- quit: Zarutian (Read error: 110 (Connection timed out)) 01:17:06 --- quit: Quartus (Read error: 104 (Connection reset by peer)) 01:27:04 --- quit: JasonWoof ("off to bed") 01:29:06 --- join: Quartus (n=trailer@CPE0001023f6e4f-CM013349902843.cpe.net.cable.rogers.com) joined #forth 01:29:06 --- mode: ChanServ set +o Quartus 01:39:20 --- quit: madgarden (Read error: 113 (No route to host)) 01:52:31 --- quit: madwork (Read error: 113 (No route to host)) 03:12:46 --- join: grub_booter (n=charlie@d5152D937.access.telenet.be) joined #forth 03:56:58 --- quit: grub_booter (Read error: 104 (Connection reset by peer)) 03:57:16 --- join: grub_booter (n=charlie@d5152D937.access.telenet.be) joined #forth 04:21:09 --- join: Zarutian (n=Zarutian@194-144-84-110.du.xdsl.is) joined #forth 04:33:22 --- quit: Zarutian (Read error: 104 (Connection reset by peer)) 04:42:11 --- quit: grub_booter (Read error: 104 (Connection reset by peer)) 04:52:51 --- join: azekeprofit (i=azekePro@82.200.251.231) joined #forth 04:57:52 --- join: grub_booter (n=charlie@d5152D937.access.telenet.be) joined #forth 05:46:16 --- quit: ecraven ("bbl") 06:22:12 --- join: tathi (n=josh@pdpc/supporter/bronze/tathi) joined #forth 06:22:12 --- mode: ChanServ set +o tathi 06:49:15 --- join: Zarutian (n=Zarutian@194-144-84-110.du.xdsl.is) joined #forth 06:57:57 --- quit: Zarutian (Read error: 145 (Connection timed out)) 07:00:11 --- join: madwork (n=foo@204.138.110.15) joined #forth 07:01:56 --- quit: Quartus_ (Read error: 104 (Connection reset by peer)) 07:31:13 I dunno about these colorforth people... 07:31:15 "My interest in CF is as a tool that allows a non-specialist to do system-level scientific and hardware programming, in a simple and 07:31:19 straightforward way. Compared to the old FIG Forth, CF is even more 07:31:22 simple, even more powerful, and even more of a joy to use." 08:12:58 --- join: Ray_work (n=Raystm2@199.227.227.26) joined #forth 08:32:59 --- join: Ray-work (n=Raystm2@199.227.227.26) joined #forth 08:50:47 --- quit: Ray_work (Read error: 110 (Connection timed out)) 08:53:00 --- join: Ray_work (n=Raystm2@199.227.227.26) joined #forth 09:08:20 --- join: zpg (n=user@smaug.linux.pwf.cam.ac.uk) joined #forth 09:08:24 hi chaps. 09:10:49 --- quit: Ray-work (Read error: 110 (Connection timed out)) 09:18:00 hi zpg 09:20:24 hey tathi, how've you been keeping? 09:26:57 --- join: Ray-work (n=Raystm2@199.227.227.26) joined #forth 09:27:05 --- quit: Ray-work (Remote closed the connection) 09:38:45 --- join: arke (n=chris@pD9E059A6.dip.t-dialin.net) joined #forth 09:38:45 --- mode: ChanServ set +o arke 09:46:02 I've been pretty well. 09:46:11 We got some snow here finally 09:46:17 glad to hear it :) 09:46:21 hey arke. 09:46:35 hi 10:05:28 --- quit: zpg ("heading off...") 10:08:12 --- join: Quartus_ (n=Quartus_@209.167.5.2) joined #forth 10:08:12 --- mode: ChanServ set +o Quartus_ 10:08:13 --- join: virl (n=virl@chello062178085149.1.12.vie.surfer.at) joined #forth 10:29:43 --- quit: crest_ ("Leaving") 10:35:47 --- quit: virsys (Read error: 104 (Connection reset by peer)) 10:44:26 --- join: neceve (n=Clau@unaffiliated/neceve) joined #forth 10:52:28 --- join: virsys (n=virsys@or-71-54-194-74.dhcp.embarqhsd.net) joined #forth 10:56:07 --- join: gno_ds (n=Gnomon@CPE0050eb372bdb-CM001692f57b56.cpe.net.cable.rogers.com) joined #forth 11:05:09 --- join: ygrek (i=user@gateway/tor/x-ab3a044471947b81) joined #forth 11:30:57 --- quit: gno_ds (Read error: 131 (Connection reset by peer)) 11:37:38 --- join: Snoopy1711 (n=snoopy_1@dslb-084-058-127-117.pools.arcor-ip.net) joined #forth 11:45:30 --- quit: Snoopy42 (Read error: 145 (Connection timed out)) 11:45:41 --- nick: Snoopy1711 -> Snoopy42 12:30:41 --- join: JasonWoof (n=jason@c-71-192-30-169.hsd1.ma.comcast.net) joined #forth 12:30:42 --- mode: ChanServ set +o JasonWoof 12:35:06 --- join: ecraven (n=nex@eutyche.swe.uni-linz.ac.at) joined #forth 12:49:13 --- part: ygrek left #forth 12:53:02 --- join: Ray-work (n=Raystm2@199.227.227.26) joined #forth 13:08:03 --- quit: neceve (Remote closed the connection) 13:08:19 --- join: slava (n=slava@CPE0080ad77a020-CM000e5cdfda14.cpe.net.cable.rogers.com) joined #forth 13:08:19 --- mode: ChanServ set +o slava 13:08:44 --- quit: Ray_work (Read error: 110 (Connection timed out)) 13:27:30 hey 13:27:41 yo 13:31:58 --- quit: ecraven ("bbl") 14:10:13 what be up? 14:10:26 adding some features to my ffi 14:12:37 Quartus: C ABI's are sort of ridiculous 14:12:47 i'm adding the ability to call C functions which return structs by value 14:12:52 heh 14:13:46 hi slava, Quartus 14:16:35 is that allowed in C? 14:16:50 could be a C99 thing. but the Cocoa runtime uses it, among other things 14:17:01 weird 14:17:10 well its a well known feature anyway 14:17:15 huh 14:17:27 i mean its part of the standardized ABIs on all the OSes I care about 14:17:33 its not gcc-specific or anything 14:17:39 ok 14:17:48 * JasonWoof hugs forth 14:17:59 I really like being able to return two values sometimes 14:18:11 me too 14:18:44 a C FFI that supports everything is a lot of work 14:19:15 i still don't have value arrays in structs working (like struct foo { int x[10]; }) or bitfields (i probably won't add those) 14:19:41 also on AMD64 passing structs by value is a huge pain because you have to take it apart into float and integer components, and i don't have that yet 14:21:01 and i have to fix some things to work on linux/ppc 14:24:30 i wish i didn't have an OS underneath, or that everybody at least used the same OS and CPU :) 14:27:10 what linux/ppc do you guys (JasonWoof, tathi) run? 14:27:14 what distro i mean 14:27:16 gentoo 14:27:21 ok 14:27:29 i need to think of something to put on my spare mac 14:27:35 its a 1.2ghz g4 14:27:41 i guess fast enough for gentoo :) 14:27:52 far as I know the only sensable choices for linux on a mac are gentoo and ubuntu 14:28:02 sure 14:28:11 I've got a dual 450 14:28:20 want to buy mine? 14:28:25 no 14:28:29 ok 14:28:55 I'm conflicted about what to do next 14:29:02 I really just want a radeon, then I'll be totally happy 14:29:20 eventually I'll probably go to x86 so I can run freebsd 14:29:49 isn't freebsd being ported to ppc? 14:29:59 they're working on it 14:30:05 I read that it's not stable enough for actual use 14:30:34 I don't want to tinker with getting the OS to work, I want to do my job 14:30:36 --- quit: Quartus_ (Read error: 104 (Connection reset by peer)) 14:30:50 why not use linux then? 14:31:00 my only real beef with my current system is that I have crappy graphics drivers 14:31:13 what drivers do you want? 14:31:27 something that can update the screen faster and do 3d 14:31:30 ah 14:31:38 in particular I want hardware accellerated scaled blits 14:31:45 yeah, if you're using linux x86 and x86-64 are your only choices there 14:32:19 I've had 3d working on this box before 14:32:26 I think it works now on tathi's 14:32:31 which driver? 14:32:37 open source radeon drivers can do 3d? 14:32:56 yeah 14:33:13 yeah 14:33:31 ah, i didn't know that 14:33:32 afaik radeon is the best-supported card for ppc linux 14:33:45 I've got a rage 128pro 14:33:48 but it's glitchy 14:33:55 I think it has hardware issues 14:34:09 I recently got a nice nvidia geforce 14:34:18 which is bigger and everything, but there's no 3d drivers for it 14:34:22 but it's more stable 14:34:42 nvidia won't release the spec, so it seems unlikely that I'll ever have accelleration on this card 14:45:21 --- join: Crest (n=crest@p54897196.dip.t-dialin.net) joined #forth 15:00:04 --- join: madgarden (n=madgarde@bas2-kitchener06-1096668571.dsl.bell.ca) joined #forth 15:07:32 --- quit: virl ("Verlassend") 15:11:47 --- quit: crc (Read error: 54 (Connection reset by peer)) 15:18:18 --- join: crc (n=crc@pool-151-197-17-190.phil.east.verizon.net) joined #forth 15:19:25 --- mode: ChanServ set +o crc 16:18:18 --- join: grfrblshntz (n=smee@66-168-78-251.dhcp.fdul.wi.charter.com) joined #forth 17:40:01 JasonWoof: barring extraordinary circumstances, I don't expect NVIDIA to ever provide enough info to write decent Open Source drivers. 17:40:25 TreyB: yeah, that's what I've heard 17:40:50 At Be, Inc., we had offices right down the street and signed NDAs and we didn't get chip docs. 17:40:52 there is a group that is working on reverse engineering the binary drivers 17:41:04 but I don't know what the likelyhood or timeline for success is 17:41:23 Is Nvidia the company that said they couldn't because they don't own all the IP? 17:41:28 We had an opaque porting layer that we started to use but then they pulled the plug on it. 17:41:36 tathi: so they claim. 17:42:51 I expect that if Intel and/or AMD deliver on their promise of integrated graphics devices with open specs NVIDIA may open up. We'll see. 17:43:10 huh 17:43:15 that'd be cool 17:43:37 I think it's pretty bizare to be able to buy something, but not allowed to know how to use it 17:43:50 we're not talking about "how it works" we're talking about "how to use it" 17:44:52 I think we'll sooner get one of Intel's massively parallel CPUs and switch to real-time ray-tracing/-casting. 17:45:23 that'd be cool 17:45:34 yeah. I want to see someone follow up on that German research project and make real-time ray-tracing hardware. 17:45:43 yeah 17:45:44 Intel's got a neat paper on their website about it. 17:46:13 tathi: I think someone was saying that that hardware was about as fast as a super-fast intel doing it in software 17:46:35 but of course that leaves no resources to the computer to do things like physics :) 17:47:46 yeah, but they were doing it in FPGAs 17:47:50 and it was a few years ago, too. 17:48:01 sounded like it would be plenty fast in custom hardware. 17:48:09 http://developer.intel.com/technology/itj/2005/volume09issue02/art01_ray_tracing/vol09_art01.pdf 17:48:53 tathi: yeah, they had some small fraction of the number of transisters that modern graphics cards at the time had 17:49:10 and on top of that there's the difference in clock speed 17:50:08 Resolving developer.intel.com... failed: Temporary failure in name resolution. 17:51:51 huh. downloaded fine from here. 17:51:59 Looks like they came to pretty much the same conclusions. 17:53:39 TreyB: I assume you've seen the SaarCOR and related work? http://graphics.cs.uni-sb.de/SaarCOR/ 18:00:39 I'd never seen it. The site hasn't seen an update in about 18 months. 18:03:31 yeah, it's dead AFAIK 18:03:58 interesting though. Pretty much the same findings as that Intel paper. 18:04:24 they built a couple of FPGA boards with fairly impressive results. 18:04:48 Indeed. 18:06:38 Mash up one of those 80 core teraflop Intel chips with IBM's on-chip eDRAM and an LCD controller and you'd have quite the rendering platform. 18:07:16 :) 18:15:03 --- join: snowrichard (n=richard@12.18.108.130) joined #forth 18:15:10 hi 18:17:58 --- quit: snowrichard (Remote closed the connection) 18:45:01 --- quit: Crest (Remote closed the connection) 18:46:51 --- quit: arke (Remote closed the connection) 18:47:43 --- join: arke (n=chris@pD9E059A6.dip.t-dialin.net) joined #forth 18:47:43 --- mode: ChanServ set +o arke 18:52:19 --- quit: tathi ("leaving") 18:52:59 --- join: snowrichard (n=richard@12.18.108.130) joined #forth 18:53:07 hi 18:53:29 --- join: edrx (n=Eduardo@200.217.105.205) joined #forth 18:54:08 hi 18:56:48 --- part: edrx left #forth 19:02:37 --- quit: snowrichard (Remote closed the connection) 19:05:48 --- quit: arke (Remote closed the connection) 19:05:48 --- quit: madgarden (Read error: 104 (Connection reset by peer)) 19:09:46 --- join: arke (n=chris@pD9E059A6.dip.t-dialin.net) joined #forth 19:09:46 --- mode: ChanServ set +o arke 19:12:33 --- quit: madwork (zelazny.freenode.net irc.freenode.net) 19:33:19 --- join: madgarden (n=madgarde@bas2-kitchener06-1096668571.dsl.bell.ca) joined #forth 20:07:22 --- join: snowrichard (n=richard@12.18.108.130) joined #forth 20:07:28 hi 20:10:40 hi 20:10:49 hello 20:10:58 hi 20:11:00 got my new shoutcast server account running today 20:12:25 25 max listeners for $1/listener/month 20:13:23 128Kbps 20:24:24 http://schizophrenicprogrammer.info 20:29:16 --- quit: snowrichard (Remote closed the connection) 21:17:22 --- quit: madgarden (Read error: 131 (Connection reset by peer)) 21:17:43 --- join: madgarden (n=madgarde@bas2-kitchener06-1096668571.dsl.bell.ca) joined #forth 21:46:55 --- quit: madgarden (Read error: 131 (Connection reset by peer)) 21:47:10 --- join: madgarden (n=madgarde@bas2-kitchener06-1096668571.dsl.bell.ca) joined #forth 21:49:24 ok, time to learn loops and arrays in javascript 21:50:42 nah 21:50:44 time for salad 21:58:32 --- nick: Raystm2- -> Raystm2 21:58:42 Hey. 21:58:49 Salad sounds good. 22:21:22 the salad dissapeared on me 22:21:29 so I had toast, stew, and a burger 22:52:32 --- join: snowrichard (n=richard@12.18.108.130) joined #forth 22:55:27 --- join: arke_ (n=chris@pD9E0721F.dip.t-dialin.net) joined #forth 22:56:19 --- quit: snowrichard (Remote closed the connection) 23:11:32 --- quit: arke (Read error: 110 (Connection timed out)) 23:20:05 --- join: neceve (n=Clau@unaffiliated/neceve) joined #forth 23:46:08 --- quit: neceve (Remote closed the connection) 23:51:47 --- join: ecraven (n=nex@eutyche.swe.uni-linz.ac.at) joined #forth 23:59:59 --- log: ended forth/07.02.15