2010-12-17 00:09 were can i get the wifi chip at for the nanonote 2010-12-17 00:22 rxvt: hi 2010-12-17 00:22 check this http://en.qi-hardware.com/wiki/Ben_NanoNote_Wi-Fi 2010-12-17 00:22 kristianpaul: i couldnt find anything on there about buying one of the chips 2010-12-17 00:23 hmm 2010-12-17 00:24 wolfspraul, wpwrak : you there? 2010-12-17 00:26 4.65mm - 3.6 mm = 1.05 mm, 7.6 mm + 1.05 mm = 8.65 mm 2010-12-17 00:27 now P1 (Digi -Key) S7002-ND the height is 8.5mm 2010-12-17 00:30 J5 (2.6mm + 6mm = 8.6mm), but actually only 6mm, so i need to find a P1 with 6.05 mm (8.65mm - 2.6mm = 6.05mm) 2010-12-17 00:30 hope I don't calculate in wrong 2010-12-17 00:34 hmm 2010-12-17 00:34 hope we can find this 2010-12-17 00:34 now we have already shipped out m1, so if anything we need to make the adjustment on the jtag-serial side 2010-12-17 00:34 yes, i am finding..:) 2010-12-17 00:34 maybe clip off the 4-pin serial header on jtag-serial? that's what yanjun luo ended up doing 2010-12-17 00:35 but it's a bit hard to clip it off, because it's a female version so it has metal, plastic, all together 2010-12-17 00:35 yeah...it's a female type 2010-12-17 00:36 will ugly with poor quality if crop it on jtag/serial brd. 2010-12-17 00:36 well..let find digi-key parts first :) 2010-12-17 01:28 wolfspraul, http://www.mouser.com/Interconnects/Rectangular-Connectors/Headers-Wire-Housings/_/N-7aunt?P=1z0wxp7Z1z0z63xZ1z0wxp6Z1z0wxp8Z1yzv7x1 2010-12-17 01:28 go to the lowest two links(datasheet) 2010-12-17 01:29 sorry, the last second and third one 2010-12-17 01:31 ok go on 2010-12-17 01:33 or this (low profile from 3M)http://www.mouser.com/ProductDetail/3M-Electronic-Solutions-Division/929984-01-04/?qs=sGAEpiMZZMtsLRyDR9nM19IUZhCvwtX27JEp18A0Hio%3d 2010-12-17 01:34 actually I don't know how boom can generate a shopping list for multiple distributors 2010-12-17 01:34 right now it only displays one list, and the p/n are digikey numbers 2010-12-17 01:34 the P1 I calculated is 6.05mm AT MOST. So we should can use 3M low profle 2010-12-17 01:35 so you will get this from mouser? 2010-12-17 01:35 i know, this P2 temporarily we may pick from other distributer 2010-12-17 01:35 how about the jtag (7*2) connector? 2010-12-17 01:35 also mouser, or that one digikey? 2010-12-17 01:35 can use that one in Digi-Key (79109-1006) 2010-12-17 01:36 of course if later we found omst of shipping list can buy from mouser, then we buy from mouser. 2010-12-17 01:37 right now , i don't know. i just tried to find the parts I am worrying first. 2010-12-17 01:38 yes sure 2010-12-17 01:38 other electronic parts should be ok. 2010-12-17 01:38 how do you think? 2010-12-17 01:38 I can discuss with wpwrak how we can extend boom to multiple distributors (it's already possible, just needs a bit of work at the surface) 2010-12-17 01:38 yes sure, all good 2010-12-17 01:38 only keep us posted for any differences from the shopping list boom generates right now 2010-12-17 01:38 let me first review all parts done in shopping list and memo the new links I found first. 2010-12-17 01:39 so for everything on that list that you actually don't buy, or buy in another quantity, or from another source, I would like to update boom 2010-12-17 01:39 but you should definitely move ahead and just get these things produced 2010-12-17 01:39 boom has to be able to handle reality :-) 2010-12-17 01:39 so no waiting 2010-12-17 01:40 yes..i just recorded on my BOOKSHELF first then we determine later... 2010-12-17 01:40 those connectors will always need to be matched manually anyway, I'm sure. that's not worth trying to automate in boom. 2010-12-17 01:40 good, yes 2010-12-17 01:40 cu 2010-12-17 01:40 [bookshelf] 2010-12-17 02:53 wpwrak, wolfspraul when i use 'dsv' to review bookshelf, the bookshelf itself only shows few components(or just classify simply already). 2010-12-17 02:54 from bookshelf it seems that I can not sure for example resistors or capacitors will be missed? is it possible? 2010-12-17 02:56 because i can see the final 'make show' parts list with every part without doubting. 2010-12-17 02:58 that was too fast for me 2010-12-17 02:58 dsv and boom are two totally separate tools 2010-12-17 02:58 which one do you want to talk about - dsv or boom? 2010-12-17 03:01 adamwang: got disconnected... 2010-12-17 03:02 dsv and boom are 2 totally separate tools 2010-12-17 03:02 dsv works with BOOKSHELF, that's all 2010-12-17 03:03 adamwang: is your question about dsv or boom? 2010-12-17 03:04 i'm trying to understanding the system more. when I review footprint of 1206/0603/0402 package 2010-12-17 03:05 i have many ways can review: one from layout/or gerber file, one from shopping list (digi-key)backward to check if the part link is correct. 2010-12-17 03:07 so i am now from the shopping list backward to review actually footprints used in PCBnew. 2010-12-17 03:07 we should pull all links to PDF files into BOOKSHELF 2010-12-17 03:08 wow..damn it. current bookshelf itself doesn't have resistors and capacitors' pdf link. 2010-12-17 03:08 so you're saying i need to do this now? 2010-12-17 03:09 let's do one together 2010-12-17 03:09 which one are you looking at? 2010-12-17 03:10 it's not that bad :-) BOOKSHELF has 12 entries right now 2010-12-17 03:11 let's add one... 2010-12-17 03:11 for example the 33pF capacitor 2010-12-17 03:11 digikey p/n is 311-1020-1-ND, as shown by boom 2010-12-17 03:12 yes, go on 2010-12-17 03:13 digikey says the datasheet is http://www.yageo.com/documents/recent/UPY-GP_NP0_16V-to-50V_4.pdf 2010-12-17 03:13 ok...now you don't need to do this 2010-12-17 03:13 i do this on my site 2010-12-17 03:13 wait a sec 2010-12-17 03:17 [commit] Wolfgang Spraul: added 33pF 0402 capacitor to BOOKSHELF http://qi-hw.com/p/mmone-jtag-serial-cable/34eaee8 2010-12-17 03:17 adamwang: hmm 2010-12-17 03:17 it worked 2010-12-17 03:17 so I added a new entry to BOOKSHELF, also with the aliases C1 and C3 2010-12-17 03:17 then I ran "dsv setup BOOKSHELF" to download the new file 2010-12-17 03:18 now I can do "dsv C1" 2010-12-17 03:18 yes, i know your way. 2010-12-17 03:18 the I dit git commit -a and git push. 2010-12-17 03:18 so right now, dsv and boom are totally separate. 2010-12-17 03:18 that means boom can choose another capacitor, and dsv will not know about it. 2010-12-17 03:18 for example when we add mouser to boom. 2010-12-17 03:18 or a new capacitor manufacturer 2010-12-17 03:19 dsv is simply a small tool to manage pdf files 2010-12-17 03:19 I think this is good right now, we can start like this. 2010-12-17 03:19 we cannot design all tools perfect at the beginning, we have to start using them, and then slowly improve. 2010-12-17 03:19 so right now, you just add those PDF links manually into BOOKSHELF, even though boom does not know about BOOKSHELF. 2010-12-17 03:20 then we can discuss with Werner how to improve the tools. Slowly because we have a long todo list of things we want to improve :-) 2010-12-17 03:20 what do you think? 2010-12-17 03:20 yes, agreed. 2010-12-17 03:21 but my gaol today is to determine order all them from Digikey or Mouser. 2010-12-17 03:21 if to do all of them...man. 2010-12-17 03:22 not that many missing 2010-12-17 03:22 I can add them if you like, including the aliases for schematics references 2010-12-17 03:22 yeah.. 2010-12-17 03:22 no problem 2010-12-17 03:22 should I do that? 2010-12-17 03:22 no 2010-12-17 03:23 311-1020-1-ND from shopping list it says 10 pcs for one set? 2010-12-17 03:23 we need 2 for one jtag-serial, and probably the price for 10 is lower than for 2 2010-12-17 03:23 but from schematic I only see TWO. 2010-12-17 03:23 am i wrong? 2010-12-17 03:23 digikey only sells 10 2010-12-17 03:24 remember that boom uses a real digikey database 2010-12-17 03:24 including volume discounts 2010-12-17 03:24 so if we need 6, then maybe buying 10 is cheaper than 6*1 2010-12-17 03:24 then boom will buy 10 2010-12-17 03:24 (for example) 2010-12-17 03:25 the things boom does not consider right now are: 2010-12-17 03:25 1) shipping costs 2010-12-17 03:25 2) lead time (it looks at stock level though) 2010-12-17 03:25 3) minimum USD amount per order 2010-12-17 03:25 wow..ok..that's the boom's 'thought' now 2010-12-17 03:26 but it does consider volume discounts 2010-12-17 03:26 if you want me to update BOOKSHELF just let me know, I am glad to be able to help you 2010-12-17 03:26 i hope there's one column which can show exactly how many 33pF we used in schematic 2010-12-17 03:27 you mean in the shopping list? 2010-12-17 03:27 yes 2010-12-17 03:27 no need? like I made mistakes in rc2 2010-12-17 03:27 i forgot to add some resistors actually. 2010-12-17 03:28 so will 'boom' happen? 2010-12-17 03:28 when you are in the bom/ directory, try this command: cat usb_jtag.ord 2010-12-17 03:29 it will list the schematics references behind each item, just for a quick look now 2010-12-17 03:29 we can ask Werner what he thinks about adding a count, or list of references, to the 'pretty printed' 'make show' shopping list 2010-12-17 03:29 ok, so this .ord file will show exact qty brd used? 2010-12-17 03:29 I know you want that for cross-referencing/double-checking. 2010-12-17 03:30 right. 2010-12-17 03:30 did you do 'cat usb_jtag.org'? 2010-12-17 03:30 yes 2010-12-17 03:30 i saw it 2010-12-17 03:30 it's good 2010-12-17 03:30 there is no count, but the schematics references are listed. you can count yourself :-) 2010-12-17 03:30 this can easily be formatted differently, when werner is back we see what he thinks 2010-12-17 03:31 well...that's why I want a quick 'count' data of column then I can see it... 2010-12-17 03:31 the i don't need to see other .org file...agreed? 2010-12-17 03:31 waste time 2010-12-17 03:31 the .ord shows you the schematics references 2010-12-17 03:32 up to you, the .ord is always there, it's part of the boom processing 2010-12-17 03:32 it's generate automatically when you run 'make clean show' 2010-12-17 03:36 pls add me to jtag member, tks. 2010-12-17 03:39 adamwang: done 2010-12-17 03:40 tks 2010-12-17 03:50 can i just use "git add BOOKSHELF" only? 2010-12-17 03:51 hm..i saw help, should be no problem. 2010-12-17 03:52 most important is git commit, then git push 2010-12-17 04:07 fatal: The remote end hung up unexpectedly<<< when i 'git push' 2010-12-17 04:08 i have long time no use 'git', i should successfully 'git commit -a' with [master 44d1c56] trying to add R15 2010-12-17 04:08 2 files changed, 21 insertions(+), 1 deletions(-) 2010-12-17 04:10 hmm 2010-12-17 04:10 did you do a new git clone after I added you as member? 2010-12-17 04:10 no 2010-12-17 04:10 ah 2010-12-17 04:11 ok...clone again 2010-12-17 04:11 tks 2010-12-17 04:11 wait one second 2010-12-17 04:11 ah yes it should be OK 2010-12-17 04:11 remember I copied you my boom parts database, but it's in another folder 2010-12-17 04:11 so I think you can safely delete the mmone-jtag-serial folder, and clone it again, with 2010-12-17 04:11 git clone git@projects.qi-hardware.com:mmone-jtag-serial-cable.git 2010-12-17 04:12 then you need to create the usb_jtag.lst file by going into eeschema, and clicking on the create bom button at the top 2010-12-17 04:12 um...hope those parts database will still there. 2010-12-17 04:12 umm..yes 2010-12-17 04:12 also if you edited the BOOKSHELF, copy it somewhere so you don't need to reenter 2010-12-17 04:12 yeah..thanks reminder 2010-12-17 04:13 just rename the whole mmone-jtag-serial-cable folder to mmone-jtag-serial-cable.old or so 2010-12-17 04:20 i still got fatal after 'git push'. Does my current 'password' not same as before you create? 2010-12-17 04:21 try: git pull 2010-12-17 04:21 that works? 2010-12-17 04:22 git pull works 2010-12-17 04:22 # On branch master 2010-12-17 04:22 # Your branch is ahead of 'origin/master' by 1 commit. 2010-12-17 04:23 i think the BOOKSHELF is being committed just no 'push' successfully. 2010-12-17 04:23 ok wait 2010-12-17 04:24 adam@adam-laptop:~/mmone-jtag-serial-cable$ git commit -a 2010-12-17 04:24 [master 1e6288c] trying to add R15 and other P1 parts found 2010-12-17 04:24 1 files changed, 14 insertions(+), 0 deletions(-) 2010-12-17 04:25 you did the git clone git@... ? 2010-12-17 04:25 yes 2010-12-17 04:26 try: cat .git/config 2010-12-17 04:26 there should be a line url = ... 2010-12-17 04:27 does it say url = git@... 2010-12-17 04:27 yes, it does 2010-12-17 04:28 [remote "origin"] 2010-12-17 04:28 fetch = +refs/heads/*:refs/remotes/origin/* 2010-12-17 04:28 url = git://projects.qi-hardware.com/mmone-jtag-serial-cable.git 2010-12-17 04:28 he :-) 2010-12-17 04:28 it does not 2010-12-17 04:28 it says git:// 2010-12-17 04:28 but we need git@ 2010-12-17 04:29 oah...what's difference? sorry I don't know. 2010-12-17 04:29 no problem, it's a bit confusing 2010-12-17 04:29 there are 2 ways for each project 2010-12-17 04:29 depending on whether you are read-only (public, anybody in the world), or read-write (only members and admins of the project) 2010-12-17 04:29 the read-only looks like this: git clone git://projects.qi-hardware.com/mmone-jtag-serial-cable.git 2010-12-17 04:30 the read-write looks like this: git glone git@projects.qi-hardware.com:mmone-jtag-serial-cable.git 2010-12-17 04:30 so i did a read-only clone? 2010-12-17 04:30 yes 2010-12-17 04:30 oah..i see 2010-12-17 04:30 there is a way to change it, but I don't know how, and xiangfu is just out 2010-12-17 04:30 so just do the git clone again 2010-12-17 04:30 new tree 2010-12-17 04:30 sorry, delete and try again 2010-12-17 04:30 yes 2010-12-17 04:31 :) 2010-12-17 04:37 [commit] Adam Wang: add R15 and P1 for other source http://qi-hw.com/p/mmone-jtag-serial-cable/2380579 2010-12-17 04:39 adamwang: congratulations! 2010-12-17 04:39 :-) 2010-12-17 04:39 ha...tks! 2010-12-17 04:53 lekernel: how do you like this: http://en.qi-hardware.com/wiki/File:AC%28EU%29_to_DC_adapter_Fairway_WN10B-050_with_Milkymist_4_pixels.png 2010-12-17 04:54 not as bad as on the side :) 2010-12-17 04:55 ok good 2010-12-17 04:55 so we go with that for now 2010-12-17 04:55 the dc-10 is slightly better too now, the one for bearstech was still glued :-) 2010-12-17 04:55 we have ordered adapters with US connector as well 2010-12-17 04:56 lekernel: another thing, I want to remove all usage of microSD, *SD* everywhere. we discussed a bit yesterday here, and our proposal is to call it 8:10 card 2010-12-17 04:56 8 pins, 10 mm (rounded) 2010-12-17 04:57 on the side we can say something like (*) microSD-like, but primarily we say 8:10 card first 2010-12-17 04:57 what do you think? 2010-12-17 04:58 I say "memory card" 2010-12-17 04:58 I've already removed usage of the "microSD" brand 2010-12-17 04:59 people will immediately understand "memory card", but "8:10 card" means nothing 2010-12-17 04:59 even in the source code it's called "memory card" 2010-12-17 04:59 both works for me 2010-12-17 05:00 ok good that is great, main point is to stop using the *SD* trademarks 2010-12-17 05:01 adamwang: did you see lekernel's feedback on the milkymist sticker? 2010-12-17 05:01 http://en.qi-hardware.com/wiki/File:AC%28EU%29_to_DC_adapter_Fairway_WN10B-050_with_Milkymist_4_pixels.png 2010-12-17 05:01 this is OK for now 2010-12-17 05:02 if we say "memory card reader that works with microSD cards", is that trademark infrigement? 2010-12-17 05:02 in such a sentence - probably not 2010-12-17 05:03 wolfspraul, ok with 4 pixels. 2010-12-17 05:03 but the risk is that our own people simplify this and write "microSD" everywhere 2010-12-17 05:04 that's why a new 'name', even if it is bulky like 8:10 card, helps align the home forces 2010-12-17 05:04 when speaking about 'our' side, the Milkymist One, the most we can say is that it is microSD-like 2010-12-17 05:04 in your sentence, you are describing that our 8:10 card holder happens to also work with microSD cards 2010-12-17 05:05 that shouldn't be a trademark infringement 2010-12-17 05:05 there is a line somewhere 2010-12-17 05:05 we don't want to dance around with this line too much 2010-12-17 05:05 the best is if microSD, or *SD*, just doesn't appear anywhere in our literature, web sites, etc. 2010-12-17 05:06 that's also the easiest to enforce and maintain 2010-12-17 05:07 he he 2010-12-17 05:08 maybe it's even better to say "memory card reader that might work with microSD cards" 2010-12-17 05:08 :-) 2010-12-17 05:08 we probably must not claim that we can guarantee compatibility 2010-12-17 05:08 sounds a bit too unprofessional 2010-12-17 05:08 because without license we have no access to the standard 2010-12-17 05:08 and without access to the standard we cannot claim compatibility 2010-12-17 05:09 there's the "simplified" standard available for free 2010-12-17 05:09 yes but you ask about my opinion. I'm not a lawyer but from past cases this is the kind of stuff you will hear from a lawyer. 2010-12-17 05:09 if you say "that works with microSD cards" - that may be too much already 2010-12-17 05:09 because you don't have access to the standard 2010-12-17 05:09 so how can you say that? 2010-12-17 05:09 "we tested it"? 2010-12-17 05:10 I don't really want to say "might work" either 2010-12-17 05:10 no I was kidding 2010-12-17 05:10 but I realized the standard and compatibility problem 2010-12-17 05:10 for example 'compatible' is a strong word 2010-12-17 05:10 we cannot use it 2010-12-17 05:10 we will be shut down legally 2010-12-17 05:10 you cannot say microSD compatible 2010-12-17 05:10 the most is microSD-like 2010-12-17 05:11 so I took that a little further to make it 'maybe' :-) 2010-12-17 05:11 "designed for microSD cards"? 2010-12-17 05:11 sounds very dangerous 2010-12-17 05:11 that's exactly what you cannot claim 2010-12-17 05:11 we can say that we bought a lot of cards, some of which claim to be microSD compatible 2010-12-17 05:11 our tests show that all of those cards work 2010-12-17 05:12 but you cannot say that you know that you are microSD compatible 2010-12-17 05:12 or that you 'support' microSD 2010-12-17 05:12 or that you 'have' microSD 2010-12-17 05:12 good morning :) let's see what's in the backlog today ... 2010-12-17 05:12 afaik the maximum is microSD-like 2010-12-17 05:13 wpwrak: sebastien is not very fond of our beautiful 8:10 card 2010-12-17 05:13 he wants to have a microSD card 2010-12-17 05:13 :-) 2010-12-17 05:13 yeah, or maybe not mention "microSD" at all 2010-12-17 05:13 (joking, joking...) 2010-12-17 05:13 of course that's the best 2010-12-17 05:13 and keep "memory card" 2010-12-17 05:13 fine by me, it's not a very central feature of Milkymist One anyway 2010-12-17 05:13 external people will eventually say "microSD" anyway 2010-12-17 05:13 fine 2010-12-17 05:13 we just need to keep ourselves clear from trademark infringement 2010-12-17 05:17 lekernel: the defense line goes like this: 2010-12-17 05:17 someone says "you need a SD HALA license" 2010-12-17 05:17 we say "no, we don't support any SD standard or protocol" 2010-12-17 05:17 they say "yes, you support microSD cards" 2010-12-17 05:17 "no, we don't" 2010-12-17 05:17 "but what is that connector there" 2010-12-17 05:17 "that's a 8:10 card holder" 2010-12-17 05:18 etc. 2010-12-17 05:19 it's difficult they have patents, copyrighted stuff, trademarks. but we need to start somewhere and staying clear of the trademarks is relatively easy. 2010-12-17 05:22 patents? besides the connector, there's nothing that's patentable (at least in EU) 2010-12-17 05:24 (boom & multi-distro) yes, you can have multiple distributors. see gta02-core. you have to modify the output generator to see them, though. (in gta02-core, you have a different makefile target for each, but that's probably not the most elegang way) 2010-12-17 05:30 (boom: count/ref) good idea. let me add it to my to do list :) 2010-12-17 05:36 lekernel: we seem to have a solution for now. We are purging *SD* everywhere. You say 'memory card', I say '8:10 card' when pressed or in tech specs, otherwise also memory card or flash memory card when explaining. 2010-12-17 05:38 (usd/8:10 - claim compatibility) i don't see why a compatibility claim would be a problem. it's an assurance you make about your product. as long as you don't say it's certified ... 2010-12-17 05:39 no, 'compatible' is definitely no good 2010-12-17 05:39 that word has been 'taken' by the other side :-) 2010-12-17 05:39 we cannot claim compatibility unless sanctioned to do so by the other side 2010-12-17 05:40 we absolutely cannot claim microSD compatibility 2010-12-17 05:41 ("memory card" vs. "8:10") i think "memory card" works fine in MM1 "product documentation", for descriptive purposes, because there's only one card anyway. the 8:10 is more something we need to identify cards if there could be other possibilities. 2010-12-17 05:43 ("compatibility") ah, language is tricky ;-) i meant the "works with microSD" or maybe "use with", so you give the customer instructions, without making any explicit claims about your product 2010-12-17 05:43 wolfspraul: if you really want to take this to the end,  then have some "8:10 card" in your shop ;-) 2010-12-17 05:44 lekernel: (card name) one problem is that any names that "sound familiar" are dangerous. it just sucks, no matter what you do. 2010-12-17 05:47 yes all sounds good, I think we are all on the same page 2010-12-17 05:47 let's see how it goes 2010-12-17 05:47 now, the dreaded connectors ... what are the possible actions available ? replace any part with one with a fitting (let's avoid "compatible" :) footprint ? replace only some parts ? re-layout JTAG ? ... 2010-12-17 05:47 (JTAG) the JTAG board i mean 2010-12-17 05:47 "use with microSD" might just be OK still, especially if it is in a larger explanatory text 2010-12-17 05:48 we have to stay away from saying that _OUR_ stuff is somehow *SD*, and we have to stay away from 'compatible', because that is understood to be a mutual thing 2010-12-17 05:48 for the rest, we do as discussed here, should be OK 2010-12-17 05:49 wpwrak: no re-layout now, because we sent the gerbers out already 2010-12-17 05:49 the connectors need to be positioned without through-hole, or soldered manually 2010-12-17 05:50 so which parts can be replaced with different ones ? 2010-12-17 05:50 different but same-footprinted 2010-12-17 05:50 (avoiding "compatible" is fun ;-) 2010-12-17 05:51 "commensurate" is a good word :) 2010-12-17 05:51 commensurate parts :) 2010-12-17 05:53 I think adamwang found solutions for the connectors already. 2010-12-17 05:53 I just want to make sure we keep updating the bom and bookshelf so our KiCad files are in great shape :-) 2010-12-17 05:54 wolfspraul: (8:10 card) you should post reason and proposed name on the list, perhaps also mentioning that in a reduced context like MM1 one can also use things like "memory card". then let's wait a few days. once the storm of indignation passes, we can start renaming the few references we already have 2010-12-17 05:55 [commit] Werner Almesberger: modules/usd-card.fpd: added measurement of total length http://qi-hw.com/p/kicad-libs/c4f0592 2010-12-17 05:55 there are no references to SD in milkymist afaik 2010-12-17 05:55 I used "memory card" everywhere 2010-12-17 05:56 what does the leaflet say? 2010-12-17 05:56 and no one said a thing btw :) 2010-12-17 05:56 memory card 2010-12-17 05:56 good 2010-12-17 05:57 lekernel: "memory card" works well in the context of a specific product, because you already know that it has to be congruent with uSD 2010-12-17 05:58 (hmm, all this avoiding of "compatibility" makes me wonder if some of the strange translations we get in the manuals of asian products may actually be intentional ;-) 2010-12-17 06:00 lekernel: "memory card" wouldn't work when specifying/discussing a new design, where is may also be full-size SD, CF, memorystick, or maybe a DIMM. 2010-12-17 06:02 lekernel: that is, unless you want to explain each time that it has to agree with uSD 2010-12-17 06:02 no big deal... 2010-12-17 06:03 see, it's about the first time I hear about this "problem" when there are already 46 milkymist boards out 2010-12-17 06:04 all using the "memory card" terminology 2010-12-17 06:04 lekernel: the "problem" right now are more those 1000+ bens out there that proudly proclaim "microSD" on the case ;-) 2010-12-17 06:04 mh 2010-12-17 06:05 just rename it to "memory card", I'd say 2010-12-17 06:05 8:10 card really does mean nothing 2010-12-17 06:06 it's a name that is descriptive yet hasn't been taken yet. so yes, it doesn't mean anything _yet_ 2010-12-17 06:06 lekernel: the point of 8:10 card is that it means nothing 2010-12-17 06:07 this is not meant to force a re-education upon people 2010-12-17 06:07 it's a placeholder for some tech specs that will give us a clean legal shield against claims of trademark infringement 2010-12-17 06:07 and it's a good name. 8 pins, 10 mm. we can use it in other places later. 2010-12-17 06:07 think of it like "the glass". if you're asking someone you're eating with to pass their glass, you won't bother to specify what the glass is like. if you go to a shop and are looking for one that matches your existing collection, you will use something more descriptive. 2010-12-17 06:07 of course we are not using 8:10 to explain anything 2010-12-17 06:08 so we are all on the same page I think 2010-12-17 06:08 memory card is fine, it's great 2010-12-17 06:08 wolfspraul: eventually, 8:10 will become a meaningful name by itself ;-) 2010-12-17 06:08 yeah, like GNU/Linux and Iceweasel... 2010-12-17 06:10 8:10 card is the fallback for places where we don't want to say memory card. how about that? :-) 2010-12-17 06:10 and for Milkymist One, we can probably say memory card almost everywhere, maybe everywhere. 2010-12-17 06:10 just wait until places like amazon get so many customes asking for "8:10 cards" that they add them as a product category ;-)) 2010-12-17 06:10 I think we are all on the same page actually. 2010-12-17 06:12 hah, better example. "meat". at a barbecue, everybody will understand things like "is the meat ready ?". but you'd look rather foolish ordering "meat" at the butcher shop. 2010-12-17 06:12 lekernel: wpwrak works on a 8:10 card that has an Atmel RF IC on it. not quite a 'memory card'. but it wouldn't fit into the m1 board anyway... :-) 2010-12-17 06:12 well, aren't SD cards more or less a dominent card standard on the market? 2010-12-17 06:12 now we can test it! 2010-12-17 06:13 zear: we don't support SD 2010-12-17 06:13 you mean you support uSD instead? 2010-12-17 06:13 what is uSD? do you mean microSD? 2010-12-17 06:13 we don't support microSD either 2010-12-17 06:14 yes, i mean micro 2010-12-17 06:14 (sorry need to warn you, you are in a guinea pig test right now...) 2010-12-17 06:14 zear: no, we don't support microSD 2010-12-17 06:14 that's a proprietary standard we don't have access to 2010-12-17 06:14 wolfspraul: at least we're not "compatible". maybe we're "friendly" ? :) 2010-12-17 06:14 wolfspraul, i just want to say that here all the non-tech people call SD cards simply by "memory card" 2010-12-17 06:14 yes we are friendly to microSD, definitely 2010-12-17 06:15 great 2010-12-17 06:15 we support many memory cards 2010-12-17 06:15 since nobody used any other format 2010-12-17 06:15 zear: your digital camera uses uSD ? 2010-12-17 06:15 zear: like the Ben uses full-sized SD ? :) 2010-12-17 06:15 yeah, exactly, that's why the "memory card" term is good (for M1 at least, where I don't plan any other use of the card connector) 2010-12-17 06:16 wpwrak, yes, i use uSD for my digital camera 2010-12-17 06:16 argh 2010-12-17 06:16 Werner is raining on my parade 2010-12-17 06:16 I didn't see any of this. 2010-12-17 06:16 wolfspraul: we're very supportive of memory cards ;-) 2010-12-17 06:16 I have never seen or heard about anything SD 2010-12-17 06:16 ahh 2010-12-17 06:16 good 2010-12-17 06:16 memory cards 2010-12-17 06:16 that I know 2010-12-17 06:16 though I'm not shocked of "wireless adapters" that plug into memory card connectors either 2010-12-17 06:17 SD means "secure digital", so it's not a good term anyway 2010-12-17 06:17 lekernel: "wireless" is a good example for a term that's easily used in an overly generic way. e.g., it would be borderline fraud if you sold the ben-wpan card simply as a "wireless card" 2010-12-17 06:18 when you say "a floppy disk", nobody thinks about 8 inch ones, am i right? 2010-12-17 06:18 SD = Synchronous Data ;-) 2010-12-17 06:18 the same way when you say "memory card" nobody thinks of anything else than SD family 2010-12-17 06:18 newcomer...  What is the problem with the uSD connector? legal issue? 2010-12-17 06:19 zear: i remember the days where you had the choice of 5.25" and 3.5", HD and DD, nicely on the rack next to each other 2010-12-17 06:19 andres-calderon: yes. the name "microSD" is protected (trademark) 2010-12-17 06:20 wpwrak, lucky you, i never had a chance to mount a floppy on linux :P 2010-12-17 06:20 zear: "sd family". perhaps. but you still don't know which member of the family. 2010-12-17 06:20 ok, SDIO is protected  too? 2010-12-17 06:20 wpwrak, yes, but you have adapters 2010-12-17 06:20 zear: i wrote some code in floppy.c ;-) 2010-12-17 06:20 wpwrak, nobody buys full SDs anymore, they usually sell microSD + fullSD adapters 2010-12-17 06:21 zear: (adapters) like for putting that full-sized SD into your phone ? :) 2010-12-17 06:21 wpwrak, no, the other way out one ;) 2010-12-17 06:21 although i have such one 2010-12-17 06:21 zear: you can still buy full-sizes SD pretty much everywhere 2010-12-17 06:21 wpwrak, they're mostly leftovers 2010-12-17 06:21 at least here 2010-12-17 06:22 see what "memory card" you get at a sony shop ;-) 2010-12-17 06:22 i think they still sell that high speed fullSDHC for cameras, for any other task they sell microSDs 2010-12-17 06:22 wpwrak, why would you want to shop there? :D 2010-12-17 06:23 the last time i went there, i returned with the only sony bravia tv that wasn't linux based 2010-12-17 06:23 quite a disappointment 2010-12-17 06:23 one criterion for the name is also that it has to be non-interactive. "a memory card" followed by "no, the other kind" is not an option. 2010-12-17 06:24 wpwrak, then call them "es-dee cards" 2010-12-17 06:24 (tv without linux) see, that's what happens if you're not specific enough ;-) 2010-12-17 06:24 i suggested 5D ;-) 2010-12-17 06:25 5D sounds great 2010-12-17 06:26 the enemy lawyers would have feeding frenzy :) 2010-12-17 06:26 s/have/have a/ 2010-12-17 06:27 lekernel: exactly, 'secure digital' is a trademark, not a name 2010-12-17 06:27 why not call them "insecure digital" then 2010-12-17 06:27 andres-calderon: we call them 8:10 cards now 2010-12-17 06:27 8 pins, 10 mm (rounded) 2010-12-17 06:28 :-) 2010-12-17 06:28 ah no, not 'them' 2010-12-17 06:28 our cards _are_ 8:10 cards 2010-12-17 06:28 we don't know whether they are compatible with microSD or not 2010-12-17 06:28 where i can found  any  document to read about the uSD issue? 2010-12-17 06:29 andres-calderon: the issue is that 'Secure Digital' and anything *SD* is trademarked 2010-12-17 06:29 in addition they claim to hold patents, and copyrighted whatever 2010-12-17 06:29 wolfspraul, what about microMMC cards, are they different? 2010-12-17 06:29 in size/number of pins 2010-12-17 06:29 yes I think that's owned by someone else 2010-12-17 06:30 ah 2010-12-17 06:30 are you asking a legal or technical question? 2010-12-17 06:30 technically it's probably 'the same' :-) 2010-12-17 06:30 though i guess the driver can support them as well if they only can fit the slot 2010-12-17 06:30 legally it's not the same 2010-12-17 06:30 we are mostly talking about legal stuff here 2010-12-17 06:31 but 8:10 cards would point to two different things then ;) 2010-12-17 06:31 microMMC has a different size. not sure about number of contacts/protocol 2010-12-17 06:31 andres-calderon: this is the issue: http://www.sdcard.org/developers/join/licensing/hala/ 2010-12-17 06:31 as copyleft hardware, we try to make hardware that is as little dependant on such proprietary technology as possible 2010-12-17 06:32 otherwise the licensing requirements, even if Sharism Ltd. would sign the license, would perpetuate upon anybody making use of the copyleftness of our work 2010-12-17 06:32 so it would taint the copyleftness of our work 2010-12-17 06:32 hence we work on removing such taintedness 2010-12-17 06:32 btw wolfspraul, i remember you mentioning somewhere once that you guys had 2 or 3 cases of nn warranty replacement due to weird stuff happening on screen, am i right? 2010-12-17 06:33 yes 2010-12-17 06:33 because my nn seems to change the LCD colors when i move with the hinge 2010-12-17 06:33 not good :-) 2010-12-17 06:33 and i'd like to know what can be the problem 2010-12-17 06:33 mine is the pre-retail unit, so i have no warranty, and the make quality is probably worse as well ;) 2010-12-17 06:33 ideally it's just a problem with the fpc going into the mainboard 2010-12-17 06:34 then you could open that, reseat the fpc, and it would be stable again 2010-12-17 06:34 ah, sounds like something an unskilled person could do 2010-12-17 06:34 worse, it could be a problem with the soldering of the connector the fpc goes into, or on the other side (the side of the lcm), where the cable is soldered onto the pcb right away 2010-12-17 06:34 you have to be careful a little 2010-12-17 06:34 SDA sowed terror in the linux kernel community a  time ago.  But after reading the legal terms they found a simple solution: "we have not signed anything" 2010-12-17 06:34 have you ever opened your nanonote? taken off the plastic around and above the keyboard? 2010-12-17 06:35 wolfspraul, nope, never 2010-12-17 06:35 how bad is the color problem? 2010-12-17 06:35 if it's not very bad, maybe fix it when it gets worse 2010-12-17 06:35 we'll fix it, no worries 2010-12-17 06:35 wolfspraul, the colors are sort of reversed 2010-12-17 06:35 always? 2010-12-17 06:35 they're not mirror reversed, so black -> white 2010-12-17 06:35 it's more like what happens when you try to run on a different color depth 2010-12-17 06:36 and only in certain hinge positions 2010-12-17 06:36 and not always, but there's about 50% chance of this occuring when you open the case and move with the hinge 2010-12-17 06:36 first thing would be to try to reseat the fpc cable on the mainboard side 2010-12-17 06:39 my nanonote is still pristine, i wish i had skills to fiddle with it a bit 2010-12-17 06:39 like, to install that serial console chip i got from wpwrak via rafa 2010-12-17 06:40 unfortunatelly certain people forgot to take soldering tools with them for the jlime meeting, so they weren't able to install it into my nn ;P 2010-12-17 06:52 zear: yeah. real pity that one. 2010-12-17 06:52 i'd love to play with the serial console, but as long as i don't find someone with hardcore soldering skills, that won't happen :( 2010-12-17 06:53 zear: here's your chance to become a hardcore soldering man yourself ;-) 2010-12-17 06:54 nah, i already toasted my pc by resoldering a broken gamepad's cable and plugging it to the usb port 2010-12-17 06:54 i don't want to experiment with soldering anymore :D 2010-12-17 06:54 zear: naw, don't worry. it's easy - and wolfgang likes to sell more bens ;-) 2010-12-17 06:55 ;D 2010-12-17 06:55 only if he accepts 100 ubuntu 5.04 cds as currency :) 2010-12-17 06:56 i once ordered 212 of them, but managed to giveaway only 112 2010-12-17 07:00 ah, the tragedy of the commons :) 2010-12-17 07:01 this was back in 2006 or something, people weren't used to linux yet 2010-12-17 07:02 we live in very different timescales, it seems ;-) 2010-12-17 07:02 if you had written 1996, maybe ... 2010-12-17 07:02 ;P 2010-12-17 07:03 well, back then there were no netbooks and linux wasn't popular on mobile phones 2010-12-17 07:04 now most of the people i talk to heard of linux and are interested in getting free printed cds 2010-12-17 07:09 how does canonical get money, btw? 2010-12-17 07:10 in the firefox, in ubuntu, they put "client=ubuntu" in the google requests. 2010-12-17 07:10 shuttleworth is also a multimilionare 2010-12-17 07:11 viric: that's all? 2010-12-17 07:11 zear: yeah, but this won't last undefinitely (except maybe through the magic of "financial instruments") 2010-12-17 07:11 no idea :) 2010-12-17 07:13 and why did he create canonical as a commercial company, if the objective is to operate at a loss? 2010-12-17 07:13 lekernel, well, he was the second space tourist, if he's still a millionaire after that, he must have a nice money flow 2010-12-17 07:13 a non-profit organization would have been more appropriate 2010-12-17 07:15 well, afaik he got all of it by selling thawte to verisign 2010-12-17 07:15 that was a huge shot of cash, not really a flow 2010-12-17 07:39 Paid developers power the Linux kernel: http://news.cnet.com/8301-13846_3-20024219-62.html  (old news) 2010-12-17 07:45 andres-calderon: like openbsd's paid developers 2010-12-17 07:45 is it? :) 2010-12-17 07:47 viric: I like to get paid for doing what I like. 2010-12-17 07:49 I refer to the FBI related funds :) 2010-12-17 07:49 http://permalink.gmane.org/gmane.os.openbsd.tech/22557 2010-12-17 07:53 viric: maybe andres would like to work for the FBI. well, CIA in his case. i'm sure they're recruiting ;) 2010-12-17 07:53 viric: wow 2010-12-17 07:54 ok ive been looking for hours and i can not find a mico sd wifi card anywere, if anyone knows were i could buy one of these and could point me in the write direction it would be nice 2010-12-17 07:56 wpwrak: jeje 2010-12-17 07:57 That risk will always exist in open source SW model. But, we just can  imagine the nice collection of  backdoors, troyan, etc in the most popular closed OS 2010-12-17 07:59 the big brother also write code. 2010-12-17 08:01 [commit] Adam Wang: Add alias names for some parts http://qi-hw.com/p/mmone-jtag-serial-cable/d222b3f 2010-12-17 08:03 excellent, Adam is committing :-) 2010-12-17 08:03 andres-calderon: we need to jump into the kicad files too! :-) 2010-12-17 08:04 lekernel: if IIRC canonical offers IT linux services like red hat and others.. so they admin servers, do virtualization solutions, etc.. Nothing special I would say, the same like red hat, suse, ibm, hp.. etc etc.. If you ask them to put a pet shop for you they will do 2010-12-17 08:04 I was slowed down by some work on snapshots and server rescue stuff, but it's almost done now, then back to more the stuff at the surface... 2010-12-17 08:04 ah, yeah 2010-12-17 12:51 if i want remove or move files, later sync with git, should i do care of soemthing? 2010-12-17 12:52 or just git add as usual and he will realize new folder and deleted files? 2010-12-17 12:52 s/he/it 2010-12-17 13:12 git rm  and  git mv   ? 2010-12-17 13:13 ahhh ;-) 2010-12-17 13:15 i'm a dumb with git :( 2010-12-17 14:24 hi 2010-12-17 14:27 ...30s? 2010-12-17 14:28 ADHD ;-) 2010-12-17 14:32 wonders if jlime has as much trouble with their menu system as openwrt has with gmenu2x ... 2010-12-17 14:32 i dont think so wpwrak 2010-12-17 14:32 well it run on X :) 2010-12-17 14:32 Xfdev** 2010-12-17 14:33 is at home today :) 2010-12-17 14:34 well comparative is not fair 2010-12-17 14:34 matchbox is not a menu 2010-12-17 14:35 and gmenu2x want to be more that a menu ;) 2010-12-17 14:35 well, "launcher" 2010-12-17 14:36 ah yes 2010-12-17 14:36 there seem to be a heck of a lot of very basic issues with gmenu2x. well, some may be just the result of an attempt to optimize for the last byte ... 2010-12-17 14:37 6Mb in ram is too much, for just a wallpeper and some icons 2010-12-17 14:38 may be i wallpaper fault ;) 2010-12-17 14:38 s/i/is 2010-12-17 14:39 Oh look what i found http://wiki.openmoko.org/wiki/Launcher 2010-12-17 14:41 "It features events notification too" ... "It is aimed at FSO framework" ... probably has some nasty dependencies 2010-12-17 14:43 :/ 2010-12-17 14:49 things get simpler when you elminate Xilinx dependent cores :) 2010-12-17 14:49 s/core/features 2010-12-17 14:49 talking about sram > buffer used on SIE shared bus 2010-12-17 14:50 portable is good :) 2010-12-17 14:50 yeah 2010-12-17 14:50 I learn that from milkymist code :) 2010-12-17 14:50 learnt* 2010-12-17 14:52 whoa it sinthetized at first try :), let see still working 2010-12-17 15:04 what's that burnt smell ? (-:C 2010-12-17 15:08 please join #qi-hardware 2010-12-17 15:08 oops 2010-12-17 15:08 wait wait not yet ;) 2010-12-17 15:08 wpwrak met Jay7 2010-12-17 15:08 morning ppl :) 2010-12-17 15:08 from kexecboot.org 2010-12-17 15:08 devel* right? 2010-12-17 15:09 lead devel ;) 2010-12-17 15:09 and single seems atm :( 2010-12-17 15:09 i just think you should met as i read lots of times abot kexec here from wpwrak  :) 2010-12-17 15:09 I've seen something like from qi people :) 2010-12-17 15:09 hi Jay7 ! ah yes, i love kexec :) 2010-12-17 15:09 but there are a LOT of kexec-based shell loaders :) 2010-12-17 15:09 Btw Jay7 are you aware of Ben Nanonote, thats what we need the bootloader 2010-12-17 15:10 s/bootloader/lancuher 2010-12-17 15:10 sorry 2010-12-17 15:10 kristianpaul: even more 2010-12-17 15:10 I got nanonote from CELF to port kexecboot there :) 2010-12-17 15:10 Jay7 also point me this http://labs.o-hand.com/psplash/ 2010-12-17 15:10 as part of proposed work 2010-12-17 15:10 Jay7: ahh !! 2010-12-17 15:10 You already suscribed in the list? 2010-12-17 15:10 still in my todo queue.. I hope this will happens around christmas holidays 2010-12-17 15:11 kristianpaul: qi's one? 2010-12-17 15:11 did you tell this before, will be neat if you do 2010-12-17 15:11 Jay7: yup 2010-12-17 15:11 no, point me :) 2010-12-17 15:12 Jay7: http://en.qi-hardware.com/wiki/Main_Page <--  Discussion List - developers and users Please fill Signup 2010-12-17 15:12 ok, mom 2010-12-17 15:15 done 2010-12-17 15:16 good :) 2010-12-17 15:16 Btw do you have screenshots of psplash ? 2010-12-17 15:17 Jay7: when i asked for app lanucher how kexecboot fits that question? 2010-12-17 15:17 kristianpaul: hm.. any of angstrom images have psplash running :) 2010-12-17 15:18 oh let me see 2010-12-17 15:18 kristianpaul: kexecboot is C program that scans available partitions on available medias, builds FB menu and allows to select one to boot from 2010-12-17 15:18 wpwrak: not burned out, but i'm getting some not expected readins, i may missed timing with my implementation of Read-only ram :) 2010-12-17 15:18 then kexec is launched 2010-12-17 15:18 so.. there is all code you need :) 2010-12-17 15:19 fb menu + executing code 2010-12-17 15:19 but fb code is changing.. I'm refactoring it slowly 2010-12-17 15:20 a screenshot would indeed be nice 2010-12-17 15:20 here is our git: http://git.linuxtogo.org/?p=groups/kexecboot/kexecboot.git;a=summary 2010-12-17 15:20 http://picasaweb.google.com/yuri.bushmelev/Kexecboot?feat=directlink 2010-12-17 15:20 here are some 2010-12-17 15:21 latest is old mockup, now we have other outlook 2010-12-17 15:21 sorry, have no screenshots of new UI 2010-12-17 15:21 I should do some for site 2010-12-17 15:22 thanks ! looks nice ! 2010-12-17 15:22 looks good 2010-12-17 15:22 new UI is even better ;) 2010-12-17 15:22 And is avalible for nanonote as well? :D 2010-12-17 15:22 it should be 2010-12-17 15:22 I've just not tried 2010-12-17 15:22 thanks !! 2010-12-17 15:23 kewl. i guess it tool some inspirations from the PS3 version ? as far as i remember, they were the first (several years ago) 2010-12-17 15:23 You can write to qi list 2010-12-17 15:23 it even was compiled last time iirc 2010-12-17 15:23 i'm sure you'll get beta testers (including me) 2010-12-17 15:23 s/tool/took/ 2010-12-17 15:23 wpwrak: thesing (Thomas Kunze iirc) is original developer 2010-12-17 15:24 may be it was inspired by PS3 something :) 2010-12-17 15:24 but kexecboot was written almost from scratch (except FB code was taken from psplash) 2010-12-17 15:25 now I've changed most part of that code to do UI faster 2010-12-17 15:25 but I have at least one bug there :) 2010-12-17 15:26 kristianpaul: I should try to run it on nanonote at least before :) 2010-12-17 15:26 Please :) 2010-12-17 15:26 well.. I'll try as soon as possible 2010-12-17 15:27 kristianpaul: what was your original problem about UI? 2010-12-17 15:27 some launcher for what? 2010-12-17 15:27 Currently owrt is used on default nanonote image 2010-12-17 15:28 inittab lanuch an app called gmenu2x, originally taken from dingox 2010-12-17 15:28 other xbusrt based device 2010-12-17 15:28 but gmenu2x well have some issues, one i'm afraid as i realized is that uses 6Mb of memory 2010-12-17 15:29 wich is a  LOT i think 2010-12-17 15:30 As far i know one of the nanonote sofware goals is fast boot 2010-12-17 15:30 that cold be achieve 2010-12-17 15:30 1: removing uboot and replace it by kexec 2010-12-17 15:31 2: replace current app launcher for one lighter and faster to run, 2010-12-17 15:31 the last one will be nice if support wallpaper and icons for each apps 2010-12-17 15:31 kristianpaul: before 1, you need some simple first-stage loader 2010-12-17 15:31 thats the original problem Jay7 2010-12-17 15:32 wpwrak: true 2010-12-17 15:32 kristianpaul: why do you think that 6MB is a lot?.. which applications you want to run which needs those 6MB of ram+free ram? 2010-12-17 15:32 zrafa: 6 MB is almost 20% of your memory :) 2010-12-17 15:32 wpwrak: yes, I know 2010-12-17 15:33 wpwrak: I want to know which applications people want to run using the ram 2010-12-17 15:33 OpenOffice, of course ;-) 2010-12-17 15:33 well.. 2010-12-17 15:33 I read all the time : it is slow and it eats a lot of ram.. but nobody seems to use the ram 2010-12-17 15:33 which something more than ls, top, moc, vim 2010-12-17 15:34 with something* 2010-12-17 15:34 i saw someone mention allocation failures. was that with emacs ? 2010-12-17 15:34 zrafa: because is ~21% from our 28M ram memory :/ 2010-12-17 15:34 kristianpaul: ?? 2010-12-17 15:34 I can create some form of laucher from kexecboot 2010-12-17 15:34 it should be easy enough 2010-12-17 15:34 zrafa: wpwrak already told that, i dint notice it :) 2010-12-17 15:34 but I can start only from 1-5 Jan 2010-12-17 15:34 kristianpaul: and what wpwrak said does not answer the question 2010-12-17 15:35 so if you need something before - do it yourself ;) 2010-12-17 15:35 the main question is which application users want to run to use the whole ram 2010-12-17 15:35 i was afraid for that answer Jay7 ;-) 2010-12-17 15:36 we can use kexecboot as second-stage loader to run kernel from any available media 2010-12-17 15:36 Jay7: We thanks your help when you can :) 2010-12-17 15:36 then run some tool based on it to run apps 2010-12-17 15:36 interface will be almost the same :) 2010-12-17 15:37 kristianpaul: if Qi can pay me for that work, I'll do it faster ;) 2010-12-17 15:37 wpwrak: (first stage) i was thiking a reduced/cuted/hacked uboot code.. 2010-12-17 15:37 wpwrak: one answer could be : users want to run 1000 ls at the same time, 50 tops and 100 vim 2010-12-17 15:37 first stage loader should just load kernel from NAND 2010-12-17 15:38 all other thing will be done by kexecboot 2010-12-17 15:38 Jay7: (pay) dont know, but as if you can help us later will be nice, all we here are unpaid :) 2010-12-17 15:38 from qi 2010-12-17 15:38 kristianpaul: well, np :) 2010-12-17 15:38 i meant 2010-12-17 15:38 it was (semi-)joke :) 2010-12-17 15:38 "I will not but that house, the extra room is small".. okey, now tell me: "who will use that extra room?".. mmehhh.. "nobody.. but I will not buy that house, the extra room is small" 2010-12-17 15:39 :P 2010-12-17 15:39 zrafa: well i dont care too much for ram, but if i can get my menu faster that now, i will be happy guy  (and others as well i think, endusers??? :)) 2010-12-17 15:39 so, I'll add this channel to znc and will hang here 2010-12-17 15:40 Wellcome then :) 2010-12-17 15:40 my working timezone is like CET :) 2010-12-17 15:40 Jay7: i'm adding #oe too to my irssi 2010-12-17 15:40 so, feel free to contact me :) 2010-12-17 15:41 zrafa: naw, uselessly wasting memory is always bad. the sooner or later, there will be something that fails because of it. remember "640 kB is enough" ? :) 2010-12-17 15:42 kristianpaul: you can look at boot.cfg sample and try to imagine some config for apps launcher 2010-12-17 15:42 kristianpaul: (reduced u-boot) naw, u-boot is a mess. don't go there. i think lars already has some small loader. 2010-12-17 15:42 wpwrak: ok 2010-12-17 15:42 just to have it before 2010-12-17 15:42 http://git.linuxtogo.org/?p=groups/kexecboot/kexecboot.git;a=blob;f=boot.cfg;h=6ec262f47a9d5d4a98445324debb089fc4ba332c;hb=HEAD 2010-12-17 15:43 wpwrak: yes, I know, but I would not be so worry about those 6mb gmenu uses.. if nobody is going to use those 6MB yet I would try to complain with other kind of stuff :) 2010-12-17 15:43 multiple sections is needed here.. but I'll do the same for multiple kernels 2010-12-17 15:49 Jay7: hey looks  simple setup (from what i can read) 2010-12-17 15:49 yes, it is 2010-12-17 15:50 bad thing that current implementation is only for single kernel (single boot.cfg) per partition 2010-12-17 15:50 but multiple kernels per partitions (i.e. multiple sections inside boot.cfg) is also proposed work for CELF 2010-12-17 15:50 so I'll do this anyway.. 2010-12-17 17:02 hmm the forth oriented CPU (J1), interesting aprouch, when talking about CPU oriented to certain programing language 2010-12-17 17:02 now wich program language to choose :) ? 2010-12-17 17:03 argg i still getting randon reading, i think i missed a verilog wire 2010-12-17 17:07 i'd pick a cpu optimized for C ;-) 2010-12-17 17:09 FPGA can beat current CPU in that way i think, plus the reconfiguration stuff 2010-12-17 17:09 you, switch from C to verilog :) 2010-12-17 17:10 well is not the same aprocuh (procedural vs cocurrent) 2010-12-17 17:10 actually, once synthesis is opened. i wonder how long it would take for someone to come up with a C compiler that programs the FPGA 2010-12-17 17:11 I was pointing, ie, from you pick, C is the assemlby language 2010-12-17 17:11 but is hard, you dint program a FPGA at all 2010-12-17 17:11 just load a hardware model 2010-12-17 17:12 i still been hardware some how, you still needing the sofware logic glue 2010-12-17 17:12 mostly because the *soft* part 2010-12-17 17:13 think of compilers for vector processors. they also need to split into vectorized and scalar part. 2010-12-17 17:13 Nice times are coming  :) 2010-12-17 17:13 some cpus also have some very low-level run-time core. e.g., look at the propeller. 2010-12-17 17:13 (or just any microcode) 2010-12-17 17:15 (vector processors) yummy :) 2010-12-17 17:18 parallax propeller, looks interesting, i dint knew it of it 2010-12-17 17:43 it's an interesting concept. probably not really worth the trouble for real-life applications, though. 2010-12-17 17:55 kristianpaul: I remember some java-bytecode-compatible processors 2010-12-17 17:55 and I'm sure we can see .net-compatible in the future 2010-12-17 18:00 are the java cpus any commercial success ? 2010-12-17 18:02 is java a sucess? 2010-12-17 18:02 no, are not  (cpu) 2010-12-17 18:03 commercially talking is hard to define sucess from techincal point of view 2010-12-17 18:04 wpwrak: seems no :) 2010-12-17 18:08 Jay7: then i wouldn't hold my breath when it comes to .net cpus ;-) 2010-12-17 18:08 well.. there will be microsoft behind ;) 2010-12-17 18:08 kristianpaul: i suspect that, by the time the things are mature enough, regular cpus will have caught up with them :) 2010-12-17 18:09 Jay7: well, M$ have a long history of "strategic" projects that are epic commercial disasters ;-) 2010-12-17 18:09 e.g., Windows HPC anyone ? ;-) 2010-12-17 18:09 I hope this will one of that :) 2010-12-17 18:10 i don't see how it could fail to be ;-) 2010-12-17 18:32 hi folks 2010-12-17 18:33 a question, what's the meaning of "qi" on the room's name? 2010-12-17 18:49 Madridman: it's about open source/copyleft hardware: http://en.qi-hardware.com/wiki/Main_Page 2010-12-17 18:50 wolfgang: small detail - if you go to the wiki, there's no direct way to find out where the "qi" comes from :-) 2010-12-17 18:51 thanks 2010-12-17 18:52 wolfgang: fun fact: www.sharism.cc -> the latest "community news" are from april 29. i must have hallucinated all the more recent ones ;-) 2010-12-17 19:13 Madridman: Qi is Chinese  related, look: https://secure.wikimedia.org/wikipedia/en/wiki/Qi 2010-12-17 19:41 he now i read zeros, well better than randon :) 2010-12-17 19:43 sounds a bit like my misadventures with the latest atusb board :-( the beast was happy enough to begin its first programming, but then failed the checksum and stubbornly refused any further updates 2010-12-17 19:47 voltages look good. soldering looks good. no shorts i can see. very mysterious. 2010-12-17 19:50 current consumption is perfect 2010-12-17 19:50 mcu issues?.. 2010-12-17 19:51 could be broken, yes. strange, though. 2010-12-17 19:52 programmer works perfectly with a different kind of board. so it's really this critter that's having issues. 2010-12-17 19:54 not a good day so far. the first board i made had an irreparable soldering problem (a solder bridge that didn't go away, no matter what i tried) 2010-12-17 19:56 then i found that the ben had a ubifs corruption that prevented it from booting. so, a little detour with a full reflash.  (reflash_ben.sh works nicely, particularly when used in combination with idbg :) 2010-12-17 19:56 and now the damn mcu won't flash :-( 2010-12-17 21:03 he 2010-12-17 21:03 i was reading an int, so make sense now ! 2010-12-17 21:03 schar* 2010-12-17 21:07 good ! 2010-12-17 21:07 now, time to dump to a file, lets see what option is better 2010-12-17 21:12 which are the options ? 2010-12-17 21:15 as this need to be fast i tought: 2010-12-17 21:15 1: allocate some Mb of memory and dump to it, when finish , write to disk 2010-12-17 21:16 that's what i'd do 2010-12-17 21:16 2: write to disk, wich is kind slow i think, i tough use memory flash 10:8, but tahts no recommended in SIE 2010-12-17 21:17 2: no way :) it also adds stray delays and such, which will probably make you overrun your buffer 2010-12-17 21:17 oops :) 2010-12-17 21:17 do you have an indication for buffer overruns ? 2010-12-17 21:17 ah... 2010-12-17 21:17 no 2010-12-17 21:18 maybe add one. otherwise, you'll have no end of trouble with strangely incorrect data 2010-12-17 21:18 ok lets see how to do it :), 2010-12-17 21:19 btw are you using some indication for buffer overruns in atusd code? :D 2010-12-17 21:19 worse yet, even if your data is perfectly good but something else is wrong, you'll always suspect the data :) 2010-12-17 21:20 right now, a new frame would just overwrite the old one 2010-12-17 21:20 ah no dump 2010-12-17 21:21 you may consider one ! ;-) 2010-12-17 21:21 there's the possibility of disabling the receiver until the frame has been received, though 2010-12-17 21:21 dump ? 2010-12-17 21:21 data dump? 2010-12-17 21:22 ( disabling the receiver) is that a question for me? 2010-12-17 21:22 hmm ? when the chip has received the frame, it generates an interrupt. then i transfer the frame. if i'm too slow and a new frame is being received, it may overwrite the first one 2010-12-17 21:22 ah ok, nv last question :) 2010-12-17 21:22 no, talking about atusd/atusb 2010-12-17 21:22 yes yes 2010-12-17 21:23 i'll probably let the microcontroller do the first response to interrupts on atusb. otherwise, it'll just sit around lazily and get fat ;-) 2010-12-17 21:24 on atusd, there's no mcu, do it's the ben who has to react 2010-12-17 21:24 s/do/so/ 2010-12-17 21:30 after all i can have a decent 8bit IO in SIE plus 13bits of addresing (multiplexing), just deleting the sram and adding some case staments 2010-12-17 21:33 simple :) 2010-12-17 21:38 whatever you say ;-) 2010-12-17 21:40 between SIE and FPGA i mean—* 2010-12-17 21:40 s/SIE/Xbusrt 2010-12-17 21:40 that's the part i understood. the rest sounds mysterious ;-) 2010-12-17 21:40 hahah 2010-12-17 21:57 kristianpaul: how do you like my latest soldering accessory ? http://downloads.qi-hardware.com/people/werner/tmp/hotplate.jpg 2010-12-17 21:59 one day I report all of this to homeland security 2010-12-17 22:00 ;-)) 2010-12-17 22:03 for completeness, here's today's opponent: http://downloads.qi-hardware.com/people/werner/tmp/nemesis.jpg 2010-12-17 22:05 Great ! 2010-12-17 22:05 adam will want one :-) 2010-12-17 22:06 You have nice workspace bte, (white) all here is brown :) 2010-12-17 22:06 s/bte/btw 2010-12-17 22:07 wow there are really tiny resistors in nemesis 2010-12-17 22:07 s/resistors/pasive components 2010-12-17 22:08 do you glue it some way before reflow? 2010-12-17 22:08 s/do/did 2010-12-17 22:09 oh i can see a Ben naked board on the right botton corner :) 2010-12-17 22:09 (workspace) all DIY :) 2010-12-17 22:10 (reflow) soldered them manually, no reflow 2010-12-17 22:10 so how helped the hotplate? 2010-12-17 22:11 if i did reflow, i wouldn't need to glue them. they don't move around too easily. but i think i need to make a stencil for proper reflow. just depositing solder paste with a syringe doesn't produce nice results. 2010-12-17 22:11 ah ok 2010-12-17 22:12 is nemesis the bad-mcu guy? 2010-12-17 22:13 the hot plate heats the board to about 100 C. so when for melting the solder, i only need to overcome a temperature difference of about 70 K, not 150 K. for simple things, this doesn't make a big difference. but in this case, i have a lot of ground and a gazillion vias connecting both sides. the ground planes suck away the heat. so there are several trouble spots where a 270 C iron is difficult or insufficient. 2010-12-17 22:14 why nemesis have that green-like wire, is not enought the pcb atenna? 2010-12-17 22:14 with the hot plate, these problems disppear :) 2010-12-17 22:14 (wire) this is for the scope, to monitor the voltage :) 2010-12-17 22:15 (nemesis) yup, that's the problem board 2010-12-17 22:15 i'm now making two new boards. i hope they'll end up being better. 2010-12-17 22:17 wolfspraul: i should actually integrate the iron into the table :) and while i'm at it, add also an area with under the table lighting, for aligning transfer sheets and such. ah well, so many ideas, so little time :) 2010-12-17 22:17 (270) wow which component needs that ? 2010-12-17 22:18 (integrate the iron into the table) good idea 2010-12-17 22:18 270 C is my regular setting with lead-free solder. not sure how hot the thing really gets. the tip is quite worn, so it's probably colder. 2010-12-17 22:21 why do you use lead-free solder? 2010-12-17 22:22 less hot to apply no? 2010-12-17 22:23 wolfspraul: to give customs no excuse ;-) 2010-12-17 22:23 ahh 2010-12-17 22:23 kristianpaul: no, it's actually very inconvenient to work with. needs more heat and generally doesn't handle as well as leaded solder. 2010-12-17 22:25 manual rework is always exempt from RoHS 2010-12-17 22:25 just fyi 2010-12-17 22:25 kristianpaul: mechanical properties after soldering probably aren't so great either. e.g., i think it's more brittle. so things may break off under stress. 2010-12-17 22:25 there are many exceptions, but a simple claim of 'manual rework' is already enough 2010-12-17 22:25 wolfspraul: also without the "re" in "rework" ? 2010-12-17 22:26 I'm not aware of any country that would really go after every gram of lead. it's quite political, and the important idea is 'self-enforcement' and to start with the big amounts somewhere, the stuff that is handled by the machines... 2010-12-17 22:26 interesting exemption. they're nicer than i would have thought. 2010-12-17 22:27 well I'm also not aware of anybody who would use that excuse and keep their machines running with leaded solder while claiming the rework thing. 2010-12-17 22:27 maybe people are more honest than thought, sometimes 2010-12-17 22:27 but for that reason, alsmost all rework people use leaded solder still, because apart from you I have never heard anyone saying lead-free is easier to work with 2010-12-17 22:28 well, customs have to process the package either way, so if they feel bored, they may cause trouble. also, they don't know if this is really a unique piece or whether there's a million more to come, each shipped individually (like bens :) 2010-12-17 22:28 (ah sorry, I misread you) 2010-12-17 22:28 you also say it "doesn't handle as well as leaded solder" 2010-12-17 22:28 yeah. it's a pain. 2010-12-17 22:28 no I doubt there is any such check ever 2010-12-17 22:28 you think too complicated again :-) 2010-12-17 22:29 RoHS is a great success, it was very effective. but that was _because_ the system was setup as a 'self enforcement' system, and with generous exceptions. 2010-12-17 22:29 well, based on my experience with argentine customs, i expect the very worst 2010-12-17 22:29 ... and sometimes still get nasty surprises 2010-12-17 22:29 oh really? 2010-12-17 22:30 I highly doubt they will go after lead, but OK. every rework station in all of Asia uses leaded solder. 2010-12-17 22:30 kristianpaul: well, i didn't have issues with RoHS so far. but they had me twice with "seguridad electrica" 2010-12-17 22:30 that means there is a good chance, < 10 %, that somewhere on every piece of electronic that are a few spots of leaded solder 2010-12-17 22:30 kristianpaul: and they also hinted once that "PCB" could be a banned chemical 2010-12-17 22:31 ahh¡¡ (PCB) 2010-12-17 22:31 thats the top 2010-12-17 22:31 amazing 2010-12-17 22:32 wpwrak: so bottom line, in my experience you can safely use leaded solder for your work, and still be rohs compliant. 2010-12-17 22:32 there are also exceptions for machine cleaning and such 2010-12-17 22:32 kristianpaul: so what would happen is that they'd hold it at customs. then i'd have to go to the airport, spend about half a day before i can hear what the issue is. then i could of course explain that pcb is the board and not the banned chemical. but they can of course simply reject this explanation. 2010-12-17 22:32 so when a factory switches between leaded and lead-free runs, they don't have to go crazy over the cleaning thing 2010-12-17 22:33 wpwrak: (reject this explanation.) reasons? technically talking 2010-12-17 22:33 kristianpaul: then i could either take a certainly complex and expensive bureaucratic appeal process, or find out how much of a financial incentive they would require for changing their mind 2010-12-17 22:33 ha 2010-12-17 22:33 kristianpaul: no technical reasons. it's a plausible explanation. of course they know there's nothing wrong. but this way, they can improve their personal income. 2010-12-17 22:34 i hope i dont have to pass for that in colombia 2010-12-17 22:34 in my experience colombian customs is good 2010-12-17 22:34 (they can improve their personal income) Wellcome to South America :) !! 2010-12-17 22:35 wolfspraul: (cleaning) nice. all this sounds amazingly reasonable. what happened ? did they exclude the politicians when they made those regulations ? :) 2010-12-17 22:35 kristianpaul: yeah ... 2010-12-17 22:35 :/ 2010-12-17 22:36 kristianpaul: argentine customs are probably among the worst 2010-12-17 22:36 well, i've heard good things said about russians/ex-USSR customs ... 2010-12-17 22:37 wpwrak: I think they understood they are dealing with mass production. 2010-12-17 22:37 so even if you pull one out, of 10,000, and you find something, then what? 2010-12-17 22:38 so a top-down, fines, punishments, regulations to the last detail approach simply would not have worked 2010-12-17 22:38 still, amazingly reasonable :) 2010-12-17 22:38 it needs to start on the other side, where the big machines are being operated 2010-12-17 22:38 focus on the x tons of solder first, not on reworks or all sorts of other small stuff happening in a real factory 2010-12-17 22:39 of course that removes the ability to deduct too much from an individual piece in front of you 2010-12-17 22:39 oh, a system that has lots of traps is good for political purposes. e.g., you can enforce it mainly against unwanted foreign competitors 2010-12-17 22:39 but that was not the point, the point was to move mass-production away from leaded solder 2010-12-17 22:39 collateral advantages :) 2010-12-17 22:39 so even if 1 piece in front of you is full of lead, that doesn't mean much in terms of RoHS, at least at the beginning 2010-12-17 22:40 so anyway 2010-12-17 22:40 you can relax about that in your home station, although the heating plate of course is very cool 2010-12-17 22:40 ah 2010-12-17 22:40 :-) 2010-12-17 22:40 hot 2010-12-17 22:40 it also helps with large chips, or when you have to work with hot air 2010-12-17 22:41 it helps to avoid cracks in the vias inside pcbs 2010-12-17 22:41 i probably need it anyway even with lead. the problem there are the vast ground planes. 2010-12-17 22:41 sure, it's good 2010-12-17 22:41 I was just surprised when you said you use lead-free solder for reworks. 2010-12-17 22:41 that sounds like additional trouble/risk for no good 2010-12-17 22:41 nobody is doing that, afaik 2010-12-17 22:42 all my vias are hand-made. so they're a little special :) one advantage of the process is that they won't crack. (it's a solid wire) 2010-12-17 22:43 kewl 2010-12-17 22:43 welcomes back the 60/40 eutectic leaded solder :) 2010-12-17 22:43 I'll ask around a bit more... 2010-12-17 22:43 maybe some factories are proud to move to a 100% lead-free process? never heard of it though 2010-12-17 22:43 ah wikireader is awsome my mother really liked it :) (no trouble with classic keyboard) 2010-12-17 22:44 wolfspraul: of course, the dark side of my environmental footprint would then be all those heavily leaded counterweights ;-) 2010-12-17 22:44 wonders if tuxbrain did anything with them 2010-12-17 22:45 I need one 2010-12-17 22:45 my ben fall all the time.. 2010-12-17 22:48 i'm actually surprised that nobody seems to complain about this 2010-12-17 22:49 hmm may be they are taking it like a faeture? :) 2010-12-17 22:51 that could be an indicador of dailly use of it, on the desk 2010-12-17 22:51 wich  as pocket computer is hard to realize 2010-12-17 22:57 hmm. if you can make people believe this is a feature, then i think we need a nobel price for marketing, and you're the first to get it :) 2010-12-17 23:15 wpwrak: just googled a bit and what I said about manual reworks and RoHS may be wrong. 2010-12-17 23:16 a good reminder that I need to refresh my RoHS knowledge again, it seems to be constantly evolving (in general tightening) 2010-12-17 23:17 puts the 60/40 leaded solder back into the drawer :-( 2010-12-17 23:17 ha :-) relax... 2010-12-17 23:17 there are still many big fat exceptions 2010-12-17 23:18 it's a moving target 2010-12-17 23:18 of course the point is not to ever get more creative to define oneself into the exceptions 2010-12-17 23:18 good for customs. so they can spring surprises 2010-12-17 23:18 http://www.rohs.gov.uk/content.aspx?id=15 2010-12-17 23:18 most people I have seen that deal with rohs take it very seriously and professionally, it's quite nice actually 2010-12-17 23:19 on the enforcement side, there is little if any aggression, on the production side, there is little if any cutting corners 2010-12-17 23:19 the telecommunications industry seems to have been quite active, see exemption 7b for lead 2010-12-17 23:21 "Lead in solders for servers, storage and storage array systems, network infrastructure equipment for switching, signalling, transmission, and network management for telecommunications" 2010-12-17 23:21 yeah, pretty broad ;-) 2010-12-17 23:21 so who knows. I still think your manual reworks are totally safe, even with leaded solder. 2010-12-17 23:21 amazingly, no exceptions for automotive 2010-12-17 23:21 not reworks 2010-12-17 23:21 manual 'works' 2010-12-17 23:22 but I need to take this more serious again too, will dig next time I visit a manufacturer. 2010-12-17 23:22 maybe they are already further than I realize 2010-12-17 23:23 on that website (seems UK related), it says about enforcement "We will help those that are aiming to comply and pursue vigorously those that intend to flout compliance." 2010-12-17 23:28 repair of "new" (> july 2006) devices is also under the directive 2010-12-17 23:28 http://www.rohs.gov.uk/FAQs.aspx 2010-12-17 23:30 there's an exception for demonstration purposes, but the interpretation may be quite narrow, perhaps only for trade shows and such, not even general in-house evaluation 2010-12-17 23:35 well, it's probably okay: "Prototypes for experimentation may be used providing they are not made available on the EU market." 2010-12-17 23:36 the next paragraph is confusing, though 2010-12-17 23:38 "Ultimately only the courts can provide a definitive answer on the meaning of the Regulations," yeah :) 2010-12-17 23:38 we need wikilaws ! then anything with "weasel words" gets deleted ;-) 2010-12-17 23:39 from what I hear, rohs is not about customs trying to hunt down individual products 2010-12-17 23:39 that would be totally impossible given the complexity of it 2010-12-17 23:40 it's about authorities working with the industry 2010-12-17 23:40 also I think rohs will be tightened more, it's such a big success 2010-12-17 23:40 so more substances, processes, what not can be attached to it :-) 2010-12-17 23:42 wpwrak: what do you think about introducing datasheet pdf urls into boom? 2010-12-17 23:45 i think the feature per se is desirable. semanstics aren't trivial, though. 2010-12-17 23:45 for best effect, the data sheets would come from multiple sources, including distributors. 2010-12-17 23:46 si the digi-key database download would also try to access data sheets, and make them available for the respective digi-key part numbers 2010-12-17 23:46 [commit] Wolfgang Spraul: removed two generated png files, leaving svg originals http://qi-hw.com/p/xue/fb852f7 2010-12-17 23:46 got it, and sounds good. on the todo list then... 2010-12-17 23:47 yup 2010-12-17 23:48 there are several access paths. e.g., by component reference, a) for the "current" data, b) for historical data. 2010-12-17 23:48 (b) could be outside boom, e.g., just archive a snapshot when doing something with the data) 2010-12-17 23:49 then by item in an order 2010-12-17 23:50 and finally in a yet-to-be-written component browser that would interact with kicad when adding a component and its characteristics in the schematics (or editing, etc.) 2010-12-17 23:54 that's the one that would make carlos happy :)