01:06 <kristianpaul> jesus there is also a brand field

01:07 <kristianpaul> not for me right now :)

01:07 <kristianpaul> and P/N

01:08 <kristianpaul> wpwrak, i guess P/N is required for boom next features?

02:07 <GitHub130> [m1-gps-expansion] kristianpaul pushed 1 new commit to master: https://github.com/kristianpaul/m1-gps-expansion/commit/df374862787c485752b59798dcd681ba55ba5e98

02:07 <GitHub130> [m1-gps-expansion/master] - Naming values and units fixed to better Understandability. - Cristian Paul Peñaranda Rojas

02:08 <kristianpaul> now going power symbols and no more eeschema edtiding for now..

02:08 <kristianpaul> and yes and add specifc boom files :-)

19:55 <kristianpaul> wpwrak: is obvious if i want to use some components from the qi-he kicad liba i have to re-draw layout, right?

19:58 <wpwrak> if you want to replace an already existing footprint with one from kicad-libs, then you have to re-layout that part, yes

20:00 <wpwrak> if it's just one piece or a small number, you only need to redo the traces that connect to it. i.e., delete the 2nd to last segment, delete track on the side of the change (deleting the track will also get rid of any tiny "technical" segments kicad may have inserted), then redraw from the point where you cut it.

20:01 <wpwrak> if you have lots of changes, maybe just keep a copy of the old layout for reference, then delete all traces and redo them. with the old layout as a reference, this usually doesn't take long.

20:02 <wpwrak> (copy) preferably such that you can load it in pcbnew and examine every little detail, if needed

20:22 <kristianpaul> I just want to improve some power labels for this desin https://github.com/kristianpaul/m1-gps-expansion.git

20:22 <kristianpaul> wpwrak can you take a look at it when you have time?

20:23 <kristianpaul> the power supply "sheet" basically i want change that labels for somemething more "apropiate"

20:23 <kristianpaul> perhaps no need

20:24 <kristianpaul> since the component cutoff was already made now i just need to reflect that on the layout and add other files boom may need

20:34 <wpwrak> if you change power labels in the schematics, that shouldn't affect the layout at all

20:35 <kristianpaul> good !

20:35 <DocScrutinizer05> hi folks

20:35 <kristianpaul> hey Doc :)

20:36 <wpwrak> are you sure you want to write 0u01 ? and not something like 10n ? :)

20:36 <DocScrutinizer05> lol

20:36 <kristianpaul> ha, i havent correlate that yet

20:36 <wpwrak> i know it can be tempting to make things not too obvious, but ... ;-)

20:36 <kristianpaul> i just took design from upstream and start working on it :)

20:37 <kristianpaul> sure go ahead, all feedbak is welcome !

20:38 <kristianpaul> still some ICs to drop i just wanted to be conservative on the ref freq sheet as well

20:39 <DocScrutinizer05> Hmm, I may plan for something *useful* now, like visiting dentist, some days on the countryside, or even starting some interesting work

20:39 <kristianpaul> for now i think i'll need some components from kicad-lib..

20:39 <kristianpaul> so should i copy or .. link? (how?)

20:41 <wpwrak> reference them in the .pro file. you can see in existing projects how it's done.

20:42 <kristianpaul> ah in the pro, i was looking at the .sch

20:42 <wpwrak> i.e., you can set the search path (board-m1) or just make an explicit path to the file (ben-wpan and so on)

20:42 <kristianpaul> ah LibDir=, quite easy :)

20:47 <kristianpaul> DocScrutinizer05: how is that, are you providing consulting to a dentist? or just going to the densist as any one do

20:48 <DocScrutinizer05> just as anyone does

20:48 <DocScrutinizer05> though most do faster than me I guess

20:49 <DocScrutinizer05> my medical doctor always gets consulting for free :-D

20:49 <kristianpaul> ;-)

20:49 <kristianpaul> and this interesting work, can you tell us a bit more, what is it about?

20:49 <DocScrutinizer05> let's see what this new dentist will be like

20:50 <DocScrutinizer05> well, for now it's more like a few visits to dentist plus offtime at the countryside. No new exciting tasks yet

20:53 <DocScrutinizer05> I'm just a bit wiser now than I've been 9 months ago. I now know what a mess LTE is inside, and I know I don't really like clearcase

20:55 <DocScrutinizer05> though maybe clearcase is just fine, when used without any windows around, and without weird wrappers to enforce weird rules for naming etc

20:56 <DocScrutinizer05> and it seems I'm getting too old for mere coding monkey business

20:57 <DocScrutinizer05> or code quality gets worse by the year, so I finnaly reached the state where I feel nausea trying to grok wtf they do

