Still waiting on my device to make it in xD
it does work but i say youre bettter off with ipq807x
but if you can get MR7350 cheap then maybe its fine, I got mine for 40$
Not looking to get a new box, was just discussing OpenWRT with someone else to be honest
I've been sat with the Pine64 guys for about 2 months I think now and learned a ton about embedded devel, written my first two drivers, so I will probably appear here again at some point to add support for OpenWRT to the new Ox64 once networking is stable
I have you to thank for getting me stepped on that whole train though :P
valku has quit [Remote host closed the connection]
jenders has joined #openwrt-devel
gladiac has quit [Quit: k thx bye]
jenders has quit [Ping timeout: 480 seconds]
that seems to be from openssl3/libcrypto? weird, I don't get that on another device
lol, that's my own ustream-ssl debug spew that leaks into uhttpd
it breaks the luci menu
rua has quit [Quit: Leaving.]
oh, heh. yah, gotta be careful with printing in things that talk to luci. gotta be real careful to use stderr :)
maciekb has quit [Read error: Connection reset by peer]
maciekb has joined #openwrt-devel
Misanthropos has joined #openwrt-devel
rua has joined #openwrt-devel
hehe yeah, my bad, but still a bit weird. I do get the same debug spew on two devices, yet it only breaks luci on one
floof58 is now known as Guest6060
floof58 has joined #openwrt-devel
Guest6060 has quit [Ping timeout: 480 seconds]
minimal has joined #openwrt-devel
I get fun luci errors when I have half it's files on an nfs share that's unmounted :)
Someone knows why on ipq807x there is this "stop spad before upgrading" need, not manifested in other targets? Plain technical curiosity.
c0xc_ has joined #openwrt-devel
So I have a I2C peripherial, that features 2 I2C master controllers, easy. But they 'share' on register address (for some global configuration). That shared register sits exactly in the middle of both addresses, so if I expand i2c0 by 1, and start i2c1 1 later, they can both cover all the needed registers. However, now we have 2 controllers accessing the same register, so I need locking. Can I have some global mutex variable in my I2C
driver, or do I have to make the i2c driver a 'tree' (i2c-ctrl with 2 children, bus0 and bus1?
c0xc has quit [Ping timeout: 480 seconds]
djfe has joined #openwrt-devel
hurricos has joined #openwrt-devel
oliv3r[m]: that sounds like a "one i2c controller, two i2c buses" to me
one i2c controller, two i2c busses, 1 pinmux controller :)
but the pinmux controller only tells you if a pin is GPIO or SDA; the drive strength etc, is in a different register (shared with all gpios)
it's a really big piece of swiss-cheese
I mean, pinmux is irrelevant, pinmux is handled by the pinctrl driver
but also i2c controller -> 2 busses -> 8 muxes per bus (ontop of that)
i2c doesn't care if the IO lines are actually routed anywhere
yeah, but, the pinctrl driver will need access to 8 bits of one register of the i2c controller :)
nebster, your first line was truncated after "looking in the"
looking in the config.gz, it says "# CONFIG_PERF_EVENTS is not set"
do you mean the vendor's config.gz? PERF_EVENTS is enablement for the perf tracing tool, i think it doesn't have much to do with device support
So, I am using the snapshot from downloads.openwrt.org. So it is the config.gz from there.
I'm assuming that means buildbot just uses the default config from the openwrt repo?
spyrral has joined #openwrt-devel
spyrral has left #openwrt-devel [#openwrt-devel]
mrkiko: it's been discussed in detail in the xiaomi ax3600 thread, but in short, there are situations when ath11k won't terminate as quickly as procd wants it to (because it has pending stuff in its queues), this means it keeps wpad running and sysupgrade gives up too early. a sleep 30 (just adding a random -untested- figure here) in sysupgrade after killprocesses, before giving up would paper over the
nebster, it might be one of those confusing interactions between the OpenWrt builtroot and the kerel build system, but I'm not certain
goliath has quit [Quit: SIGSEGV]
I just got a BPi R3 and haven't flashed my first image yet, heh
nebster: CONFIG_PERF_EVENTS depends on CONFIG_PROFILING to be effective and that appears to be off in the generic kernel config
jow: That's so weird that a config flag can be on without its dependencies and there is no error. I guess I will start building a custom image then. Thanks so much!
nebster: the config fragments are sometimes hand edited
jow: I mean I'm surprised the configs aren't checked programatically for things like this, the options are just silently disabled. Do you think a PR would be accepted to set the CONFIG_PROFILING flag to "y" in that file?
Kufat: It seems like a fun little router! I have two and I'm going to try to upgrade my current mesh that works awfully (random ping spikes, maybe even packet loss, I don't remember).
Not sure if that is just because the devices are underpowered or because I have so many wifi-enabled microcontrollers chattering over the network
djfe has joined #openwrt-devel
cmonroe has joined #openwrt-devel
nebster: depends on the runtime performance and store footprint implications of CONFIG_PROFILING
Tapper has quit [Quit: Tapper]
cmonroe_ has quit [Ping timeout: 480 seconds]
nebster: the question I'm asking myself at the moment is how I want to configure the filesystems. Options are rootfs+overlay in flash, emmc mounted to /mnt or similar; rootfs in flash and emmc as overlay; rootfs and overlay on emmc; or something else, like throwing extroot in there
but I suppose that's more on-topic for #openwrt