**** BEGIN LOGGING AT Sat Jul 04 03:13:14 2020
**** ENDING LOGGING AT Sat Jul 04 07:17:23 2020

**** BEGIN LOGGING AT Sat Jul 04 11:19:18 2020
**** BEGIN LOGGING AT Sat Jul 04 12:32:05 2020
Jul 04 16:04:25 <jonmason> paulbarker: you available for questions/issues with meta-kernel? 
Jul 04 16:12:06 <paulbarker> jonmason: Hey, what's the q?
Jul 04 16:13:37 <jonmason> I'm having a problem with the KBUILD_DEFCONFIG not applying
Jul 04 16:13:47 <jonmason> and I'm just making sure I'm not being stupid :)
Jul 04 16:14:53 <jonmason> I have 'KBUILD_DEFCONFIG = "multi_v7_defconfig"' in my machine config
Jul 04 16:15:05 <jonmason> am I incorrect in assuming that should work?
Jul 04 16:15:10 <paulbarker> jonmason: I've never been able to get that to work myself
Jul 04 16:15:28 <jonmason> so, "patches welcome" is the answer?  
Jul 04 16:16:16 <jonmason> It looks like all that fun should be working in the kernel.bbclass.  So I am confused why it wouldn't be working, since that is included
Jul 04 16:16:19 <paulbarker> The code copies the defconfig instead of running `make multi_v7_defconfig` so the config dependencies aren't expanded
Jul 04 16:17:10 <paulbarker> https://git.openembedded.org/openembedded-core/tree/meta/classes/kernel.bbclass#n552
Jul 04 16:17:13 <jonmason> it is working on linux-yocto
Jul 04 16:18:03 <paulbarker> I usually set KERNEL_CONFIG_COMMAND myself
Jul 04 16:18:39 <jonmason> np, I'll mess around with it then.  I mostly wanted to make sure I wasn't being massively stupid  :)
Jul 04 16:18:50 <paulbarker> This should be handled correctly in kernel.bbclass and not need kernel-yocto.bbclass but it's another thing on my long backlog
Jul 04 16:19:04 <jonmason> if I can get it working, I'll send a patch
Jul 04 16:19:17 <paulbarker> jonmason: Cheers
Jul 04 16:19:21 <jonmason> I'm trying to kill the upstream kernel stuff in meta-arm and use meta-kernel for it
Jul 04 16:20:07 <jonmason> thanks
**** BEGIN LOGGING AT Sat Jul 04 18:57:26 2020
Jul 04 20:51:06 <jonmason> paulbarker: disregard everything.  I'm stupid.  It is working.  Patch for a 5.3 kernel coming your way soon-ish
Jul 04 22:55:19 <mort> do I have to do something special in my devicetree in order to make linux know about GPIO pins?
Jul 04 22:56:34 <mort> I had a really simplistic model of how this works, just enable pin N by writing to /sys/class/gpio/export, then you can use that PIN and it corresponds to some hardware PIN. However, I suppose maybe I need to manually map a GPIO PIN to the right hardware or something, but I can't figure out how
**** ENDING LOGGING AT Sun Jul 05 03:01:09 2020