**** BEGIN LOGGING AT Fri Jan 11 02:59:57 2019
Jan 11 03:50:41 <dansan> what is codeload?
Jan 11 05:56:37 <jow> nbd: ping
Jan 11 05:56:58 <jow> nbd: https://bugs.openwrt.org/index.php?do=details&task_id=2054 - can you make sense of it?
Jan 11 09:39:17 <jow> 'lo ldir
Jan 11 09:40:01 <ldir> jow: greetings
Jan 11 12:03:36 <DonkeyHotei> to refresh my memory: if support for a particular board requires weird defaults in uci, where do i put that? thanks
Jan 11 12:04:57 <jow> uci-defaults
Jan 11 12:12:24 <DonkeyHotei> target/linux/*/base-files/etc/uci-defaults/ appears to contain scripts, though
Jan 11 12:14:10 <DonkeyHotei> and the scripts are target-specific rather than board-specific
Jan 11 12:15:13 <DonkeyHotei> the defaults that the board needs are for non-led gpio's
Jan 11 12:19:18 <DonkeyHotei> jow: is there a better place for those?
Jan 11 12:20:59 <jow> keep in mind that usually all boards share the smae base-files scripts
Jan 11 12:21:11 <jow> or rather the same rootfs
Jan 11 12:21:39 <jow> so your script needs to be subtarget or target-wide and check at runtime if its on the correct board
Jan 11 12:22:35 <DonkeyHotei> i'm not even sure yet that uci is the best way to do this, but any other way i can think of seems even worse
Jan 11 12:32:16 <rex_victor> Hey guys, I am in need of modifying u-boot. Yesterday I was directed here to the build_dir directory. I was looking around there and there are different u-boot directories and not all of them have the make nconfig option
Jan 11 12:32:29 <rex_victor> Can someone point me in the right direction?
Jan 11 12:39:21 <jow> rex_victor: package/boot/uboot-*
Jan 11 12:40:00 <rex_victor> jow: There I only see the patches
Jan 11 12:45:28 <KanjiMonster> rex_victor: that's the way the build system works, it downloads the u-boot sources, extracts them to build_dir/target-*/.../u-boot-*/, then applies those patches to the extracted sources - so any persistent changes you want to do need to e expressed as patches; if you just one to change and build stuff once you can directly modify the sources in build_dir/
Jan 11 12:47:02 <rex_victor> KanjiMonster: I need the menuconfig.
Jan 11 12:47:25 <KanjiMonster> then you need to run it within the extracted u-boot sources
Jan 11 12:47:37 <rex_victor> I have 4 different u-boot folders
Jan 11 12:47:47 <KanjiMonster> yes, one for each u-boot build target
Jan 11 12:48:20 <rex_victor> so one folder is u-boot-vgv7510kw22_brn
Jan 11 12:48:42 <KanjiMonster> that's the u-boot for the vgv7510kw22_brn device
Jan 11 12:48:43 <rex_victor> this folder contaions one folder: u-boot-2013.10
Jan 11 12:49:34 <rex_victor> and inside this folder running make nconfig says mips_4KC-gcc not found and no target menuconfig
Jan 11 12:49:52 <rex_victor> *nconfig=menuconfig
Jan 11 12:54:35 <rex_victor> KanjiMonster: I'd really appreciate any help here. The wiki is not up to date for this device and the u-boot image from the download page and the one from the build root don't really work
Jan 11 12:55:13 <rex_victor> So I'm hoping by compiling uboot with appropriate settings, it will work
Jan 11 12:55:35 <dedeckeh> jow:ping
Jan 11 12:57:15 <jow> dedeckeh: pong
Jan 11 12:58:01 <KanjiMonster> rex_victor: no idea where this error comes from, seems to be an issue with the old u-boot version. I had no issues running menuconfig with the mvebu u-boot, which uses 2016.03, but I can see the error message when running menuconfig with the older lantiq u-boot
Jan 11 12:58:13 <dedeckeh> jow:uclient installs wget in /bin while busybox installs it in /usr/bin
Jan 11 12:58:31 <dedeckeh> shouldn't that be aligned ?
Jan 11 12:58:45 <jow> dedeckeh: the decision predates alternatives support
Jan 11 12:59:00 <jow> before that was available, we used /usr/bin to override /bin
Jan 11 12:59:14 <dedeckeh> ok so there's no objection to align this and work with ALTERNATIVES
Jan 11 12:59:15 <jow> now that alternatives are available, aligning it makes sense
Jan 11 12:59:23 <rex_victor> KanjiMonster: So have you any idea, what I could do?
Jan 11 13:00:02 <KanjiMonster> rex_victor: you probably need to point CROSS_COMPILE to the openwrt toolchain
Jan 11 13:00:26 <rex_victor> as an export?
Jan 11 13:01:10 <jow> rex_victor: uboot's ./arch/mips/config.mk contains CROSS_COMPILE ?= mips_4KC-
Jan 11 13:01:30 <jow> rex_victor: means it will try to invoke mips_4KC-gcc, mips_4KC-ld, mips_4KC-nm etc. when no CROSS_COMPILE env var is set
Jan 11 13:02:07 <jow> rex_victor: you should set it to  export CROSS_COMPILE=mips-openwrt-linux-musl-
Jan 11 13:02:26 <rex_victor> Does it need an absolute path?
Jan 11 13:02:32 <jow> rex_victor: and make sure that  staging_dir/toolchain-mips_24kc_gcc-7.4.0_musl/bin/  (actual path might differ depending on version) is set in PATH
Jan 11 13:02:42 <rex_victor> ok
Jan 11 13:03:01 <jow> this assumes hat you compiled at least the toolchain once in your current buildroot
Jan 11 13:05:11 <rex_victor> jow: KanjiMonster: Ok I did this
Jan 11 13:05:28 <rex_victor> Now it says no rule for target menuconfig
Jan 11 13:05:47 <KanjiMonster> yeah, I have no idea how this old u-boot is supposed to work
Jan 11 13:05:55 <KanjiMonster> I can see that as well
Jan 11 13:06:47 <rex_victor> It seems that lantiq is not included in mainline
Jan 11 13:07:10 <KanjiMonster> might be u-boot 2013 didn't include a menuconfig yet
Jan 11 13:08:41 <rex_victor> What wonders me is that there is also a folder u-boot-2018.03
Jan 11 13:10:47 <KanjiMonster> yeah, menuconfig was added 2014
Jan 11 13:11:32 <KanjiMonster> the new one is just the build dir for the fw_env userspace utilities
Jan 11 13:11:44 <rex_victor> I see
Jan 11 13:12:03 <rex_victor> So what were people doing instead of menuconfig in 2013?
Jan 11 13:12:47 <KanjiMonster> I guess using a texteditor of their choice to hand write configs
Jan 11 13:14:46 <rex_victor> Is there any chance I could use a newer version?
Jan 11 13:16:31 <KanjiMonster> not really, you would need to port the patches to a newer u-boot version
Jan 11 13:16:57 <KanjiMonster> and I doubt that's less work than writing/modifying a config by hand
Jan 11 13:23:30 <rex_victor> KanjiMonster: I see
Jan 11 13:23:51 <rex_victor> Where can I find the default config?
Jan 11 13:27:04 <KanjiMonster> rex_victor: include/configs/<boardname>.h
Jan 11 13:28:42 <rex_victor> KanjiMonster: Thanks! But I'm guessing I won't get ethernet working that way
Jan 11 13:31:36 <KanjiMonster> rex_victor: ethernet configuration you'll find in the appropriate board/?/?.c
Jan 11 13:34:18 <rex_victor> KanjiMonster, jow:Thanks a lot for your time and help!
Jan 11 13:43:00 <rex_victor> Do you know danielschwierzeck?
Jan 11 13:49:15 <DonkeyHotei> [Fri 2019-01-11 04:21:39 AM PST] <jow> so your script needs to be subtarget or target-wide and check at runtime if its on the correct board <------ why not just use /etc/board.d?
Jan 11 14:23:26 <jow> DonkeyHotei: you can use this as well
Jan 11 14:24:02 <jow> its still a series of scripts that run for every board, you need to guard your board specific code in case switches or if conditions
Jan 11 15:07:34 <owrt-snap-builds> build #774 of layerscape/armv8_32b is complete: Success [build successful]  Build details are at http://phase1.builds.lede-project.org/builders/layerscape%2Farmv8_32b/builds/774
Jan 11 15:16:09 <owrt-snap-builds> build #1194 of x86/geode is complete: Success [build successful]  Build details are at http://phase1.builds.lede-project.org/builders/x86%2Fgeode/builds/1194
Jan 11 15:29:03 <rmilecki> jow: i think opkg crashes when trying to install .ipk-s for a different arch
Jan 11 15:29:11 <rmilecki> jow: i've to verify that on 18.06 / master with clean repo
Jan 11 15:29:16 <rmilecki> i noticed that in 17.01
Jan 11 15:29:18 <rmilecki> just a heads up
Jan 11 15:37:54 <owrt-snap-builds> build #1155 of kirkwood/generic is complete: Success [build successful]  Build details are at http://phase1.builds.lede-project.org/builders/kirkwood%2Fgeneric/builds/1155
Jan 11 17:59:10 <rubberduck> hi, i'd like to ask if there is someone here who knows the lantiq chips in fritzbox 73[23]0
Jan 11 18:35:09 <rubberduck> Hauke: are you online?
Jan 11 18:39:32 <Hauke> rubberduck: yes I am online
Jan 11 18:39:57 <rubberduck> Hauke: i saw that you were active for the fritzbox 7312 port
Jan 11 18:40:58 <Hauke> rubberduck: I do not have such a device
Jan 11 18:41:03 <Hauke> what is your question?
Jan 11 18:41:10 <rubberduck> i have a simmilar problem that was on the 7312 where the ar8030 did not work
Jan 11 18:41:30 <Hauke> do you have a link to the problem on the 7312
Jan 11 18:41:51 <rubberduck> the LAN Port on the AR8035 (gigabit) appears but the second port on the AR8030 (10/100) does not.
Jan 11 18:42:34 <rubberduck> i have a 7330 where only one of the two lan ports is working with openwrt and i think that the driver does not recognize the second phy
Jan 11 18:42:57 <Hauke> I am not familiar with the old ethernet driver, I think Daniel Golle looked into that
Jan 11 18:43:16 <rubberduck> with (latest) avm firmware both ports are working so the hardware is ok
Jan 11 18:43:24 <Hauke> he changed the MII delays
Jan 11 18:43:31 <rubberduck> how can i contact Daniel?
Jan 11 18:45:00 <Hauke> rubberduck: daniel@makrotopia.org
Jan 11 18:45:11 <Hauke> sometimes he is alos in IRC
Jan 11 18:45:31 <rubberduck> Hauke: what is his native language?
Jan 11 18:45:40 <Hauke> German
Jan 11 18:46:25 <rubberduck> Thank you very much.
Jan 11 20:35:53 <owrt-snap-builds> build #266 of gemini/generic is complete: Failure [failed images]  Build details are at http://phase1.builds.lede-project.org/builders/gemini%2Fgeneric/builds/266  blamelist: Rafa? Mi?ecki <rafal@milecki.pl>, Felix Fietkau <nbd@nbd.name>, Hans Dedecker <dedeckeh@gmail.com>
**** ENDING LOGGING AT Sat Jan 12 02:59:57 2019