#qi-hardware IRC log for Wednesday, 2011-06-22

wolfspraulwpwrak: did you see Harald's blog post about his legal fun with AVM and the GPL?01:19
wolfspraulyou must like this one: "rmmod proprietary_module" violates the copyright of the owner of proprietary_module :-)01:20
wolfspraulthat is indeed a whole new way to think about it...01:20
wolfspraulhttp://laforge.gnumonks.org/weblog/2011/06/21/#20110621-avm_cybits_court_hearing01:21
qi-bot[commit] Xiangfu Liu: libsdl-gfx: copy the missing .pc files, thanks Jiva http://qi-hw.com/p/openwrt-packages/51fc69f01:36
kristianpaul(rmmod) how they could.., that a so _void_ argument, well, thinking in pro of AVM,  i wonder if you can imponse that some how, in a extreme case by warranty void is module removed or something, same as when you root a phone..01:44
kristianpaulbut violate copyright, how come... :S01:45
wolfspraulwe see what happens. it's a nice self-referential argument. if I first claim that you have no license for my proprietary component, and then I claim that you also have no right to remove it, that's a nice one :-)01:46
wolfspraulit's in line with their lawyers saying that "avm provides all gpl sources so people can do whatever they like with the software, just not on our devices"01:47
wolfspraulbut of course I do understand their side, they will claim that a 3rd party messes with the integrity of their product, leave a lot of stuff in the GUI still saying 'avm', but changing functionality...01:48
wolfspraula lot of those things have never been thought through in earnest by free software folks, maybe because so few of them actually run a company :-)01:48
wolfspraulit's a nice way to point expensive customer support problems at your competitors...01:48
kristianpaul(modded GUI with avm), i see, thats a fair point01:50
wolfspraulfor copyleft hardware, I think we should design everything from day 1 so that it is very easy to re-brand the device including software under a new name01:50
wolfspraulactually I'm already doing that, removing unnecessary references to sharism, trying to pull brand names into fewer places so they can be renamed easily01:51
kristianpaulhum i still wondering where i can read sharism ;)01:51
wolfspraulbrand names and the use of trademark law arguments in legal disputes go against the ideas of the GPL and free software in some places. so I think best is to separate them clearly.01:52
kristianpaulindeed01:52
wolfspraulso anybody has the chance to either reuse a brand name, or make a new brand name. And whatever choice they make they then have to be able to hold up to trademark disputes.01:53
kristianpaulbut.. is not linux a trademark, so, how you could include modules/blobs with other trademarks and not deal later with it?, or do i miss the point here?01:57
wolfsprauldon't understand01:58
wolfspraulI think if you would take an AVM box, remove any references to AVM on the box, in any software GUI, etc., then AVM wouldn't care or even have started this legal case02:00
wolfspraulbut this other company and AVM are quite intertwined, my understanding is that they add certain features to the AVM box, but the entire experience of the box is still an 'AVM experience', and AVM doesn't like that.02:00
wolfspraulwhich I can understand02:00
kristianpaulthe copyright that AVM claim for the linux module then use code with trademark from then?02:01
kristianpaulah, okay02:01
kristianpauli see it now02:01
wolfspraulso now, as in many legal cases, they come up with whatever logic their lawyers can come up with to make their point02:01
wolfspraulI just specifically like the argument that 'rmmod module' violates the rights of the owner of the proprietary module. that's a good one :-)02:01
kristianpaulhe, thats a bit hard some times, imaging removing Link sys brading from my router that run openwrt if therically want to comercialize a product with a custom firmare :-)02:02
wolfspraulyou make removing your thing a violation of your thing. that way you can force whatever you want upon the other side. Now they only need to get the court to agree :-)02:02
kristianpaulafaik some buffalo routers ship/uses dd-wrt, i wonder what agreement they did..02:02
wolfspraulkristianpaul: yes exactly. If you go on to sell those 'linksys' routers under that brand name with modified firmware, sooner or later linksys will not accept it.02:03
wolfspraulwhether they can win the legal case I don't know02:03
wolfspraulthey will claim it's a whole system, where you may claim that the linksys box is just the hardware...02:03
kyakxMff: ping05:17
wpwrakwolfspraul: (saw it in the news, yes) sounds like a very tricky case. it may get decided on technicalities.06:57
DocScrutinizermoo07:22
DocScrutinizernever knew AVM is "on the dark side"07:23
wolfspraulDocScrutinizer: so what is Nokia's plan with the N9?07:36
DocScrutinizerhi wolfspraul 07:36
DocScrutinizerI don't know, really07:36
wolfspraulthey announce it and then?07:36
DocScrutinizerit's the stillborn concept from my PoV07:36
wolfspraulhow open is the OS compared to N900?07:37
wolfspraulcan you rebuild an entire image from scratch? how many binary blobs?07:37
DocScrutinizerlook, inofficial mantra for N900 always been "it's not a phone, it's a computer". For N9 things seem to have changed to "This is not a computer (or NIT), this is a me-too-Android"07:38
DocScrutinizerwolfspraul: I have no idea about how open this maemo-meego-harmattan chimera is07:39
DocScrutinizerobviously still a lot of blobs07:39
wolfspraulthe N9 software side/community is not connected to N900?07:40
wolfspraulI lost overview over all the twists and turns in their software...07:40
DocScrutinizer http://harmattan-dev.nokia.com/pool/harmattan-beta/non-free/07:40
wolfspraulwhat is the software continuity between N900 and N9?07:41
DocScrutinizerbasically none07:41
DocScrutinizerat least none defined or intended07:41
wolfspraulouch07:42
DocScrutinizerharmattan been called maemo6, while N900 is running fremantle M5, and N8x0 had diablo M407:42
wolfspraulthat looks like 50-100 binary blobs in the url you posted07:42
DocScrutinizerthere's not really any compatibility from M4 -> M5 -> M607:42
wolfspraulI see07:43
DocScrutinizerwolfspraul: I never even looked at that URL07:43
DocScrutinizerthen they decided M5 harmattan now has to become meego-harmattan07:43
DocScrutinizerwhich doesn't help things07:44
DocScrutinizererr M6 harmattan -> meego-harmattan07:44
DocScrutinizerintel is bitching "THIS IS NOT MEEGO!!!1!1!!!"07:44
DocScrutinizerlot of maemo community is moaning "this is way too much meego"07:45
DocScrutinizerand the "best" part of it all that *really* makes me throw up: aegis & security framework07:46
DocScrutinizerhttp://harmattan-dev.nokia.com/unstable/beta/Fremantle_Update7_vs_Harmattan_Beta_content_comparison.html07:48
DocScrutinizeraegis: http://www.slideshare.net/peterschneider/maemo-6-platform-security07:49
DocScrutinizerWAAAAAHH!! >:-((07:49
wolfspraulwell it will all be dead soon, but I'm wondering where to look for the best bits and pieces, if any, for future projects07:50
wolfspraulis any significant or interesting stuff going upstream anywhere, or manages to create a small community around itself?07:50
DocScrutinizerno, it's not BL-locked. You can choose "open mode" any time, you just have to accept an arbitrary number of core functions will cease to work then07:50
wolfspraulor is it all tied to the titanic?07:51
wolfspraulok but let's assume this will all be dead soon. all paid engineers let go or reassigned to wm.07:51
DocScrutinizergustloff07:51
wolfspraulwhich part can survive?07:51
DocScrutinizernot titanic07:51
wolfspraulare there any significant/interesting things that were developed as free software and can survive?07:52
DocScrutinizermaemo community can survive, on N900 carefully treated like a treasure07:52
wolfspraulwhich parts see the heaviest upstreaming efforts?07:52
wolfspraulis it possible to port maemo to n9?07:52
DocScrutinizershould, modulo the closed stuff mainly core apps like dialer, calendar, contacts07:53
DocScrutinizerbut then that's probably meego-harmattan in the end07:54
DocScrutinizersee URL above07:54
DocScrutinizercontent comparision07:54
DocScrutinizeronly common denominator seems to be Qt07:55
wolfspraulhmm07:56
DocScrutinizerand, surpise surprise, that's the main new SDK the ship with N907:56
wolfsprauldo you think the Maemo community can survive with Nokia corporate support/sponsorship totally gone?07:56
DocScrutinizerQML actually07:56
DocScrutinizeraiui07:56
DocScrutinizerI think they *could* but will bleed out til zombie state07:57
wolfspraulso N900 will proudly follow the FreeRunner?07:57
DocScrutinizeryep07:57
DocScrutinizerone big fsckng deja-vu07:57
DocScrutinizerevery single gory detail of it07:58
DocScrutinizermy dreamy hopes are on N950, as Nokia wouldn't have developed that device just to deliver 250 devel-devs to community. They must have plans to eventually market it08:00
wolfspraulthat's not the N9? yet another one?08:01
DocScrutinizerthis would open a perspective for new devices coming from Nokia so the whole linux thing isn't tagged with its own date of extinction, and also the device is attractive enough to keep maemo community alive08:01
DocScrutinizerhttp://storage3.static.itmages.ru/i/11/0621/h_1308650003_5628d0de58.jpeg08:02
DocScrutinizerthe device they actually have for contractors and community to develop on it for N9 yet to come08:03
DocScrutinizerfor a long time everybody thought this will be next device and N900 successor08:05
DocScrutinizerrumour has it they got CE cert problems, and also some yield problems or sth08:06
DocScrutinizerso can't sell it to mass market (yet?)08:06
wolfspraulI know you are in this for a long time, but for me it's too many twists and turns and renames and stuff. I just wait until it's all dead and then see what can be resurrected in new products :-)08:07
wolfspraulI bought the original N770 years ago. that was a good start. then it went into all sorts of directions, until today :-)08:07
DocScrutinizerI'm hoping to get one, by support of Nokia employees supporting my application for one of the 25008:07
wolfspraulneeds a phd to understand how it all connects together (or not)08:07
wolfspraulmaybe some pieces of reusable free software will survive08:08
DocScrutinizer(N770) yeah, Nokia really knows how to kick balls of their community and act like 3 stooges when it comes to marketing08:08
DocScrutinizer(reusable sw) not really much aiui08:09
wolfspraulyep08:09
wolfspraulexpensive lines of code :-)08:09
wolfspraulbut we take anything, right? even 100 lines that someone sunk 1 billion into writing... :-)08:09
DocScrutinizeryep. though you definitely want to talk to mickey about that, he's way better on that domain08:09
wolfspraulI have no specific plans, just wondering what happens and where reusable pieces might be.08:10
wolfspraulprimarily my starting point is the NanoNote, then add things to that08:10
DocScrutinizerhe already reused part of that intel phone stack08:10
wolfspraulso N950 has a keyboard, but N9 is touch-only, I guess08:10
DocScrutinizeryes08:11
DocScrutinizerN9 = capacitive mt with 848*480 AMOLED08:11
DocScrutinizern950 is classical, but same resolution08:12
Last message repeated 1 time(s).08:12
DocScrutinizeroops08:12
DocScrutinizerhttp://www.developer.nokia.com/dp?uri=http://sw.nokia.com/id/3744886f-69c1-4544-8ad3-72b352b4a832/Nokia_N950_OneClickFlashers_Release_Notes08:12
DocScrutinizern9 vs n95008:12
DocScrutinizerthe most annoying part in all this embedded stuff right now is: it won't earn me a breakfast, which I'm going to have now. so ttyl08:19
wolfspraulinteresting doc about N9 vs N950 differences - thanks08:25
kyakjow_laptop: may i ask you to have a look at https://dev.openwrt.org/ticket/9573 ?10:56
kyaki think it's worth accepting in openwrt10:56
jow_laptopok11:00
jow_laptopdone11:03
kyakthanks!11:10
wolfsprauljow_laptop: yeah, awesome! thanks! that was quick...11:10
qi-bot[commit] hauke: firmware-utils: fix build on big endian systems http://qi-hw.com/p/openwrt-xburst/bf48bee11:55
qi-bot[commit] jow: [include] cmake.mk: fix bogus values for FIND_ROOT_PATH_MODE_*; kept plplot from compiling (#9573) http://qi-hw.com/p/openwrt-xburst/0fba51d11:55
qi-bot[commit] Mirko Vogt: add <http://downloads.qi-hardware.com/software/mirror-openwrt-sources/> http://qi-hw.com/p/openwrt-xburst/7fdf51f11:55
qi-bot[commit] Xiangfu Liu: optimize for ben nanonote http://qi-hw.com/p/openwrt-xburst/10b92a711:55
qi-bot[commit] Xiangfu Liu: [xburst] Improve mounttime http://qi-hw.com/p/openwrt-xburst/aaa1f5211:55
qi-bot[commit] Xiangfu Liu: nanonote optimize http://qi-hw.com/p/openwrt-xburst/47bf3ac11:55
qi-bot[commit] Xiangfu Liu:  Add-gfortran-compiler-support-to-the-toolchain http://qi-hw.com/p/openwrt-xburst/5d89d8a11:55
qi-bot[commit] kyak: add kernel patch for setfont2 http://qi-hw.com/p/openwrt-xburst/df3fa8b11:55
qi-bot[commit] Xiangfu Liu: optimize for ben nanonote http://qi-hw.com/p/openwrt-xburst/f15aaa511:55
qi-bot[commit] kyak: config-2.6.37: enable battery, disable RNDIS http://qi-hw.com/p/openwrt-xburst/341513611:55
qi-bot[commit] kyak: patches-2.6.37: support for Ben NAND partitioning http://qi-hw.com/p/openwrt-xburst/e4c52ef11:55
qi-bot[commit] David K├╝hling: linux kernel: add CONFIG_PROC_PAGE_MONITOR=y to allow for clean user-space DMA http://qi-hw.com/p/openwrt-xburst/ce9677e11:55
qi-bot[commit] kyak: config-2.6.37: enable options needed for keymouse http://qi-hw.com/p/openwrt-xburst/9e2522611:55
qi-bot[commit] kyak: trunk: fix kernel keymap for VolUp/Down and Del http://qi-hw.com/p/openwrt-xburst/0cc25e611:55
qi-bot[commit] kyak: trunk: build sound modules in kernel http://qi-hw.com/p/openwrt-xburst/b0931b811:55
qi-bot[commit] kyak: trunk: add ks7010 support patch http://qi-hw.com/p/openwrt-xburst/fa3d46911:55
qi-bot[commit] Xiangfu Liu: base-files, move it to openwrt-package/nanonote-files http://qi-hw.com/p/openwrt-xburst/bdec59d11:55
qi-bot[commit] kyak: uboot-xburst: don't install empty dir http://qi-hw.com/p/openwrt-xburst/9a2787111:55
qi-bot[commit] kyak: Disable syslogd and klogd http://qi-hw.com/p/openwrt-xburst/9f1d7f111:55
qi-bot[commit] Xiangfu Liu: uboot-xburst: update to 2010.06 http://qi-hw.com/p/openwrt-xburst/a2997e211:55
DocScrutinizeris there anything like a DNS-ping tool? To evaluate answer/RTT delay of my DNS?11:58
GNUtoohmmm I guess dig or nslookup don't count as ping tool?12:00
DocScrutinizeresp they don't do multiple lookups of different addresses, and time that12:05
DocScrutinizerI got web browsing slow as geotectonics, and I wonder is it caused by laggy servers not delivering content, or is it my DNS delaying each resolve query for the usually dozens of advert banners etc12:07
DocScrutinizerhard to tell apart from watching browser fetch a webpage12:08
DocScrutinizerhttp://video.google.com/videoplay?docid=-5115609628556940516&q=trusted+computing#  took like minutes to start12:08
DocScrutinizerwhich would mean it's probably general thruput / bandwidth issue12:09
DocScrutinizerOTOH ct.de was fast like hell12:09
GNUtoofor me the anti trusted computing video is fast12:19
GNUtoobut I've add-block12:19
GNUtooand I've my own dns too12:19
DocScrutinizerI guess sth is wrong with my DSL12:30
DocScrutinizerthough even the mere view of the TPM video was completely strange, as if Google had a new page layout or dunno what12:31
whitequarksaw some news about nokia releasing developer variants of n913:09
whitequarkis that a sort of agony?13:09
B_Lizzardheh13:10
B_LizzardMost likely an uncompleted version of that scrapped Meego phone with the keyboard13:10
B_LizzardSo they fix whatever hardware issue it might've had and release it as a "developer" phone because obviously the software isn't up to snuff.13:11
mthDocScrutinizer: some IPv6 misconfigurations can cause DNS to be really slow (takes some time before it falls back to IPv4)13:12
DocScrutinizermth: aah, maybe telecom did some tests recently13:13
DocScrutinizerI also had strange downtimes of several minutes on reconnect13:13
DocScrutinizermth: thanks13:14
DocScrutinizerwhitequark: B_Lizzard: see backscroll13:15
B_LizzardDocScrutinizer, wasn't in13:34
B_LizzardIn any case...13:34
qi-botThe build was successfull, see images here: http://fidelio.qi-hardware.com/~xiangfu/compile-log/openwrt-xburst.full_system-06212011-1026/13:47
`antonio`Hi, I am trying to flash my image in my nanonote using the reflash_ben.sh script, but I have some problems: after the script has finish, when I boot it the screen becomes blank  13:47
`antonio`is that normal ?13:47
`antonio`when i boot it there are some lines, and it says "starting kernel..." after that the screen becomes black13:48
wolfspraul`antonio`: not normal :-)13:53
wolfsprauldo you have the latest xburst-tools and reflash_ben.sh installed?13:53
`antonio`yes13:54
`antonio` I am just recompiling the toolchain from scratch now13:54
`antonio`following the wiki13:54
wolfspraulrecompiling the toolchain? wow13:54
wolfspraulthat shouldn't be needed simply for reflashing your Ben13:55
wolfsprauloh wait, you have created your own image?13:55
`antonio`yes13:55
wolfspraulahh. got it now. well then there's probably a number of things that could have gone wrong.13:55
wolfspraulunfortunately I haven't built my own image from scratch in a long time, so others may know better what to look out for13:56
`antonio`are there some specific packages or libraries I need to compile ? 13:56
`antonio`ok13:56
wolfspraulyour boot fails very early13:57
wolfspraul'starting kernel', I guess that means at least u-boot successfully loaded the kernel, then it executes it but that's it, it doesn't even start13:57
wolfspraulotherwise the kernel would display more messages, the next choking point would be to mount the rootfs, but you don't even get there it seems13:57
`antonio`yeh 13:58
`antonio`so basically it's more a toolchain issue there must be something missing 13:59
`antonio`is there a wiki for the packages required in the toolchain? 14:00
wolfspraulnot sure how that can affect kernel compilation14:03
wolfspraulwhich openwrt config file do you use as a starting point?14:03
`antonio`http://downloads.qi-hardware.com/software/images/NanoNote/Ben/latest/feeds.conf14:07
`antonio`this you mean?14:07
`antonio`I am trying follow this http://en.qi-hardware.com/wiki/Building_Software_Image#Feeds14:12
kyak`antonio`: can you give more details about "blank screen"?14:18
kyakdoes it react to buttons? what about Ctrl+Alt+F1/F2? did you try pinging/sshing into it?14:19
`antonio`I tryed both but nothing14:20
`antonio`let me reflash it again14:20
kyakmake sure you use your kernel and rootfs images with reflash_ben.sh14:23
`antonio`sure 14:24
stefan_schmidtwpwrak: ping14:57
wpwrakstefan_schmidt: moo :)15:05
DocScrutinizerwow, stefan_schmidt - HI!15:07
stefan_schmidtDocScrutinizer: hi, I _know_ you looked like a bot (wrt infobot name change)15:11
stefan_schmidtwpwrak: hi15:11
DocScrutinizerhehe15:11
stefan_schmidtwpwrak: who is Richard, the sub skeleton driver guy?15:11
stefan_schmidtwpwrak: I'm getting frustrated with my other ieee802154 device which makes me more interested in getting a driver for atusb ready :)15:12
DocScrutinizerlast time I did this with infobot in channel under name of Guest3464533, infobot grabbed the nickname DocScrutinizer immediately in reply ;-P15:12
wpwrakstefan_schmidt: richard = Richard Sharpe15:13
wpwrakstefan_schmidt: (other device) hehe ;-)15:13
stefan_schmidtwpwrak: is he here in IRC?15:14
stefan_schmidtwpwrak: Don't wanted to start a usb driver from scratch just because of my time pressure :)15:14
DocScrutinizerooh I forgot to mention, N9 has NFC, whatever they use15:14
DocScrutinizermight be 802.15.4?15:14
wpwrakstefan_schmidt: naw, how only showed up here once or twice15:15
wpwrakstefan_schmidt: how bad is the time pressure ? i've finished the basics of what's needed to get a proof of concept atusb driver to work. there are some races, though.15:15
wpwrakstefan_schmidt: my next steps are to change the build process of the atusb fimrmware a bit, because i can no longer have identical object files for boot and application (too much overhead in the application's usb core, making the boot loader exceed its 4 kB)15:16
wpwrakstefan_schmidt: next, an atben driver that registers as SPI. that would also be an example for structuring the atusb driver15:17
wpwrakstefan_schmidt: do you have any atbens ? or only atusb ?15:17
wpwrakDocScrutinizer: NFC sounds more like RFID15:18
wpwrakDocScrutinizer: IEEE 802.15.4 has 10-100x the desired range ;-)15:18
DocScrutinizer:nod:15:19
DocScrutinizernfc about nfc15:20
DocScrutinizerall I know is there are at least 2 different standards15:20
wpwrakgot some really nice spam: "McDonalds invites you to The Free Dinner Day"15:21
DocScrutinizerso dunno what they actually mean when calling it NFC nowadays15:21
wpwrakwith a voucher in the form of a .zip and of course a .exe inside. i think we can all guess what the .exe would do :)15:22
stefan_schmidtsorry, working chat in the other window.15:22
stefan_schmidtwpwrak: time pressure: already some weeks behind diploma schedule :)15:22
wolfspraulhas anybody heard from Tuxbrain how atben and atusb sales are going?15:22
wolfspraulhe is totally silent even though I ordered some boards from him :-)15:23
stefan_schmidtwpwrak: So I would like to test any atusb driver you might come up with. Giving you a hand on fixing would be fine15:23
wpwrakthe funny thing is, if they had actually attached some real-looking voucher, people may have stormed macdonalds, causing no end of trouble :)15:23
stefan_schmidtwpwrak: only atusb devices15:23
stefan_schmidtI don't have a nanonote at all15:23
wpwrakstefan_schmidt: (weeks later) aw :(   well, the sooner you fall behind, the more time you have to catch up ... :)15:23
stefan_schmidtwolfspraul: well, with my six atusb I ordered 5% of the stock of these already. ;)15:23
stefan_schmidtwpwrak: heh15:24
wpwrakstefan_schmidt: (atusb) all i have is richard's atusb skeleton. he said he'd work on it this week.15:25
stefan_schmidtwpwrak: woould you be able to send me this with the other changes you may have?15:25
wpwrakwolfspraul: he's in semi-vanished mode again. he popped up briefly 1-3 days ago, but didn't say anything about sales15:25
stefan_schmidtwpwrak: the problem is a bit that neither of my devices works at the low level so I can start my actual work. :)15:25
stefan_schmidtwpwrak: (work on it) great15:26
wpwrakstefan_schmidt: i've forwarded you his skeleton15:27
wpwrakstefan_schmidt: the problem he mentioned in his mail was a misunderstood return value. so his code did the right thing.15:27
stefan_schmidtwpwrak: thanks a lot15:27
stefan_schmidtwpwrak: going to cinema now (social stuff you know) and will have a look after this15:28
wpwrakstefan_schmidt: i don't have any changes on top of it. all my stuff is in git anyway.15:28
wpwrakstefan_schmidt: enjoy ! ;-)15:29
qi-bot[commit] Werner Almesberger: at86rf230: RX vs. TX synchronization, further corrections http://qi-hw.com/p/qi-kernel/fd8fe5315:49
methril_workwpwrak, when did you arrive to Porto Alegre?16:18
wpwrakmethril: i will arrive on the 28th16:39
wpwrak(weather and volcano willing :)16:39
methril_workwpwrak, i'm going to Porto Alegre the 29th18:00
methril_workaround 19:00 h in the airport18:00
rjeffrieshere we go: a hack that might connect a real keyboard to Ben Nanonote over Werner's atben + a gadget in the middle.18:29
rjeffrieshttp://dangerousprototypes.com/2011/06/22/wireless-networked-at-keyboard/18:29
dvdklooks like openwrt-trunk C++ compiler is broken wrt. exceptions20:32
dvdkdoing a throw() results in my programs getting SIGABRT20:32
dvdkfound this open ticket at openwrt.org:20:33
dvdkhttps://dev.openwrt.org/ticket/918520:33
dvdkany ideas?20:33
bartbesas the thing mentions that happens if you link against stdc++ and then run with uclibc++20:38
wpwrakmethril: great ! i'll have my talk the next day (the 30th). that may be an easy way to catch me.20:38
dvdkdoesn't seem to be the prob.20:39
dvdkldd ./exptest20:39
dvdklibstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x2ad48000)20:39
dvdkl..]20:39
wpwrakmethril: otherwise, we'll have to synchronize electronically. hmm, have to prepare my laptop for travel ...20:45
dvdktrying to rebuild my toolchain with --enable-sjlj-exceptions21:07
methril_workwpwrak, i'm going to be there only the 29th21:13
methril_workthen i've t ogo back home (work)21:14
wpwrakmethril: oh :-( a busy man21:16
methril_workwpwrak, unfortunately i have no license to stay on Porto Alegre :(21:17
methril_worki'm really sad, because it was a good opportunity to know some Qi-people ;)21:17
wpwrakrjeffries: seems you've found what you're looking for :)21:32
rjeffrieswpwrak well, it is a kludge however22:14
wpwrakrjeffries: of course it is. what did you expect - an iKeyboard, hand-carved from a block of magnesium ? ;-)22:16
kristianpaulwpwrak: what you understand with binary reference clock  ?22:41
kristianpaulactually " frequency plan is based on a binary reference clock rather than the GPS chip clock."22:41
wpwrakkristianpaul: hmm, do you have more context ?22:49
kristianpaulwpwrak: do you have sige4162 evb/IC datasheet?22:50
kristianpaulbut22:50
kristianpaul"The IF filter is centred at 2.556 MHz. The 1575.42 MHz GPS RF input is mixed down to a 2.556 MHz IF by a 1572.864 MHz LO (96*16.384 MHz). A complex mix to baseband is made with an internal NCO. The data is decimated and filtered by 4 to give 2.048 MSPS data, and serialized."22:50
kristianpauli think it may add a bit more context22:51
kristianpaulwpwrak: i'm _finaklly_porting namuru correlator to milkymist, but this sige chip is not the others22:51
kristianpauli still having doubts about the samping clock value..22:51
kristianpaulwich is this case seems to be not the same as other old sige IC and other frontends, in wich asmpling clock is synchronized wiht the GPS signal22:53
kristianpaulfor now i guessed sampling freq is same as sampling rate, so then 2.048Mhz22:54
wpwrakkristianpaul: (data sheet) it seems i lost it :(22:57
wpwrakkristianpaul: (data sheet) well, all of the sige ones. so i don't even know which ones i had22:57
wpwrak(sampling freq/rate) sounds synonymous, yes22:58
freakazoid0223em23:05
stefan_schmidtwpwrak: still around?23:57
Action: stefan_schmidt never got behind wpwrak sleeping schedule.23:57
--- Thu Jun 23 201100:00

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