<damo22>
i dont know how to make an installation path
lu_zero has quit [Server closed connection]
lu_zero has joined #openwrt-devel
wille-io has quit [Server closed connection]
wille-io has joined #openwrt-devel
Ansuel has quit [Server closed connection]
Ansuel has joined #openwrt-devel
KanjiMonster has quit [Server closed connection]
KanjiMonster has joined #openwrt-devel
killgufo has quit [Remote host closed the connection]
killgufo has joined #openwrt-devel
<damo22>
if i tftpboot into openwrt, what process/which image do i flash next?
<damo22>
is that an acceptable installation method for merging a new port?
<mrkiko>
damo22: so you are in the mr200 v6 ?
<damo22>
not currently but i can boot it yes
<damo22>
ive done most of the port
<mrkiko>
damo22: so ... in general it is acceptable to require the user to tftpboot and the uuse sysupgrade, even tough you may define other actions
<mrkiko>
damo22: maybe I am stating the obvious - but ... you should modify the relevant files to implement sysupgrade for your specific device
<damo22>
ok so how do i test sysupgrade for my device?
<damo22>
ive backed up the entire flash
<mrkiko>
damo22: first of all, I guess you have a complete backup of the flash stored in a safe place
<mrkiko>
ok
<damo22>
im not sure what i need to implement for sysupgrade exactly
<mrkiko>
damo22: what i would do would be first to check the platform.sh file and see the code, to understand how things are organized. and look for similar devices. If youdevice is not defined here, no sysupgrade operation will take place
<damo22>
*)
<damo22>
default_do_upgrade "$1"
<damo22>
tplink,archer-c50-v6)
<damo22>
MTD_ARGS="-t romfile"
<damo22>
default_do_upgrade "$1"
<mrkiko>
damo22: infact I was wrong actually, looking at things myself right now
<damo22>
what does "-t romfile" do?
<mrkiko>
damo22: eheh, good question. And I don't know the answer. Look at the code and see
<damo22>
* TP-Link recovery flag set and unset code for ramips target
<damo22>
-t <partition> write TP-Link recovery-flag to <partition> (for write)
<mrkiko>
damo22: but probably you won't need that
<damo22>
err, why not?
<damo22>
its a tplink devic
<mrkiko>
damo22: because I guess otherwise you would have already found out
<damo22>
but ive never tried sysupgrade yet
<mrkiko>
damo22: ok, after a cursory look I think it might actually work. PART_NAME variable should be "firmware" by default, if your layout does match then things might work
<mrkiko>
damo22: but of course no promise
<damo22>
i see
<mrkiko>
damo22: taking for granted the device has not special requirements ...
<damo22>
cat /proc/mtd
<damo22>
mtd2: 00da0000 00010000 "rootfs"
<damo22>
dev: size erasesize name
<damo22>
mtd0: 00020000 00010000 "boot"
<damo22>
mtd1: 00200000 00010000 "kernel"
<damo22>
mtd3: 00010000 00010000 "config"
<damo22>
mtd4: 00010000 00010000 "romfile"
<damo22>
mtd5: 00010000 00010000 "radio"
<damo22>
i think -t romfile might be the right setting?
<mrkiko>
damo22: uh, you miss a firmware partition... I haven't looked at your DTS file. So no, take a look at similar device and try to see how to set things. I can't answer your question on the romfile aspect - because any device is different to some extent. And TP-Link is not known for having an omogeneous design across all it's boards
<mrkiko>
damo22: ah ok, so it's ok
<damo22>
:D
<mrkiko>
damo22: I would try to leave the romfile partition alone at first, and see how things go... but it's all speculation. In my mr200 V1 romfile was - if I am right, not touched
<damo22>
ah good to know
<mrkiko>
but maybe we are too noisy, pm if you want
<damo22>
ok
damo22 has quit [Ping timeout: 480 seconds]
karlp has quit [Server closed connection]
karlp has joined #openwrt-devel
zkrx has quit [Server closed connection]
zkrx has joined #openwrt-devel
bbezak has quit [Server closed connection]
bbezak has joined #openwrt-devel
mrkiko has quit [Server closed connection]
KGB-2 has quit [Server closed connection]
KGB-2 has joined #openwrt-devel
oreovon has quit [Read error: Connection reset by peer]
slh has quit [Remote host closed the connection]
slh64 has quit [Quit: gone]
slh has joined #openwrt-devel
FLD has quit [Server closed connection]
FLD has joined #openwrt-devel
<rmilecki>
nbd: i'm happy to see MLO for MT7925
<rmilecki>
nbd: do you know if MT7996 is planned anytime soon?
<rmilecki>
at all?
goliath has quit []
<nbd>
rmilecki: i'm actively working on MLO for mt7996 in my pending branch
<rmilecki>
ah, great! thanks!
<nbd>
will be at least a few more weeks until it's ready for testing
<hurricos>
mrkiko: if a QCA9984 PCIe card lacks an EEPROM, calibration data is almost certainly on the host, yes? or do the QCA99x4 have some kind of on-die calibration
<hurricos>
Hmm, OK. I think it's better to use new AsiaRF MT7915 modules for the new network @ $45 each, rather than attempting to harvest QCA9984's from Norton Cores at $10 each. Probably easier to support, too.
<mrnuke>
hurricos: both. MAX_PORTS looks fine to me. It's silly that we do stack variables for ports but dynamic malloc for packets. I see no issues with bumping it
<hurricos>
I have their source but they use an ancient qsdk and it's, hmm, I'm not ever going to find that calibration data :^)
<hurricos>
mrnuke: C stickler. :^)
<hurricos>
ACK to bumping it. Bumping the openwrt/packages, though, let's see.
<mrnuke>
hurricos: I do want to get the refactors in, as the realtek dialect stuff is prettu much married to it now
<hurricos>
I will have a JG928A at some point soonish and can actually run-test it and a few other devices. Then hopefully find time to turn around and run-test those refactor PRs
<hurricos>
since I know it was svanheule's goal to ah, generate ... generate ... that poe conf file from .. something agnostic ..?
<Habbie>
i was just typing on a 1920-24G and i'm really curious what running openwrt on it would mean in practice for my usage
<hurricos>
Probably nothing
<hurricos>
slower port init
<hurricos>
I like the genericization of hardware personally. It means I don't have to do much thinking when it comes to installing it.
<Habbie>
yeah, i get that
<hurricos>
that's about it.
<Habbie>
i was just complaining on another channel about pulling a VLAN through two switches from different vendors
<hurricos>
I doubt micropython will run happily on it, but if it did, ta-da, ansible wink wink
<hurricos>
(don't do this)
<Habbie>
haha
<Habbie>
but, i'm confused, the PR says tested on 928A but you don't have one?
<hurricos>
realistically my standard for hardware these days is openwrt and an external serial port for when I inevitably break the configuration. Making your configuration and security standards harmonized is a sanity-maker, but it's not worth the cost of development
<hurricos>
bit iffy. Run-tested by the other user.
<Habbie>
ah got it
<Habbie>
and yes, as a device owner doing the port, the effort has no return on investment ;)
<Habbie>
we do it for others and the environment
<hurricos>
it does eventually in the form of cheap hardware but then you own it
<hurricos>
the cost of maintenance
<hurricos>
pulling down all your APs to swap in ath9k cards because your qca9880s are crashing
<Habbie>
hehe
<hurricos>
and you're too stupid to think of a way to detect the crash and reboot
<hurricos>
because you're not a sysadmin, you're a developer
<hurricos>
IDK we live life the way we do. If I had half a brain I'd refuse to continue to manage the WiFi here without control of the DHCP server. Instead I bank on slower cards throttling users well enough to prevent gateway bottleneck
<Habbie>
huh, i wonder where i left my openwrt branch for juniper srx
<hurricos>
sounds like octeon, sounds like a bad time
<hurricos>
you should let it be dead
<Habbie>
it is octeon
<Habbie>
it boots to a shell!
<hurricos>
it ain't coming back, Habbie.
<hurricos>
Let it die.
<Habbie>
hehe
<Habbie>
i might just publish my notes as a thing people can read when they're doing openwrt ports
<Habbie>
i learned a lot doing that
<Habbie>
i don't even care much about publishing the port in the end
<hurricos>
+1
goliath has joined #openwrt-devel
nixuser has quit [Ping timeout: 480 seconds]
xes has quit [Ping timeout: 480 seconds]
f00b4r0 has quit [Quit: bbl]
nixuser has joined #openwrt-devel
xes has joined #openwrt-devel
SlimeyX has quit [Read error: Connection reset by peer]