<bkallus__>
plntyk, printenv is not exactly the same; the sg200 has some extra variables, but the ones they share are mostly the same except for bootcmd and other openrg-specific stuff
zjason has quit [Quit: ERC (IRC client for Emacs 28.0.50)]
<numero53>
Is someone using a router or board with mt7622? I am trying to add support for a new router (Belkin RT3200/Linksys E8450) but I have a problem with the flash and the bad block management table when jffs2 tries to erase rootfs_data ...
nitroshift has quit [Quit: Gone that way --->]
dorf has joined #openwrt-devel
dorf_ has quit [Ping timeout: 264 seconds]
dorf_ has joined #openwrt-devel
dorf has quit [Remote host closed the connection]
noltari has quit [Ping timeout: 264 seconds]
<blogic>
numero53: there is a patch in felix's staging tre for that
<numero53>
blogic: Thanks for the answer! I am already using that one, but it get recreated every boot because it conflicts with the one in the bootloader... I managed to fix most of the problems changing the define BB_TABLE_MAX from 0x2000U to 0x1000U... But I don't don't know if it's right
linzst has joined #openwrt-devel
<mrkiko>
rmilecki: have you seen my mails recarding bcm63xx target - netgear d6400
nitroshift has quit [Quit: Gone that way --->]
<rmilecki>
mrkiko: that one I assume? [bcm63xx] help in adding Netgear D6400 support
<rmilecki>
mrkiko: it seems you generated & flashed image that CFE can't understand
<rmilecki>
I don't know bcm63xx's CFE enough to help with that
Darkmatter66 has joined #openwrt-devel
linzst has quit [Quit: Leaving]
Tost has joined #openwrt-devel
HeN has quit [Quit: Connection closed for inactivity]
valku has joined #openwrt-devel
Tost has quit [Ping timeout: 256 seconds]
plntyk has quit [Quit: Leaving]
dorf has joined #openwrt-devel
dorf_ has quit [Remote host closed the connection]
<mrkiko>
rmilecki: well, it flashes the image, while otherwise saying it's invalid when I try to flash e.g.: the vendor .chk image or a dump of the partition
<mrkiko>
but yes, definitely can't find the jffs2 entry for vmlinux.lz
<mrkiko>
I hoped in some answer, but not been lucky so far
ivanich has quit [Quit: Konversation terminated!]
<rmilecki>
mrkiko: just because firmware format is OK, it doesn't mean firmware is totally valid
<rmilecki>
mrkiko: format validation is usually some basic check to make sure you don't flash random garbage
<mrkiko>
rmilecki: yeah. What I meant - was I don't have a clear term of comparison or a way to go on since I don't have a "totally" valid firmware then
<mrkiko>
I tried looking at the gpldump for my device as well.
<mrkiko>
In the ky SR102 port I seen noltari replaced CFE with a generic one, but maybe it's late for me to try that? The "w" - wholeimage, command doesn't seem to work.
<mrkiko>
CFE also fails to start any elf application I pass it
danitool has quit [Quit: Cubum autem in duos cubos, aut quadratoquadratum in duos quadratoquadratos]
<mrkiko>
I wanted to avoid replacing the bootloader if possible ... to make it easier for an user to install openwrt without risking too much and to keep nvram values.
<mrkiko>
but in the end I'll happily do so if i can understand how without bricking the device.
decke has quit [Quit: Leaving.]
* mrkiko
misses u-boot
hsp has quit [Quit: WeeChat 3.0]
hsp has joined #openwrt-devel
plntyk has joined #openwrt-devel
gch9812133289452 has joined #openwrt-devel
snh has quit [Ping timeout: 260 seconds]
Darkmatter66 has quit [Ping timeout: 246 seconds]
Borromini has joined #openwrt-devel
snh has joined #openwrt-devel
snh has quit [Read error: Connection reset by peer]
<nlowe>
jow: That's for the option names only, where most were already upper camel case and not descriptions
<jow>
"Associated Clients" is also not entirely correct
<jow>
that list shows all associations
<jow>
in case of ad-hoc it shows the peers, in case of a client the PAI associated to, in case of an AP the stations
hsp has quit [Quit: WeeChat 3.0]
<jow>
s/PAI/AP/
<nlowe>
Associations would be more accurate then, not associated stations
gromero1 has quit [Quit: WeeChat 2.9]
<jow>
also please use … and not three dots
<jow>
also after this change, all translations need to be resynced
<jow>
preferably in a way that does not invalidate all existing langauges
<jow>
for that the existing english strings need to be substituted by the new ones while keeping the translation
<jow>
in the various *.po files
<nlowe>
Gotcha, for ... I changed that for consistency with others already in the file - can change all the other way
hsp has joined #openwrt-devel
<dorf>
… is your friend.
<dorf>
or maybe not, depends on context :)
HeN has joined #openwrt-devel
<nlowe>
jow: Re: upper camel case for names (not descriptions), to me it genuinely looks a lot better when seen in a browser, not just in a commit diff. Happy to switch all around for consistency though if that's desired. I don't think a mix of the two is good.
<jow>
just remeber some native speaker complaining here a while ago that all camel case is not the proper thing to do
<jow>
and that randomly sprinkling uppercase chars throughout labels is a rather german thing
<nlowe>
Either way, perhaps a guideline or style guide could be helpful for the future to work towards?
Darkmatter66 has joined #openwrt-devel
Darkmatter66 has quit [Client Quit]
goliath has quit [Ping timeout: 240 seconds]
<jow>
nlowe: I am not a native english speaker myself, idealler a native and/or someone with technical writing or documentation background should weigh in
<jow>
*ideally
<jow>
I agree that camel-casing produces a more esthetically pleasing appearance in many cases
<jow>
but it feels weird to captialize almost all words
goliath has joined #openwrt-devel
<nlowe>
I agree it would be weird and wrong if in descriptions, but for names and titles only, I personally think it is preferable