**** BEGIN LOGGING AT Tue Oct 30 02:59:59 2018 **** BEGIN LOGGING AT Tue Oct 30 06:23:09 2018 **** BEGIN LOGGING AT Tue Oct 30 06:50:27 2018 **** BEGIN LOGGING AT Tue Oct 30 08:34:28 2018 Oct 30 09:39:19 hi ant_work Oct 30 09:39:27 hi greguu Oct 30 09:39:42 I am just building 4.19.0 for borzoi Oct 30 09:39:50 so far its the same as 4.14 Oct 30 09:40:05 issue with gpio (keypad) Oct 30 09:40:16 pcmcia not detected after boot Oct 30 09:40:41 I will have some patches to workaround and 4.19 Oct 30 09:40:49 will work Oct 30 09:41:28 I have done my toolchain fixes, now was waiting for 4.20 Oct 30 09:42:08 or 5.0 who knows Oct 30 09:42:34 yes, as you said, after 4.14 there are many issues Oct 30 09:42:58 well, so far the 4.19 has only the same issues as 4.14 had Oct 30 09:44:04 4.114 is not bad, I don't remember outstanding issues Oct 30 09:44:45 afais only patches for tosa Oct 30 09:45:36 I'll retest again on c860 but the images I uploaded did bot and run Oct 30 09:45:41 all 4.1x. suffer the same fate - gpio issue for keypad (some keys do not work with left shift-combo) and pcmcia not being detected after a kernel boot Oct 30 09:46:08 no change for 4.19. Oct 30 09:46:25 I remember slow detection of CF and SD card but this is common to 4.x Oct 30 09:46:36 (deferred probing) Oct 30 09:47:00 no, the issues we had with gpio (keypad) and pcmcia (detection) are still in mainline Oct 30 09:47:04 I asked Varti to test these images Oct 30 09:47:06 https://github.com/LinuxPDA/test-images-2018-09-23 Oct 30 09:47:27 about keyboard, ye3s, there is some issue Oct 30 09:47:35 ouch.. Oct 30 09:48:04 one for all, I could not find SysRq Oct 30 09:48:21 and the kb mapping are wrong iirc Oct 30 09:48:49 but lcd/backlight was ok, sound ok, networking ok, bluetooth ok Oct 30 09:49:24 we must fix the kb... Oct 30 09:50:49 and pcmcia Oct 30 09:53:30 I am pretty sure I booted from CF... Oct 30 09:53:48 the issue is that CF card is not detected after boot Oct 30 09:54:03 if card is inserted at boot time it will work, CF storage or NIC Oct 30 09:54:32 ah, ok, the wrong GPIO is triggered for the insertion maybe? Oct 30 09:54:48 its a pcmcia change not GPIO Oct 30 09:54:56 (those zaurus gpio's are 10yrs old) Oct 30 09:55:14 it was introduces with 4.6.7+ Oct 30 09:55:57 for 4.14.x this works https://github.com/greguu/linux-4.14.18-c3x00/commit/2e2cfd2c542e36c795874092988ae6f960a857c1 Oct 30 09:56:05 I am just porting it to 4.19 Oct 30 09:56:38 GPIO may still be a part of the issue Oct 30 09:57:18 I have not yet taken a dive in the power domains/regulators :) Oct 30 09:57:52 afair older Z have any Oct 30 09:57:59 I think it is just the way the function returns the state.. Oct 30 10:01:57 see https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/log/drivers/pcmcia?h=next-20181030 Oct 30 10:02:13 maybe the two 2018-09 gpiolib patches? Oct 30 10:05:03 I think it is just the way the function returns the state.. Oct 30 10:07:37 these patches came after 4.19 Oct 30 10:08:10 seems they exactly change the way data is passed Oct 30 10:10:00 this patch is unrelated Oct 30 10:14:13 well, and theon one of today about regulators :) Oct 30 10:14:23 https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/log/arch/arm/mach-pxa?h=next-20181030 Oct 30 10:14:26 topmost Oct 30 10:15:09 so you see, the floor is moving... Oct 30 10:15:38 we must catch up, no way to keep up reverting Oct 30 10:17:08 did not touch Zaurus directly it seems Oct 30 10:18:01 really here it is 'just' matter of debugging why the wrong state is returned Oct 30 10:35:16 greguu, sigh, I'll have really to attack https://01.org/linuxgraphics/gfx-docs/drm/driver-api/regulator.html Oct 30 11:08:45 * greguu floor was moving quite a bit today - 6.2 quake Oct 30 11:58:18 sh*t **** ENDING LOGGING AT Wed Oct 31 02:59:58 2018