21:06 <DocScrutinizer05> anyway it's abit depressing to quit a job after you spent 6 month with 90% of the time only learning new weird stuff (like clearcase, chip docs, document management system and why you never find what you are serching for), then slowly go productive to maybe 50% of the time doing real work and only 50% learning weird useless stuff, and then you quit and would prefer to rm -rf /knowledge/busines/2012/* in your brain

21:08 <DocScrutinizer05> I haven't touched any electronic meter or tool in the whole time :-/

21:08 <DocScrutinizer05> except Lauterbach

21:08 <wpwrak> at least something :)

21:09 <DocScrutinizer05> yeah. Indeed Lauterbach is mighty mighty magic

21:09 <DocScrutinizer05> not so much the hw, the sw is what does all the really amazing stuff

21:09 <wpwrak> next, you'll join some electronics repair shop in a 3rd world country. back to basics ;-)

21:10 <mth> people say the main attraction to ClearCase is the dynamic views, but to me it looks like a feature that optimizes to minimize the use of the cheapest resource

21:10 <mth> as in, hard drive space is cheap nowadays, but server load and network bandwidth are not

21:11 <DocScrutinizer05> I actually already forgot if we were supposed to use dynamic views or err the opposite (private?)

21:11 <mth> git optimizes the exact opposite way and that works really well

21:11 <DocScrutinizer05> (local?)

21:13 <DocScrutinizer05> but yes, the views (basically bindmounted virtual volumes with directory strucure) were the most annoying thing, since they are slow, instable, and ... windows-infested

21:14 <DocScrutinizer05> only thing more annoying than the views themselves is composing a view for your needs

21:16 <DocScrutinizer05> since there's never been a simple revision/checkpoint/whatever to checkout, but you always needed to pick the right branch&version of each module to create a complete view for your own

21:17 <mth> we had about 100 people with the ClearCase server being a 60 MHz Sun server... I was so glad that my team could use CVS instead

21:17 <DocScrutinizer05> and of course there been no HEAD or anything like that

21:17 <mth> (this was in a time that our desktops were 500-1000 MHz)

21:17 <DocScrutinizer05> lol

21:20 <mth> is the "no HEAD" a problem of ClearCase or of the company you were working at?

21:23 <mth> document management system where you never find what you're looking for sounds familiar as well

21:23 <mth> people figured out that the only search option that actually worked reliably was searching by author

21:23 <mth> so you could find a document as long as you knew who wrote it

21:33 <DocScrutinizer05> yes, kinda identical to my experience

21:34 <DocScrutinizer05> only for us it's project number, like 1683015

21:34 <DocScrutinizer05> so if you know the project number of that chip, you might find the datasheet for it

21:35 <DocScrutinizer05> the no-HEAD problem been an organisational one I guess

21:35 <DocScrutinizer05> since basically on clearcase you could share views

21:36 <DocScrutinizer05> or simply define a proper top mudule that includes all you n4eed

21:36 <DocScrutinizer05> or simply define a proper top module that includes all you need

21:36 <DocScrutinizer05> dang, typos

21:39 <DocScrutinizer05> btw it turned out we got (at least) THREE concurrent DMS

22:19 <LunaVorax> evening

22:33 <mth> larsc: in jz4740-pcm.c, there is this line: for (stream = 0; stream < SNDRV_PCM_STREAM_LAST; ++stream) {

22:34 <mth> shouldn't that be "<=" instead?

22:34 <mth> since SNDRV_PCM_STREAM_LAST is equal to the last item in the enum (SNDRV_PCM_STREAM_CAPTURE)

22:34 <Ayla> it'd be a problem if SNDRV_PCM_STREAM_LAST is 0

22:35 <mth> it's 1

22:35 <Ayla> hence the "would" :)

22:36 <mth> it makes a diference for any _LAST value that is not negative

22:36 <mth> I noticed because the Ingenic 4770 driver has very similar code to larsc's driver, but has a hardcoded "2" there

22:37 <mth> so I checked whether I could replace 2 by SNDRV_PCM_STREAM_LAST and it turns out the values don't match

22:38 <mth> larsc's driver is the only user of that constant in the entire sound/ tree, by the way

22:38 <mth> so we could just as easily declare the constant wrong and larsc's code right ;)

22:39 <mth> I prefer exclusive upper bounds anyway

22:42 <mth> it seems ALSA always uses _LAST for an inclusive upper bound, but most of the rest of the kernel uses it exclusive

22:42 <mth> this is the kind of thing where an enforced coding style would really help

22:44 <mth> actually, the rest of the kernel uses exclusive and inclusive about as often

22:44 <mth> and sometimes it uses _AFTER_LAST to be explicit about being exclusive