2014-01-19 00:33 Guest88517 has joined #qi-hardware
2014-01-19 00:49 wolfspraul has quit [Read error: Operation timed out]
2014-01-19 00:53 wolfspraul has joined #qi-hardware
2014-01-19 01:09 Guest88517 has quit [Ping timeout: 265 seconds]
2014-01-19 01:23 jekhor has quit [Ping timeout: 260 seconds]
2014-01-19 01:39 Jay7 has quit [Read error: Connection reset by peer]
2014-01-19 01:40 Jay7 has joined #qi-hardware
2014-01-19 01:45 jow_laptop has quit [Ping timeout: 245 seconds]
2014-01-19 01:52 jow_laptop has joined #qi-hardware
2014-01-19 02:27 pcercuei has quit [Quit: dodo]
2014-01-19 02:33 dos1 has quit [Ping timeout: 248 seconds]
2014-01-19 04:58 wej has quit [Ping timeout: 245 seconds]
2014-01-19 05:00 wej has joined #qi-hardware
2014-01-19 05:05 Coyo has joined #qi-hardware
2014-01-19 07:25 jow_lapt1p has joined #qi-hardware
2014-01-19 07:25 qi-bot4 has joined #qi-hardware
2014-01-19 07:25 jow_laptop has quit [Ping timeout: 264 seconds]
2014-01-19 07:25 qi-bot has quit [Ping timeout: 264 seconds]
2014-01-19 07:25 larsc has quit [Ping timeout: 264 seconds]
2014-01-19 07:26 qi-bot4 is now known as qi-bot
2014-01-19 07:26 larsc has joined #qi-hardware
2014-01-19 08:38 rz2k has joined #qi-hardware
2014-01-19 08:49 jekhor has joined #qi-hardware
2014-01-19 09:31 valhalla has quit [Ping timeout: 245 seconds]
2014-01-19 09:39 valhalla has joined #qi-hardware
2014-01-19 09:41 lekernel has joined #qi-hardware
2014-01-19 10:31 <whitequark> look: http://hackaday.com/2014/01/17/1-coin-cell-charger/?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+hackaday%2FLgoM+%28Hack+a+Day%29
2014-01-19 10:31 <whitequark> so apparently LR* cells are chargeable! I always wondered about that, their internal structure seemed pretty damn similar to chargeable Li batteries
2014-01-19 11:33 wej has quit [Ping timeout: 260 seconds]
2014-01-19 11:34 dos1 has joined #qi-hardware
2014-01-19 11:35 wej has joined #qi-hardware
2014-01-19 11:43 <nicksydney> wpwrak: fancy of adding a charger for the batter as per the hackaday.com link :)
2014-01-19 11:47 <whitequark> actually, now that I think about it, the RTC battery on old-ish motherboards was just such a coin cell and it certainly was being charged
2014-01-19 11:47 <whitequark> so apparently they can survive such mode of operation for years
2014-01-19 11:50 <whitequark> larsc: why does your hostname refer to a bear?
2014-01-19 11:50 <whitequark> a... sea bear, apparently?
2014-01-19 11:51 <whitequark> my latin is rusty
2014-01-19 11:54 <wpwrak> ah, polar bear. in german, eisbaer ("ice bear"). maybe it's a reference to a song that at its time was quite famous: http://www.youtube.com/watch?v=cTuTc_liKS4
2014-01-19 11:54 <wpwrak> (battery charger) sounds like a nice little standalone project :)
2014-01-19 11:56 <wpwrak> (polar baer) the lyrics are "i'd like to be a polar bear in the cold arctic. then i wouldn't have to shout/scream anymore. everything would be so clear." and "polar bears never have to cry." (supposedly because the tears would freeze, which would be kinda inconvenient)
2014-01-19 11:57 <whitequark> sounds like something DocScrutinizer05 would say
2014-01-19 11:58 <whitequark> that being said, the freezing point of tears can be considerably lower than 0°C, since they're salty
2014-01-19 11:59 <whitequark> and bears certainly have to keep the mucous membrances from freezing over, either way
2014-01-19 12:02 <nicksydney> wpwrak: another USB design http://ctrlv.in/285034 based on this schematic http://www.555-timer-circuits.com/police-siren.html :) ... not pretty
2014-01-19 12:03 <wpwrak> they also can go for a swim at times. so yes, they are able to deal with water.
2014-01-19 12:03 <nicksydney> wpwrak: oh and also laying out the track by hand not auto-routing :)
2014-01-19 12:03 <whitequark> wpwrak: well, if water is already liquid, why would it freeze on them?
2014-01-19 12:05 <wpwrak> here in argentina they even get to spend a lot of time in water if they live in captivity. we have one left in a zoo where it is exposed to peak temperatures of up to 40 C. of course without an overly fancy cooling system. one year ago, the polar bear in the zoo of buenos aires died, due to too much heat and getting irritated by the christmas/new year fireworks.
2014-01-19 12:06 <wpwrak> whitequark: (liquid) if it loses heat to the environment quicker than thermal leakage of the body can warm it, then it could reach freezing temperature. e.g., consider windchill.
2014-01-19 12:10 <wpwrak> nicksydney: circuit is starting to look good :) but your footprints are weird - they have silk screen on the pads. if a factory uses that "as is", the boards will be unusable
2014-01-19 12:10 <wpwrak> (of course, in diy, you typically  just ignore the silk screen)
2014-01-19 12:10 <nicksydney> wpwrak: i'm testing the footprint from this site http://smisioto.no-ip.org/elettronica/kicad/kicad-en.htm to see how it looks like
2014-01-19 12:11 <whitequark> wpwrak: right. but also consider this: how would it lose heat?
2014-01-19 12:11 qwebirc37386 has joined #qi-hardware
2014-01-19 12:11 <wpwrak> let's hope the others are better :)
2014-01-19 12:11 <whitequark> it can lose it by radiation, convection and evaporation of water
2014-01-19 12:12 <whitequark> and I'm pretty sure the latest effect would be the strongest in short timespans. but! evaporation of water makes the solution more concentrated, hence lowering the freezing point even more
2014-01-19 12:13 <qwebirc37386> hi there, i have  short question regarding 3-Way CrossFireX and if it's in any way related to CPU
2014-01-19 12:14 <qwebirc37386> could somebody help e about it, aparently it's an obscure search for google
2014-01-19 12:14 <nicksydney> wpwrak: learn something new when doing layout for a single side board like that using +5V's and GND's pad on the side really help on the routing
2014-01-19 12:14 <nicksydney> wpwrak: was thinking of the concept (when doing the routing) 1-to-many in database world :)
2014-01-19 12:17 <qwebirc37386> i think i asked in the wrong chat room right ?
2014-01-19 12:18 <whitequark> qwebirc37386: yes
2014-01-19 12:19 <qwebirc37386> uups, sorry about that then, i'll be more carefull, anyway thanks
2014-01-19 12:19 <qwebirc37386> nice day to you
2014-01-19 12:20 qwebirc37386 has quit [Quit: Page closed]
2014-01-19 12:20 <whitequark> he was quite nice
2014-01-19 12:25 nicksydney has quit [Remote host closed the connection]
2014-01-19 12:26 nicksydney has joined #qi-hardware
2014-01-19 12:31 <apelete> larsc: hi there
2014-01-19 12:35 <apelete> larsc: wondering which value should be assigned to dst_maxburst member of struct dma_slave_config:
2014-01-19 12:35 <apelete> http://paste.debian.net/77188/
2014-01-19 12:37 <apelete> larsc: looking at datasheet, I can't figure out if that should be half the fifo size (8 words ?) or something else
2014-01-19 12:44 <wpwrak> (http://ctrlv.in/285034) hmm, why do the vias (!) have silk screen rings around them ? did you put components for them ?
2014-01-19 12:45 <wpwrak> nicksydney: also, your vias do noting ;-) a) you board is single-layer, you there's nothing they could connect to
2014-01-19 12:45 <nicksydney> wpwrak: it's not vias it's a pad ....
2014-01-19 12:45 <wpwrak> b) even if it was double-sided, you wouldn't need all these vias. you probably copied the concept from RF boards. there, they're needed because of RF. but your board is much much slower ;-)
2014-01-19 12:46 <wpwrak> ah, that's why
2014-01-19 12:46 <wpwrak> well, anyway. not needed :)
2014-01-19 12:46 <wpwrak> just draw a straight trace and you're good
2014-01-19 12:47 <nicksydney> wpwrak: was having difficulty running the track between the 2 chip and was wondering how to make it easy so that i can run the track nicely...so i put a pad vertically and put them as +5V and GND so I can run the trace neatly instead of going around too long as it was super duper ugly :)
2014-01-19 12:48 <wpwrak> for components that have a specific orientation, e.g., U1 and U2, you may want to put some sort of marker on copper. e.g., i often put a little triangle (made of traces not connected to anything else) a bit outside the corner of pin 1.
2014-01-19 12:48 <nicksydney> wpwrak: when using the pad I can run the track neatly and nicely otherwise it will look like a sphagetti :)
2014-01-19 12:49 <wpwrak> that way, i can see how to turn the part when soldering and i'm less likely to mis-rotate it
2014-01-19 12:49 <nicksydney> wpwrak: (marker) good point will do that
2014-01-19 12:50 <wpwrak> (pad) but you still don't need them :) you can just branch off a trace. when drawing the trace, you have to begin somewhere the trace connects to so that kicad will know which net you're routing, but that's all.
2014-01-19 12:51 <wpwrak> and if you find that restriction bothersome (it can sometimes be), then you can just turn off DRC while doing that
2014-01-19 12:51 <nicksydney> didn't think about turning off DRC...will try that
2014-01-19 12:52 <wpwrak> but in general there's no issue. you can also end a trace when you're in the area you want to go to and then add more things later
2014-01-19 12:52 <wpwrak> turning off DRC is usually a bad idea. but when you really need to, then it's nice that you can.
2014-01-19 12:53 <wpwrak> typical scenarios are when you have an orphaned trace that no longer has a net associated with it and try to connect it again
2014-01-19 12:54 <wpwrak> DRC won't let you do that. so you can turn it off, make the connection (be very careful :), then turn it on and run a DRC check (the bug symbol). kicad will then notice the connection and update the trace's net information. so you'll see net name on the trace in small print and can check whether it's what you intended to get.
2014-01-19 12:55 <nicksydney> (marker) to do this do you use the "Add text  on copper layer..." right ? .... i came out the same layer as the copper....can you change the colour ?
2014-01-19 12:55 <wpwrak> another useful feature is "delete segment" if you want to rearrange a trace without deleting all of it, you delete the last segment of the bothersome part, before it reaches the good part
2014-01-19 12:55 <wpwrak> then you can "delete" the entire bad part(s) without affecting the good part
2014-01-19 13:07 pcercuei has joined #qi-hardware
2014-01-19 13:18 <nicksydney> ok found it need to add keepout area and add the text in :) ..duh !
2014-01-19 13:20 <wpwrak> (marker) you don't want to change the color ;-) after all, you want copper. since this is what you'll already "print" with toner transfer. so it's no extra work. you could of course also transfer a silk screen (where you already have such markers), but that's messy.
2014-01-19 13:20 <wpwrak> you could also just go over the board after etching and manually mark things. but that's lame :)
2014-01-19 13:21 <wpwrak> and i wouldn't use text for that. text needs a lot of space. if you look here: http://downloads.qi-hardware.com/people/werner/anelok/tmp/ybox-draft-20140118.png
2014-01-19 13:22 <wpwrak> the chips have little copper triangles in the corner with the triangle on the silk screen, just a little farther from the center (so that they remain visible when placing the chip, and also to make sure they don't make any accidental contact)
2014-01-19 13:23 <nicksydney> i put an 'o' http://ctrlv.in/285049
2014-01-19 13:24 <wpwrak> i'd put it somewhere where you can still see it when the chip is placed. but the O shape is good.
2014-01-19 13:27 <nicksydney> this is how it looks like when plotted http://ctrlv.in/285051
2014-01-19 13:27 <wpwrak> nice :) what trace width did you use ?
2014-01-19 13:29 <nicksydney> 0.45 mm :)
2014-01-19 13:30 <wpwrak> ah, i mean for the "o". that's about 0.15 then ?
2014-01-19 13:30 <nicksydney> but you see some traces are still small as it's not even in sizes .. don't know why
2014-01-19 13:30 <nicksydney> for the '0' it's 0.1mm
2014-01-19 13:30 <wpwrak> ah, i was wondering about that. maybe you did something strange in the design rules. that's not something that normally happens.
2014-01-19 13:32 <nicksydney> this is what i set in my DRC ... http://ctrlv.in/285054 .. http://ctrlv.in/285055
2014-01-19 13:32 <nicksydney> http://www.straitstimes.com/breaking-news/technology/story/flying-car-spreads-its-wings-slovakia-20140119
2014-01-19 13:34 <wpwrak> setting look safe enough. maybe you drew part of it with other settings, then changed them
2014-01-19 13:37 <nicksydney> let me redraw them and see
2014-01-19 13:42 <nicksydney> interesting project http://www.indiegogo.com/projects/ice-xpc-a-modular-computer-as-small-as-your-phone
2014-01-19 13:42 rz2k has quit []
2014-01-19 13:45 <nicksydney> what I like about Neo900 is the form factor is very much suitable for any other project/product :)
2014-01-19 13:50 <wpwrak> yeah, it'll be a good project to scavenge from :)
2014-01-19 13:51 <wpwrak> pity they're quite constrained in their choice of chips. but if the thing flies well, maybe they'll make a neo1000 where they can take more chances :)
2014-01-19 13:53 <nicksydney> wpwrak: you know looking around I haven't found any open source project in similar kind of form factor as neo900....it is an attractive proposition if another non-mobile product can be created out of neo900
2014-01-19 13:56 <wpwrak> yeah, neo900 takes a very smart approach: do something that seems overwhelmingly hard by reusing already existing complex parts (case, sw)
2014-01-19 13:57 <whitequark> NEO9000
2014-01-19 13:58 <wpwrak> hehe ;-)
2014-01-19 14:00 <nicksydney> OpenPhoenux Neo900 Progress Update - January (showblockers resolved) --> http://www.reddit.com/r/linux/comments/1via7r/openphoenux_neo900_progress_update_january/
2014-01-19 14:05 lekernel has quit [Ping timeout: 252 seconds]
2014-01-19 14:05 <wpwrak> the world is full of naysayers who are all to eager to projects their own limitations on others ;-)
2014-01-19 14:13 <nicksydney> that's why the world is not a safe place to live in :)
2014-01-19 14:18 lekernel has joined #qi-hardware
2014-01-19 14:46 jekhor has quit [Ping timeout: 272 seconds]
2014-01-19 15:18 mth has quit []
2014-01-19 15:50 <apelete> larsc: made a few changes in jz4740_mmc.c, in particular requesting the mmc memory region for dma operation (instead of requesting it for void __iomem *base member of struct jz4740_mmc_host) in probe(): http://paste.debian.net/77217/
2014-01-19 15:51 <apelete> larsc: seems to boot fine -> http://paste.debian.net/77218/
2014-01-19 15:54 <apelete> larsc: but what do you think about those changes ?
2014-01-19 15:55 <apelete> I'm asking before replacing jz4740_mmc_{read,write}_data() with the dma equivalent functions since I guess I may experience data corruption if something goes wrong :)
2014-01-19 15:55 mth has joined #qi-hardware
2014-01-19 16:13 <larsc> devm_ioremap-resource does the request_mem_region interally
2014-01-19 16:14 <larsc> otherwise looks good
2014-01-19 16:15 <larsc> for max_burst you need to make sure that max_burst + DMA request threshold <= FIFO size
2014-01-19 16:22 <larsc> anyway need to go, I'll be back tomorrow
2014-01-19 16:28 rz2k has joined #qi-hardware
2014-01-19 16:51 porchaso0 has joined #qi-hardware
2014-01-19 16:52 porchao has quit [Ping timeout: 272 seconds]
2014-01-19 17:32 jow_lapt1p is now known as jow_laptop
2014-01-19 17:59 uwe_ has quit [Ping timeout: 252 seconds]
2014-01-19 18:10 uwe_ has joined #qi-hardware
2014-01-19 18:55 Luke-Jr has quit [Ping timeout: 245 seconds]
2014-01-19 19:03 Luke-Jr has joined #qi-hardware
2014-01-19 19:11 porchao has joined #qi-hardware
2014-01-19 19:12 porchaso0 has quit [Ping timeout: 246 seconds]
2014-01-19 19:20 uwe_ has quit [Ping timeout: 272 seconds]
2014-01-19 19:42 uwe_ has joined #qi-hardware
2014-01-19 19:54 arielenter has joined #qi-hardware
2014-01-19 20:02 arielenter has quit [Quit: Leaving.]
2014-01-19 20:02 arielenter has joined #qi-hardware
2014-01-19 20:04 wej has quit [Ping timeout: 252 seconds]
2014-01-19 20:05 wej has joined #qi-hardware
2014-01-19 20:11 arielenter has quit [Ping timeout: 272 seconds]
2014-01-19 20:13 arielenter has joined #qi-hardware
2014-01-19 20:15 arielenter has quit [Client Quit]
2014-01-19 20:15 arielenter has joined #qi-hardware
2014-01-19 20:20 arielenter has quit [Client Quit]
2014-01-19 20:21 arielenter has joined #qi-hardware
2014-01-19 20:26 jekhor has joined #qi-hardware
2014-01-19 20:27 arielenter has quit [Ping timeout: 265 seconds]
2014-01-19 20:30 rz2k has quit []
2014-01-19 21:09 arielenter has joined #qi-hardware
2014-01-19 21:17 jekhor has quit [Ping timeout: 248 seconds]
2014-01-19 22:11 <qi-bot> [commit] Paul Cercueil: Sort links once they have all been added to the menu (master) http://qi-hw.com/p/gmenu2x/8bb58f6
2014-01-19 22:11 <qi-bot> [commit] Paul Cercueil: Change sort order so that OPKs are listed after normal links (master) http://qi-hw.com/p/gmenu2x/1792e63
2014-01-19 22:12 porchaso0 has joined #qi-hardware
2014-01-19 22:13 porchao has quit [Ping timeout: 246 seconds]
2014-01-19 22:15 arielenter has quit [Quit: Leaving.]
2014-01-19 22:19 arielenter has joined #qi-hardware
2014-01-19 22:21 qwebirc96208 has joined #qi-hardware
2014-01-19 22:23 <qwebirc96208> anywhere I can get info about upcoming qi-hardware projects?
2014-01-19 22:23 <qwebirc96208> is there anything in the works?
2014-01-19 22:23 <whitequark> wpwrak has anelok
2014-01-19 22:28 arielenter has quit [Quit: Leaving.]
2014-01-19 22:29 <wpwrak> the main information source is the qi-hardware mailing list
2014-01-19 22:29 <wpwrak> as far as code is concerned, anelok has its repos here: https://gitorious.org/anelok
2014-01-19 22:43 <nicksydney> wpwrak: code and schematics to be precise inside the repo :)
2014-01-19 22:44 <wpwrak> yeah, almost all that matters :) pictures are here: http://downloads.qi-hardware.com/people/werner/anelok/tmp/
2014-01-19 22:45 <nicksydney> wpwrak: well you don't have your picture in the repo though :) ... hahhaah
2014-01-19 22:46 Luke-Jr has quit [Excess Flood]
2014-01-19 22:46 Luke-Jr has joined #qi-hardware
2014-01-19 22:53 pcercuei has quit [Quit: brb]
2014-01-19 22:54 <nicksydney> wpwrak: do you know how long it took for the Neo900 to be fully laid out and routed ?
2014-01-19 22:54 pcercuei has joined #qi-hardware
2014-01-19 23:08 lekernel has quit [Quit: Leaving]
2014-01-19 23:36 uwe_ has quit [Ping timeout: 252 seconds]
2014-01-19 23:42 uwe_ has joined #qi-hardware