--- Log opened Sun Jan 21 00:00:04 2018 00:05 -!- Horwitz [~mich1@p200300800E2E3300022268FFFE64E7C4.dip0.t-ipconnect.de] has quit [Ping timeout: 256 seconds] 00:13 #navit: <@KaZeR> ilovekiruna: ha? 00:18 -!- Horwitz [~mich1@p200300800E3A4400022268FFFE64E7C4.dip0.t-ipconnect.de] has joined #navit 00:18 -!- mode/#navit [+o Horwitz] by ChanServ 00:19 #navit: <+ilovekiruna> ha? 00:20 #navit: <+ilovekiruna> we ofc also need to change the header file 00:20 #navit: <+ilovekiruna> but still i dont get why only linux fails 00:26 #navit: <@KaZeR> "i understand the issue i think" so i wondered what you found :) 02:20 -!- Celelibi [celelibi@par69-9-88-166-81-29.fbx.proxad.net] has joined #navit 02:34 -!- jeremy_ [~jeremy@rla39-h01-176-133-215-10.dsl.sta.abo.bbox.fr] has joined #navit 02:35 -!- jeremy_ is now known as Guest2670 02:38 -!- youte [~jeremy@rla39-h01-176-133-215-10.dsl.sta.abo.bbox.fr] has quit [Ping timeout: 256 seconds] 03:36 -!- xenos1984 [~xenos1984@b133.tll.aero] has joined #navit 03:36 -!- mode/#navit [+v xenos1984] by ChanServ 03:48 -!- xenos1984 [~xenos1984@b133.tll.aero] has quit [Quit: Leaving.] 04:17 -!- noradtux [~noradtux@port-6055.pppoe.wtnet.de] has quit [Ping timeout: 256 seconds] 04:18 -!- noradtux [~noradtux@2a02:2028:723:9501:ec4:7aff:fe33:3dc1] has joined #navit 09:32 -!- Guest2670 is now known as youte 09:33 -!- mode/#navit [+v youte] by ChanServ 10:23 -!- pini [~pini@bou-fi.pustule.org] has joined #navit 11:31 -!- xenos1984 [~xenos1984@88.128.82.163] has joined #navit 11:31 -!- mode/#navit [+v xenos1984] by ChanServ 11:42 -!- xenos1984 [~xenos1984@88.128.82.163] has quit [Quit: Leaving.] 12:57 #navit: <+ilovekiruna> ping youte 13:47 -!- Mineque [~Mineque@public-gprs206877.centertel.pl] has joined #navit 13:57 #navit: <+ilovekiruna> hi all 14:01 #navit: < pmckinley> hi 14:02 #navit: <+jkoan> Hi ilovekiruna 14:02 #navit: <+jkoan> Hi pmckinley 16:33 #navit: <+youte> ilovekiruna, 17:07 #navit: <+jkoan> hi youte 17:22 -!- youte [~jeremy@rla39-h01-176-133-215-10.dsl.sta.abo.bbox.fr] has quit [Read error: Connection reset by peer] 17:22 -!- youte [~jeremy@rla39-h01-176-133-215-10.dsl.sta.abo.bbox.fr] has joined #navit 17:46 #navit: <@KaZeR> jo tjere 17:46 #navit: <@KaZeR> uh 17:46 #navit: <@KaZeR> hi there 17:48 #navit: <+jkoan> hi KaZeR 17:49 #navit: <+jkoan> KaZeR: now i have chroot on the NavitTom. it was only deactivated :D 17:50 #navit: <+jkoan> current work is going to switch from OpenTom to Buildroot or at least figure out if it is possible. i understand more and more how buildroot is working, if i manage it we will have a defconfig for it soon 17:55 #navit: <@KaZeR> jkoan: nice! 17:55 #navit: <@KaZeR> buildroot is really nice. that's how i build the image for my car 17:55 #navit: <@KaZeR> what base config are you using (for the board)? 17:56 #navit: <@KaZeR> i have a custom package for navit : https://github.com/pgrandin/navit-buildroot/tree/cherokee/packages/navit 17:57 #navit: <+jkoan> now the most complex path could be the convert to the initramdisk and the linux kernel image to the ttsystem file, but i try my best ;) 17:59 #navit: <+jkoan> i am not on the point to ren applications on buildroot. right now the first step is to write the new buildroot defconfig and be able to compile the kernel 17:59 #navit: <@KaZeR> what's the base of your work around buildroot? if you find a profile, it probably also generate the correct image at the end via a post-image script 17:59 #navit: <@KaZeR> ha, so everything from scratch 17:59 #navit: <@KaZeR> ok 18:00 #navit: <+jkoan> yes, i will probably need to add ttimagetools (https://github.com/navit-gps/NavitTom/tree/master/src/tools/ttimage_tools) as a host package and use it as a post script, so i get out the real ttsystem file 18:01 #navit: <+jkoan> but first little steps 18:02 #navit: <+jkoan> nice thing about buildroot will be the sd image feature, i can generate a image file with partitions in it easily 18:02 #navit: <@KaZeR> exactly 18:05 #navit: <+jkoan> so as i told you yesterday in the private chat the image could have a first partition formatted with fat (needed by tomtom) a second for the system and a last one would become the maps partition 18:07 #navit: <+jkoan> inside the first one would be the ttsystem with the initramfs which is only booting into the second partition. there the real system could nicely run and the 3. has enough space to have the whole planet.bin :) 18:07 #navit: <+jkoan> good plan? 18:10 #navit: <@KaZeR> yep 18:21 #navit: <+ilovekiruna> youte: and news about logo and stuff? 18:21 #navit: <+jkoan> hi ilovekiruna 18:21 #navit: <+ilovekiruna> hi jkoan 18:23 #navit: <+ilovekiruna> KaZeR: can we proceed with the PR? 18:27 #navit: <+ilovekiruna> what is left? 18:40 #navit: <@KaZeR> hi ilovekiruna 18:40 #navit: <@KaZeR> let me have another look 18:51 #navit: <@KaZeR> your doxygen comments are missing the return doc. random example : https://github.com/navit-gps/navit/blob/trunk/navit/navit.c#L236 18:53 #navit: <@KaZeR> "sprintf(command,"./contraction-hierarchies-20080621/main " wtf is that... (not you, just discovered that :) ) 18:53 #navit: <+ilovekiruna> no clue 18:53 #navit: <+ilovekiruna> where is that? 18:54 #navit: <@KaZeR> ch.c around line 230 18:54 #navit: <@KaZeR> i doubt that this code is still useful 18:55 #navit: <+ilovekiruna> seems for winCE 18:55 #navit: <+ilovekiruna> but no clue :( 18:55 #navit: <@KaZeR> in maptool.c, i'd avoid declaring a write_result variable, and just wrap the check in a if () 18:55 #navit: <@KaZeR> actually i think it's for not WinCE :) 18:56 #navit: <@KaZeR> it's a ifndef 18:56 #navit: <+ilovekiruna> ah, yeah 18:56 #navit: <+ilovekiruna> is the function called anywhere? 18:56 #navit: <@KaZeR> in tile.c, we should probably skip to the next iteration in the while loop too 18:56 #navit: <@KaZeR> we'll have to dig yeah 18:57 #navit: <+ilovekiruna> am checking already 18:57 #navit: <@KaZeR> in zip.c we probably need to return false also if the read failed, so also need to change the return type 18:57 #navit: <@KaZeR> thanks 18:57 #navit: <+ilovekiruna> nice that we have things like grep :D 18:58 #navit: <+ilovekiruna> linux ftw 18:58 #navit: <+ilovekiruna> grep just showed it in ch.c itself 18:59 #navit: <+ilovekiruna> and that only in the function ch_generate_tiles 19:00 #navit: <+ilovekiruna> u mean in zip_write_file_data? 19:20 #navit: <@KaZeR> zip_write_index 19:22 #navit: < youte> ilovekiruna, see to kazer for logo on tshirt, new? old??? i'l blocked 19:23 #navit: <+ilovekiruna> youte, the idea about old logo, was that we should give the new logo time, discuss properly 19:23 #navit: < youte> for me use old logo on tshirt is not a good idea 19:24 #navit: <+ilovekiruna> why? 19:25 #navit: <+ilovekiruna> I see just two options, 1. we can now rush with the logo to make the t-shirts or 2. dont make any t-shirts at this poing 19:25 #navit: <+ilovekiruna> point 19:26 #navit: <+ilovekiruna> remember jkoan and I are going to FOSDEM 3rd of feb 19:29 #navit: < youte> for logic, you show a logo, people rememeber logo, new logo, communication is 0 19:31 #navit: <+ilovekiruna> youte: so your conclusion it is better to go without our t-shirts or to rush with the new logo at the risk of not making a broad discussion? 19:32 #navit: <+ilovekiruna> for logic, i would say it is still better that people remember us as navit members, instead of we being just nobody in the crowd 19:32 -!- mode/#navit [+v youte] by ChanServ 19:33 #navit: <+ilovekiruna> and nobody would know that we were even there 19:46 #navit: <@KaZeR> i'd suggest sticking to the current logo then - i agree that having tshirts would definitely help being remembered 19:46 #navit: <+youte> pl 19:46 #navit: <@KaZeR> changing the logo on time to get the tshirts would need to really rush, and i don't really want to rush 19:52 #navit: <+youte> ok i work this night on design of teeshirt 19:54 #navit: <@KaZeR> afk 20:00 #navit: <+ilovekiruna> thanks youte 20:09 -!- pini [~pini@bou-fi.pustule.org] has quit [Ping timeout: 246 seconds] 20:24 #navit: <+youte> ilovekiruna, 20:24 #navit: <+youte> the format is only one face? 20:24 #navit: <+ilovekiruna> can be two faces, I guess, u mean front side and back side, right? 20:25 #navit: <+youte> 2 face 2 file? 20:25 #navit: <+youte> 2 file 297*420? 20:26 #navit: <+youte> the color of teeshirt is not on file? 20:27 #navit: <+ilovekiruna> yes two pages like that 20:27 #navit: <+ilovekiruna> what do you mean by color? 20:28 #navit: <+ilovekiruna> it should be in cmyk color format 20:28 #navit: <+ilovekiruna> and min 600 dpi 20:28 #navit: <+ilovekiruna> best I would still guess vector graphic 20:29 #navit: <+youte> 600 dpi ! 20:29 #navit: <+youte> it's very big 20:29 #navit: <+youte> the color pof tee shirt 20:31 #navit: <+youte> 29,7 x 42,0 cm (ohne Zusatzbeschnitt) mit einer Auflösung von 300 dpi. 20:32 #navit: <+ilovekiruna> I guess i know where you read it, somewhere else they mention 600 20:32 #navit: <+ilovekiruna> 300 is fine then :) 20:33 #navit: <+youte> in the website 20:34 #navit: <+ilovekiruna> youte: I read here: https://www.wir-machen-druck.de/tpl/manns-partner/media/ddb/druckdatenskizzen/t-shirt_mit_rundem_halsausschnitt__vorne_+_hinten_bedruckt_mit_ihrem_motiv_1.pdf 20:40 #navit: <+youte> ok hard hard lol 21:05 #navit: <+youte> KaZeR, you have a font of navit? 21:10 -!- youte [~jeremy@rla39-h01-176-133-215-10.dsl.sta.abo.bbox.fr] has quit [Read error: Connection reset by peer] 21:11 -!- youte [~jeremy@rla39-h01-176-133-215-10.dsl.sta.abo.bbox.fr] has joined #navit 21:14 -!- mode/#navit [+v youte] by ChanServ 21:20 -!- youte [~jeremy@rla39-h01-176-133-215-10.dsl.sta.abo.bbox.fr] has quit [Ping timeout: 256 seconds] 21:28 -!- youte [~youte@rla39-h01-176-133-215-10.dsl.sta.abo.bbox.fr] has joined #navit 21:29 -!- mode/#navit [+v youte] by ChanServ 22:02 -!- Mineque [~Mineque@public-gprs206877.centertel.pl] has quit [Quit: Leaving] 23:35 -!- j_f-f [~quassel@rs-7.jff-webhosting.net] has quit [Ping timeout: 264 seconds] 23:47 -!- j_f-f [~quassel@rs-7.jff-webhosting.net] has joined #navit --- Log closed Mon Jan 22 00:00:06 2018