**** BEGIN LOGGING AT Mon Aug 27 03:00:00 2018 Aug 27 07:01:50 Jasu_M:awesome! I rally need an FTDI cable now :) Aug 27 07:17:16 Kero: I built mine from an old FTDI adapter I had, I soldered a female USB-A (usb 1.0/2.0) connector to it, and then just used a regular USB3 cable Aug 27 07:19:32 not at home: I don't think I have anything ftdi. I'm sure I don't have more USB-C than the cable I receuved with my Gemini Aug 27 07:20:49 well, usb-to-serial adapters are dirt cheap. And it really doesn't have to be FTDI, but it needs to support 921600 baud Aug 27 07:22:30 true. perhaps I sho Aug 27 07:22:59 (I hit enter on my gemini sometimes when I aim for backspace...) Aug 27 07:25:19 ha :P I haven't so far used the gemini's keyboard that much, I only wrote a shell script to download and flash my latest build Aug 27 07:25:51 and named it "a" so I only have to type a to flash it. And I also changed the default password to "a" Aug 27 07:26:10 I really haven't used the thing for anything yet Aug 27 07:42:11 trying to use it as much as possible :) Decent companion on the road - running Android. Aug 27 07:47:43 Jasu_M: it looks like your pulling 4.17.19 for your kernel work, someone here mentioned that 4.19 had some good things for us (still rc1), any particular reson for not picking 4.18.5? Aug 27 07:48:11 It's 4.18.5, buildroot pulls kernel headers for 4.17.19, since it doesn't yet support newer Aug 27 07:48:16 i.e. userspace is built against 4.17.19 Aug 27 07:48:27 ahh interesting Aug 27 07:48:51 I'm planning to apply the patchsets from 4.19 (or mediatek for-next) manually, since 4.19 moves currently super fast Aug 27 07:49:51 sounds good, are your patches going to be pushed upstream? or are they not relevant to other users of the same chip Aug 27 07:50:13 I'm going to send the CLK patch maybe today Aug 27 07:50:28 the SCPSYS patch still requires work, as MFG (Mali) power domain initialization fails Aug 27 07:50:51 it might be that the MFG power domain has to be made into a separate driver, since there's so much stuff going on that's not directly related to SCPSYS Aug 27 07:51:02 sounds like you properly know what your doing : ) Aug 27 07:51:31 nah, this is the first time I've written any kernel code Aug 27 07:51:59 well you've at least studied it enough to bluff your way through Aug 27 07:52:07 that's how I roll Aug 27 09:55:08 ok, ordered some usb serial stuff. Should arrive on my birthday ;) Aug 27 09:56:56 Jasu_M: I don't think I need to build the cross-compile toolchain (already got one, built a mainline kernel, dumped it on the gemini and then saw nothing, of course; but no spontaneous reboot, either, which I interpret as bootloader-saw-a-kernel-and-tried-to-boot) Aug 27 09:59:05 I guess I'm mostly interested in patches and the .config file Aug 27 10:03:00 mm, I think I can find that from your buildroot repo. Aug 27 10:04:17 Jasu_M: Quite an extensive documentation :O Aug 27 10:05:14 Jasu_M: friend of mine is trying to build LittleKernel, did you have to do that, or is the bootloader just fine with that mainline kernel? Aug 27 11:06:31 Kero: I'm using the default bootloader Aug 27 11:06:40 the LK release from Planet is out of date Aug 27 11:06:46 it doesn't support the multi-boot things, I think Aug 27 11:07:54 You can configure buildroot to use an external toolchain with make menuconfig, but it doesn't work with just an aarch64 gcc+binutils, it requires something that allows chrooting into a full cross-compiler environment, like Linaro or something Aug 27 11:08:26 configs are under board/ Aug 27 11:08:49 the linux config has nothing super special in it though, the boot command line forcing is the most important one I think Aug 27 11:09:27 Jasu_M: they released updated lk a few days ago (its all in branches though so you might not notice) Aug 27 11:09:29 the DTS might be more interesting though, and the create boot image script, as it adds the required extra space in the DTB Aug 27 11:10:11 adam_b: nice! I've been looking at a local copy I made over a week ago Aug 27 11:10:27 hat's the chroot necessary for? Aug 27 11:11:30 dts, sure. There is one for mt6797 in mainline (found it when preparing my blank-screen boot.img for 4.18.4, yesterday) Aug 27 11:12:27 but I have zilch experience with DTS's, so I'm kinda hoping it's limited to the SoC and we need no adjustments for Gemini Aug 27 11:12:52 otoh, it might be the reason to learn about dts and dtb (and dive deeper into hardware stuff) Aug 27 11:19:38 no idea, that's imposed by buildroot Aug 27 11:22:26 https://buildroot.org/downloads/manual/manual.html see 6.1.2. External toolchain backend, but it isn't super informative Aug 27 11:26:08 I'm guessing to create rootfs's Aug 27 11:30:55 shouldn't be in the way of building a kernel. But I can only see that once I can get to my cables. Fri/Sat. Aug 27 11:41:10 in theory, what components are needed before either adapting current mainline DRM driver or forward-porting MediaTek's video driver could be attempted? Aug 27 11:54:13 I think it'll need M4U, SMI, DRM, panel driver. I think that adapting the mainline will be easier than porting the Android driver, it's kind of a mess Aug 27 11:54:39 panel driver might not even be necessary at first, as bootloader leaves the display initialized Aug 27 12:08:15 and scpsys is missing the DISP power domain, but it's probably left on by the bootloader Aug 27 15:18:00 trying to set up mobile data-use under debian (https://github.com/gemian/gemini-keyboard-apps/wiki/DebuggingMobile ) Aug 27 15:38:02 I got to up to (and including) `ofono-setup` without errors so far. After that one I get "Could not retrieve the ril mute state" https://paste.debian.net/1039521/ Aug 27 16:37:12 tobra: did you restart the device after adding the user/group stuff? (its not written there but might be needed) Aug 27 16:37:43 also do you have a pin on your sim? (I never tested that) Aug 27 16:38:38 depscribe: you got a second Gemini? and did you never turn it on in android before flashing sfos/debian? Aug 27 16:52:11 adam_b : i looked at android a time or two, but i never had a SIM card in it at the time, and didn't put the SIM card in until after i'd flashed linux-sfos only. Aug 27 16:52:23 carrier is tmobile. Aug 27 16:52:46 and no, only the one gemini. Aug 27 16:52:50 depscribe: yea that might have been enought though, need to find someone who had the problem I guess Aug 27 16:53:13 depscribe: thought you had one early enought to have been an x25 user Aug 27 16:53:28 the only android reference to a SIM card when i booted it was that there wasn't one installed. Aug 27 16:53:58 yea but the complaint from x27 folks was that if they never booted into android they couldnt get sim stuff to work in sfos Aug 27 16:54:25 i'd brought over my contacts on the SIM and specifically didn't want to give androis/google access to them. Aug 27 16:54:37 androis=android Aug 27 16:54:51 well I commented on the wiki that it may or may not be the case Aug 27 16:55:03 nah. order #6993. Aug 27 16:55:42 right. was just noting that that wasn't my experience, though i was concerned it might be. Aug 27 18:16:07 * keithzg[m] 's problem with the SIM card is that he doesn't have even the ability to put one in but neither Android nor SailfishOS seem to quite understand that :P Aug 27 19:19:54 keithzg[m], maybe you could solder it somehow :) Aug 27 19:20:55 NeKit: Hehe Aug 27 21:21:20 You know you're all compromised with the baseband radio anyway, so avoiding google/android isn't really much Aug 27 21:21:39 Hayes AT command set in every smartphone is full of vulns. Aug 28 00:24:37 There's still plenty of point. You're only excusing your own laziness. Also consider the fact that Android is not very pleasant to use compared to GNU/Linux. Aug 28 02:31:17 don't those vulnerabilities require usb access? **** ENDING LOGGING AT Tue Aug 28 03:00:02 2018