#qi-hardware IRC log for Monday, 2012-03-19

qi-bot[commit] Werner Almesberger: cameo: "area" now also adds the outline cuts (master) http://qi-hw.com/p/cae-tools/35c062400:07
qi-bot[commit] Werner Almesberger: cameo: don't duplicate paths already cleared by the outline (master) http://qi-hw.com/p/cae-tools/5a599e100:07
qi-bot[commit] Werner Almesberger: cameo/area (hit_segment): only consider vectors pointing in the right direction (master) http://qi-hw.com/p/cae-tools/b60781600:07
qi-bot[commit] Werner Almesberger: cameo/area.c (touch): also consider whether we're looking for entry/exit (master) http://qi-hw.com/p/cae-tools/6fbdfd700:07
qi-bot[commit] Werner Almesberger: cameo/area.c: removed debugging and obsolete code (master) http://qi-hw.com/p/cae-tools/6811df500:07
qi-bot[commit] Werner Almesberger: cameo: documented "area"; miscellaneous cleanup (master) http://qi-hw.com/p/cae-tools/489ca9c00:07
wpwrakDocScrutinizer: btw, any more comments on the ether PHY ? anything that looks/sounds suspicious ?01:00
DocScrutinizerdang I forgot to follow up on it yesterday, been wasted when I came home01:01
wpwrakheh ;-))01:01
wpwrakwell, no rush. tomorrow is another day :)01:02
DocScrutinizerthe schematics in that awful chinese datasheet look unsuspicious01:03
DocScrutinizerall pins poroperly named01:04
DocScrutinizerI'd simply connect it the way the pin names suggest01:04
DocScrutinizerNFC about TCT and RCT01:05
DocScrutinizerdepends on chip that drives it01:05
DocScrutinizerif the chip doesn't need them, keep them NC01:05
DocScrutinizerwait a minute, didn't you also link to the current schematics in 'our' device?01:06
DocScrutinizerwpwrak: I'd have looked into your current design as well, to check if it looks fishy in any way, but I don't know where to find it01:09
wpwrakhttp://downloads.qi-hardware.com/hardware/milkymist_one/sch/tmp/MILKYMISTONE.pdf01:12
wpwrakthat's the current draft for r4. ether is the same as for rc301:12
cladamwDocScrutinizer, would you like me to update the latest draft sch to applied sch from all replies from last reviews of mail threads ?01:16
DocScrutinizercladamw: no problem for now01:17
cladamwDocScrutinizer, okay. :)01:17
DocScrutinizerwhich page is ethernet?01:18
wpwrakDocScrutinizer: (pin names) there are the confusing differences between the component we use and all the others. e.g., 1) parallel transformers followed by antiparallel ones vs. antip. followed by parallel. 2) that the pin numbering suggests that TX and RX are swapped, along with the +/- polarity. not sure if the latter is a real difference or if they just got it wrong in the data sheet01:18
DocScrutinizer(this friggin thing isn't searchable)01:18
wpwrakthe 3rd page01:19
wpwrakit is !01:19
wpwrakthe previous version (rc3) wasn't01:19
DocScrutinizerwpwrak: these are all differences I'd expect to see between upstream and downstream or between hub/switch and PC component01:20
wpwrakhmm :)01:21
DocScrutinizeryou recall my 0modem patchcable remark ?01:21
DocScrutinizerthis component is not symmetric thus won't really work well with the automatic swapping of newer chips01:22
wpwrakthe AP vs. P. issue is trickier: some have P-AP on TX and RX. some have P-AP on one and AP-P on the other. now is this equivalent ? if yes, why would even the same company sometimes have both variants ?01:22
wpwraksomething doesn't quite add up there01:22
DocScrutinizerthis component is meant for chips that never swap RX and TX01:24
wpwrakhmm, that may be troublesome then01:24
DocScrutinizerother designs might chose to use TX config for both channels, as RX works with that suficently well while TX can't work with RX scheme01:25
wpwrakwhat's the likely consequence of doing it regardless ? massive degradation ? or just a very marginal difference ?01:25
DocScrutinizerod swap RX and TX in my last statement01:25
DocScrutinizeror*01:25
DocScrutinizerdunno01:25
wpwrakdamn :)01:25
DocScrutinizeranyway, correctly connecting this component shouldn't yield any problems01:26
DocScrutinizeras afaik the chip can't do swapping either01:26
DocScrutinizerjust make sure you connected RX to RX and TX to TX01:27
wpwrakour chip can swap TX and RX01:27
DocScrutinizerooh01:27
wpwrakand if the pin numbering doesn't lie, TX and RX are reversed with respect to the reference component01:28
DocScrutinizerhaven't seen any such switch/mux in the block diagram01:28
wpwrakit's inside the chip01:28
wpwrakah. that block diagram01:28
wpwraklemme see ...01:28
DocScrutinizerblock diagram of chip of course :-D01:28
wpwrakyeah .. i';m a bit slow ;-)01:29
DocScrutinizerand I'm a bit late01:29
wpwrakanyway. page 21 quite clearly explains that is can do crossover01:29
DocScrutinizerummm01:29
DocScrutinizerthen for sure you're better off with a symmetric component for transformer01:29
wpwrakcladamw: how would you feel about replacing that connector with one of the many recommended by micrel ?01:31
DocScrutinizernot that I'd expect a huge impact with this one, it probably will still work flawlessly01:31
wpwrakDocScrutinizer: heh :) that's basically the answer i'm after. one of 1) it may be different, but irrelevant in practice. 2) it's something we can worry about later, when we're really bored some day. 3) what we have a is a very crippled ethernet that performs way below specification.01:32
wpwrakif it's 1) or 2), we can move on01:32
DocScrutinizerI'd not bet on 1 or 2, unless I have to01:33
cladamwwpwrak, although as a review you discovered which has such a great feedback, but those possible 'thoughts' were existed too as you just pointed three scenario.01:34
DocScrutinizermy guess is it's mainly about EMI 01:34
wpwrakaah, another scenario: 4) it'll work but the death rays we emit will kill the entire neighbourhood :)01:35
cladamwwpwrak, no matter what if it's 1) or 2), M1 has not been retested for EMI test. 01:35
DocScrutinizerand honestly it will still work great in at least one of two modes01:35
cladamwwpwrak, sure your 4) if later found.01:36
wpwrakcladamw: did you change J4 in the history of M1 ?01:36
wpwrakDocScrutinizer: you mean with TX/RX swapping ? only if the other side does that too (or if the data sheet has the pin numbering wrong)01:37
DocScrutinizerso while it may fail, perform sub par, or emit RF noise with one kind of patch cable, it will work absolutely correct with the other kind01:37
wpwrakokay. i think that's good enough for now :)01:37
wpwrakpeople regularly get cable crossing wrong. so we just blame the customer if it doesn't work properly :)01:39
cladamw(rc1 final) http://downloads.qi-hardware.com/hardware/milkymist_one/sch/20100424/MilkymistOne_draft2.pdf01:39
DocScrutinizer1, 2 is TX in M1 schematics, so everything ok for me01:39
cladamw(rc2 final) http://www.milkymist.org/mmone/old/rc2_schematics.pdf01:39
cladamw(rc3 final) http://downloads.qi-hardware.com/hardware/milkymist_one/sch/20110523/rc3_design_20110523.pdf01:40
wpwrakDocScrutinizer: oh, and does it matter what we connect the midpoints (TCT, RCT) to ? we have them directly on 3.3 V. i saw one other design that had them via a series cap at GND01:41
DocScrutinizerdang, that for sure matters01:42
wpwrakcladamw: looks the same. so no change ?01:42
cladamwwpwrak, DocScrutinizer from http://en.qi-hardware.com/wiki/Milkymist_One_Schematic_Change_History there's no changes on J4 but replaced to UDE part. 01:42
wpwrakhah ! ;-)01:42
DocScrutinizerit's depending on your chip's driver desigmn01:42
cladamwwpwrak, yeah...no changed in pin swapped or somethings in sch. 01:42
DocScrutinizerif your chip has open-collector outputs to GND on TX TX' then you want TCT on +whatever. if chip drivers are to +whatever, you need TCT to GND01:44
DocScrutinizerand if chip has a full H-bridge, you want to keep TCT NC01:45
wpwrakwith or without series cap ?01:45
DocScrutinizerwithout of course01:45
wpwrak"output pin"01:45
DocScrutinizerseries cap to GND only makes sense for input aka RX, I'd say01:47
DocScrutinizerthere's really no black magic in all that01:48
DocScrutinizerjust think it's audio ;-)01:49
DocScrutinizeror RF01:49
wpwrakno black magic in audio ? since when ? ;-))01:49
wpwrakso you would disagree with page 3 of http://ww2.pulseeng.com/products/datasheets/H325.pdf    ?01:50
DocScrutinizeranyway regarding TCT RCT do *exactly* what chip manuf suggests01:50
wpwrakthey suggest absolutely *NOTHING* :-(01:52
wpwrakdon't think i'd be bothering you if i had found an obvious solution ;-)01:53
DocScrutinizernah, they must have some hint on that. don't they offer a application note?01:54
kristianpaulDocScrutinizer: the are LTE USB Dongles?01:54
kristianpaulwhy i cant find none in ebay...01:54
DocScrutinizerkristianpaul: eh?01:54
DocScrutinizernot yet01:54
kristianpaulah !01:54
kristianpaulwhy? :-)01:55
DocScrutinizerwell, maybe because the chips are not ready yet01:55
kristianpaulfair point01:55
DocScrutinizerwpwrak: yep, that p.3 is horrible01:56
rohthere are some, but not easily avail yet01:56
wpwrakhmm, they have a design kit. let's see ... 01:56
wpwrakhttp://www.micrel.com/_PDF/Ethernet/hw_designkit/8001/KS8001_v1.2_DP.zip01:56
DocScrutinizerand it just says "typical" on p.301:56
DocScrutinizerthis doesn't mean it's always the correct way to design it01:57
wpwrakno APP note. only MAC-PHY. let's see what the schematics offer ..01:57
DocScrutinizeresp regarding that C1+2 part01:57
wpwrakheh ;-)01:57
wpwrak"this is how people typically get it wrong" ;-)01:57
rohi meant lte dongles01:58
rohhttp://www.modem3g.com/samsung-gt-b3740-lte-vodafone-stick-4g-usb-modem-100mbps.html01:59
DocScrutinizerwpwrak: btw you noticed that this typical circuit on p.3 is about a component for auto-crossover02:00
DocScrutinizerwhich may well imply different circuitry inside chip regarding TX drivers than what's usually found on a non-xover version02:01
DocScrutinizerwhich in turn means that those TCT and RCT are diferent too02:01
wpwrakall voltage rails (V3.3, 1.8, and 2.5) connected to each other02:01
DocScrutinizerhonestly read your chip datasheet, it has to yield some clue02:02
DocScrutinizern802:02
wpwrakokay, thanks !02:02
wpwraki think the data sheet is hopeless. but at least there's nothing directly contradicting our design in the reference design02:03
DocScrutinizeryour mayor problem is RCT02:07
wpwraki don't now what to do about it02:08
DocScrutinizeras TCT will either just outright fail when done wrong, or will just result in output voltage  doubled02:08
wpwrakthe part we haev to J4 is too confusing02:09
DocScrutinizerfor RCT it depends on what the inputs need for bias02:09
wpwrakthe reference design (that assumed a symmetric transformer) has positive voltage on TCT and RCT02:10
wpwrakassumed->assumes02:11
DocScrutinizerthen that's all ok02:11
DocScrutinizeralso those 4 pcs 49.9R (what a value ;-D) suggest that02:12
wpwrak50 Ohm seems to be unusual. so they optimized the sourcing for us. it's like this also in the reference design :)02:13
qi-bot[commit] Werner Almesberger: bacon/case/: top case part (almost machineable fped model) (master) http://qi-hw.com/p/wernermisc/b54f4a504:23
qi-bot[commit] Werner Almesberger: cameo/zstack.pl: convert 2.5D paths into a stack with limited Z steps (master) http://qi-hw.com/p/cae-tools/085754f04:23
qi-bot[commit] Werner Almesberger: cameo/fped2d2z.pl: convert fped 2D stacks into 2.5D paths with Z information (master) http://qi-hw.com/p/cae-tools/219e0a504:23
qi-bot[commit] Werner Almesberger: cameo/zstack.pl: option -r to reverse the stack (master) http://qi-hw.com/p/cae-tools/5ecce7d04:23
qi-bot[commit] Werner Almesberger: cameo: "area" now works on Z layers individually (untested) (master) http://qi-hw.com/p/cae-tools/18c947704:23
qi-bot[commit] Werner Almesberger: cameo/area.c (subordinates): fix trimming of list of subordinates (master) http://qi-hw.com/p/cae-tools/fb117b204:23
qi-bot[commit] Werner Almesberger: gp2rml: improved distance calculation; corrected compiler invocation (master) http://qi-hw.com/p/cae-tools/76b1b3e04:23
DocScrutinizer*sigh*06:12
DocScrutinizer5 min sleep, how refreshing ;)06:12
wolfspra1ltreat yourself well06:13
DocScrutinizerhah, my plans were different. I would enjoy retirement since 12 years, and only do jobs I like 06:26
DocScrutinizer:-/06:27
DocScrutinizerlast naviy cis yesterday gave me strange mod, when Gibs told his boss "Vacations? do something pleasant? No thanks, my job is pleasant enough"06:29
DocScrutinizermood*06:29
wpwrakthat's the spirit ! :)06:44
DocScrutinizerthat's the job for this spirit - at least for him06:54
DocScrutinizerwell, I guess I should be happy it's some LTE module I may work on with winXP and clearcase and without proper docs even inhouse06:56
DocScrutinizerthough quite obviously my company would make beter use of my talents when I was in chip design, not driver debugging06:57
DocScrutinizerI mean, when you got a function block with 5 fifo, but only 4 of them have the appropriate IRQs roted to IRQ controller... :-/06:58
DocScrutinizerrouted*, and this takes me 2 weeks to find out, when the according macro for the IRQ line is not defined in our sources06:59
DocScrutinizeryou wonder what those chip designers do whole day07:00
wpwrakthey spend their days thinking about practical jokes to play on the sw guys ;-)07:02
DocScrutinizerobviously ;-)07:49
qi-bot[commit] Xiangfu: cgminer: add /etc/init.d/cgminer for autostart (master) http://qi-hw.com/p/openwrt-packages/f5c5a9708:00
ezdagorWhich configure options should I pass along to mp3lib? I'm trying to get GMU working...10:10
xiangfuezdagor, make TARGET=nanonote MORE_DECODERS="decoders/mpg123.so" when compile gmu10:15
xiangfuezdagor, also you needs compile libmpg123 by yourself.10:15
ezdagorNod. I have. I noticed there are several options (for libmpg123) for "no fpu" machines. Just not sure which one to use.10:16
ezdagormpg123 plays MP3s fine. But, when I launch and then run GMU, it doesn't work.10:17
ezdagorI mean, it won't play MP3s.10:17
ezdagorLet me run through this once more. Then i'll try from scratch, using your suggestions.10:19
wolfspraulsuggestions? :-) I need to purge all this from the chatlogs... oh well :-)10:20
wolfspraulben nanonote cannot play mp310:20
wolfspraulif you proove otherwise we send you straight to some good friends we know who will take care of you :-)10:21
wolfspraul(just kidding, just kidding)10:21
zrafawhitequark: when usb host idea came (and we knew v-usb exists) we found this as well http://instruct1.cit.cornell.edu/courses/ee476/FinalProjects/s2007/blh36_cdl28_dct23/blh36_cdl28_dct23/index.html10:26
whitequarknow this is more interesting11:00
wejezdagor, have a look at the BUILD.txt file. everything is explained there, there is no such thing as MORE_DECODERS11:07
wejit is DECODERS_TO_BUILD11:07
wejalso for libmpg123 you should use the generic-no-fpu flag.11:11
Aylajz-kernel 3.3 soon? :D11:20
DocScrutinizerhah, nice. A sw USB HC implementation11:29
Aylanow we just need a linux driver for it11:55
zeardoes USB HC for any chance stand for "host controller"?12:01
zearha, yes! Awesome12:01
Aylawith such a driver, and the UBB, we could have USB host on the dingoo/nanonote :D12:03
GNUtoobut is the hardware capable of it?12:04
GNUtoobecause usb device don't have that many endpoints12:04
zearwell, for one you wouldn't be able to plug devices that don't have their own power source12:05
AylaI believe it just needs four GPIOs12:05
zearbecause (at least in the dingoo, but i bet also the nn) the usb port is unpowered12:05
zearbut any other than that - i've got no idea12:06
zearbut it would be nice if only for "linking" two devices together12:06
wpwrakzear: on the ben, you'd use UBB. as far s i remember, you can't bit-bang the USB controller enough to do some kind of reverse host12:12
wpwrakzear: with UBB, you have a 3.3 V power supply. so add a step-up converter, and voila ...12:12
zear:)12:12
Aylawpwrak: but that software implementation does bit-bang the USB controller, no?12:25
whitequarkAyla: no, it bangs some GPIOs12:28
whitequarkbit-banging USB controller is impossible, at least on NN12:28
whitequarkand, well, it is barely enough for maybe an USB mouse or keyboard12:28
whitequarkno WiFi, no mass storage12:28
AylaI don't get the difference12:28
whitequarkit won't work with the integrated USB port because processor pins which go to the port cannot be bit-banged12:29
whitequarkbut the pins going to 8:10 slot can be12:29
AylaI know, what I meant is to use the UBB12:30
Aylaok, I didn't understand what wpwrak said, now I get it12:31
wpwrakwhitequark: yeah, the problem with mass-storage is that the device gets to choose whether we use low- or full-speed. there's no negotiation. and low-speed USB disks are kinda hard to find ... :)12:33
whitequarkwpwrak: to be fair, I just thought that it'd be a performance disaster12:34
whitequarke.g. bitbanging an SD card on MIPS routers is _painfully_ slow (10k/s maybe) even on 250mhz or something12:34
whitequarkand here we have a slow device and a protocol with even more overhead12:34
whitequarkplus a non-RTOS12:35
whitequarkbut yes, absence of negotiation makes this just impossible12:35
Aylawhitequark, I get 250kb/s on dreamcast12:36
Ayla(bitbanging an SD card)12:37
whitequarkAyla, what platform is it?12:37
whitequarkCPU/SoC12:37
AylaSuperH 412:37
whitequarkno knowledge of that12:37
whitequarkthese 10k/s come from my experience with wrt54gl12:37
whitequarkmaybe it was a little bit faster, but still unsuitable for anything real12:37
AylaI *think* the implementation on dreamcast uses the 4-bit interface, not the 1-bit one12:38
whitequarkI doubt it12:38
whitequarkthere is no spec for the 4-bit iface12:38
Aylahmm12:39
whitequarkif this is opensource, then a) it is violating some copyright laws b) can I take a look?12:39
Aylasure, take a look at the Linux source code12:39
whitequarkah.12:40
whitequarkno, it is SPI interface12:40
whitequarkeven slower than the 1-bit one12:40
whitequarksee, SD cards have four data lanes, each running on 25MHz12:40
whitequarkbound together, they can form a 100 Mbit/s interface12:40
whitequarkbut it is proprietary and closed12:40
whitequark(they have even higher speeds, but I don't know anything about that)12:41
Aylaah, yes, I saw the 4-bit interface when reading some code, but it was not on the mmc-gpio driver12:43
Aylawell, the dreamcast implementation does use SPI12:45
whitequarkyes, it is significantly faster than bitbanging12:45
whitequarkdepending on impl it can reduce the amount of functions called in kernel by 4x to 16x12:46
Aylait's still bitbanging, the SD is connected to four GPIOs12:46
whitequarknope12:46
whitequarkhardware SPI is not bitbanging12:46
whitequarkit is a proper way to hook up an SD card12:47
whitequarkthrough not very fast12:47
Aylathe hardware has no SPI12:47
whitequarkmy MIPS router did not have a hardware SPI port12:47
whitequarkahh12:47
Aylathe UART controller of the dreamcast can be disactivated, so that the TX/RX and CTS/RTS lines can be used as GPIO12:48
Aylathat's where the SD is connected12:48
whitequarkwpwrak: suppose I want to connect two microcontrollers13:34
whitequarkone has 2.8V IO and the other one has 3.3V IO (but the actual voltage is near to 3.0 due to Schottky diode in the VDD)13:35
whitequarkshould placing a 200 ohm resistors between every IOs enough to protect the low-voltage uC?13:35
rohwhitequark: depends on the uC. sometimes it does. for when not or you need high speed its better to use level shifters13:41
kristianpaul a usb tranceiver is pretty easy to make 14:09
kristianpaulGNUtoo: 14:09
kristianpaulyou just need bit.bang to drive that logic14:10
kristianpaulsorry late comment..14:10
GNUtoook14:16
whitequarkroh: I think it's 9600 baud. maybe 115200, but definitely not more15:16
wpwrakwhitequark:  depends on whether you have clamp diodes on the 3.3 V side and how they are rated15:26
wpwrakbut yes, the voltage differential seems to be small enough that there usually shouldn't be problems15:27
whitequarkwpwrak: on the 3V3 side there's STM3215:42
whitequarkit should be able to deal with 10mA of current or something like that15:42
wpwrakthe higher-voltage side is usually the one who suvives :)15:43
whitequarkyeah, I was a bit surprised by your question16:00
whitequarkdid you mean "clamp diodes on 2V8 side?"16:01
wpwrakyes16:26
wpwrakah .. indeed, i was confused. now i see it :)16:26
whitequarkso16:28
whitequarkI don't know anything about 2.8V side16:28
whitequarkbut it has an ARM926EJS core16:28
whitequark... and it has successfully withstanded a connection of 3.3V UART without any damage16:28
whitequark(I, errrr, misread the datasheet)16:29
wpwrak;-)16:59
Action: kristianpaul reads about Eye-fi cards17:38
kristianpaulargh, boring17:47
wpwrak;-)17:53
kristianpaulmix of saas plus wifi you dont know what does..17:53
kristianpaulhardware driven by SaaS is scary more if related to personal stuff17:54
whitequarkeyefi is almost dead afaik17:58
whitequarkseriously. you won't find a good SDIO wifi card. I searched for months17:58
whitequarkhttp://www.microchip.com/pagehandler/en-us/press-release/microchips-8051-mcus-are-100-c.html17:58
whitequarkwpwrak: just look at these necrophiliacs17:58
viricwhitequark: there is that relatively new chip from TI17:58
viricwhitequark: not a sdio card, but it's a full wifi device in a block, with sdio interface.17:59
kristianpaulwhitequark: yeah, i decied move to wpan definitelly18:03
kristianpaulfor the nanonote wireless link18:03
viricI can't find the TI link18:06
viricbut the chip was sold for 30¬18:06
whitequarkviric: so the device would be twice as expensive18:06
whitequarknah. I'd rather buy, like, three android tablets for the same cost. it's the problem with wifi.18:07
viricwhitequark: http://openlink.org/18:07
whitequarkwpan is a good project as of itself, but not a solution to the wifi problem.18:07
whitequarkviric: TI's wireless drivers are of exceptionally bad quality18:08
whitequarkand, at least in some cases, they require some parts of the stack to be blobs while being advertised as "open"18:08
kristianpaul we evenually will need our own network and tech anyway no?18:08
whitequarknot sure if in this they do18:08
viricwhitequark: I've no idea about that18:08
whitequarkkristianpaul: not quite18:08
whitequarkyou're not going anywhere saying "I don't like all that technology produced in counts of billion because I just don't like it"18:09
whitequark("because it's nonfree" = "because I don't like it")18:09
kristianpaulno no i dont want meant that18:09
whitequarkas I've said18:09
whitequark802.15.14 is great and it has a really interesting future as a part of "Internet of Things" or how do they call wireless sensor networks18:10
whitequarkbut it is very new (in terms of market) yet, I'd say18:10
viricisn't there bluetooth over sdio and ip over bluetooth?18:11
whitequarknot known to general public. not even mostly known to geeks (compare with Arduino, or maybe Atmel)18:11
whitequarkviric: theoretically yes18:11
kristianpaulbluetooth have pan ys18:11
whitequarkbut IP over Bluetooth is either PPP or encapsulateed ethernet18:11
whitequarkgood luck implementing that (apart from the fact that bt is just as nonfree as wifi is)18:12
viricok18:12
whitequarkwell, I'm not saying it is hard as it is18:13
whitequarklinux already does both18:13
whitequarkbut it relies on a non-free firmware in the dongle18:13
whitequarkviric: (openlink) wait, that might be more sane than I thought18:16
whitequarkdid they just release a fully open wifi stack?18:16
viricwhitequark: That happened one year ago... and I thought I might use it with one of those sdio boards...18:17
viricwhat was the name... made by wpwrak 18:17
whitequarkviric: UBB?18:18
viricthat.18:18
viricbut I got interested by other things meantime :)18:18
whitequarkprocrastination!18:19
viricwhitequark: go investigate the openlink :) I did not read deep about it18:19
whitequarkwell18:25
Action: whitequark looks a 40 episodes long series of some random youtube shit18:26
kristianpaulwhitequark: better get your milkymist and experiment a bit? :)18:27
whitequarkkristianpaul: my brain is too sleepy to do anything sensible now, unfortunately18:29
whitequarkbut when I'd get rid of higher priority projects, it's M1 time18:29
kristianpaulgood !18:29
whitequarkit is a good opportunity to make something really useful. shouldn't miss it.18:30
qi-bot[commit] Werner Almesberger: cameo/zstack.pl (usage): describe option -r (master) http://qi-hw.com/p/cae-tools/ce243b619:07
qi-bot[commit] Werner Almesberger: cameo/fped2d2z.pl: added option -r, like in zstack.pl (master) http://qi-hw.com/p/cae-tools/9f5751a19:07
qi-bot[commit] Werner Almesberger: cameo/fped2d2z.pl: added Z position substitution (master) http://qi-hw.com/p/cae-tools/4ea94e719:07
qi-bot[commit] Werner Almesberger: bacon/case/: various bits and pieces for parametrization and correct positioning (master) http://qi-hw.com/p/wernermisc/3e39ae019:07
qi-botThe build was successful: http://fidelio.qi-hardware.com/~xiangfu/build-nanonote/openwrt-xburst.full_system-20120318-1841 19:39
kristianpaulhaha http://www.techradar.com/news/internet/pirate-bay-to-take-its-servers-to-the-skies-107208919:53
Aylaawesome :)19:59
larscfree clay pigeons! ;)20:02
kristianpaulroh: whitequark you know the thiness of the osPID case?20:05
kristianpaulI'm planning do sent to manufacture another M1 case, and was hoping also take advatage os full acrylic sheet so.. :-)20:05
whitequarkkristianpaul: hm no20:23
whitequarkbut they have CAD files lying around at github20:23
whitequarkosPID still not arrived yet, so I can't just measure it20:23
kristianpaulcad are 2d svg20:24
kristianpauli dint noticed acrylic specs on the file20:24
kristianpaulanyway alreay sent those to get a quote lets wait for tomorrow :)20:25
whitequarkkristianpaul: oh. full acrylic sheet21:37
whitequarkthis will probably be my source of pain21:38
kristianpaulwhy?21:54
whitequarkbecause I want my case to be made from exactly "2mm green transparent acrylic"22:22
whitequarkand my initial investigation suggests that this is by some reason not the most often sourced material in local fabs22:23
whitequark(apart from the part that a lot of them will refuse to work with me whatsoever if the cost of work is less than $200. that's several meters of acrylic sheet.)22:23
kristianpaulhmm22:48
rohacryllic 3mm is about 30-50E per m²23:14
--- Tue Mar 20 201200:00

Generated by irclog2html.py 2.9.2 by Marius Gedminas - find it at mg.pov.lt!