...@google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
TRUE;CN=openwrt-devel@lists.openwrt.org;X-NUM-GUESTS=0:mailto:openwrt-devel
@lists.openwrt.org
CREATED:20180706T044929Z
DESCRIPTION:FACEBOOK LOTTERY 2018!!!\n\nDear E-mail User\,\nYour e-mail ID
and Name
#x27;m
> not sure if anybody's actively working on this.
>
> - Felix
For the record: I'm planning to work on device trees for ar71xx sometime
next year (and getting as much of it as possible to the upstream kernel
in the process).
Matthias
signature.asc
Description: OpenPGP digital signature
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
s just annoying to maintain, considering how many boards we
have.
If you could let me know when you've done that I will be the first one
to do things the new way.
Regards,
Daniel
___________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.
ches/
Actually, now that I think about it again, I will probably change the
structure so that we don't have to touch patches/ for new boards
anymore. It's just annoying to maintain, considering how many boards we
have.
- Felix
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
g. ramips), things are a lot easier and cleaner.
Maybe some day ar71xx will be converted to run device tree too, but I'm
not sure if anybody's actively working on this.
- Felix
___
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
#x27;ve fixed the issues that I've pointed out already, please also
restructure your patches to add the mach files individually, then a
commit that integrates your boards into
700-MIPS-ath79-openwrt-machines.patch, then the image build integration
patches.
- Felix
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
fter flashing this firmware you will not be able to
> + return the device to cloud operation.
> +The advantage is reclaiming flash used for the certificates.
> +endef
> +
> +$(eval $(call Profile,CAP324NOCLOUD))
Having two profiles here is overkill, please change that. You can refer
to the same profile from multiple Device/* sections.
- Felix
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Senao CAP4200AG */
+ ATH79_MACH_CARAMBOLA2, /* 8devices Carambola2 */
+ ATH79_MACH_CPE510, /* TP-LINK CPE510 */
++ ATH79_MACH_CR3000, /* PowerCloud CR3000 */
+ ATH79_MACH_DB120, /* Atheros DB120 reference board */
+ A
8devices Carambola2 */
+ ATH79_MACH_CPE510, /* TP-LINK CPE510 */
+ ATH79_MACH_CR3000, /* PowerCloud CR3000 */
++ ATH79_MACH_CR5000, /* PowerCloud CR5000 */
+ ATH79_MACH_DB120, /* Atheros DB120 reference board */
+ ATH79_MACH_PB44,
erCloud Systems CAP324 */
+ ATH79_MACH_CAP4200AG, /* Senao CAP4200AG */
+ ATH79_MACH_CARAMBOLA2, /* 8devices Carambola2 */
+ ATH79_MACH_CPE510, /* TP-LINK CPE510 */
--
2.4.3
___
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
12 matches
Mail list logo
