| Fallenou | just to let you know Milkymist One RC3 is published on Solderpad : http://solderpad.com/solderpad/milkymist-one/ | 00:35 |
|---|---|---|
| Fallenou | Paul and Andrew, two guys I met in London are the founders of Solderpad, they are open source hardware activists | 00:36 |
| Fallenou | they contacted me about it in october 2011 but they didn't want me to talk about it, it was still not released and not accounced publicly | 00:37 |
| Fallenou | but it seems they have gone public now so I can release it here :) | 00:38 |
| Fallenou | feel free to contact them after RC4 release, I could contact them to ask them to update their data | 00:38 |
| Fallenou | lekernel_: I paste again because you got disconnected : | 00:39 |
| Fallenou | 01:40 < Fallenou> just to let you know Milkymist One RC3 is published on Solderpad : http://solderpad.com/solderpad/milkymist-one/ | 00:39 |
| Fallenou | 01:40 < Fallenou> Paul and Andrew, two guys I met in London are the founders of Solderpad, they are open source hardware activists | 00:39 |
| wpwrak | the schematics as one massive image. the PNG from hell for sure ;-) | 00:46 |
| Fallenou | their viewer is nice | 00:49 |
| Fallenou | the zooming is easy | 00:50 |
| Fallenou | it's funny the M1 is lost among tons of Arduino*** projects ahah :) | 00:51 |
| Fallenou | on the http://solderpad.com/solderpad/ pae | 00:51 |
| Fallenou | page* | 00:51 |
| Fallenou | but soon Milkymist will be able to fight back for the "blinking LED war" | 00:52 |
| Fallenou | ;) | 00:52 |
| Fallenou | it will be the shiniest, for sure | 00:52 |
| wpwrak | yeah. victory in the LED arms race shall be ours ;-) | 00:58 |
| wpwrak | what i don't quite understand is what value solderpad adds. are they just rebroadcasting projects that are already properly hosted somewhere else ? | 00:58 |
| Fallenou | good question | 00:59 |
| wpwrak | ;-) | 00:59 |
| Fallenou | I think they would prefer project maintainers to update their project page themself | 00:59 |
| Fallenou | I emailed them about that | 00:59 |
| Fallenou | warning them about one of OpenCores problem | 00:59 |
| Fallenou | you don't want to maintain two repositories | 01:00 |
| Fallenou | so usually one ends up not maintained | 01:00 |
| Fallenou | and it's usually opencore's / solderpad | 01:00 |
| wpwrak | why should project maintainers maintain solderpad's project page ? | 01:00 |
| Fallenou | but they rely on git, and they answered me that it's easy to automate publishing to two remotes (using hooks) | 01:00 |
| wpwrak | if they already have their own infrastructure | 01:00 |
| wpwrak | it doesn't make sense | 01:00 |
| wpwrak | yes, you can easily duplicate a git. but why ? | 01:01 |
| kristianpaul | The number of logical LUT blocks exceeds the capacity for the target device. :-| | 01:01 |
| Fallenou | they want to centralize stuff I guess | 01:01 |
| Fallenou | to be like the github of Open Source Hardware | 01:01 |
| Fallenou | it makes sense | 01:01 |
| Fallenou | there is one website for social+source for open source *software* | 01:02 |
| Fallenou | why not making one for open source *hardware* | 01:02 |
| Fallenou | kristianpaul: woow :x | 01:02 |
| Fallenou | kristianpaul: your GPS project ? | 01:02 |
| kristianpaul | nope | 01:02 |
| kristianpaul | some sha256 stuff.. | 01:02 |
| wpwrak | Fallenou: well, but github offers hosting. that's a useful service. much like qi-hw, sourceforce, launchpad, etc., offer repository, wiki, mailing lists, etc. | 01:03 |
| Fallenou | wpwrak: they will be adding functionnalities, like diffing between schematics | 01:03 |
| wpwrak | Fallenou: but mirroring these places seems kinda pointless | 01:03 |
| Fallenou | well I think they offer/will offer hosting too | 01:04 |
| Fallenou | but for already existing projects indeed it's mirroring | 01:04 |
| Fallenou | their goal, as they told me is : "we just | 01:05 |
| Fallenou | want to build something that is useful to them and try to improve | 01:05 |
| Fallenou | collaboration in electronics." | 01:05 |
| Fallenou | I think it's early to say, let's see what kind of service/value they will add :) | 01:05 |
| Fallenou | but knowing these people, i think it could get interesting | 01:05 |
| kristianpaul | Fallenou: https://github.com/ngzhang/Icarus | 01:06 |
| Fallenou | they really are interesting and experienced men :) | 01:06 |
| Fallenou | so they must have a real value that I don't get yet | 01:06 |
| kristianpaul | some boring waste of time bitcoin miner ;-D | 01:06 |
| Fallenou | oh ok | 01:06 |
| Fallenou | I've hread of it | 01:06 |
| wpwrak | well, there's no harm in keeping in touch :) | 01:07 |
| Fallenou | yep | 01:07 |
| Fallenou | I just wanted to let you know about the page | 01:07 |
| Fallenou | not more actually | 01:07 |
| Fallenou | kristianpaul: 2 Spartan 6 wow, is the PCB built already ? is it working ? | 01:10 |
| kristianpaul | yes | 01:14 |
| Last message repeated 1 time(s). | 01:16 | |
| Fallenou | gn8, tomorrow debugging why lm32_dcache does not work in ISIM ! | 01:27 |
| azonenberg | Hmm, I think i'm going about FPGA development more like ASIC development | 06:31 |
| azonenberg | I have printouts of spartan6 slices at various magnifications (ranging from 1x2 slices to the whole XC6SLX45) | 06:32 |
| azonenberg | that i mark up with a pencil | 06:32 |
| azonenberg | doing physical layout :p | 06:32 |
| azonenberg | whoever sent me the link to Lava, i cant thank you enough | 06:32 |
| wolfspraul | azonenberg: cool! :-) | 06:41 |
| wolfspraul | do you care to upload some high-res photos about that? | 06:41 |
| wolfspraul | the physical realities on the fpga die seem to be overlooked too often | 06:41 |
| azonenberg | wolfspraul: this isnt physical, its from planahead | 06:45 |
| azonenberg | although i am studying physical | 06:45 |
| azonenberg | as well | 06:45 |
| azonenberg | i have some XC9536 CPLDs that are decapped already and being imaged shortly | 06:45 |
| azonenberg | i hav esome pics already but they're not full die | 06:45 |
| wolfspraul | yes but if you have nice looking graphics or photos, I am always interested in promoting them a little | 06:45 |
| azonenberg | spartan3a will be next | 06:45 |
| azonenberg | s6 is further out as they're pricier :p | 06:46 |
| azonenberg | i might do like an LX4 at some point though | 06:46 |
| wolfspraul | visual understanding can help a lot | 06:46 |
| azonenberg | Yeah | 06:46 |
| azonenberg | actually, let me upload a pic of this design now | 06:46 |
| wolfspraul | nice :-) | 06:46 |
| azonenberg | pencil on paper printout from planahead lol | 06:46 |
| wolfspraul | thanks! | 06:46 |
| azonenberg | i'm not one of those "write the HDL and let the synthesis tool do the rest" types lol | 06:48 |
| azonenberg | in fact, as soon as i fully understand one level of abstraction i find myself wanting to see what's underneath | 06:48 |
| azonenberg | did you see my BGA board btw? http://colossus.cs.rpi.edu/pictures/2012/January/1-31-2012%20-%20BGA/S7302457.JPG | 06:48 |
| azonenberg | this is spartan3a but i have some XC6SLX16 in the same package that are going on the next board | 06:48 |
| azonenberg | home soldered | 06:48 |
| azonenberg | that's FTG256 | 06:49 |
| azonenberg | http://i.imgur.com/KYotZ.jpg | 06:49 |
| azonenberg | sorry for bad lighting, its 2 AM here and my room isnt the brightest place | 06:49 |
| wolfspraul | what is planahead - is that some software? | 06:50 |
| azonenberg | you're working with xilinx FPGAs and you've never used it??? | 06:51 |
| azonenberg | you have no idea what you're missing | 06:51 |
| azonenberg | it's part of ISE | 06:51 |
| wolfspraul | me 'working' with xilinx fpgas may overstate what I do every day | 06:51 |
| wolfspraul | ah ok, googling didn't find anything but that makes sense :-) | 06:52 |
| azonenberg | it lets you do graphical IO pin planning, view a placed design on a physical (though somewhat stylized) layout of the chip | 06:52 |
| wolfspraul | azonenberg: I'm in the learning department, forgive me ;-) | 06:52 |
| azonenberg | color-code by hierarchal blocks | 06:52 |
| azonenberg | view critical paths on the physical layout so you can get a feel for what's trying to talk to what | 06:52 |
| azonenberg | that combined with color-coding by hierarchy is a very powerful tool for understanding when you're constrained by routing and placement rather than too many gate delays | 06:53 |
| azonenberg | http://i.imgur.com/6JKOB.png | 06:53 |
| azonenberg | random example of how i'd use it for timing analysis | 06:54 |
| azonenberg | this is a rather extreme design (note the timing constraint in the lower panel) | 06:54 |
| azonenberg | so i was hand-placing every FF and LUT | 06:54 |
| wolfspraul | interesting | 06:54 |
| wolfspraul | does this relate to your homecmos project in any way? | 06:54 |
| wolfspraul | or separate line of activity... | 06:54 |
| wolfspraul | how is homecmos doing btw? I admit I am not regularly reading the backlog of the channel... | 06:55 |
| azonenberg | It's been slow due to school etc | 06:55 |
| azonenberg | current bottleneck is still deep Si etching | 06:55 |
| wolfspraul | it's difficult to extract the bottom line after some months of intricate technical details | 06:55 |
| azonenberg | i determined that i need to be able to etch with an evaporated Ni hardmask | 06:55 |
| azonenberg | my last experiment failed because i couldnt evaporate it using the default configuration of the tool on campus | 06:56 |
| wolfspraul | so homecmos is still ongoing? | 06:56 |
| azonenberg | because nickel sublimes rather than melting and then evaporating | 06:56 |
| azonenberg | So the current TODO is designing an adapter to hold my wafer *above* the evaporatoin source instead of below it like the tool is normally used | 06:56 |
| azonenberg | there's room in the bell jar if i do it right | 06:56 |
| azonenberg | and i have some aluminum bar stock that should work fine at those vacuum levels | 06:57 |
| azonenberg | i just have to actually find time to go down to the machine shop | 06:57 |
| wolfspraul | last I remember something about comb drive... | 06:57 |
| azonenberg | and yes, there's a lot of process development going on so i havent had much to show | 06:57 |
| azonenberg | right now its tooling | 06:57 |
| azonenberg | for example, i built myself a fume hood over break | 06:57 |
| wolfspraul | maybe you write a blog post one day summing up the bottom line for the dummies :-) | 06:57 |
| azonenberg | now i can work with more aggressive etchants safely | 06:57 |
| azonenberg | or just larger volumes of the existing ones | 06:58 |
| azonenberg | the next step is to make a nicer spin coater | 06:58 |
| azonenberg | i'll be blogging on those shortly | 06:58 |
| azonenberg | i also did some work on high aspect ratio etching of copper | 06:58 |
| azonenberg | will be posting on that as soon as i get SEM cross section images of the sample | 06:58 |
| azonenberg | when *that* happens is TBD | 06:58 |
| wolfspraul | nice. when you blog, also talk about what use cases this could potentially lead to. because I'm sure a lot of readers would ask that... | 06:59 |
| azonenberg | of course | 06:59 |
| azonenberg | anyway so did you see the pencil image i linked a minute or two ago? | 06:59 |
| wolfspraul | yes | 06:59 |
| azonenberg | that's part of a device i am hoping to have done by weds | 06:59 |
| azonenberg | it's a clock glitch generator for an in-class demo | 07:00 |
| azonenberg | i want to be able to generate a ~5 MHz clock signal | 07:00 |
| azonenberg | with one pulse (at a precise position in the train) a lot shorter | 07:00 |
| azonenberg | but always the same length, and at the same offset | 07:00 |
| azonenberg | so the thinking is to make a tapped ring oscillator much like the delay-locked loop in a DCM | 07:00 |
| azonenberg | except the tap position is user controlled rather than being based on detecting phase shifts | 07:01 |
| azonenberg | so i can hold it at tap 15 for a while, then suddenly jump to tap 3 | 07:01 |
| azonenberg | and the period of the signal suddenly gets longer | 07:01 |
| azonenberg | the hard part will be glitch-free shifting of frequencies | 07:02 |
| azonenberg | so i can jump straight from Fa to Fb with no unwanted pulses of different lengths | 07:02 |
| wolfspraul | understand (and not) | 07:05 |
| wolfspraul | but sounds good | 07:05 |
| azonenberg | lol | 07:05 |
| azonenberg | i'm the TA for a class on cryptography at my school | 07:05 |
| azonenberg | we're talking about hardware vulnerabilities and fault attacks | 07:06 |
| azonenberg | how flaws in the physical implementation can make a strong algorithm like AES or RSA fail | 07:06 |
| azonenberg | so i'm gonna try and put together a nice demo | 07:06 |
| azonenberg | run a stripped down RSA on a little 8-bit microcontroller or something | 07:06 |
| azonenberg | clocked by my gadget | 07:06 |
| azonenberg | and demonstrate how we can cause single-bit errors by giving it a glitchy clock | 07:06 |
| wolfspraul | azonenberg: colossus.cs.rpi.edu/pictures are all your pictures? | 07:30 |
| wolfspraul | I'm browsing through some of that... | 07:30 |
| azonenberg | Thats a raw dump of every photo i've taken since 2004 | 07:30 |
| azonenberg | except for a tiny fraction that i didnt want public for one reason or other | 07:31 |
| wolfspraul | they are all freely licensed like your homecmos pics? | 07:31 |
| wolfspraul | (just asking in case I want to include one somewhere, with attribution of course...) | 07:31 |
| azonenberg | I've never officially set licenses on them since the server is mostly there for me to show people specific pics without the hassle of uploading it on demand | 07:32 |
| azonenberg | i'd probably be willing to share almost all under cc-by-nc or similar | 07:32 |
| wolfspraul | can you remove the -nc still? | 07:32 |
| azonenberg | I'd have to decide on an exact license depending on the pic | 07:32 |
| azonenberg | if its stuff of my lab work, then cc-by or cc-by-sa would be fine | 07:33 |
| wolfspraul | ok, too much hassle :-) | 07:33 |
| wolfspraul | cc screwed up royally with -nc | 07:33 |
| azonenberg | but if you're talking, say, my nature photos i might want -nc on those | 07:33 |
| azonenberg | Ok, how about this | 07:34 |
| wolfspraul | totally inefficient to set or even enforce | 07:34 |
| wolfspraul | but I like how the chinese shanzhai now steal -nc licensed ifixit photos | 07:34 |
| wolfspraul | that's so twisted my head hurts | 07:34 |
| azonenberg | any pics of gadgets i've built or lab stuff are cc-by | 07:34 |
| azonenberg | anything else, ask | 07:34 |
| azonenberg | i'm not opposed to sharing, understand | 07:34 |
| wolfspraul | ok, I think that's clear for me | 07:34 |
| wolfspraul | I'm more and more leaning to just public domain | 07:35 |
| azonenberg | but the archive is something like 30,000 pics and its hard to make a blanket statmeent :p | 07:35 |
| wolfspraul | copyright is broken, and cannot be fixed with more copyright | 07:35 |
| azonenberg | Agreed | 07:35 |
| azonenberg | It really boils down to two things | 07:35 |
| wolfspraul | that's just my personal opinion though, hope this doesn't set off a flame war here... | 07:35 |
| azonenberg | I want to be credited when my work is used | 07:35 |
| wolfspraul | oh you bet | 07:35 |
| wolfspraul | but that's a matter of courtesy, social standards and values | 07:35 |
| wolfspraul | like I don't spit in my hand before shaking yours :-) | 07:35 |
| wolfspraul | to be very blunt the Chinese way :-) | 07:36 |
| azonenberg | And i would like, but do not mandate, for people to drop me a line and say what it's being used for | 07:36 |
| wolfspraul | sure | 07:36 |
| wolfspraul | I am 100% with you | 07:36 |
| wolfspraul | and cc failed on all of this | 07:36 |
| azonenberg | i understand thats far too complex to put in a license, nearly impossible to enforce, and sometimes too restrictive | 07:36 |
| wolfspraul | instead they have poeple argue about -nc -nd -sampling or whatever clauses | 07:36 |
| azonenberg | which is why i dont mandate it | 07:36 |
| wolfspraul | yes but that's what matters, anyway, I got it and THANK YOU! | 07:37 |
| azonenberg | The only time i would do -nd is if i had a very specific reason not to have the image modified | 07:37 |
| azonenberg | like, say, an identifiable person or event | 07:37 |
| wolfspraul | if I ever want any of those pics, and that will be the technical ones (gadgets or lab stuff), I know you are happy about that | 07:37 |
| wolfspraul | and the attribution and all come included when I do anything | 07:37 |
| azonenberg | Yep | 07:37 |
| wolfspraul | yes but -nd doesn't work either :-) | 07:37 |
| azonenberg | Yeah, again thats just when i'd consider it | 07:38 |
| wolfspraul | it's unpractical, unenforceable, I would argue even unsocial | 07:38 |
| wolfspraul | just rubbish | 07:38 |
| azonenberg | realistically, i dont expect to profit off any of my photography | 07:38 |
| azonenberg | and i dont want to limit what other people can do with it, within reason | 07:38 |
| wolfspraul | my favorite now are Chinese Shanzhai repair manuals (sold for a profit of course) using -nc licensed ifixit photos | 07:38 |
| wolfspraul | I love that | 07:38 |
| azonenberg | lol | 07:38 |
| wolfspraul | first ifixit has a very twisted busines model | 07:38 |
| wolfspraul | and then the strange shanzhai add their 3 twists on top of that | 07:38 |
| wolfspraul | wonderful | 07:38 |
| azonenberg | just out of curiosity, which pics in particular were you thinking of using and for what? | 07:39 |
| wolfspraul | they even leave the ifixit watermark in there, so what | 07:39 |
| azonenberg | I like to have some idea of what my work is being used for :) | 07:39 |
| azonenberg | if nothing else it gives me a hint as to what would be most useful to others if i did more of it | 07:39 |
| wolfspraul | none right now, I'm just trying to not trample over your work and how you feel it should be used | 07:39 |
| wolfspraul | probably technical pictures that are kind of eye-opening to newbies | 07:39 |
| wolfspraul | something that opens a window to a new thought or imagination | 07:40 |
| azonenberg | Yeah | 07:40 |
| wolfspraul | can't pin it down more than that now | 07:40 |
| azonenberg | well i probably have a lot of that | 07:40 |
| azonenberg | all of Silicon Exposed is intended to be breaking down barriers as to what's assumed possible for hobbyists | 07:40 |
| azonenberg | including but certainly not limited to ic fab | 07:40 |
| kristianpaul | morning | 13:45 |
| lekernel | hi | 13:48 |
| wolfspraul | n8 (calling it a day :-)) | 14:08 |
| Fallenou | n8 ! | 14:11 |
| kristianpaul | n8 | 14:56 |
| mwalle | lekernel: do you know if there is a difference between an fpga bitstream and a cpld 'bitstream' apart from the fact that the actual plds have another architecture | 16:25 |
| lekernel | well, because of that different architecture, there are probably large differences in the bitstream format as well? | 17:20 |
| mwalle | mh there doesnt seem to be a 'bit' file for cplds.. seems to be called jed (jedec bit map or sth like that) | 17:28 |
| lekernel | haha, still the old PAL/GAL stuff? | 17:36 |
| GitHub150 | [milkymist-ng] sbourdeauducq pushed 2 new commits to master: http://git.io/Ouvlaw | 18:19 |
| GitHub150 | [milkymist-ng/master] flash: remove splash screens - Sebastien Bourdeauducq | 18:19 |
| GitHub150 | [milkymist-ng/master] Add tools - Sebastien Bourdeauducq | 18:19 |
| GitHub14 | [migen] sbourdeauducq pushed 1 new commit to master: https://github.com/milkymist/migen/commit/629e771fc00911f1d1477adc40f61278cf410a1e | 18:37 |
| GitHub14 | [migen/master] fhdl/structure: binary constant builder - Sebastien Bourdeauducq | 18:37 |
| GitHub27 | [milkymist-ng] sbourdeauducq pushed 1 new commit to master: http://git.io/yHqzoA | 18:59 |
| GitHub27 | [milkymist-ng/master] Memory map - Sebastien Bourdeauducq | 18:59 |
| GitHub51 | [milkymist-ng] sbourdeauducq pushed 2 new commits to master: http://git.io/GakbGw | 19:06 |
| GitHub51 | [milkymist-ng/master] Update gitignore - Sebastien Bourdeauducq | 19:06 |
| GitHub51 | [milkymist-ng/master] BIOS: hello world - Sebastien Bourdeauducq | 19:06 |
| lekernel | azonenberg: you should combine lava with the bitstream reverse engineering work at recobus.de / debit | 19:42 |
| Fallenou | lekernel: my lm32 D_DAT_O stays at 0x00000000 even with a few lb r1, (r0+something) | 21:02 |
| Fallenou | strange | 21:02 |
| lekernel | D_DAT_O is used to transmit the data to *write* to memory - lb *reads* memory | 21:44 |
| Fallenou | err my D_ADR_O sorry | 21:45 |
| Fallenou | I had to remove a few bottom lines from lm32_cpu.v about registers initialization in case of simulation | 21:51 |
| Fallenou | because it didn't compile | 21:51 |
| Fallenou | maybe it's the source of my problems | 21:51 |
| Fallenou | http://pastebin.com/C0dUN9yt | 21:52 |
| Fallenou | this | 21:52 |
| lekernel | I can't see why it shouldn't compile | 22:00 |
| Fallenou | ok it works now | 22:05 |
| Fallenou | I removed this code which does not compile and I put an initial begin ram[0] = {data_width{1'd0}}; end in lm32_dp_ram.v | 22:05 |
| Fallenou | and now data works :) | 22:05 |
| Fallenou | D_ADR_O changes from 0 and it seems way better now | 22:06 |
| Fallenou | going to bed, gn8 ! | 22:07 |
| mwalle | lekernel: old pal/gal stuff? | 22:07 |
| mwalle | Fallenou: gn8 | 22:08 |
| kristianpaul | n8 | 22:09 |
| lekernel | http://en.wikipedia.org/wiki/Programmable_Array_Logic | 22:24 |
| kristianpaul | who sell PALs right now? and what integration scale? | 22:31 |
| wpwrak | kristianpaul: the museum of prehistoric arts ;-) | 22:31 |
| kristianpaul | wpwrak: ;) | 22:32 |
| kristianpaul | lattice seems to call it GAL | 22:32 |
| wpwrak | lekernel: what would you think of giving xiangfu commit access on github, with the stipulation that he should do things that need review (like his current softusb work) in topic branches ? | 22:34 |
| kristianpaul | bah discuntinued.. | 22:35 |
| kristianpaul | lekernel: what was the point of showing us this wikipedia article? | 22:35 |
| mwalle | kristianpaul: i think because i asked about pals | 22:36 |
| kristianpaul | ahh ;) | 22:37 |
| mwalle | lekernel: what was the other project about fpga bitstream revers engineering besides debia/ulogic.org ? | 22:38 |
| lekernel | mwalle: recobus | 22:44 |
| lekernel | wpwrak: so far he hasn't sent so many soc patches... | 22:45 |
| lekernel | he already has commit access to FN and RTEMS | 22:45 |
| wpwrak | now he's working on softusb, those hid(eous) reports | 22:46 |
| wpwrak | (fn) ah, didn't know that | 22:46 |
| kristianpaul | oh dear, http://paste.debian.net/155141/ | 23:49 |
| kristianpaul | lekernel: how do i know wich parts of a HDL code is requiring more fpga resources? | 23:50 |
| dvdk | kristianpaul: what did you attempt to do? | 23:52 |
| kristianpaul | dvdk: fit a bitcoin miner core in the M1's lx45 fpga | 23:52 |
| dvdk | kristianpaul: good luck. for a sha256 hash algo you need > 256 bits of registers. that's a tough number of slices (at least 64?). most miner designs might use >1 hashing circuits, | 23:55 |
| dvdk | but the error message is something more specific. | 23:55 |
| dvdk | no, it's 8 register bits per slice. | 23:56 |
| kristianpaul | btw di you get a M1 right? | 23:57 |
| kristianpaul | s/di/did | 23:57 |
| dvdk | yup | 23:57 |
| kristianpaul | nice | 23:57 |
| dvdk | ok, but from the error message, it looks quite clearly like you defined waay to many registers. | 23:57 |
| kristianpaul | yes, but i need find the "leak" of registers first :) | 23:58 |
| dvdk | so I'd guess you instantiated some 100-way parallel miner. | 23:58 |
| kristianpaul | and all the other warnigns are nothing but friendly to suguest part of code to check | 23:58 |
| dvdk | the hash algo needs lots of regisers, go look how many of these algos are instantiated | 23:59 |
| kristianpaul | what is 100-way? | 23:59 |
| kristianpaul | i still getting in to this miner world :) | 23:59 |
| --- Mon Feb 6 2012 | 00:00 | |
Generated by irclog2html.py 2.9.2 by Marius Gedminas - find it at mg.pov.lt!
