> > Well, the upstream code does not support VLAN/Bridge Forwarding. So,
> > all traffic goes through the CPU (with the expected lower
> > performance). I implemented that part in the driver but the maintainer
> > rejected it as my implementation was based on Shared VLAN Learning and
> > he already
> The clean code, without my downstream patch is already here
> https://github.com/openwrt/openwrt/commit/f24c47fa8a2fb653288d34e7a0bcdc6eafa5736e
> . I'll still test it on my device before submitting.
PR: https://github.com/openwrt/openwrt/pull/17654
It does not include the vlan/forwarding extra
Hi Linus,
> > Maybe we should back port the upstream changes (and fixes),
> > similar to what I did in
> > https://github.com/luizluca/openwrt/commit/d145c6845d7cdd2d49722a85988f16b17014dfa4
> > (it needs to be updated and rebased). I might have time to rebase that
> > branch soon.
>
> What about
> > The upstream was rearranged in such a way that reverses the relation
> > between subdrivers and interfaces. It will probably break your
> > packages.
>
> Indeed. It was a bit annoying...
>
> We are falling behind mainline again.
>
> > Maybe we should back port the upstream changes (and fixes),
Hi Linus,
Em dom., 12 de jan. de 2025, 20:15, Linus Walleij
escreveu:
>
> This adds kernel packages for the Realtek RTL836x switches.
>
> My intended usage is for RTL8366RB, but let's package
> RTL8365MB while we are at it. I did not create separate
> packages for the two switches, as it complic
> The realtek target supporting the Realtek switches is the only target in
> OpenWrt main still on Linux kernel 5.15, all other targets are at least
> on kernel 6.1, most of them are on Linux kernel 6.6.
>
> The next OpenWrt major release will use kernel 6.6 only, all targets not
> migrated to kern
>
> Replace mount + overlay with manually built tar archive that gets
> prepended to the actual config files backup. This allows more
> flexibility with including extra backup files. They can be included at
> any paths and don't require writing to flash or mounting an overlay
> which has its own li
Hello Rafał,
Sorry for the late review.
I know this will be used for a limited context but it can be
constructed in such a way it could be used for more cases without
increasing its complexity.
> From: Jo-Philipp Wich
>
> This allows building uncompressed tar archives from shell scripts (and
>
Hello,
There is a small fix for uhttpd pending in github.
https://github.com/openwrt/uhttpd/pull/2
If github should not be used for that, it would be nice to have it
explicitly mentioned in the github project or a Readme.md file.
Regards,
---
Luiz Angelo Daros de Luca
luizl
> On 21.02.2024 20:52, e9hack wrote:
> > root@WLAN-DSL9:~# sysupgrade -b /var/config-backup.tar.gz
> > Wed Feb 21 20:48:30 CET 2024 upgrade: Saving config files...
> > tar: var/dhcp.leases: No such file or directory
> > tar: var/lib/logrotate.status: No such file or directory
> > tar: var/log/logro
nd this solution to make it more generic:
> 1. Always mount overlay while creating backup
> 2. Overlay whole / to don't limit it to /etc/backup/
>
> This allows including any additional files in backups and adding more
> sysupgrade features.
It is a nice feature. Thanks.
>
&
> Am 12.02.2024 um 17:59 schrieb Christian Marangi (Ansuel):
> > Would be ideal to know what target are we talking about.
>
> The device is a TP Link C7 converted to using DSA.
It is a good opportunity to use it as a loadable module. It is tricky
but it works if configured correctly.
Regards,
Lu
> >I would choose 6.1: to get more time for some things to stabilize out and
> >because I am under the impression the kernel size is growing too fast and so
> >we are accelerating hw obsolescence.
The firmware overall size is not the only problem. Some bootloaders
might have trouble loading larg
> Thanks, Alberto. I'm wondering how much work making it cross-build packages
> is going to be...
>
> Digging into it now...
>
You should take a look at ksmbd package. It does compile an out-of-tree module.
Maintaining a package like that might be challenging for a stable
version. The kernel in
> Would it be too complex to implement a log limit for fw4?
Not really. But I might not have followed the best practices as this
is my first run on ucode/nftables:
https://github.com/luizluca/firewall4/tree/log_limit
It needs some more tests on cases that I'm not using in production and
a test i
gards,
---
Luiz Angelo Daros de Luca
luizl...@gmail.com
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Em sáb., 6 de mai. de 2023 06:12, Arınç ÜNAL escreveu:
>
> Hi.
Hi Arinç,
> I see a lot of development on the network drivers like DSA, PHY, etc.
> Are there any plans to put all these drivers on the realtek target on
> mainline Linux? To fully support these SoCs on mainline Linux?
>
> Arınç
>
I
> When reading https://openwrt.org/docs/guide-user/virtualization/start it
> is clear this hasn't seen much love. Several portions seemed to
> exclusively target developers and not really be meant for serious use.
> As such I was unsurprised to discover:
> https://openwrt.org/docs/guide-developer/
> Thanks all!
> Finally buy: D-LINK DGS-1210-48 G1.
>
> U-Boot 2011.12.(2.1.5.67086)-Candidate1 (Apr 13 2017 - 13:58:11)
>
> Board: RTL839x CPU:700MHz LXB:200MHz MEM:400MHz
> DRAM: 128 MB
> SPI-F: 1x32 MB
>
> Next:
> - connected serial cable
> - stop in uboot
> - boot from
> tftp/openwrt-realt
>
>
> > D-Link DGS-1210-48 HW Ver. G1 - will be fine? I need some confirmation.
> > Anyone could confirm?
>
D-Link DGS-1210-52 F does work in snapshot. You'll need to wait for
the next 23.x for a stable release.
I think there is only one switch with >=48 ports supported in 22.03:
zyxel gs1900. And
I know that autorelease has introduced some problems but it would be
good to keep a way to automatically bump releases. Every second we
could save from devs/maintainers is more time to do really useful
things.
Can't we have a central way to publish the "official list of package
releases''? It coul
> The default uhttpd configuration has this:
>
> # HTTP listen addresses, multiple allowed
> list listen_http0.0.0.0:80
> list listen_http[::]:80
>
> Now, I know there's lots of practical reasons for this to be the case,
> and I know also that the firewall setup in O
> > The previous fixup was incomplete, and the offsets for the
> > queue and crc_error cpu_tag bitfields were still wrong on
> > RTL839x.
> >
> > Fixes: 545c6113c93b ("realtek: fix RTL838x receive tag decoding")
> > Suggested-by: Jan Hoffmann
> > Signed-off-by: Bjørn Mork
> > ---
> > Jan pointed
> - Bridge device "br-vlan10" containing "lan1.10 lan2.10 lan3.10"
> - VLAN filtering disabled
Bridging virtual 802.1q interfaces might fail in some scenarios, like
when you use vlan1 or mix tagged with untagged traffic
(https://github.com/openwrt/openwrt/issues/9066)
I do recommend bridge-vlan
> On Sun, Jul 31, 2022 at 03:36:32PM +0200, Sander Vanheule wrote:
> > On Sat, 2022-07-23 at 22:53 +0200, Jan Hoffmann wrote:
> > > Add the 7zr command line tool, which is a version of the 7z application
> > > that only supports 7z archives.
> > >
> > > 7z is one of the two compression formats supp
Em dom., 17 de jul. de 2022 06:55, Paul Fertser escreveu:
>
> On Sat, Jul 16, 2022 at 11:32:52PM -0300, Luiz Angelo Daros de Luca wrote:
> > It uses SOC := rtl8380 while all existing dgs-1210 F1 variants use
> > rtl8382 (except for the pending -52 variant). The commit didn'
> On Tue, 2021-10-05 at 22:40 +0300, Paul Fertser wrote:
> > I only have D-Link DGS-1210-10P R1 for testing but other devices should be
> > very
> > similar judging by the photos. Would be nice to share support for all the
> > features available rather than get just R1 fully working.
> >
> > Paul F
; able to operate with a 2048-bytes frame (included single VLAN tag).
Are you ignoring CONFIG_SOC_MT7621 support for this driver? (it is
indeed upstream for recent kernels).
The patch worked as expected! Thanks a lot! Do you plan to submit it?
Tested-by: Luiz Angelo Daros de Luca
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Hi Andrey,
> It simple a) don't apply to master tree; b) not working - MAX_RX_LENGTH
> constant not
> touched, GSW_REG_GMACCR not tweaked for accepting jumbo frames.
a) Sorry, I missed your answer and thanks for the review. Yes, it was
not applying to master. It was based on another patch deeper
> I've started to look at the first vulnerability, but it is not as
> straightforward as I was hoping. Perhaps Luiz Angelo Daros de Luca,
> reporter and author of the fixes, can help me out with this.
Sure. And I do have interest in getting it fixed. It is both a
security fix (wh
Registers in MT7620A_GDMA_OFFSET range were incorrect, except for the
first one GDM_FWD_CFG (which is actually the only one in use).
The next and last register is GDM_SHPR_CFG. All others are not mentioned
in docs.
Signed-off-by: Luiz Angelo Daros de Luca
---
.../ramips/files/drivers/net
mt7620 can forward jumbo frames. The fe_change_mtu() was already
compatible except for the GDM_FWD_CFG address.
An MTU greater than 1500 is required to use DSA tags with a stacked
switch chip.
Signed-off-by: Luiz Angelo Daros de Luca
---
.../files/drivers/net/ethernet/ralink/mtk_eth_soc.c | 13
fe_change_mtu didn't update the registers if the interface was down.
DSA increases the CPU port MTU to accommodate the CPU tag. As this
happens while the CPU port was still down, the chip regs didn't get
updated and larger frames were dropped.
Signed-off-by: Luiz Angelo Dar
uot;ethtool
--offload eth0 tx off" but it would be nice to have it back.
Regards,
---
Luiz Angelo Daros de Luca
luizl...@gmail.com
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
The package update is not a perfect solution but it is better to have
it as is than to remove it.
Updated packages are also used by imagebuilder and attended
sysupgrade. I normally generate a new image to apply updates because
some devices cannot afford the extra installation. If we need updated
p
";
Specially rtl8367 that is used just by a single device. Isn't it
bloating the kernel for that target?
Regards,
---
Luiz Angelo Daros de Luca
luizl...@gmail.com
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
> > @@ -301,9 +301,26 @@ interface_ip_add_target_route(union if_addr *addr,
> > bool v6, struct interface *if
> > route->mask = v6 ? 128 : 32;
> > memcpy(&route->addr, addr, addrsize);
> > memcpy(&route->nexthop, &r_next->nexthop, sizeof(route->nexthop));
> > - route->mtu = r
> I think that netifd really wanted to add a dependency to the first
> route, not the second one.
> Maybe netifd should ignore those routes with types for host
> dependencies, but I don't know the consequences of that change.
Or maybe it is ok to monitor those kinds of routes if their type is pre
ifd really wanted to add a dependency to the first
route, not the second one.
Maybe netifd should ignore those routes with types for host
dependencies, but I don't know the consequences of that change.
Regards,
---
Luiz Angelo Daros de Luca
lui
aybe in the "18.06 era".
Regards,
---
Luiz Angelo Daros de Luca
luizl...@gmail.com
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
> I believe what he meant to say was to make another 19.07.x point
> release with an updated sysupgrade mechanism which would improve the
> situation when upgrading to 21.02.x and, for example, allow
> flashing with non-matching DEVICE_COMPAT_VERSION already when
> specifying the '-n' flag to not k
> > 2) I was pretty fuzzy about what people should do if their target did
> > migrate to DSA. Do we have a guide to help those people through the
> > transition?
>
> We do not support a migration and people have to start with a new fresh
> installation. Doing a backup and restoring some settings
wever, I get no output from:
https://buildbot.openwrt.org/openwrt-21.02/packages/#/builders/12/builds/58/steps/24/logs/stdio
Is there any place to get full buildbot output for packages? Or an
easy way to locally simulate a buildbot?
Regards,
---
Luiz Angelo Daros de Luca
ce the user to set a password.
However, it will never get merged if that setup applies to everything
as it would break many provisioning. It might be overkill but maybe it
looks like a new image flavor...
My 2 cents,
---
Luiz Angelo Daros de Luca
luizl...@gmail.com
Em ter., 6 de j
not sure what it means.
I also used "not retaining the current configuration" as Luci (nor
sysupgrade) does not mention wipe but "Keep settings and retain the
current configuration" (which, by the way, seems to be two redundant
sentences).
Regards,
---
Luiz A
gt; C7,product_ver:5.0.0,special_id:4B52}\n",
>
> .part_trail = 0x00,
> - .soft_ver = "soft_ver:1.0.0\n",
> + .soft_ver = "soft_ver:7.0.0\n",
>
> /* We're using a dynamic kernel/rootfs split here */
> .partitions = {
>
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/mailman/listinfo/openwrt-devel
---
Luiz Angelo Daros de Luca
luizl...@gmail.com
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
et the reader
(wireshark) do it afterwards. But that workaround is not
an option while capturing through the same interface you need to
capture traffic on.
Is this really expected? Maybe a weird mips bug? Or a bad side effect
from some openwrt size optimization?
Regards,
---
Luiz Angelo
> When saving the list of installed pkgs, also store the status of the
> system services. The list is created in the etc/backup folder also
> and formated as:
>
> /etc/init.d/ {enable|disable}
>
> This way it can be sourced after sysupgrade, to restore the previous
> state.
I also liked the idea.
tificate]
[Generate a new certificate request] / [Import the signed
certificate] # if a CSR was generated
[Generate a new Let's Encrypt certificate] # it would be a nice add-on
[Remove current certificate and disable encryption]
The next luci request will redirect the browser to https:/
ifinet_OpenWrt2 # directly referencing
config interface lan
option device brlan #device instead of ifname
option proto static
config interface lan6
option device @lan #the value for lan.device
option proto static
config interface wan
# option device wifinet_wan
option proto dhcp
---
Luiz Angelo Daros de Luca
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
> after-reboot).
It would be better if all migration could occur immediately after the
restore. However, there are two moments when a restore happens: when
the user asks for it and during
a sysupgrade that keeps existing configuration or provides a backup file.
Regards,
---
isagree with point 3. Having a network config that automagically translates
> into different things on different boards makes debugging potential issues
> very hard. The uci network config is too low level for that imho.
You are right. It would not be nice
asier than current swconfig and dsa proposed
configuration.
The main points are to split L2 and L3 confs, split port list into
individual options and let the system decide the best way to implement
the proposed setup.
Regards,
---
Luiz Angelo Daros de Luca
luizl...@gmail.com
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
>
>
>
> Thanks. Where is the beginning of the whole disk image (and end) if I
> want to “dd” it onto an SSD or SD?
>
Meta is at the end. Gunzip will give you a warning and ignored it when
expanded.
First byte of the expanded image is the disk sector 0. It is a normal disk
image with partitions.
em.
---
Luiz Angelo Daros de Luca
luizl...@gmail.com
---
Luiz Angelo Daros de Luca
luizl...@gmail.com
Em sex., 20 de mar. de 2020 às 15:07, Hauke Mehrtens
escreveu:
>
> This updates the shared-lib patch to the recent version from debian
> found here:
only openwrt-19.07 got a fix
(d91b52b1a2edd3645c88b29deb1091ae5f82fda8)
Regards,
---
Luiz Angelo Daros de Luca
luizl...@gmail.com
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo
-0:00
[uid=, driv]
[3.227646] eth0: Atheros AG71xx at 0xb900, irq 4, mode: rgmii
I'm using serial interface and I'm testing using initram.
Wireless and swconfig seems to be OK. However, I get not eth0.
Does anyone have a clue where it is broken?
Regards,
---
Luiz An
Hello,
Thinking on which info the client side would need, I would remove the
minors info if we can just skip to latest. And, It's missing a changelog
link. Also, each release can have its own info.json with more info.
How would it deal with devices that cannot be upgrades (like the past case
of 4
package dir and it built
nicely.
Once a package kernel module is changed on a stable branch, can we rebuild
it with each previous dot releases SDK for each target and subtarget? And,
finally, add the new kmod*.ipk to the respective
//kmods//?
Regards,
---
Luiz Angelo Daros de Luca
> There's no need for this. If it's implemented we could simply
> use it on all chips and gain the increased flash reading speed.
>
Ok. I'm using it during my tests, but I could remove it in the final
version.
> On memory-mapped flash reading, spi controller issues 0x0b
> fast-read instruction.
ast-read" does not fix the issue as well.
Regards,
---
Luiz Angelo Daros de Luca
luizl...@gmail.com
Em qui., 6 de fev. de 2020 às 23:57, Chuanhong Guo
escreveu:
> Hi!
>
> On Fri, Feb 7, 2020 at 6:44 AM Luiz Angelo Daros de Luca
> wrote:
> >
> > Hello,
>
any clue of what could have caused this?
Regards,
---
Luiz Angelo Daros de Luca
luizl...@gmail.com
Em sex., 31 de jan. de 2020 às 03:53, Luiz Angelo Daros de Luca <
luizl...@gmail.com> escreveu:
> Hello,
>
> I'm trying to debug
> https://bugs.openwrt.o
all and without any sequence of printable chars.
There are plenty of longs in the bug report.
Has someone faced something similar?
Regards,
---
Luiz Angelo Daros de Luca
luizl...@gmail.com
___
openwrt-devel mailing list
openwrt-devel@list
clude them.
Can someone add it?
Regards,
---
Luiz Angelo Daros de Luca
luizl...@gmail.com
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Hello,
19.07 page has a Roadmap without dates:
https://openwrt.org/releases/19.07/start#roadmap
It should have some real info with dates, something to make clear that it
does not have a real schedule ("It's ready when it is ready") or simply get
removed.
Regards,
---
Luiz
ws the user to wrongly install snapshot
versions.
Regards,
---
Luiz Angelo Daros de Luca
luizl...@gmail.com
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Hello,
There are a significant amount of devices out there that has 4/32
specs. Even brand new ones.
If there is stability issues with newer OpenWrt versions on those
devices, we should rethink LEDE EOL.
Maintenance burden is directly related to the amount of software to
maintain. At the same tim
Regards,
--
Luiz Angelo Daros de Luca
luizl...@gmail.com
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
.com/luizluca/netifd/commit/7ab84972bda51d34295d1938e07ed7efc3b2215d
Regards,
---
Luiz Angelo Daros de Luca
luizl...@gmail.com
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Hi Paul,
> Very nice, but having read the mail thread around Luiz' his patch, I want to
> ask for a discussion, but outside of that patch.
>
> AFAICT from the discussion it follows that sysupgrade, opkg and UCI should be
> kept (as much as possible) orthogonal. From the thread: opkg cannot alway
quot;DHCP server + static IP address" still works with enterprise but
"DHCP Client", even with an alternative static IP address, might not
work for some home users.
For enterprise users, maybe it's time to customize their own firmware.
Some simple uci-defaults script can do
kages. If a user asked for it, it only
saves a list of installed packages to help reinstalling them.
Regards,
---
Luiz Angelo Daros de Luca
luizl...@gmail.com
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
patches
on github (77) or patchwork (44)
is from developers without commit access. They are potential future
developers that will keep the project
alive. I'm not specific talking about my patches but it would be kind to
encourage new devs to have their work
considered, even to say "
rade for flashing (passing the backup
archive using -f). Flashing depends on external files (/lib/upgrade)
whose changes might also depend on a sysupgrade change.
Regards,
---
Luiz Angelo Daros de Luca
luizl...@gmail.com
___
openwrt-de
gs opkg install
# rm etc/sysupgrade.installed
Signed-off-by: Luiz Angelo Daros de Luca
---
package/base-files/files/sbin/sysupgrade | 30 ++
1 file changed, 30 insertions(+)
diff --git a/package/base-files/files/sbin/sysupgrade
b/package/base-files/files/sbin/sy
changed.
Signed-off-by: Luiz Angelo Daros de Luca
---
package/base-files/files/sbin/sysupgrade | 46 +---
1 file changed, 43 insertions(+), 3 deletions(-)
diff --git a/package/base-files/files/sbin/sysupgrade
b/package/base-files/files/sbin/sysupgrade
index 4d221ef5d
With '-u', for a file /aaa/bbb/ccc enlisted for backup,
it will only get into backup if /rom/aaa/bbb/ccc does not
exist or /aaa/bbb/ccc is different from /rom/aaa/bbb/ccc.
It also works with '-c', but only effective for files touched
but not modified.
Signed-off-by: Luiz
Renamed add_uci_conffiles to add_conffiles as it includes
any conffiles listed, not only UCI ones.
Make do_save_conffiles arg mandatory
Allow other options after -l (like -c)
Signed-off-by: Luiz Angelo Daros de Luca
---
package/base-files/files/sbin/sysupgrade | 15 ---
1 file
My previous patch on Nov2017
(http://lists.infradead.org/pipermail/lede-dev/2017-November/009892.html)
generated some discussion because it depends on the presence of /rom to become
effetive. So I opted to turn it into a new sysupgrade option (-u).
Besides that, I added some more stuff to sysupgr
my
> location.
>
> Many thanks!
> - Nick
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
>
--
Luiz Angelo Daros de Luca
luizl...@gmail.com
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
e than someone's project. However, there is
no need to anyone to leave but a need of power transferring.
The ones with current decision power at OpenWRT will either give away some
of its power or they will lose it all (in favor of a rebooted OpenWRT
leaded by LEAD or because
anies
> > who follow and/or contribute to OpenWrt will stick with it too.
> >
> > kathy
> > ___
> > openwrt-devel mailing list
> > openwrt-devel@lists.openwrt.org
> > https://lists.openwrt.org/cgi-bin/mailman/listi
openwrt customized pkg_extract.c than to
maintain an full opkg fork (with known issues).
deb and rpm are already possible busybox applet. Maybe opkg could also
become one (and share some code with tar/gzip).
Regards,
--
Luiz Angelo Daros de Luca
luizl...@gmail.com
.openwrt.org
> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
>
--
Luiz Angelo Daros de Luca
luizl...@gmail.com
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
free (like #18320) :-)
Regards,
--
Luiz Angelo Daros de Luca
luizl...@gmail.com
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
n to do an upgrade and not a reflash. If you and
the packages are doing the backup correctly, you just need to reinstall all
extra packages after the new system is installed.
Regards,
Em qua, 30 de mar de 2016 02:30, Michal Hrusecky
escreveu:
> Luiz Angelo Daros de Luca - 1:41 30.03.16 wrot
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
>
--
Luiz Angelo Daros de Luca
luizl...@gmail.com
___
openwrt-devel mailing list
not PARTUUID=-02.
I'm able to boot if I manually replace PARTUUID=-02 by /dev/sda2.
Regards,
--
Luiz Angelo Daros de Luca
luizl...@gmail.com
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/ma
we can find a better way
>
> John
> ___________
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
>
--
Luiz Angelo Daros de Luca
luizl...@gmail.com
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
BTW, buildbots are failing because of the change in git check prereq
http://buildbot.openwrt.org:8010/builders/ath25/builds/168/steps/compile_1/logs/stdio
Em sáb, 5 de mar de 2016 às 17:55, Luiz Angelo Daros de Luca <
luizl...@gmail.com> escreveu:
> If a prereq-build command check
If a prereq-build command check defines a command env var (ex: MANPAGER=cat git
...)
prereq SetupHostCommand breaks. This is because it looks for the binary using
which on
the first space-separated item (which might be the env var definition)
This patch replaces bash substitution by a sed regex
o compile again.
> >
> > "
> > elfutils: bump to 0.165
> >
> > Signed-off-by: Luiz Angelo Daros de Luca
> > git-svn-id: svn://svn.openwrt.org/openwrt/trunk@48393
> > 3c298f89-4303-0410-b956-a3cf2f4a3e73"
> Fixed in r48429.
>
> Luiz, the updated elfutils v
Signed-off-by: Luiz Angelo Daros de Luca
---
package/libs/elfutils/Makefile | 8
package/libs/elfutils/patches/003-libint-stub.patch | 2 +-
package/libs/elfutils/patches/005-build_only_libs.patch | 4 ++--
package/libs/elfutils/patches/006-libdw_LIBS.patch
sfdisk $disk --force < /tmp/sfdisk.before >&/dev/null
> + fi
> +}
> +
> platform_do_upgrade() {
> platform_export_bootpart
>
> if [ -b "${BOOTPART%[0-9]}" ]; then
> sync
> + [ $SAVE_PARTITIONS =
t;>
>> --
>> Eric Schultz, Community Manager, prpl Foundation
>> http://www.prplfoundation.org
>> eschu...@prplfoundation.org
>> cell: 920-539-0404
>> skype: ericschultzwi
>> @EricPrpl
>>
>> ___
>> openwrt-devel mailing list
>> openwrt-devel@lists.openwrt.org
>> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
>>
>>
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
>
--
Luiz Angelo Daros de Luca
luizl...@gmail.com
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
t;openwrt-devel mailing list
> >>openwrt-devel@lists.openwrt.org
> >>https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
> >_______
> >openwrt-devel mailing list
> >openwrt-devel@lists.openwrt.org
> >https://lists.openwrt.org/cg
[ "and",
> > [ "eq", "SUBSYSTEM", "usb-serial" ],
> > [ "regex", "DEVNAME",
> > [ "^ttyUSB", "^ttyACM" ]
> > ],
> > ],
>
gt; curious.
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
>
--
Luiz Angelo Daros de Luca
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Patches are refreshed except for elfutils-portability, which is gone:
https://lists.fedorahosted.org/pipermail/elfutils-devel/2015-October/005290.html
Signed-off-by: Luiz Angelo Daros de Luca
---
package/libs/elfutils/Makefile |4 +-
.../patches/001-elfutils
ly appreciated.
>
> BR,
>
> -- Emmanuel Deloget
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
>
--
Luiz Angelo Daros de Luca
__
1 - 100 of 150 matches
Mail list logo
