**** BEGIN LOGGING AT Tue Nov 17 02:59:58 2015 Nov 17 04:27:55 interesrting bencoh. i never once got a reboot from that Nov 17 04:28:09 klopsi-u3: i do need FM tx Nov 17 09:56:12 hi Nov 17 10:15:38 wouldn't anyone know of an electronics parts management software? Nov 17 10:15:42 kind of an inventory Nov 17 10:16:17 spreadsheet? Nov 17 10:16:32 something on which several people can work on Nov 17 10:16:39 so, probably something web based Nov 17 10:16:42 google spreadsheet? Nov 17 10:17:16 don't like that much Nov 17 10:17:29 there's this thing, partkeepr Nov 17 10:17:32 you can always write one from a scratch in php Nov 17 10:17:35 but it's a bit complex Nov 17 10:17:45 i wanted something inbetween Nov 17 10:17:54 not just a spreadsheet but also not a monstrosity :) Nov 17 12:14:40 http://www.techamok.com/?pid=16699 Nov 17 12:14:41 lol Nov 17 12:14:44 bme is not that bad Nov 17 12:15:03 though few times my n900 also hung after all-niter Nov 17 21:42:56 6 days uptime .. was just doing something in gnumeric and system has hung :( Nov 17 21:43:07 forced reboot incoming, i guess. Nov 17 21:50:08 watchdog hasn't kicked in yet .. ssh disconnected Nov 17 21:50:23 and power button not helping Nov 17 21:52:10 :/ Nov 17 21:58:08 recovered :) Nov 17 21:58:22 *without reboot, that is Nov 17 22:50:00 hmm ... is there a good reason why we dont have hostapd in -extras? Nov 17 22:58:09 is our chip supported? Nov 17 22:59:42 and will we have enough processing power and memory for it? Nov 17 23:00:31 hmm Nov 17 23:01:21 but it sure would be nice to have Nov 17 23:01:28 looks like TI worked on hostapd+wl12xx Nov 17 23:02:18 and they have some hostapd accesspoint examples on their wiki Nov 17 23:04:22 Note: There is a different firmware file for station and for access-point modes. Make sure you pick the right one (or both). http://linuxwireless.sipsolutions.net/en/users/Drivers/wl12xx/ Nov 17 23:04:26 I dont like that Nov 17 23:08:13 perhaps you can build in SB :) Nov 17 23:10:35 build hostapd? probably, but what I'm worried about is the need to change firmware, and possibly NVS calibration Nov 17 23:11:01 even though we could load a different firmware since we keep loading/unloading wireless drivers in maemo Nov 17 23:12:11 i think so Nov 18 00:57:04 calib and firmware are two independent things Nov 18 00:57:29 and iirc the calib tools are even available on same site as the firmware Nov 18 00:57:57 what sucks is closed blob firmware, but that's life Nov 18 01:56:13 Its a pitty we dont have an Atheros chip in there to play with Nov 18 01:56:33 if https://www.youtube.com/watch?v=pO7Y_241cyo is to be believed, they are extremely well documented and open Nov 18 02:17:59 jonwil: have you checked size and power rating? And interface Nov 18 02:18:10 yeah true :) Nov 18 02:19:35 Neo900 / Openphoenux searched for years and in the end it's WiLink each single time Nov 18 02:21:15 there might be smaller chips, also maybe cheaper chips. But invariably it's about open documentation and source-ability Nov 18 02:21:57 so in the end WiLink 5/6/7/8 nine e1even thirwelve Nov 18 02:24:56 many of those extremely open and versatile chips are actually "stack runs on system CPU", something you really don't want for a battery powered embedded system Nov 18 02:30:08 true Nov 18 02:30:41 compare to ancient cheap printers, where the windows CPU did each phase of the stepper motors and shaped each pulse of each single needle Nov 18 02:31:28 I know various Snapdragon chips contain Atheros bits in there, I wonder if Atheros is as open with the WiFi parts of those as they are with their standalone WiFi chips... Nov 18 02:32:07 when I hear snapdrogon I turn and leave Nov 18 02:32:51 whats wrong with Snapdragon? Nov 18 02:33:00 I don't think i've seen a Snapdragon SoC that would work without *massive* blobs for bootloader or whatever Nov 18 02:33:06 oh ouch Nov 18 02:33:27 I wonder why Qualcomm would want to be so closed about that stuff Nov 18 02:35:51 isn't qualcom a synonym for "closed blobs"? Nov 18 02:36:58 It wouldn't surprise me if a number of the vendors who use Snapdragon SoCs LIKE the fact that everything is closed and you have to go through the vendor to get any updates to drivers etc Nov 18 02:37:21 I know lots of Android vendors would rather not share anything because then people can run newer versions of Android on older devices Nov 18 02:37:33 Or even just custom versions of Android that dont have all the usual OEM/carrier bloatware Nov 18 02:37:53 In any case Neo900 has to use OMAP3 chips to be compatible with N900 Nov 18 02:38:08 and we have to use whatever limited documentation on the OMAP stuff we can find Nov 18 02:38:23 plus whatever binary GPU blobs we can get Nov 18 02:40:40 ((wouldn't surprise)) yep, most do Nov 18 02:41:21 docs on OMAP are pretty comprehensive Nov 18 02:41:35 and nicely public Nov 18 02:42:21 so other than the GPU are there any other things in the particular OMAP chip we are using that are undocumented but where having documentation would be of potential benefit to Neo900? Nov 18 02:42:41 or is everything else worth knowing documented in the OMAP tech docs? Nov 18 02:44:31 no Nov 18 02:44:46 yes Nov 18 02:44:54 :) Nov 18 02:45:17 Do we have all the stuff worth having in regards to the DSP parts? Nov 18 02:45:36 for the GP devices afaik every bit of info is publicly available (well, except exact bytecode of ROMBOOT) Nov 18 02:46:17 hmm, I think DSP is a tad thin but docs should be available, maybe from gray market / darknet Nov 18 02:47:17 then OTOH this series of TI DSPs is legendary and age old, and I guess they are all somewhat similar. But I have to admit I never looked into them Nov 18 02:48:34 would be surprised if there wasn't a well documented assembler for those DSP cores Nov 18 02:49:33 TMS320 series Nov 18 02:49:52 yeah true Nov 18 02:50:19 sounds like the PowerVR core is the only part of the OMAP chip that is undocumented then Nov 18 02:50:31 and even if it was documented we wouldn't want to write our own GPU driver anyway Nov 18 02:50:37 we would still want to use something that exists Nov 18 02:51:49 https://en.wikipedia.org/wiki/Texas_Instruments_TMS320C6400 Nov 18 02:52:59 http://www.ti.com/lit/an/spra396/spra396.pdf Nov 18 02:55:24 The biggest missing piece of the puzzle for Neo900 has nothing to do with the OMAP anyway, its the blobs we need for the audio :) Nov 18 02:58:13 I think we could do without, worst case Nov 18 02:59:43 The main problem there is finding someone with enough knowledge of ARM reverse engineering to finish the job of reverse engineering the blobs (that or the source code for the blobs falling out of the sky somehow :) **** ENDING LOGGING AT Wed Nov 18 02:59:59 2015