| 00:08.27 | Oksana | jonwil: About localization patches: exception-en-US.diff should still be done, but the patch may need to be modified because of different line numbers (Mozilla changed their code slightly, but it does not affect -+diff, only the line numbers and pretext of the edit). |
| 00:08.29 | Oksana | bug137606.diff is no longer needed, since Mozilla-trunk does not mention File menu anymore. |
| 00:08.30 | Oksana | bug157237.diff should still be done. Not sure whether line numbers are still the same or changed. bug87973.firefox.hardcoded.diff should still be done. Bug 336029 for Mozilla, by the way. |
| 00:09.32 | *** join/#neo900 xes (~xes@unaffiliated/xes) |
| 00:09.57 | j4s0nmchr1st0s | Oksana: Are you a programmer? |
| 00:09.59 | DocScrutinizer05 | well, patch is extremely smart |
| 00:10.28 | Oksana | I did not make the patches. I just read them. |
| 00:11.01 | DocScrutinizer05 | would you like to _read_ my little fancy at ~flashing? :-) |
| 00:11.21 | Oksana | ~flashing |
| 00:11.21 | infobot | well, maemo-flashing is http://wiki.maemo.org/Updating_the_tablet_firmware, or - on linux PC - download http://maemo.cloud-7.de/maemo5/patches_n_tools/maemo-my-private-workdir/, cd into it, do ./flash-it-all.sh |
| 00:12.06 | dos1 | DocScrutinizer05: well, one of my ex-mozilla devices is still untouched, so I could reflash it |
| 00:13.07 | DocScrutinizer05 | dos1: great! |
| 00:13.20 | DocScrutinizer05 | it's made for exactly that |
| 00:16.49 | Oksana | Interesting script. Too complicated to read through, at least when I do not actually use it. :-) |
| 00:25.15 | DocScrutinizer05 | complicated? it's only a 82 lines, some 20..30% of those comments or empty |
| 00:25.39 | dos1 | RX-51_2009SE_21.2011.38-1_PR_COMBINED_MR0_ARM.bin is not known (has no checksum line in local file md5sums.txt for checking file integrity). Aborting. |
| 00:25.57 | DocScrutinizer05 | ummmph |
| 00:28.24 | DocScrutinizer05 | fixed |
| 00:29.06 | DocScrutinizer05 | but it's easier to do `echo '095259c2380e894dc1d6a2999526ec9f RX-51_2009SE_21.2011.38-1_PR_COMBINED_MR0_ARM.bin' >>md5sums.txt |
| 00:29.51 | Oksana | What is libxul-sdk? Because there is some trouble around toolkit |
| 00:29.57 | DocScrutinizer05 | well, dunno what's easier, wget http://maemo.cloud-7.de/maemo5/patches_n_tools/maemo-my-private-workdir/md5sums.txt or the above |
| 00:30.16 | dos1 | already wgeted, it's downloading the image now |
| 00:30.30 | DocScrutinizer05 | *shhhh*! ;-) |
| 00:32.01 | dos1 | I mean http://maemo.cloud-7.de/flash-moko11_uSD-image.tar.gz of course ;) |
| 00:32.08 | DocScrutinizer05 | aaah |
| 00:32.16 | Oksana | jonwil: about romaxa: https://github.com/romaxa Also, Ctrl+F romaxa here: http://store.ovi.com/content/257468 |
| 00:32.57 | DocScrutinizer05 | I wonder if I should do sth about gaining root in the script |
| 00:33.47 | dos1 | yep, I read the script before so I knew I should launch it as root |
| 00:33.51 | DocScrutinizer05 | prticularly since wget shouldn't run as root, but flasher must run as root, also the blacklist hack and modprobe needs root permissions |
| 00:33.57 | dos1 | ~flashing doesn't say so though |
| 00:34.04 | DocScrutinizer05 | :nod: |
| 00:34.39 | dos1 | hehe |
| 00:34.42 | dos1 | ./flash-it-all.sh: line 65: 0xEEEE-3.5_2.5.2.2/EEEE-3.5: Permission denied |
| 00:34.50 | DocScrutinizer05 | ugh |
| 00:35.00 | DocScrutinizer05 | ffs |
| 00:36.57 | DocScrutinizer05 | ls -l 0xEEEE-3.5_2.5.2.2/EEEE-3.5 |
| 00:38.02 | DocScrutinizer05 | or did you store the maemo-my-private-workdir/ on a nonexecute fs? |
| 00:38.56 | dos1 | wgetting directory doesn't preserve permissions :P |
| 00:39.02 | DocScrutinizer05 | dang! |
| 00:39.32 | dos1 | they're not even available over http after all |
| 00:39.49 | DocScrutinizer05 | of course :-S |
| 00:40.00 | dos1 | .tar.gz file might be a good idea ;) |
| 00:40.09 | DocScrutinizer05 | already pondered it |
| 00:40.21 | DocScrutinizer05 | gonna change that stuff accordingly |
| 00:41.21 | Oksana | jonwil: Or is romaxa impossible to reach this way, too? http://maemo.org/profile/view/romaxa/ |
| 01:00.45 | DocScrutinizer05 | dos1: could you refresh please? |
| 01:03.30 | Oksana | jonwil: About crashes: 854ab30d101e.diff was already fixed by Mozilla, so no longer needed. GetChannelIsUnsafe_bug117540.diff should still be done. attachment.cgi%3fid=46259.diff was already fixed by Mozilla, so no longer needed. |
| 01:07.14 | jonwil | Put the information about the patches in the tmo thread otherwise it will go missing :) |
| 01:07.31 | Oksana | jonwil: Will try to. |
| 01:09.17 | jonwil | Will email romaxa with a nice well-written well-thought-out email I guess :) |
| 01:17.40 | Oksana | Wonder if he checks it... Good luck! |
| 01:32.47 | DocScrutinizer05 | infobot: no, maemo-flashing is http://wiki.maemo.org/Updating_the_tablet_firmware, or - on linux PC - download http://maemo.cloud-7.de/maemo5/patches_n_tools/maemo-my-private-workdir(/*|.tgz), cd into it, do ./flash-it-all.sh |
| 01:32.47 | infobot | DocScrutinizer05: okay |
| 01:33.08 | DocScrutinizer05 | dos1: better? |
| 01:52.12 | DocScrutinizer05 | GRRRR! could somebody please help me out how to store+quit in EMACS? |
| 02:01.44 | DocScrutinizer05 | nm, done |
| 02:02.44 | j4s0nmchr1st0s | Oksana: Is there a prototype yet? |
| 02:05.14 | Oksana | j4s0nmchr1st0s:<DocScrutinizer05>a pity but what can we do? proto_V2 will not appear before end of year |
| 02:06.00 | Oksana | So, proto_V1 was done, some time ago, and proto_V3 will be the final prototype, equivalent to mass-production-device. |
| 02:06.24 | DocScrutinizer05 | at least when we're lucky :-) |
| 02:07.50 | DocScrutinizer05 | that's why we take a great deal of care to get everything right in proto_V2 already, so no surprises in proto_V3 |
| 02:15.12 | jonwil | hmmm, dont know what to say in this email to romaxa (subject in particular) |
| 02:40.23 | Oksana | "MicroB: new Gecko" ? |
| 02:42.49 | jonwil | How about "Updaring Gecko in Microb" |
| 02:44.45 | Oksana | Updating*, even :-) |
| 02:45.26 | Oksana | Or "MicroB and latest Gecko"? |
| 02:45.53 | DocScrutinizer05 | how about s/MicroB/fremantle browserd/ |
| 02:46.50 | DocScrutinizer05 | aiui microB is mainly the closed UI part |
| 02:47.02 | Oksana | All of this sounds alright. And MicroB probably sounds catchier, and more encompassing, than browserd. Not sure, though. |
| 02:47.59 | DocScrutinizer05 | "updating MicroB's rendering engine from Gecko to <whatever> - help wanted" |
| 02:48.16 | j4s0nmchr1st0s | Oksana: Send me a prototype. |
| 02:48.20 | Oksana | MicroB-engine, for short. |
| 02:49.21 | Oksana | j4s0nmchr1st0s: Device prototype is not cheap. And I do not have one. Who is the head of Neo900 UG? |
| 02:50.02 | jonwil | "Updating Gecko in microb-engine to a newer version" works |
| 02:50.14 | jonwil | or better yet "Updating Gecko in microb-engine to a recent version" |
| 02:50.42 | Oksana | j4s0nmchr1st0s: If you want a prototype, pre-order one. Around 1500 euro, or what was it? proto_V2 will not appear before end of year |
| 02:50.55 | DocScrutinizer05 | I'd not feel excited to rwad such mail when I had touched that stuff a 4 years ago last time. Subject sunds like a press announcement |
| 02:51.14 | DocScrutinizer05 | read* |
| 02:51.33 | jonwil | how about "Help wanted updating Gecko in microb-engine to a recent version"? |
| 02:51.50 | Oksana | "Help needed/wanted: updating MicroB-engine" |
| 02:52.07 | DocScrutinizer05 | "wow, that guy is updating microb-engine, whatever that means. Relevant for me? no. Next mail" |
| 02:52.56 | jonwil | I think "Help wanted updating microb-engine to a more recent Gecko version" works |
| 02:53.21 | DocScrutinizer05 | you start to get an idea what it sounds like when werner, sebastian and me are drafting a new newsletter ;-) |
| 02:53.44 | DocScrutinizer05 | we can do that game a full week |
| 02:54.03 | Oksana | Hopefully, he is still thinking about Linux-phone and Firefox-on-mobile-Linux. |
| 02:58.27 | j4s0nmchr1st0s | 1500! |
| 02:58.34 | j4s0nmchr1st0s | eu |
| 02:59.16 | Oksana | Pre-order for final device is 100 euro. |
| 02:59.25 | j4s0nmchr1st0s | I used to get hardware for beta testing free. |
| 02:59.31 | Oksana | Estimated price for final device is 700 euro. |
| 02:59.51 | Oksana | Prototypes are hand-made and thus costly. |
| 03:00.03 | j4s0nmchr1st0s | Sign up for a reseller program Oksana |
| 03:00.24 | Oksana | Why reseller? Of prototypes, specifically? |
| 03:00.39 | DocScrutinizer05 | j4s0nmchr1st0s: the project is completely financed by donations. Do you think it's fair to Oksana and all the other donors to use their money to build a proto for 1400EUR and send it to you for free? |
| 03:01.32 | j4s0nmchr1st0s | Depends on how many grants the company gets. |
| 03:01.35 | Oksana | If I am lucky, I will buy several final devices, and sell them to second-wave buyers. For the same price as I got them. Just for the sake of increasing the size of the batch. |
| 03:01.42 | j4s0nmchr1st0s | Let me look at the budget. |
| 03:02.06 | DocScrutinizer05 | or let me put it this way: we already have ~300 betatesters who would *love* to get a prototype for a little less than the 1400 bucks it costs to build them |
| 03:02.06 | Oksana | Grants? No grants, just donors. Aka 'future owners of devices'. |
| 03:02.57 | jonwil | his last github contribution was to nemomobile-packages/gecko-dev on 26th september 2014 |
| 03:03.03 | jonwil | so he is obviously active |
| 03:03.08 | j4s0nmchr1st0s | Is this a business or what that isn't a very well planned business model. |
| 03:03.33 | DocScrutinizer05 | please don't suffer our headaches |
| 03:03.42 | j4s0nmchr1st0s | Sounds more like you are building phones for James. |
| 03:04.00 | DocScrutinizer05 | sounds like you're a really smart guy |
| 03:05.21 | DocScrutinizer05 | you're welcome to donate a 500k EUR so we could easily hand out free prototypes to betatesters |
| 03:05.27 | Oksana | j4s0nmchr1st0s: It's going to be high-quality phone. With stereo speakers, stereo microphone, and such. With pressure-temperature sensors. With accelerometer and gyroscope. With resistive dual-touch. Read the specifications. |
| 03:05.57 | j4s0nmchr1st0s | Did you see that movie The Matrix? |
| 03:06.08 | j4s0nmchr1st0s | Compare the audio quality to the TP7 |
| 03:06.15 | Oksana | With dual-SIM, NFC, infra-transceiver and FM transceiver. |
| 03:06.17 | DocScrutinizer05 | HUH? |
| 03:06.37 | j4s0nmchr1st0s | What is the CPU? |
| 03:06.51 | DocScrutinizer05 | RTFWebpage! |
| 03:07.22 | Oksana | j4s0nmchr1st0s: http://neo900.org |
| 03:07.24 | j4s0nmchr1st0s | If it is going to live up to its name it needs something like the transmetta CPU |
| 03:07.46 | DocScrutinizer05 | http://neo900.org/faq http://neo900.org/specs |
| 03:07.47 | pigeons | its name is neo900... |
| 03:08.02 | pigeons | so the cpu seems to fit |
| 03:08.30 | DocScrutinizer05 | and we're way behond the point of discussing CPU |
| 03:09.43 | Oksana | j4s0nmchr1st0s: CPU: TI DM3730, 1 GHz; RAM: 1GB |
| 03:09.59 | DocScrutinizer05 | choosing a SoC/CPU is not like picking your fav meal from a menu |
| 03:10.39 | Oksana | Storage: 64GB internal + SD card external |
| 03:10.50 | j4s0nmchr1st0s | It isnt living up to what Neo would use. |
| 03:10.52 | DocScrutinizer05 | http://pandoralive.info/?p=2834 |
| 03:11.29 | DocScrutinizer05 | j4s0nmchr1st0s: maybe that's actually funny but sorry I'm a tad allergic to this sort of "discussion" |
| 03:11.33 | j4s0nmchr1st0s | It needs to be able to do what Kevin can do automatically. |
| 03:12.09 | jonwil | The Neo900 CPU is (IIRC) the best/most powerful CPU we can get that is still backwards compatible in the ways we need it to be. |
| 03:12.26 | DocScrutinizer05 | !!! http://pandoralive.info/?p=2808 !!! |
| 03:12.37 | Oksana | j4s0nmchr1st0s: If you need more CPU-RAM, you can look up this: http://www.dragonbox-pyra.org/specs.html But it will not have the sensors |
| 03:13.00 | DocScrutinizer05 | and no phone |
| 03:13.01 | j4s0nmchr1st0s | no rudder |
| 03:13.44 | Oksana | I mean, DragonBox-Pyra can optionally include cellular module |
| 03:14.09 | Oksana | "Wifi, Bluetooth and optional 3G/UMTS/GPS" |
| 03:14.13 | DocScrutinizer05 | >>When some company releases a new device, itâs fairly easy to jump on your gun and point out âHey, Are You Stupid? Why didnât you choose THAT SoC instead? Itâs more powerful!â. Well, most people actually forget one of the key market constraints: Supply.<< |
| 03:14.27 | j4s0nmchr1st0s | The phone also needs an FRS band for maintaining rugulatory network silence. |
| 03:14.45 | DocScrutinizer05 | j4s0nmchr1st0s: please stop that! |
| 03:14.54 | j4s0nmchr1st0s | If it cannot go local its just another consumer product. |
| 03:15.31 | j4s0nmchr1st0s | DocScrutinizer05: Stop what , chatting? |
| 03:15.48 | DocScrutinizer05 | yes, this type of noisy meaningless chatter |
| 03:16.50 | j4s0nmchr1st0s | The suggestion about transmetta is not about crunching power but about compatibility. |
| 03:18.27 | DocScrutinizer05 | IOW: read the links I poted above, read http://talk.maemo.org/showthread.php?t=91142 *completely* from first to last post, then come back and ask your questions or even contribute with suggestions and criticism. But please not before you did all that |
| 03:19.27 | Oksana | j4s0nmchr1st0s: Or join ##chat : The problem with additional, country-specific features is that they add complexity (and cost), and are useless for many consumers |
| 03:21.04 | j4s0nmchr1st0s | But James. |
| 03:21.09 | Oksana | That's what hacker-bus is for. |
| 03:22.54 | DocScrutinizer05 | Oksana: he won't know what's hackerbus, never even heard of. He doesn't know what CPU the device is using and why. Futile noise |
| 03:23.38 | j4s0nmchr1st0s | Same as the nook. |
| 03:23.48 | j4s0nmchr1st0s | Omap |
| 03:24.09 | Oksana | Maybe, he will get curious. Instead of trying to push his beloved features into the device, he will research how to add them to the device, without imposing costs onto people who would not want these features. |
| 03:24.20 | j4s0nmchr1st0s | My suggestion was for the same stated "why" compatibility. |
| 03:24.41 | DocScrutinizer05 | sorry, I fail to parse you posts |
| 03:25.24 | j4s0nmchr1st0s | Amd knows exactly how to compete with intel. |
| 03:26.35 | DocScrutinizer05 | for a rule of thumb: we are refining and discussing specs of this device with roundabout 300 peaople for over a year now. Guess how often we heard suggestions like yours already, and how often we mumbled "not *again* please" while typing an answer |
| 03:27.14 | DocScrutinizer05 | and neither AMD nor intel is *any* relevant in this channel and for this device |
| 03:27.14 | j4s0nmchr1st0s | DocScrutinizer05: Do you know anything about transmetta? |
| 03:27.21 | Oksana | "Omap", "nook": what is that about? Compatibility - with what - can be achieved by using Transmeta? Neo900 strives for compatibility with Nokia N900, and thus uses TI processor, just a bit newer one. |
| 03:28.08 | DocScrutinizer05 | :-/ |
| 03:28.27 | Oksana | Transmeta seems to be used for laptops and workstations, not mobile phones. |
| 03:29.23 | DocScrutinizer05 | will you PRETTY PLEASE - with lots of sugar on top - read http://pandoralive.info/?p=2808 |
| 03:29.31 | j4s0nmchr1st0s | A phone needs not compete with intel but with other phones. The transmetta chip can do morphing. |
| 03:29.49 | DocScrutinizer05 | and now please stop it, finally |
| 03:30.55 | j4s0nmchr1st0s | I like sugar. |
| 03:31.13 | DocScrutinizer05 | when you're so convinced about your transmeta, I suggest you start your own phone building business and use your advantage over all the competitors, incl Neo900 |
| 03:31.54 | DocScrutinizer05 | and statements like your last one are no longer tolerated in this channel, I asked you two times already to reduce noise |
| 03:32.16 | Oksana | j4s0nmchr1st0s: Go into PM? DocScrutinizer does not enjoy noise |
| 03:33.25 | j4s0nmchr1st0s | Oksana: If you insist, go on, privmsg. |
| 03:36.44 | DocScrutinizer05 | [2014-11-09 Sun 17:53:06] <DocScrutinizer05> some nice "mature" (2003) background read about OMAP strategy and design considerations: http://www.ocpip.org/uploads/documents/Chapter_5_Winning__SOC_Revolution.pdf |
| 03:39.04 | DocScrutinizer05 | particularly see the considerations regarding embedded and power saving |
| 03:39.20 | DocScrutinizer05 | ...which didn't change at all since 2003 |
| 03:39.59 | DocScrutinizer05 | you cannot choose a embedded SoC same way you choose your PC CPU |
| 03:41.02 | pigeons | I just donated :) |
| 03:42.35 | Oksana | :-) |
| 03:44.39 | jonwil | http://pastebin.com/VbGh2Yg9 is what I have for the email to send to Oleg |
| 03:45.00 | jonwil | Anyone want to comment on whether I am saying the right things? |
| 03:48.05 | jonwil | Guess not... |
| 03:49.11 | Oksana | I am opening the link :-) |
| 03:49.24 | jonwil | :) |
| 03:50.05 | Oksana | relavent - relevant |
| 03:50.49 | Oksana | Multiple times? Or is it an alternative, also correct spelling? |
| 03:51.05 | Oksana | If there is anything you can add to the discussion ... then what? |
| 03:51.30 | jonwil | nope, its a typo |
| 03:51.47 | Oksana | 3 times :-) |
| 03:52.38 | jonwil | "then please do so." |
| 03:52.53 | jonwil | does that sound right to you? |
| 03:53.12 | jonwil | wait better idea |
| 03:53.21 | jonwil | no, that wont work |
| 03:53.28 | Oksana | Yes :-) Though you could somehow mention IRC channel, too. |
| 03:55.15 | jonwil | updated http://pastebin.com/index/VbGh2Yg9 |
| 03:55.30 | jonwil | anything more to add? |
| 03:56.05 | Oksana | Maybe, in signature? Or is it the last place where he will be looking for contact information? |
| 03:56.12 | Oksana | Cannot see the new version. |
| 03:57.10 | Oksana | This paste has been removed!: http://pastebin.com/VbGh2Yg9 |
| 03:57.15 | jonwil | http://pastebin.com/RP3ZRF1Z |
| 03:57.21 | jonwil | wrong link |
| 03:57.25 | jonwil | that one should work |
| 03:58.03 | Oksana | Yes :-) |
| 04:04.34 | jonwil | anything more to say about the email? |
| 04:04.41 | jonwil | or should I go ahead and send? |
| 04:13.07 | jonwil | guessing nothing more to add :P |
| 04:14.48 | jonwil | mail sent |
| 04:37.50 | jonwil | Lets hope it results in something useful/positive |
| 05:34.34 | jonwil | He said "All you need is:" "1) Build latest GTK firefox (gecko engine) on Neo900 SDK" "2) rewrite microb-eal mozilla using latest Gecko engine API's.". Going to reply :) |
| 05:35.33 | Oksana | :-) |
| 06:16.05 | *** join/#neo900 astr (~astr@79-69-194-151.dynamic.dsl.as9105.com) |
| 07:27.34 | *** join/#neo900 Oxyd76 (~quassel@gateway/tor-sasl/oxyd76) |
| 07:47.47 | *** join/#neo900 Oxyd76 (~quassel@gateway/tor-sasl/oxyd76) |
| 08:30.54 | fling | Is there anything new about the project? Not much news on the site. |
| 08:53.58 | *** join/#neo900 Sveta (quasselcor@freenode/staff/fsf.member.svetlana) |
| 08:57.48 | *** join/#neo900 Sveta (gry@freenode/staff/fsf.member.svetlana) |
| 09:02.11 | *** join/#neo900 Svetlana (gry@freenode/staff/fsf.member.svetlana) |
| 09:37.31 | *** join/#neo900 jonwil (~jonwil@27-33-80-219.tpgi.com.au) |
| 10:17.08 | *** join/#neo900 che1 (~che@h201.tum.vpn.lrz.de) |
| 10:23.48 | *** join/#neo900 jonwil (~jonwil@27-33-80-219.tpgi.com.au) |
| 10:34.08 | Oksana | fling: Since the speakers of N900 were knowles TINY (not manufactures anymore), Neo900 is likely going to use knowles GRAND. They have slightly different dimensions, but *might* be feasible. http://neo900.org/stuff/joerg/random-media/speakers-IHF/ |
| 10:42.14 | *** join/#neo900 Oxyd76 (~quassel@gateway/tor-sasl/oxyd76) |
| 10:47.26 | bencoh | wow, so much dust |
| 11:01.17 | *** join/#neo900 arcean (~arcean@aada206.neoplus.adsl.tpnet.pl) |
| 11:15.47 | dos1 | DocScrutinizer05: Image(s) flashed successfully in 33.931 s (7543 kB/s)! |
| 11:17.23 | DocScrutinizer05 | good |
| 11:23.25 | kerio | yay |
| 11:41.02 | *** join/#neo900 sixwheeledbeast (~paul@2a01:348:6:860a:884f:dfdd:8ed:bdee) |
| 11:43.10 | DocScrutinizer05 | kerio: you tested it? |
| 11:43.31 | kerio | what |
| 11:43.37 | DocScrutinizer05 | ~flashing |
| 11:43.37 | infobot | maemo-flashing is probably http://wiki.maemo.org/Updating_the_tablet_firmware, or - on linux PC - download http://maemo.cloud-7.de/maemo5/patches_n_tools/maemo-my-private-workdir/*, cd into it, do ./flash-it-all.sh |
| 11:43.50 | kerio | i don't even have linux |
| 11:43.56 | DocScrutinizer05 | silly lil scriptie |
| 11:44.51 | DocScrutinizer05 | fails to see how people can _live_ without linux |
| 11:45.32 | bencoh | kerio: wait, what ? |
| 11:47.34 | kerio | "wait, what?" what? |
| 11:48.00 | fling | Oksana: good news! |
| 11:48.44 | bencoh | 12:43 < kerio> i don't even have linux |
| 11:49.03 | kerio | happens |
| 11:49.19 | bencoh | yeah, it's just ... surprising |
| 11:50.11 | kerio | os x is best os |
| 11:50.13 | kerio | it even has a x |
| 11:50.35 | bencoh | ooh, osx, okay :) |
| 11:50.40 | bencoh | still unix inside |
| 11:51.03 | DocScrutinizer05 | kerio always knows how to troll in a inspired way :-) |
| 11:51.15 | DocScrutinizer05 | yep, unix ftw |
| 11:51.56 | DocScrutinizer05 | idly ponders if that silly lil scriptie could learn multi-platform |
| 11:52.44 | kerio | why do you want to flash everything anyway |
| 11:52.45 | kerio | flash uboot |
| 11:52.52 | kerio | uboot is good :3 |
| 11:52.56 | DocScrutinizer05 | lol |
| 11:53.28 | DocScrutinizer05 | that script evidently is for the clueless and the lazy |
| 11:54.07 | DocScrutinizer05 | and meant to cover the most general case of "flashing the N900" |
| 11:54.24 | bencoh | could be handy if you need to test cssu install on a fresh device as well |
| 11:54.57 | bencoh | (heavy flash/test/flash/test) |
| 11:54.58 | DocScrutinizer05 | I got 55 devices with sort of messed up firmware on them |
| 11:55.01 | bencoh | haha |
| 11:55.18 | DocScrutinizer05 | had to write a script to handle flashing |
| 11:55.34 | bencoh | gonna be a lot of pressed U |
| 11:55.43 | DocScrutinizer05 | no need to press U |
| 11:56.33 | DocScrutinizer05 | fire script, plug in device, wait until script tells to insert battery. profit |
| 11:56.57 | DocScrutinizer05 | dos1: right? |
| 11:57.54 | DocScrutinizer05 | just ponders to augment the script to even customize the freshly flashed device without ever touching it |
| 11:59.29 | DocScrutinizer05 | shouldn't be too hard to install a slightly patched bootmenu via rescueOS |
| 12:00.33 | DocScrutinizer05 | or maybe even create a customized FIASCO image |
| 12:04.34 | *** join/#neo900 mvaenskae (~mvaenskae@unaffiliated/mvaenskae) |
| 12:09.11 | mvaenskae | wheeee, reddit thread \o/ |
| 12:09.25 | DocScrutinizer05 | hmm? |
| 12:09.47 | mvaenskae | DocScrutinizer05: https://www.reddit.com/r/linux/comments/2lr90t/til_that_there_is_a_completely_open_and/ |
| 12:09.56 | DocScrutinizer05 | yeah, I know |
| 12:10.05 | DocScrutinizer05 | not the first one |
| 12:10.07 | mvaenskae | nice to see a thread :) |
| 12:14.22 | *** join/#neo900 astr (~astr@79-69-194-191.dynamic.dsl.as9105.com) |
| 12:18.23 | mvaenskae | still the amound of replies is a nice sight for sore eyes, close to 200 messages and on my second page of subreddits i am subscribed to :) |
| 12:24.03 | DocScrutinizer05 | and many of them would need a reply by somebody registered and entitled to post to reddit. Like the lord_skittles guy who obviously can't discern between open hardware and open source software |
| 12:26.38 | DocScrutinizer05 | having a modem module that has whatever firmware on chip doesn't flaw the claim of "open hardware", just like using a ambient light sensor with a tiny MCU in it that does the A/D and calculations and I2C communication doesn't mean the device that's using this chip and clearly specifies how to talk to it via I2C is a closed hardware |
| 12:28.08 | DocScrutinizer05 | heck, for most of the slightly more complex than "just 4 gates" chips you don't even know if they might have a MCU inside, and for sure you don't have access to any firmware running on such MCU |
| 12:28.44 | DocScrutinizer05 | but all this is hardly related to *open hardware* |
| 12:29.29 | jonwil | treating such things as a black box is the right way |
| 12:30.22 | jonwil | i.e. you know what goes in and what goes out and you can be sure its not doing anything weird because its not possible for it to access things it would need to access to do weird things |
| 12:30.22 | DocScrutinizer05 | in the end you need to do exactly this (treat as blackbox) with every single chip and even every single transistor you use |
| 12:30.48 | DocScrutinizer05 | yep, exactly |
| 12:31.10 | mvaenskae | DocScrutinizer05: anyone can register on reddit btw, no need to be entitled from what i can tell |
| 12:31.24 | DocScrutinizer05 | I for sure won't do that |
| 12:31.41 | jonwil | btw I am getting closer to tracking down a particular revision in mozilla hg that matches PR1.3 microb-engine |
| 12:32.10 | DocScrutinizer05 | I probably once tried and it had hurdles of the type "only works on FireFox" or "you need google+ for that" or whatever |
| 12:32.57 | jonwil | the last relavent changelog entry for microb-engine was Sync up engine to last mozilla 1.9.2 branch and the last 1.9.2 branch as of that date is GECKO1922_20100315_RELBRANCH which is what I am now pulling |
| 12:33.01 | DocScrutinizer05 | or simply "please fill that form which asks for a humble 182 personal dates of yours" |
| 12:33.24 | jonwil | a diff should tell me how close I am to matching things up |
| 12:35.27 | jonwil | I would say that microb-engine is up there as one of the most complex pieces of FOSS software on the entire N900 |
| 12:37.56 | DocScrutinizer05 | protestor, 19h ago >>There are concerns that even offline work can be compromised, since the baseband processor can run code on the other processor<< Simple but necessary answer: "NO Sir, not on Neo900" |
| 12:38.00 | mvaenskae | DocScrutinizer05: is that in regards to reddit? to post you need a reddit account consisiting of nick/password and if wanted an email :) (just to clear it up) |
| 12:38.40 | DocScrutinizer05 | I'm generally not interested in registering at facebook, reddit, google+, twitter, younameit |
| 12:39.12 | mvaenskae | DocScrutinizer05: just wanted to clear it up :) it is by far the least worrysome of the large websites |
| 12:40.52 | mvaenskae | DocScrutinizer05: maybe it would be good for you to pick the wrong things and correct them, post them to the maemo forums and them dos posts a link to there that everyone can then see |
| 12:41.19 | mvaenskae | or dos can just copy-paste them directly into the responses |
| 12:47.40 | DocScrutinizer05 | ratatask 2 points 2 hours ago >>People have already built their own GSM base station (http://www.openbts.org), and the baseband for one old motorola phone (http://bb.osmocom.org)<< S/He missed to notice the not so obvious link between osmocom and openmoko. Check Harald Welte, Dieter Spahr, among others. All are members of both the osmocom team and the openmoko crew |
| 12:50.46 | mvaenskae | DocScrutinizer05: out of interest, how legal was the base station? |
| 12:50.57 | DocScrutinizer05 | 100% |
| 12:51.04 | mvaenskae | :o |
| 12:51.08 | DocScrutinizer05 | with a temporary licence |
| 12:51.11 | mvaenskae | ahhh |
| 12:53.05 | DocScrutinizer05 | which is kind of funny since that licence afaik does _not_ require evaluation and certification of the protocols/"firmware" used, so such a test BTS could legally do rogue things (which it kinda did on CCC ;-D ) |
| 12:57.39 | DocScrutinizer05 | directhex 1 point 4 hours ago >> But it's not a maxed out iPhone 6. It's essentially an OMAP3 with performance found on high-end phones from 2010 ... So over $1000 for a phone from 2010 in terms of spec<< DUDE, go buy a antique car e.g. from the 1950s, ALL NEW and in mint condidtion. Then guess how much its value in terms of spec and how that compares to contemporary cars with same price |
| 12:58.46 | mvaenskae | DocScrutinizer05: 1950s? the neo900 ain't that old... |
| 12:59.25 | DocScrutinizer05 | your point being? |
| 13:00.44 | DocScrutinizer05 | >>I can't be the only person who thought that the phone was literally transparent?<< HUH what? |
| 13:02.11 | bencoh | no offense, but neo900 isnt exactly an "antique car" ;) |
| 13:02.26 | mvaenskae | the neo900 is more like a pontiac firebird |
| 13:02.37 | bencoh | there is no added value in it being "from the old days" |
| 13:03.26 | bencoh | mvaenskae: :] |
| 13:03.52 | mvaenskae | bencoh: there is, my parents bought a microwave over 20 years ago... it still works |
| 13:04.01 | mvaenskae | try that with new age stufff... nah, not gonna happen |
| 13:04.17 | bencoh | hmm ... point taken :) |
| 13:04.43 | DocScrutinizer05 | it is. exactly for e.g. using a "old days" concept of not integrating modem into SoC, a concept that was essential for recent years' price drops on smartphones |
| 13:04.52 | bencoh | (though I'm not sure it's old enough for that) |
| 13:05.35 | mvaenskae | also my dad reapired the 20 year old washing machine regularily for the past 2 years just because he could |
| 13:05.39 | bencoh | DocScrutinizer05: yup, but we could go for a shiny-new-imx6 and have the same result |
| 13:06.00 | DocScrutinizer05 | no, see http://pandoralive.info/?p=2808 |
| 13:06.08 | mvaenskae | would be stupid if just to change the coal one would need to buy a whole new engine |
| 13:07.02 | bencoh | DocScrutinizer05: yeah, I know about that, but it doesnt say why imx6 wouldnt be good enough for our purpose ;) |
| 13:07.22 | bencoh | (afaik it has the same issue than omap/powervr) |
| 13:07.35 | DocScrutinizer05 | you should compare Neo900 to e.g. TI Zoom-II which sold for almost 2000 bucks iirc |
| 13:08.08 | DocScrutinizer05 | rather than a silly insecure mainstream mass market smartphone like iPhone or Galaxy |
| 13:08.22 | bencoh | hmmm, okay, it does (logistical reason) |
| 13:08.39 | DocScrutinizer05 | when even TI themselves cannot go cheaper for their development platform, how could we? |
| 13:09.47 | DocScrutinizer05 | add to that that we want to be binary compatible to fremantle/N900 and there you are |
| 13:10.26 | mvaenskae | DocScrutinizer05: the iphone is pretty bold, not insecure; look at how well it advertises just how nice it looks! |
| 13:10.47 | DocScrutinizer05 | I pondered for a long time whether to go for OMAP5 like pyra, but decided that it's probbaly not compatible enough and too high risk |
| 13:11.55 | DocScrutinizer05 | wonders what's wrong with his sense of humer. Notices that frowning is the regular reaction on such jokes, rather than smiling |
| 13:13.11 | bencoh | DocScrutinizer05: compatible enough with ? software ? |
| 13:13.22 | DocScrutinizer05 | with N900 |
| 13:13.30 | bencoh | yeah, but software-wise ? |
| 13:13.44 | DocScrutinizer05 | err, what else? color wise? |
| 13:13.58 | mvaenskae | bencoh: look-wise |
| 13:14.04 | bencoh | :-)) |
| 13:14.28 | mvaenskae | DocScrutinizer05: how much more R&D + unit cost (just the part) would the switch have caused? |
| 13:14.36 | mvaenskae | to omap5 |
| 13:14.51 | DocScrutinizer05 | for OMAP3 we have lots of existing apps and even several closed blobs proven to work in maemo |
| 13:14.55 | bencoh | I dunno, there might have been some hw bus you might want to use the same way ... :) |
| 13:15.23 | mvaenskae | DocScrutinizer05: is the omap5 not necessarily compatible to omap3 code? |
| 13:15.59 | DocScrutinizer05 | mvaenskae: lemme put it this way: OMAP3 is a tested proven design, for OMAP5 we're wandering terra incognita |
| 13:17.17 | DocScrutinizer05 | porting a partially closed OS to a new platform is hard enough already, even without changing the CPU during that enterprise |
| 13:17.19 | mvaenskae | but we want incognito mode per default D: (joking aside, i understand your concerns fully) |
| 13:18.40 | *** join/#neo900 che1 (~che@j008.tum.vpn.lrz.de) |
| 13:18.41 | DocScrutinizer05 | csolisr 2 points 10 hours ago >>Laws say that the firmware must be compliant with the guidelines of regulation organisms (such as the FCC), not that the firmware must be proprietary. If a team develops a patent-free alternative and it's approved as compliant with said guidelines, no problem.<< DANG that person completely failed to grok what "cerification" means |
| 13:26.43 | DocScrutinizer05 | >>However, the PowerVR drivers and baseband firmware are still closed-source. The idea their claim of "100% Free Software stack" is complete bullshit.<< that statement is complete BS, please RTFFAQ |
| 13:27.23 | mvaenskae | DocScrutinizer05: reading is a difficult task, comprehending even more so :) |
| 13:28.45 | DocScrutinizer05 | http://neo900.org/faq#floss http://neo900.org/faq#gfx http://neo900.org/faq#peripherals http://neo900.org/faq#privacy |
| 13:29.33 | DocScrutinizer05 | could you please post that one line to this reddit thread, ideally in answering some of the BS talkers? |
| 13:32.18 | mvaenskae | DocScrutinizer05: i can post those links in a few likely (currently having lectures); please give me some sample direct links to the messages where i should reply to and i will post those there :) |
| 13:33.11 | DocScrutinizer05 | >>What about evernote, amazon, ebay, aliexpress, humble bundle games, camscanner, cerberus, google drive, dropbox, car sharing apps, public transport apps, bank apps, flappy bird, ifttt, ingress, instagram, pushbullet, reddit, shazam, tripadvisor, waze. none of those was available when my n900 broke.<< this is really completely weird. How's for example reddit depending on an *APP* to use it? |
| 13:33.39 | DocScrutinizer05 | ""DUDE, go get an iPhone, so you may pay for reddit app"" |
| 13:34.45 | DocScrutinizer05 | mvaenskae: well, basically you can post it top level, it's obviously a mandatory read for all those who posted in that thread |
| 13:35.50 | mvaenskae | DocScrutinizer05: the first line of OP literally has /faq already even in bold |
| 13:35.56 | DocScrutinizer05 | >>App store was painfully slow as well because it did a full reload of the repositories after installing one app from the GUI. Installing from the command line didn't have that problem.<< get speedyham! and be happy! |
| 13:36.44 | mvaenskae | i might need to break rediquette by posting a trojan that opens those links you posted every 2 seconds in a full screen window + screen reader at full volume |
| 13:36.58 | DocScrutinizer05 | >>...the N9 has whatsapp and a music player.<< -- huh? and the N900 didn't, or what? |
| 13:37.23 | mvaenskae | the n900 never had a music player... it had a media player ;) |
| 13:37.36 | DocScrutinizer05 | ooh, yes :-D |
| 13:39.07 | DocScrutinizer05 | h3llm17 6 points 23 hours ago >>Resistive touch screen? What a joke.<< |
| 13:39.08 | DocScrutinizer05 | Engival 27 points 22 hours ago >>Yeah, it looks horrible: https://www.youtube.com/watch?v=66RBfrBgL2E<< -- LOL, exactly right answer |
| 13:39.35 | *** join/#neo900 b1101 (~b@209.222.7.238) |
| 13:39.35 | *** join/#neo900 b1101 (~b@fsf/member/b1101) |
| 13:40.40 | *** join/#neo900 Kabouik (~quassel@230.154.92.79.rev.sfr.net) |
| 13:41.19 | DocScrutinizer05 | Glimt 2 points 14 hours ago >>unless you use an active pointing device, like in Samsung's Galaxy Note line.<< -- which isn't working on capacitive principle at all |
| 13:41.22 | mvaenskae | DocScrutinizer05: so, should i still post the links? i mean it is part of the very first line of the OP |
| 13:41.43 | DocScrutinizer05 | I thnk it cannot hurt |
| 13:42.05 | mvaenskae | ok, i will do that after changing my rooms :) |
| 13:42.10 | mvaenskae | give me some moments :) |
| 13:45.44 | DocScrutinizer05 | >>maybe even modular so you can select then later upgrade a your camera module, put some other sensor there instead or have nothing.<< YEEEHAAAA FINALLLLY! phonebloks. No discussion about a new phone without some geek jumping in and shouting "MODULES, it needs MODULES!!" |
| 13:46.57 | bencoh | :D |
| 13:46.58 | *** join/#neo900 kolp (~quassel@55d471f8.access.ecotel.net) |
| 13:47.08 | bencoh | DocScrutinizer05: I think you're hurting yourself :) |
| 13:48.45 | DocScrutinizer05 | well, same dude later on in same post writes >>the best feature of course would be a modular aerial, that way you can choose to have a gert big sticking out one rather than the slim lined ones so popular today or even an external plug in roof aerial to get top notch reception even in a basement office or campervan.<<. No more to say to comment that |
| 13:51.48 | DocScrutinizer05 | >> Was I the only one confused when the picture of the phone showed a device not constructed from transparent plastic as if it was a gameboy from the mid 90s?? Then I realized what the title meant, and I became a bit less excited.<< HMMM, we might offer transparent cases, should be available like silver, gold, and white ones ;-) Honestly it seems there's an actual ambiguity in our website. dos1, could you tackle that maybe? |
| 13:52.44 | bencoh | ambiguity ? |
| 13:54.55 | pigeons | unfortunately more people probably care about the transparency of their case than the rest of the system |
| 13:58.37 | *** join/#neo900 paulk-collins (~paulk@gagarine.paulk.fr) |
| 14:00.03 | DocScrutinizer05 | indeed |
| 14:00.23 | DocScrutinizer05 | but those will not pay the high price anyway |
| 14:00.55 | DocScrutinizer05 | they want a cheap geeky possibly transparent plastics case phone, no matter if it works or not |
| 14:01.03 | DocScrutinizer05 | just to show off |
| 14:09.55 | *** join/#neo900 Oxyd76 (~quassel@gateway/tor-sasl/oxyd76) |
| 14:11.41 | *** join/#neo900 Oxyd76 (~quassel@gateway/tor-sasl/oxyd76) |
| 14:55.02 | *** join/#neo900 modem (~modem@LAubervilliers-656-01-215-246.w217-128.abo.wanadoo.fr) |
| 14:55.38 | *** join/#neo900 modem (~modem@fsf/member/modem) |
| 15:50.13 | *** join/#neo900 che1 (~che@g184.tum.vpn.lrz.de) |
| 16:04.20 | DocScrutinizer05 | yeah, almost done with schematics review |
| 16:30.39 | *** join/#neo900 Nokiabot (~Nokiabot@182.66.31.228) |
| 16:31.39 | Nokiabot | Somebody post that reddit link please :) |
| 16:34.00 | Nokiabot | Btw about that post on ridiculing resistive touch i think that guy should be pointed to "look what i drew on my phone thread ;)maybe a link on neo900 faq too |
| 16:34.30 | Nokiabot | Docscrutinizer05^^^ |
| 16:35.09 | DocScrutinizer05 | [2014-11-10 Mon 14:39:07] <DocScrutinizer05> h3llm17 6 points 23 hours ago >>Resistive touch screen? What a joke.<< |
| 16:35.10 | DocScrutinizer05 | [2014-11-10 Mon 14:39:07] <DocScrutinizer05> Engival 27 points 22 hours ago >>Yeah, it looks horrible: https://www.youtube.com/watch?v=66RBfrBgL2E<< -- LOL, exactly right answer |
| 16:35.21 | DocScrutinizer05 | https://www.reddit.com/r/linux/comments/2lr90t/til_that_there_is_a_completely_open_and/ |
| 16:36.03 | Nokiabot | Ah that was the link sorry for making it reposting |
| 17:11.57 | DocScrutinizer05 | LOL! http://www.fsf.org/news/gluglug-x60-laptop-now-certified-to-respect-your-freedom, I honestly doubt they got FOSS software for the kbd and system management / fan processor (the one you need to patch when you don't like the weird kbd layout regarding blue and control key). Nor for the harddisk controller, nor for any other of the obviously hidden_from_FSF little MCUs inside that thing |
| 17:12.59 | Pali | do you have open source code for EC? :D |
| 17:13.13 | DocScrutinizer05 | EC? |
| 17:13.38 | Pali | embeded controller with lot of fun... |
| 17:13.46 | DocScrutinizer05 | :nod: |
| 17:14.13 | DocScrutinizer05 | thermal management aka fan control is a nightmare on those thinkpads under linux |
| 17:14.33 | DocScrutinizer05 | thanks to that system management controller |
| 17:15.08 | Pali | that part which mix keyboard, mouse, PS/2 ports data for i8042... also that implement keyboard fn keys, and I bet that EC also controls fan, brightness and other parts |
| 17:15.45 | Pali | maybe sensors (temp, hdd protection) are connected to that EC too.. |
| 17:16.10 | DocScrutinizer05 | yes, correct |
| 17:17.39 | Pali | firmware in EC implements also i8042 multiplexer for supporting more mouse devices at one time (touchpad, trackpoint, external mouse) |
| 17:17.57 | Pali | and once firmware is bad you cannot do anything |
| 17:19.03 | DocScrutinizer05 | http://support.lenovo.com/us/en/downloads/ds014916 http://forum.notebookreview.com/lenovo/474396-fn-ctrl-swap-all-lenovo-laptops-solved.html# http://support.lenovo.com/us/en/docs/MIGR-70443 (404 :-/ ) |
| 17:20.13 | Pali | also what to do with firmware in touchpads? |
| 17:20.28 | Pali | I bet that fsf does not provide any free firmware for it |
| 17:21.05 | Pali | and what with intel amt which is part of intel mainboard and is flashed by official bios flasher package? |
| 17:21.18 | Pali | they provide open source version of that intel amt firmware too? |
| 17:21.44 | Pali | and microcode for wifi card? |
| 17:22.06 | Pali | this fsf "Respect Your Freedom" is just fun |
| 17:22.56 | Pali | and intel txt and intel ethernet code? :D |
| 17:24.46 | DocScrutinizer05 | ooh right, there's for sure a MCU on NIC |
| 17:25.48 | DocScrutinizer05 | as they most likely won't hardwire all the low layer ethernet stuff |
| 17:25.59 | DocScrutinizer05 | just think WOL |
| 17:26.18 | Pali | when you are flashing official windows "bios" exe package it provides all above pieces and flashing them (except ec and touchpad) |
| 17:26.31 | Pali | yes, wake-on-lan |
| 17:26.49 | DocScrutinizer05 | RYF is a big hoax basically |
| 17:27.05 | Pali | so they probably provides only some of above pieces and other are untouched... |
| 17:27.14 | Pali | so yes, hoax |
| 17:30.40 | DocScrutinizer05 | idly wonders if a genuine VT52 terminal would qualify for RYF |
| 17:33.49 | DocScrutinizer05 | or think about a hypothetical setup where the GLES "blob" runs off-board on some remote server and you send GLES commands to there and server returns binary values to write to the GPU registers. Is it entitled for RYF? Why not? |
| 17:34.53 | Pali | and SMM handler for x86 SMM mode? |
| 17:35.03 | Pali | (x86 system management mode) |
| 17:35.15 | DocScrutinizer05 | think of a cellular modem that hypothetically needs to download own firmware OTA on each boot, but offers no way to load the firmware from local APE. Eligible for RYF? |
| 17:36.04 | DocScrutinizer05 | I'd say it is, but obviously shouldn't |
| 17:36.55 | Pali | and can be any device with any cellular modem RYF? |
| 17:36.59 | DocScrutinizer05 | FSF/RMS literally "thinking only inside the box" for RYF |
| 17:37.28 | Pali | mobile operator can send java apps and start them in SIM card without any user interaction |
| 17:37.36 | Pali | just only via cellular network |
| 17:37.46 | Pali | it is ok for RYF? |
| 17:37.51 | DocScrutinizer05 | unless you remove SIM ;-P |
| 17:38.12 | DocScrutinizer05 | so the phone is RYF but the SIM isn't |
| 17:38.25 | DocScrutinizer05 | rotfl |
| 17:38.44 | Pali | modem without sim card is ok :D funny |
| 17:40.23 | Pali | is there open source firmware for sim cards? |
| 17:40.27 | Pali | probably not |
| 17:40.49 | DocScrutinizer05 | how about a blackbox peripheral with clearly defined command interface based on a very Very VERY Long Instruction Set? Where e.g. the "reset device" instruction is some 580kB in size? |
| 17:42.13 | DocScrutinizer05 | what's wrong with VLI ? |
| 17:43.15 | Pali | and processor microcode burned into SOC? |
| 17:43.16 | DocScrutinizer05 | "other controllers need initialization sequences of up to 500 64bit commands, ours only needs one single 580kB command" |
| 17:46.01 | DocScrutinizer05 | or think of FPGA and the amount of config data needed to get sent to them before they start working, none of those bytes/words is actually explained in detail how they work internally *on lowest level* inside the FPGA chip. When we specify 20 commands a 4kB length to get sent to a WLAN chip to initialize it, what's so fundamentally different in that, in the end? |
| 17:54.16 | DocScrutinizer05 | the "it needs to be FOSS" part in "when some peripheral needs firmware uploaded, then that firmware needs to be FOSS" is also quite funny when you look closer. Any manufacturer could claim thet their hackers developed the firmware code in hex and the hex dump of the binary is already the best source code you could get for that particular firmware. And even when it was in assembler mnemonics, who says that those mnemonics do make any |
| 17:54.16 | DocScrutinizer05 | sense to anybody, since the CPU running the code is not publicly documented. |
| 17:56.12 | Pali | stupid question, but can be binary hex firmware licensed as GPL? :D |
| 17:57.13 | Pali | e.g. you will release some binary file as GPL (same as you can release text file with .c suffix as GPL) |
| 17:57.30 | Zero_Chaos | Pali: gpl requires code |
| 17:57.45 | Pali | Zero_Chaos: binary file is code itself |
| 17:58.01 | Pali | what is different between file with .c suffix and file with .bin suffix? |
| 17:59.26 | Zero_Chaos | Pali: gpl requires source code, not just executable code |
| 17:59.26 | Pali | any C interpeter can execute file with .c suffix |
| 17:59.26 | Pali | so file with .c suffix is executable code too (for C interpeter) |
| 17:59.27 | Zero_Chaos | sigh |
| 17:59.27 | Zero_Chaos | Pali: I'm not hear to debate you, read the license yourself, it's very clear |
| 18:00.00 | Pali | but really somebody can design CPU (with its own micorcode) which can execute C file directly |
| 18:00.00 | Pali | Zero_Chaos: I read it |
| 18:00.29 | DocScrutinizer05 | and files with .py suffix are for sure executables |
| 18:00.29 | Pali | and in my opinion some hexdump can be source code too |
| 18:00.29 | Pali | why not? |
| 18:00.39 | DocScrutinizer05 | exactly my point |
| 18:00.41 | Pali | yes file with .py or .sh suffix is also sorce code |
| 18:00.46 | Pali | and also it is executable code |
| 18:01.18 | Pali | and both are accepted by CPU/VM which understand that language |
| 18:01.25 | DocScrutinizer05 | something being "executable" doesn't mean it's no sourcecode as well |
| 18:02.20 | Pali | and x86 assembler code? there is 1:1 mapping between binary instructions and text equivalents |
| 18:02.20 | DocScrutinizer05 | remove the .bin ending and replace it by .txt ;-P |
| 18:02.48 | DocScrutinizer05 | voila, your sourcecode |
| 18:03.08 | DocScrutinizer05 | prove the opposite if you can! |
| 18:03.09 | Pali | or is source code defined with chars if ( c >= 32 && c < 128 ) |
| 18:03.17 | DocScrutinizer05 | not afaik |
| 18:03.19 | Zero_Chaos | just because it's executable doesn't mean it isn't source code, I agree entirely. However, if it's pure binary it's almost certainly not source code. |
| 18:03.26 | DocScrutinizer05 | sourcecode is not limited to ASCII |
| 18:04.35 | DocScrutinizer05 | actually I did write code in hex for several years |
| 18:04.39 | Zero_Chaos | from gpl: |
| 18:04.39 | Zero_Chaos | The âCorresponding Sourceâ for a work in object code form means all the source code needed to generate, install, and (for an executable work) run the object code and to modify the work, including scripts to control those activities. |
| 18:04.39 | Zero_Chaos | that seems pretty clear to me |
| 18:04.41 | Zero_Chaos | if you are writing it in binary, then that's the source |
| 18:04.43 | Zero_Chaos | if you are generating it, that it's |
| 18:04.45 | Zero_Chaos | isn't* |
| 18:04.48 | DocScrutinizer05 | 0xCD jumps to a subroutine, 0xC9 returns from subroutine (IIRC) |
| 18:05.00 | DocScrutinizer05 | etc pp |
| 18:05.20 | DocScrutinizer05 | I literally edited the stuff into a hex editor. So what's the sourcecode then? |
| 18:06.09 | Zero_Chaos | DocScrutinizer05: you edited it, or originally wrote it, in a hex editor? |
| 18:06.20 | DocScrutinizer05 | both |
| 18:06.27 | Zero_Chaos | DocScrutinizer05: then that's the source |
| 18:06.33 | DocScrutinizer05 | exactly |
| 18:06.40 | Zero_Chaos | DocScrutinizer05: if it's generated, that's not source, if you wrote it, that's source. |
| 18:06.43 | DocScrutinizer05 | binary == source |
| 18:06.44 | Zero_Chaos | the license is pretty clear on this |
| 18:07.03 | Zero_Chaos | DocScrutinizer05: more like binary sometimes ~= source |
| 18:07.07 | bencoh | (what it doesnt say is how it can affect your sanity level :>) |
| 18:07.19 | DocScrutinizer05 | in this particular case it is |
| 18:08.06 | DocScrutinizer05 | bencoh: oh yeah, particularly calculation of jump distances, without a hex calculator at hand |
| 18:08.35 | bencoh | :)) |
| 18:10.57 | DocScrutinizer05 | anyway, when I put that binary blob under GPL then it's absolutely OK for firmware upload to a peripheral, even under FSF's RYF rules |
| 18:11.07 | DocScrutinizer05 | I just proved that it's sourcecode, and the tools to process the sourcecode and generate a executable from it are commonly available |
| 18:12.44 | DocScrutinizer05 | so FSF is pretty much out of luck when WLAN manufs put their binary blobs under GPL and declare it been written in hex editor directly to the file |
| 18:12.51 | Pali | Zero_Chaos: another question, that with Knuth's TEX? If I run web2c on TEX source code and then I modify it (because C is more readable then some WEB), then I cannot release C source code without TEX source code (in case TEX code is GPL)? |
| 18:15.11 | dos1 | DocScrutinizer05: "Honestly it seems there's an actual ambiguity in our website." nope, we don't use "transparent" in our communication. the reddit post had "transparent" in its title |
| 18:15.12 | DocScrutinizer05 | nope, no problem, since TEX already is publicly available |
| 18:15.12 | Pali | then we will have another project, but instead WEB language was used C and instead C was binary |
| 18:15.12 | DocScrutinizer05 | dos1: AAAAH! many many thanks! :-) |
| 18:15.29 | DocScrutinizer05 | dos1: I already started wondering which drug they mixed into my beer to make me agree on something so obviously unprecise and ambiguous |
| 18:17.51 | DocScrutinizer05 | dos1: I however agree with the notion uttered last day that we need tpo make more clear that Neo900 does NOT develop or ship ANY particular software / firmware with the device |
| 18:20.13 | DocScrutinizer05 | we *will* ship some testing software to check the hardware functionality, plus a BSP which is basically the same |
| 18:21.13 | *** join/#neo900 mvaenskae (~mvaenskae@unaffiliated/mvaenskae) |
| 18:21.24 | DocScrutinizer05 | everything beyond (e.g. a working SHR system installation) is a give away we add in for free, but we don't sell it and don't support or warrant it in any way |
| 18:22.34 | DocScrutinizer05 | and the particular amount and type of such giveaway software shipped with device is subject to change any time without prior notice |
| 18:23.17 | DocScrutinizer05 | think ASUS motherboard, or beagleboard |
| 18:24.15 | DocScrutinizer05 | we are actually NOT selling a *phone* (product), we strictly sell some hardware only |
| 18:25.02 | DocScrutinizer05 | it turns into a phone only when user installs according software of his liking to it |
| 18:25.38 | DocScrutinizer05 | just like a beagleboard is no html-webserver |
| 18:26.02 | DocScrutinizer05 | you can turn it into one by installing linux and apache |
| 18:27.44 | DocScrutinizer05 | in that sense original early state of FSO was a BSP for GTA02 |
| 18:28.29 | DocScrutinizer05 | it came with a cheesy dialer and some tools |
| 18:28.47 | DocScrutinizer05 | wasn't meant for end customers for daily usage |
| 18:29.54 | DocScrutinizer05 | and of course it shipped FSO middleware. Which been it's main purpose |
| 18:30.04 | DocScrutinizer05 | its* |
| 18:31.00 | DocScrutinizer05 | I'd love to do exactly same for Neo900, with FSO, together with Mickey maybe :-) |
| 18:32.19 | DocScrutinizer05 | though I guess you're competent and eager to implement such FSO based BSP on your own |
| 18:32.54 | DocScrutinizer05 | maybe with a little help on kernel driver level, where needed (CRTOUCH, sensors, etc) |
| 18:36.02 | DocScrutinizer05 | one of those posts on reddit was pretty brillliant to the point regarding all the "doesn't ship with hardware" topic |
| 18:37.31 | DocScrutinizer05 | >>The Neo900 concept, on the other hand, are simply FSF/Linux ideals turned into a cell phone. Complete openness and decoupling software from hardware. They want a device that is just like a PC. Put in a bootloader and run whatever OS you like. Awesome.<< https://www.reddit.com/r/linux/comments/2lr90t/til_that_there_is_a_completely_open_and/clxl1vy |
| 18:41.07 | DocScrutinizer05 | dos1: how about simply quoting the above post on neo900.org frontpage? |
| 18:41.47 | DocScrutinizer05 | couldn't have put it better |
| 18:43.44 | *** join/#neo900 wazrus (~wazrus@host17-187-dynamic.21-87-r.retail.telecomitalia.it) |
| 18:51.41 | pigeons | love the tangental argument on which laptop rms uses |
| 18:55.41 | DocScrutinizer05 | hehe >> My brother is one of those N900 users, and I get the feeling you can pry the N900 from his cold, dead hands (he has a second spare one in case his current one dies). I used his N900 for a few weeks as my primary phone, and I found it slow, cumbersome, frustrating, heavy, and generally unpleasant to use - yet I still loved messing around with it, since it felt like using a real computer, instead of a locked-down, idiot-proof " |
| 18:55.42 | DocScrutinizer05 | smart"-phone.<< http://www.osnews.com/story/27545/From_Providence_to_Lahaina_the_Jolla_review -- a worthwhile read |
| 19:00.36 | ds2 | heh... I cansay the same thing about most current android devices :D |
| 19:02.12 | ds2 | maybe change it down right unpleasant to use |
| 19:10.24 | DocScrutinizer05 | haha http://www.heise.de/newsticker/meldung/SSL-abhoeren-Kritik-an-BND-Plaenen-zu-Zero-Day-Exploits-2445246.html (german!) |
| 19:16.32 | kerio | ds2: no way man |
| 19:16.34 | kerio | android is linux |
| 19:16.40 | kerio | it's free |
| 19:16.49 | kerio | didn't you hear |
| 19:17.03 | pigeons | well its mostly open source, dont know bout free |
| 19:17.04 | ds2 | :) |
| 19:17.19 | ds2 | you mean free like "enter a drawing now" and get a lifetime of spam? :D |
| 19:19.42 | ds2 | but free don't matter |
| 19:19.52 | ds2 | the UI is downright unpleasant to us |
| 19:19.55 | ds2 | e |
| 19:20.11 | ds2 | requires too many taps to do things. not as win8 but bad enough |
| 19:21.14 | pigeons | its annoying to worry about bionic libc compatability too |
| 19:21.38 | *** join/#neo900 nox- (noident@freebsd/developer/nox) |
| 19:21.43 | ds2 | I don't see that as too bad |
| 19:21.57 | ds2 | but then I am used to dealing with libc of the day (uClibc/glibc/etc) |
| 19:22.12 | ds2 | if anything bionic, IMO, is a good thing that should be used in more projects |
| 19:32.12 | Wizzup | not musl? |
| 19:33.20 | Wizzup | musl++ |
| 19:51.29 | bencoh | is bionic actually usable for real posix stuff now ? |
| 19:51.41 | bencoh | I remember it having crippled pthread support |
| 20:10.50 | pigeons | it has pthreads, no pthread__atfork(), no cancellation, etc |
| 20:27.24 | *** join/#neo900 jonwil (~jonwil@27-33-80-219.tpgi.com.au) |
| 20:50.16 | *** join/#neo900 sparetire_ (~sparetire@unaffiliated/sparetire) |
| 21:04.10 | Pali | bios is and was not usable for real suff |
| 21:04.11 | Pali | s/bios/bionic/ |
| 21:04.25 | Pali | bios (as int api) too :D |
| 21:39.59 | *** join/#neo900 j4s0nmchr1st0s (~Thunderbi@172.56.10.89) |
| 21:47.06 | *** join/#neo900 unclouded (~neil@2001:4428:200:80fc:7e05:7ff:fe0d:d421) |
| 21:50.07 | *** join/#neo900 norly (~norly@enpas.org) |
| 22:10.59 | Oksana | I am not interested in registering at FB, reddit, google+, twitter, whatever, generally. But my preferred method is flooding the system with irrelevant information, when I have time to bother with it. |
| 22:36.17 | DocScrutinizer05 | I just tested a blue LED since we were interested in some properties of those, for another topic we just chew on. the results: 3V4 @ 10mA; 2V3 @ 0.02mA with already visible blue light. I guess for a red LED the current threshold for visibility is roundabout same, while voltage may be even lower. Neo900 probably will have quite a number of inexpensive simple diagnostic LEDs on power supply rails and signal lines, each consuming a max of |
| 22:36.19 | DocScrutinizer05 | 20µA |
| 22:37.33 | Oksana | Interesting. So no need to measure the currents and such when LEDs already tell you what is happening? |
| 22:37.45 | DocScrutinizer05 | yep, that's the idea |
| 22:38.26 | DocScrutinizer05 | "what the heck, why is this thing still sending an IRQ signal while it should already be shutdown?" |
| 22:38.37 | Oksana | :-) |
| 22:39.03 | DocScrutinizer05 | "why does CPU take 5s to react on a RING signal sent from modem?" |
| 22:39.41 | DocScrutinizer05 | "why is master system clock running all the time, despite CPU supposed to be in zero-clock?" |
| 22:41.05 | DocScrutinizer05 | "Thanks, dear customer, for this bug report. Could you please tell us if the LED marked "E5" in figure 9 of your manual is showing dim light or not?" |
| 22:42.33 | DocScrutinizer05 | even "please make a photograph of the device in a completely dark room without flashlight, and send this picture. Thanks!" |
| 22:42.39 | Oksana | :-) Great customer support. |
| 22:44.46 | DocScrutinizer05 | LEDs and resistors are cheap, and small |
| 22:45.16 | DocScrutinizer05 | and now we know they also don't necessarily consume worrying amounts of power |
| 22:46.40 | DocScrutinizer05 | of course it's my task as EE and architect to place those LEDs in a way so they usually are off and only light up in the exception-case |
| 22:47.14 | DocScrutinizer05 | for everything except power rails this shouldn't be a problem |
| 22:48.02 | pigeons | mozilla is advocating for the clear cases too http://www.theguardian.com/technology/2014/nov/10/mozilla-transparency-iphone-android-smartphones |
| 22:48.17 | DocScrutinizer05 | system clock generator enabled already eats a few milliAmpere, so a few more microAmpere won't hurt |
| 22:48.40 | DocScrutinizer05 | pigeons: hehe |
| 22:48.59 | DocScrutinizer05 | now with LED concept, I can't help but hoining in ;-) |
| 22:49.10 | DocScrutinizer05 | joining, even |
| 22:49.10 | ds2 | how much are blueleds in volume? |
| 22:49.39 | DocScrutinizer05 | LEDs are generally a few cent... a dozen |
| 22:49.42 | j4s0nmchr1st0s | Are the iphones well designed? |
| 22:50.02 | DocScrutinizer05 | no, since they have the wrong name printed on body |
| 22:51.46 | ds2 | thought that was only non blue/white? |
| 22:52.44 | DocScrutinizer05 | http://www.digikey.com/product-detail/en/LTST-C190KFKT/160-1434-2-ND/386813 |
| 22:52.59 | DocScrutinizer05 | we don't need to use blue |
| 22:53.08 | ds2 | ah |
| 22:54.35 | j4s0nmchr1st0s | DocScrutinizer05: The name iphone? |
| 22:54.35 | DocScrutinizer05 | blue, for you :3 http://www.digikey.com/product-detail/en/LTST-C191TBKT/160-1647-2-ND/388530 |
| 22:55.58 | DocScrutinizer05 | seems for 3 bucks we could get a 50 |
| 22:56.25 | DocScrutinizer05 | not that I'm expecting to find use for 50 diagnostic LEDs in Neo900 |
| 22:57.02 | DocScrutinizer05 | so make that 25 per device for 1,50 bucks |
| 22:57.49 | DocScrutinizer05 | we can kick them out any time, to make device 2 EUR cheaper, for mass production ;-) |
| 22:58.27 | ds2 | do you want to annoy the PnP programmer by changing your BOM? ;) |
| 22:58.38 | DocScrutinizer05 | the what? |
| 22:59.00 | DocScrutinizer05 | pick&place? |
| 22:59.06 | DocScrutinizer05 | no isse |
| 22:59.09 | DocScrutinizer05 | issue |
| 23:00.35 | ds2 | pick and place guy |
| 23:00.46 | *** join/#neo900 norly (~norly@enpas.org) |
| 23:00.52 | DocScrutinizer05 | I doubt there's much manual work involved, except for applying a offset tuning patch to new gerber from last run |
| 23:01.42 | DocScrutinizer05 | unless you move components around on PCB, in which case you obviously need to readjust the placement |
| 23:02.02 | DocScrutinizer05 | or at least check if it needs adjustment |
| 23:02.42 | ds2 | it should as simple as uncommenting the part that stuffs it but... |
| 23:03.08 | DocScrutinizer05 | it actually is even simpler, you set a flag for a variant in eagle |
| 23:04.08 | DocScrutinizer05 | then generate new Gerber from that, then apply offset adjustment patch to that as mentioned above, and done you are |
| 23:04.30 | DocScrutinizer05 | basically a press of two buttons |
| 23:05.06 | ds2 | you doing it on the PCB level... |
| 23:05.25 | ds2 | i was referring to just not stuffing it by asking the PnP operator to DNP the LED + resistor |
| 23:09.38 | DocScrutinizer05 | can't be done since they are used in several positions, we probably don't use sequenced tape P&P |
| 23:10.12 | DocScrutinizer05 | unless we run short of slots for components on the P&P machine |
| 23:10.52 | DocScrutinizer05 | if that happens, we would need to make specially sequenced tape, also quite silly |
| 23:10.54 | freemangordon | jonwil:hi! Any progress on that big mysterious structure? |
| 23:11.32 | DocScrutinizer05 | (silly) making special tape with empty positions that is |
| 23:12.25 | freemangordon | jonwil: just curious, not that I am trying to put pressure on you :) |
| 23:12.48 | freemangordon | BTW there are 3 more functions and xprot will be ready |
| 23:12.56 | DocScrutinizer05 | \o/ |
| 23:13.13 | freemangordon | yeah, though those re like spaghetti |
| 23:13.17 | freemangordon | *are |
| 23:13.32 | freemangordon | but still doable |
| 23:14.02 | Oksana | Silly off-topic question: most dialogs have two, at most three buttons. Like, Yes-No-Cancel. Why cannot it be done with one software button and two-or-three mouse buttons? Left=Yes, Right=No, Middle=Cancel? |
| 23:14.25 | freemangordon | Oksana: ever seen fremantle? |
| 23:15.11 | Oksana | Yes... |
| 23:15.20 | Oksana | It does not have mouse? |
| 23:15.39 | freemangordon | well, then you should have know things can be done some other way |
| 23:15.41 | freemangordon | sure |
| 23:15.48 | freemangordon | well, not really |
| 23:15.54 | freemangordon | it can have mouse |
| 23:16.31 | Oksana | But it would be cumbersome for walk-use outdoors. |
| 23:17.03 | bencoh | :D |
| 23:17.05 | Oksana | And even with dual-touch you could imitate two mouse buttons, at most: one finger or two fingers. |
| 23:18.00 | freemangordon | anyway, there you have the needed buttons to take the actions and you click outside of the "dialog" for cancel. not exactly what you want, but IMO it is more sane. what if you need a context menu, what you should do in your UI, click-n-hole the right button? |
| 23:18.17 | freemangordon | *hold |
| 23:19.10 | freemangordon | it is obvious that I am old-fashioned, but n-touch is too complicated for me :) |
| 23:19.47 | freemangordon | I simply can't grok the multi-touch paradigma |
| 23:20.09 | DocScrutinizer05 | I'd often prefer push&drag buttons, kinda like lockscreen slider, just with more than one dimension/direction |
| 23:20.19 | freemangordon | anyway, /me is going afk |
| 23:20.26 | DocScrutinizer05 | too |
| 23:23.29 | Oksana | Alright :-) I was just struggling with desktop. When mouse auto-jumps to default dialog button, and I want to click No instead of Yes, it makes sense to wish for one unified dialog button, with three different actions tied to three mouse buttons. |
| 23:24.25 | Oksana | Clicking outside of dialog for cancel makes sense, especially for one-window interface (such as Fremantle). |
| 23:26.40 | DocScrutinizer05 | for desktop I'd consider it a *really* *really* useful concept when unsolicited popup requesters would get delayed (at least they focus grabbing) until you stop typing on kbd for at least 1500ms |
| 23:27.09 | DocScrutinizer05 | of course that last value should be adjustable by user, just like speed of doubleclick |
| 23:27.41 | Oksana | That's not unsolicited popup. :-) That's Close with saving, Close without Saving, Cancel Closing dialog. |
| 23:28.05 | Oksana | And I have to go through repetitive motions (including this dialog) a lot of times. |
| 23:28.37 | DocScrutinizer05 | I can't count how often I typed in an incorrect new password instead of keeping the already pre-populated old one, when kmail suddenly pops up a requester informing me about "authentication to POP3 server XYZ failed! Please enter correct user name and password!" |
| 23:29.52 | DocScrutinizer05 | ever thought about using hotkeys for those "close, save, cancel" requesters? |
| 23:30.03 | Oksana | Hmm... Cannot it use some kind of tray-tooltip, with textfield included? |
| 23:30.20 | Oksana | Hotkeys? Like, arrow right, space? |
| 23:30.52 | DocScrutinizer05 | like enter, escape, "alt-S" |
| 23:31.05 | Oksana | I mean, I have a program which persistently shows a tooltip from its tray. It's highly visible, yet it does not steal focus or stop you from typing anything else. |
| 23:31.37 | DocScrutinizer05 | afk, cya |
| 23:31.47 | Oksana | If such tooltip included textfields with pre-populated usename and password, it would not steal focus. |
| 23:32.01 | Oksana | Good night :-) |
| 23:32.42 | *** join/#neo900 watchman_ (6023bd0c@gateway/web/freenode/ip.96.35.189.12) |
| 23:33.54 | jonwil | no progress on pulseaudio, no |
| 23:35.46 | *** join/#neo900 wazrus (~wazrus@host17-187-dynamic.21-87-r.retail.telecomitalia.it) |
| 23:40.32 | DocScrutinizer05 | orange LED: 1,5V 1uA non visible. 1,6V 11uA visible. 1,7V 59uA clearly brightly visible |
| 23:43.14 | Oksana | Visibility: in bright sun or in dark room? |
| 23:43.39 | DocScrutinizer05 | in dimmed room of course |
| 23:44.56 | DocScrutinizer05 | in bright sun not even LCD backlight at blasting full power of 9V6@36mA is visible |
| 23:45.41 | Oksana | :-) |
| 23:49.34 | DocScrutinizer05 | a device with 25 of such LEDs shining all the time would deplete a standard BL-5J battery from full to empty in as short as >100 days |
| 23:50.03 | DocScrutinizer05 | 110 actually |
| 23:50.29 | DocScrutinizer05 | hardly any issue regarding maximum standby time, eh? |
| 23:51.28 | DocScrutinizer05 | ~25*0.08 |
| 23:51.28 | infobot | 2 |
| 23:51.43 | DocScrutinizer05 | already two bucks for 25 LEDs |
| 23:52.19 | DocScrutinizer05 | real estate (assuming the R's are as big as those LEDs): |
| 23:52.35 | DocScrutinizer05 | ~0.8 * 1.6 * 2 |
| 23:52.35 | infobot | 2.56 |
| 23:52.48 | DocScrutinizer05 | ~2.56 * 25 |
| 23:52.48 | infobot | 64 |
| 23:53.01 | DocScrutinizer05 | 8 x 8 mm area |
| 23:53.34 | DocScrutinizer05 | ok, i cheated a little since you can't pack them without any gaps between |