IRC log for #neo900 on 20150930

01:21.16*** join/#neo900 infobot (ibot@69-58-76-73.ut.vivintwireless.net)
01:21.16*** topic/#neo900 is http://neo900.org | CCCAMP15 lightning talks at http://neo900.org/stuff/cccamp15/ - major: http://neo900.org/stuff/cccamp15/ccc2015talk/neo900-wpwrak_CCC2015.webm | conversations are logged to http://infobot.rikers.org/%23neo900/ and http://irclog.whitequark.org/neo900
01:21.16*** mode/#neo900 [+v infobot] by ChanServ
01:37.13*** join/#neo900 tomeff (~tomeff@ip-78-102-111-158.net.upcbroadband.cz)
01:59.49*** join/#neo900 Defiant (erik@78.54.180.116)
03:32.03DocScrutinizer05http://wstaw.org/m/2015/09/30/plasma-desktopJc9051.png
03:37.13DocScrutinizer05http://www.silabs.com/Support Documents/TechnicalDocs/AN332.pdf
03:37.54DocScrutinizer05I wonder (not really ;D ) what FSF would think of that
03:39.15OksanaThat changable firmware should have source code openly available to the people using the firmware, and they should be able to verify that their firmware is indeed compiled from this source code?
03:39.17DocScrutinizer05the chip has *) embedded firmware that *) can't get updated *) nevertheless it may receive 'blob' non-FOSS software, but that's not mandatory
03:40.37DocScrutinizer05Oksana: the firmware in chip can't even get read out, so how would you confirm the firmware in chip is what your sourcecode (non-existent) suggests it is?
03:42.10DocScrutinizer05and Nota Bene: the firmware is NOT changeable
03:42.36OksanaIf you trust it with flashing process, flash it with completely new component image?
03:42.51DocScrutinizer05it just can get temporarily overridden by a patch blob
03:43.04DocScrutinizer05you cannot flash that thing!
03:43.41OksanaPatch can be used ... to download an entirely new component image?
03:44.06DocScrutinizer05you can upload encrypted signed firmware patches into the volatile RAM, so they override the fixed firmware in device
03:45.34DocScrutinizer05and yes, that could as well be a complete new firmware image (which is ~15kB size then)
03:45.46OksanaOkay, so you would need to re-upload at each start-up, and somehow you would need to be sure of contents of encrypted signed firmware patch and the image it downloads?
03:46.16DocScrutinizer05err yes?
03:46.59Oksanais not sure if image is inside-the-patch or downloaded-from-elsewhere-by-the-patch . And not sure if it is possible to verify how source code matches-or-not encrypted-signed-binary
03:47.46DocScrutinizer05err, how would a chip "download from elsewhere"?
03:48.13OksanaOkay, so large-patch=completely-new-component-image
03:48.18DocScrutinizer05via FM? from WWleetHaxor?
03:49.52DocScrutinizer05http://wstaw.org/m/2015/09/30/plasma-desktopvr9051.png
03:58.01DocScrutinizer05btw this is probably the most common scheme found on those little controllers - be it Ambient Light Sensor or accelerometer or whatever. Just most of them don't even mention the register function, those registers are simply listed as "internal" and not supposed to get used by user. Some chip manufs warn to never write to those registers since that may damage the chip irrecoverably. Very few actually document the patch feature
04:00.14DocScrutinizer05FSF approach regarding peripheral subsystems is just to simplistic
04:01.05DocScrutinizer05in times where virtually everything (sure every chip with a moderate or higher complexity) has a tiny MCU inside
04:07.05DocScrutinizer05every NIC in your PC has a firmware. Your HDD, your DVD drive, your USB controller, heck even your power supply probably has (an arbitrary number >=1 of) MCUs embedded into chips embedded into the device, and each of those little MCUs has firmware
04:08.15DocScrutinizer05just usually you don't even know _that_ they have any MCU and firmware, you only can guess
04:09.39DocScrutinizer05neither do you know if that firmware could get updated, until the manuf is kind enough to document that update feature
04:10.31DocScrutinizer05which is the moment where FSF forbids to use the chip since then it's obvious that it has a firmware and no public source for it
04:11.25DocScrutinizer05result: not what FSF hopes for, but rather the opposite - no manuf will mention the firmware update feature so they don't get involved into futile debates with FSF
04:15.08OksanaWell, it would be nice if the "inner" documents with details on patches and updates were easily available. To be fair, I haven't ever tried to disassembly a power supply and take a look at its chips, and the firmware for them
04:16.45DocScrutinizer05sure it would be nice. However for many companies that's more than 50% of their vital assets which they don't want to disclose to anybody, particularly not to competitors
04:19.07DocScrutinizer05see SiLabs and their FM chip. It even has patents on the inner structure. Now you can bet they made those patents in a way that doesn't give away too much on how they actually implemented that stuff, and likewise they wouldn't want to publish detailed specs on the chip's internals. However such details are mandatory for anybody to understand the firmware sourcecode
04:23.17OksanaTear apart?
04:23.28DocScrutinizer05maybe they even developed their own proprietary programming language to write the firmware for the chip. So what would you do with the sourcecode when ypu don't have the language "educational books" nor the detailed specifications of each single internal register in the chip. And those internal registers in turn don't make much sense when you don't have detailed manual for the DSP and other custom made function blocks they control
04:27.29DocScrutinizer05lemme give you an example:  http://paste.opensuse.org/78917648 would be part of) the "sourcecode" for a very tiny customer configurable chip we're going to use for simmux in Neo900. Now if there wasn't a publicly available tool to make use of that "sourcecode", what would you do with it?
04:28.58DocScrutinizer05the binary from such sourcecode is a 1024bit dump you upload/flash to the chip
04:30.10DocScrutinizer05honestly, hardware a tad different a world than SOFTWARE which is what Free SOFTWARE Foundation is all about
04:34.07OksanaFirst, I would need to read from XML into a good variable. Second, I would need to decipher what these values are to be used for? This thing looks like it described a GUI, something with pictures and text. To control power from CPU to modem, maybe? Just a wild guess
04:34.59DocScrutinizer05yes, exactly. almost. To control power from modem, CPU, NFC to SIM
04:35.17DocScrutinizer05however that sourceode gives you nothing
04:36.05DocScrutinizer05you need the kanguage definition too, or the actual compiler. Then FSF would require the compiler also is FOSS which it clearly isn't, and so on ad infinitum
04:37.59DocScrutinizer05exactly same with our EDA/ECAD eagle. Yes, we may eventually publish the project files, however they are worthless for FSF since the 'compiler' (eagle) is not FOSS
04:38.31OksanaLanguage definition may allow to write a compiler, or interpreter into different language. As long as you already know architecture of the chip (MCU?) for which you need to compile. And I am guessing that compiler has to fit the final binary into the memory-limits of the chip. | Does ECAD have a language definition?
04:40.10DocScrutinizer05nobody is going to ever publish such language definition for the project files of closed-source tools. Not even M$ did, for .doc format
04:42.49OksanaAnd for docx? How does OpenOffice read-write them? | Arduino uses Eagle, how does FSF live with that? | And yes, I do not see anything open-source working with Eagle files
04:43.09DocScrutinizer05go ask any write to please provide the "sourcecode" for their text they published. I.E. the .doc file. Then you realize that it's worthless without M$ word to process it, then you ask for a "language definition" so you could write a OpenOffice so you could actually use the 'source code' to modify it... OK we all know .doc has been RE'ed and there already exists an OpenOffice which mostly knows how to handle .doc files, though not always
04:43.27DocScrutinizer05any writer*
04:44.56OksanaSome writers do provide source code. But when they care about that, they provide tex. I was actually wondering if publishers could keep the "source code" for a century-or-so, to publish when work goes into public domain
04:44.57DocScrutinizer05anyway this is an age old problem
04:47.36DocScrutinizer05and FSF won't solve it with their approach of  "don't tell us you used M$ word to produce that text on that page of paper! Let us believe you panted it by hand, dot by dot, or we will refuse the read that paper until you hand us a FOSS sourcecode"
04:51.34OksanaKiCad: There are also tools to help with importing components from other EDA applications, for instance EAGLE. Eagle 6.xx PCB files can be directly imported to KiCad. What's your version of Eagle?
04:54.35DocScrutinizer05this changes with release of new versions
04:57.07DocScrutinizer05anyway that's all irrelevant since I'm not willing to let FSF define which wristwatch I may use to check it's time to stop work and go to sleep now. Based on the assertion that such wrist watch might have non-FOSS firmware
04:57.21DocScrutinizer05n8
04:57.27OksanaGood night ;-)
04:58.43DocScrutinizer05when no linux code getting executed on it, FSF please keep your fingers off that subsystem
05:01.57OksanaHeh... /looking at Pebble Time and wondering about firmware in it/
05:44.28OksanaNice... https://github.com/upverter/schematic-file-converter Eagle <-> KiCad, and other formats too
05:59.20*** join/#neo900 ploopkazoo (~ruukasu@unaffiliated/ruukasu)
07:02.39*** join/#neo900 tomeff (~tomeff@ip-89-176-75-234.net.upcbroadband.cz)
07:23.52*** join/#neo900 bencoh (~bencoh@unaffiliated/bencoh/x-184637)
07:30.18*** join/#neo900 MonkeyofDoom (~~Monkeyof@159.63.167.146)
07:42.28*** join/#neo900 jonsger (~Thunderbi@2a02:8070:791:2f00:f451:e80:944c:46fa)
09:17.37*** join/#neo900 sparetire_ (~sparetire@unaffiliated/sparetire)
09:22.44*** join/#neo900 hoijui (~hoijui@ipservice-092-208-205-098.092.208.pools.vodafone-ip.de)
09:47.31*** join/#neo900 vakkov (~vakkov@s3n104.brunel.ac.uk)
10:12.16*** join/#neo900 vakkov (~vakkov@ic-s221n26.brunel.ac.uk)
10:26.14*** join/#neo900 che1 (~che@2001:a61:1120:1601:213:e8ff:fe9b:fb3f)
11:06.46*** join/#neo900 qwazix (~qwazix@Maemo/community/ex-council/qwazix)
11:07.13*** join/#neo900 Oksana (~chatzilla@Maemo/community/ex-council/Wikiwide)
11:17.10*** join/#neo900 jonsger (~Thunderbi@2a02:8070:791:2f00:f451:e80:944c:46fa)
12:25.15*** join/#neo900 jonsger (~Thunderbi@2a02:8070:791:2f00:f451:e80:944c:46fa)
12:27.07enychrrms
12:27.32*** join/#neo900 SylvieLorxu (~TheLastPr@dhcp-077-251-165-191.chello.nl)
13:25.25*** join/#neo900 sdfdsdsdfdsfsdfs (2bfb9d9d@gateway/web/freenode/ip.43.251.157.157)
13:25.30sdfdsdsdfdsfsdfshello all
13:25.45sdfdsdsdfdsfsdfswhat is the release date to the neo900?
13:26.22sdfdsdsdfdsfsdfsDocScrutinizer05: dos1 wpwrak, u guys here?
13:26.53sdfdsdsdfdsfsdfsalso, in the microblog you guys said pre-ordering now if i want to be in the first batch?
13:27.27sdfdsdsdfdsfsdfsdoes that means if i dont preorder now i wont be able order a neo900 when you actually start sending them out?
13:31.03DocScrutinizer05hi! unclear. Right now we are about to source the first 250 N900 devices, and it's not warranted that we can get more with a second order
13:32.04DocScrutinizer05release date estimated is still Q1/2016
13:32.25DocScrutinizer05we're optimists :-)
13:33.49sdfdsdsdfdsfsdfsDocScrutinizer05: do you already have 250 preorders? is it too late for me?
13:34.02DocScrutinizer05it's not too late
13:34.17sdfdsdsdfdsfsdfshow many left?
13:34.18DocScrutinizer05but about time
13:34.43sdfdsdsdfdsfsdfsim not sure ill be able to source the cash now it may take me a few weeks
13:34.45sdfdsdsdfdsfsdfsam i fucked?
13:34.54DocScrutinizer05well, some 10 of dirst batch are still without 'owner'
13:34.58DocScrutinizer05first*
13:35.20sdfdsdsdfdsfsdfsoh no
13:35.29sdfdsdsdfdsfsdfsso they'll be gone by next week probably
13:35.32sdfdsdsdfdsfsdfs:(
13:35.33sdfdsdsdfdsfsdfs:'(
13:35.44DocScrutinizer05no, actually recently not that many orders
13:36.27MonkeyofDoomoh, right
13:36.36MonkeyofDoomI don't know if I ever did the voucher thing or whatnot
13:36.44MonkeyofDoomhow does that work...
13:37.51sdfdsdsdfdsfsdfsDocScrutinizer05: if i place preorder now are you guys guaranteeing u will deliver final product and won't disappear with all our money?
13:37.57DocScrutinizer05place your preorder, insert voucher code
13:38.17MonkeyofDoommm
13:38.34DocScrutinizer05yes, I didn't find a black hole large enough to swallow me yet :-)
13:39.02DocScrutinizer05sorry, busy. BBL
13:39.57*** join/#neo900 asddsfsdadsd (2bfb9d9d@gateway/web/freenode/ip.43.251.157.157)
13:40.10asddsfsdadsdhey DocScrutinizer05 its me sdssfdsddsds i got disconnected
13:40.39asddsfsdadsdi was asking is there a guarantee by u guys to deliver final product or give us our money back?
13:41.00asddsfsdadsdor is it like "oh well we'll try but if money disappears sry nothing can do about it"
13:41.04edwinhttp://irclog.whitequark.org/neo900/2015-09-30#14169018;
13:41.39edwinasddsfsdadsd: see the irc logs there for the time you were disconnected
13:42.19asddsfsdadsdedwin: he didnt answer my question
13:50.20MonkeyofDoomDocScrutinizer05: I can't seem to select a state in the address editor :x
13:50.31MonkeyofDoomit worked when signing up for the account, but I wanted to add a billing address
13:51.02MonkeyofDoomafter picking "united states", the state field doesn't show up until you try to submit the form; once you do submit, the only item in the state drop-down is "-"
13:53.53DocScrutinizer05asddsfsdadsd: [2015-09-30 Wed 15:38:34] <DocScrutinizer05> yes, I didn't find a black hole large enough to swallow me yet :-)
13:54.11DocScrutinizer05MonkeyofDoom: please check JS support in your browser, try different browser
13:55.02asddsfsdadsdDocScrutinizer05: but wait isnt a black hole a singularity?
13:55.14asddsfsdadsdDocScrutinizer05: or are you talking about the event horizon?
13:55.35asddsfsdadsdDocScrutinizer05: how could you not find black hole with big enough event horizon literally any black hole would do
13:55.41DocScrutinizer05I'm talking about vanishing which I seem incapable to do even from IRC
13:56.09DocScrutinizer05though I have some shopping to do before closing hours
13:56.23MonkeyofDoomeh, managed to get it working via poking at form values...
13:56.25asddsfsdadsdDocScrutinizer05: well yeah thats what they all say b4 they run off with all ur money
13:56.47jake42asddsfsdadsd: there is a "terms of service" you have to agree before placing your order. Read and understand :-)
13:56.47asddsfsdadsdDocScrutinizer05: is there any legal binding u have to not disappear?
13:56.54DocScrutinizer05sorry, I can't hand you a pledge
13:57.26asddsfsdadsdjake42: oh so in ToS it states he is obliged to give me money back if he doesnt deliver?
13:57.38DocScrutinizer05sure, I have 300 customers who will get out their pitchforks and chase me to court
13:58.07asddsfsdadsdDocScrutinizer05: as a privacy expert im sure u know how to disappear
13:58.14DocScrutinizer05and I have a legit company registered at Handelsregister
13:58.53DocScrutinizer05sorry, really busy. 'funny' conversation but I have to run
13:59.25asddsfsdadsdi dont like his tone seems too cheeky
13:59.35asddsfsdadsdlike hes employing reverse psychology
13:59.45DocScrutinizer05when you feel unconfortable, please do not order
14:00.03asddsfsdadsdok ill order
14:01.40*** join/#neo900 asddsfsdadsdf (2bfb9d9d@gateway/web/freenode/ip.43.251.157.157)
14:01.51asddsfsdadsdfhey does anyone here actually know him personally?
14:01.58asddsfsdadsdflike where he lives and such?
14:02.41jake42asddsfsdadsdf: doc lives where his company lives (see address on neo900.org)
14:03.10asddsfsdadsdfoh i see
14:03.15asddsfsdadsdfok i guess
14:03.44jake42have visited him once in a bar near by, he's a nice guy
14:04.54*** join/#neo900 asddsfsdadsdfs (2bfb9d9d@gateway/web/freenode/ip.43.251.157.157)
14:05.08asddsfsdadsdfsall con artists seem like nice guys, jake42
14:05.20asddsfsdadsdfsdid u catch a glimpse of his soul?
14:05.54jake42asddsfsdadsdfs: you're right
14:06.01EndZdftt.
14:06.01jake42how do I know :-)
14:06.29asddsfsdadsdfsjake42: when u looked into his eyes what did u see?
14:06.41asddsfsdadsdfsjake42: did u see greed?
14:07.36asddsfsdadsdfsjake42: and what was he doing in the bar? was he scamming people with bar bets?
14:08.24jake42certainly not, though if he would be a con, I wouldn't know :-)
14:08.56asddsfsdadsdfshmmm
14:08.58jake42asddsfsdadsdfs: mostly drinking and talking
14:09.35asddsfsdadsdfswe should dig up his background
14:09.45asddsfsdadsdfssee where he studied high school
14:09.53asddsfsdadsdfsask his classmates about his personality
14:09.57*** join/#neo900 louisdk (~louisdk@static-5-103-130-65.seas-nve.net)
14:10.07asddsfsdadsdfsanyone got any info on which high school he finished?
14:12.15asddsfsdadsdfssrsly am i the first one who asked for some background on this guy?
14:12.47asddsfsdadsdfsi wud imagine there would already be a detailed file on him prepared for people like me asking about him
14:13.02asddsfsdadsdfswe are literally giving him thousands of euros
14:13.07jake42what would info about his background change?
14:13.33jake42if he wanted to run with the money he would have done it already
14:13.48asddsfsdadsdfsno he's waiting for the final moment
14:13.54asddsfsdadsdfsraking in as much as he can
14:13.54jake42which would be?
14:14.01MonkeyofDoomopen source hardware is not exactly a "get rich quick" scheme...
14:14.14MonkeyofDoomyou'd be more effective by taking a job at some engineering company
14:14.32asddsfsdadsdfs1. open up website with a picture of nokia n900 and list cool features
14:14.44asddsfsdadsdfs2. reach out to privacy crowd
14:14.49asddsfsdadsdfs3. get popular in privacy crowd
14:14.55asddsfsdadsdfs4. ask for preorders
14:15.00DocScrutinizer05http://talk.maemo.org/showthread.php?t=91142
14:15.04asddsfsdadsdfs5. say if not enough preorders than no product
14:15.32asddsfsdadsdfs6. wait until last possible moment and u got hundreds of preorders
14:15.54asddsfsdadsdfs7. disappear with over 100k euro
14:16.02asddsfsdadsdfsfucking brilliant if u ask me
14:16.34DocScrutinizer05dude, If I had worked in industry instead of doing this damn project, I had made twice as much in the same time
14:16.35jake42no, the project also is spending money on progressing
14:16.58MonkeyofDoom100k euro... now you can retire and live the good life!
14:17.03MonkeyofDoom:|
14:17.08asddsfsdadsdfswell
14:17.14jake42and you can watch the progress by yourself
14:17.18MonkeyofDoom^
14:17.21DocScrutinizer05please don't order!!
14:17.35asddsfsdadsdfsDocScrutinizer05: no stop with ur reverse psychology im going to order
14:18.20DocScrutinizer05I hope I can reject that order. I got other stuff to do than to babysit worried customers
14:18.45DocScrutinizer05I got a device to develop and produce
14:18.57asddsfsdadsdfsDocScrutinizer05: no pls i need that phone
14:19.00asddsfsdadsdfspls dont reject
14:20.10asddsfsdadsdfsr u data mining me?
14:20.15asddsfsdadsdfspls stop DocScrutinizer05
14:20.42asddsfsdadsdfsu r violating my privacy
14:22.06asddsfsdadsdfsDocScrutinizer05: wtf stop pinging me
14:22.33asddsfsdadsdfsdude ur going against ur own principles
14:22.33*** mode/#neo900 [+o DocScrutinizer05] by ChanServ
14:22.48*** mode/#neo900 [+q asddsfsdadsdfs!*@*] by DocScrutinizer05
14:22.59Wizzupthx
14:23.02DocScrutinizer05yw
14:23.07*** mode/#neo900 [-o DocScrutinizer05] by ChanServ
14:23.24DocScrutinizer05actually doing nothing, sent a CTCP VERSION *once*
14:23.54EndZclassic IRC trolls.
14:24.24DocScrutinizer05now for real: BBL
14:28.54*** join/#neo900 lobito (~lobito@190.177.227.184)
14:30.45*** join/#neo900 itbaron (~kvirc@a88-115-15-207.elisa-laajakaista.fi)
14:31.05DocScrutinizer05btw I noticed it's hard to find the TOS since there's no link, so here they are: https://my.neo900.org/index.php?id_cms=3&controller=cms&id_lang=1&content_only=1
15:18.14*** join/#neo900 paulk-collins (~paulk@gagarine.paulk.fr)
15:45.32*** join/#neo900 tomeff (~tomeff@ip-78-102-111-158.net.upcbroadband.cz)
15:57.49*** join/#neo900 louisdk (~louisdk@static-5-103-130-65.seas-nve.net)
16:16.03*** join/#neo900 modem (~modem@fsf/member/modem)
16:23.15useretailhey, can anyone tell default $PATH for root?
16:26.11*** join/#neo900 Pali (~pali@Maemo/community/contributor/Pali)
16:38.35*** join/#neo900 vakkov (~vakkov@s3n104.brunel.ac.uk)
17:28.25*** join/#neo900 Mentalysion (~quassel@ipservice-092-209-014-213.092.209.pools.vodafone-ip.de)
17:48.54*** join/#neo900 xes (~xes@unaffiliated/xes)
17:56.08*** join/#neo900 paulk-collins (~paulk@gagarine.paulk.fr)
18:00.59*** join/#neo900 vakkov (~vakkov@ic-s221n26.brunel.ac.uk)
18:44.11*** join/#neo900 jonsger (~Thunderbi@2a02:8070:791:2f00:f451:e80:944c:46fa)
19:34.56*** join/#neo900 SylvieLorxu (~TheLastPr@dhcp-077-251-165-191.chello.nl)
20:45.29*** join/#neo900 Pali (~pali@Maemo/community/contributor/Pali)
20:45.55*** join/#neo900 marcXDXD (~marcXDXD@124.Red-83-54-73.dynamicIP.rima-tde.net)
22:23.41*** join/#neo900 Pali (~pali@Maemo/community/contributor/Pali)
22:28.29*** join/#neo900 jonsger (~Thunderbi@2a02:8070:791:2f00:f451:e80:944c:46fa)
23:45.53*** join/#neo900 wazrus (~wazrus@host131-124-dynamic.12-79-r.retail.telecomitalia.it)

Generated by irclog2html.pl Modified by Tim Riker to work with infobot.