Re: [LEDE-DEV] openwrt and lede - remerge proposal V3

[Felix Fietkau]

On 2017-05-29 09:03, John Crispin wrote:
> (resend, this time as plain text)
> 
> Hi,
> 
> here is a V3 of the remerge proposal, I tried to fold all the comments 
> people made into it, if anything is missing let me know. Please remeber 
> that post remerge anything can be voted on, so cluttering the proposal 
> with many details will delay the remerge even more.
> 
> Ideally we manage to vote during this week.
ACK.

- Felix

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] [OpenWrt-Devel] openwrt and lede - remerge proposal V3

[Rafał Miłecki]

On 29 May 2017 at 09:03, John Crispin  wrote:
> here is a V3 of the remerge proposal, I tried to fold all the comments
> people made into it, if anything is missing let me know. Please remeber that
> post remerge anything can be voted on, so cluttering the proposal with many
> details will delay the remerge even more.
>
> Ideally we manage to vote during this week.

Looks good

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] openwrt and lede - remerge proposal V3

[Eric Luehrsen]

On 05/29/2017 03:03 AM, John Crispin wrote:
> (resend, this time as plain text)
> 
> Hi,
> 
> here is a V3 of the remerge proposal, I tried to fold all the comments 
> people made into it, if anything is missing let me know. Please remeber 
> that post remerge anything can be voted on, so cluttering the proposal 
> with many details will delay the remerge even more.
> 
> Ideally we manage to vote during this week.
>
>  John

I agree with respect to participation as an outsider. Rules, voting, and 
email line items should (continue to) encourage high participation. 
Shifting OpenWrt name to the current LEDE home, bug tracker, and git 
trees might be psychological reenforcement of the same.

- Eric
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] openwrt and lede - remerge proposal V3

[John Crispin]

*) rules
- owrt will adopt the lede rules and voting system



ACK from me aswell.





*) branding
- the owrt side sees no option of using the lede brand
- a (minor) majority voted for openwrt as a name over lede whilst most 
people said they did not care
- as the last vote had a 100% ACK for a remerge using the owrt brand 
is the only feasible option


*) domain
- transfer owner ship to SPI for openwrt.org and lede-project.org
- add them to the pool of urls at digital ocean
- post remerge build a setup where we have several DNS servers in 
various locations

- point git.openwrt.org at the lede git server
- point bugs.openwrt.org to the lede flyspray instance
- keep both wikis and forums as is (we should decide post remerge how 
to proceed to avoid these issues blocking the progress)
- update the lede domain entries for build/download/rsync/... servers 
so that the openwrt domain also points at them


*) SPI
- nominate a new liaison team (imre and john offer to do this, if 
anyone else is interested let us know)

- inform SPI of the new liaisons, voters and project rules
- this should be done early in the remerge process s.t. the domains 
can be handed over


*) github
- start pushing to the openwrt organisation
- cleanup the list of owners in the openwrt organisation
- obsolete all issues on the openwrt organisation and close the issue 
tracker
- go through the open openwrt and lede PRs, pickup whats useful and 
close the rest, asking people to repost (things wont be rebasable anyhow)

- close the lede PR tracker
- obsolete the lede github org after a grace period of 3-6 months

*) landing page
- add a letter of intent / notice to both current landing pages 
announcing the remerge

- update the lede landing page to represent the openwrt name
- update the landing page to have the same look & feel as the current 
openwrt landing page

- point openwrt.org at the lede landing page
- try to find some design guru that will transform the owrt theme to 
one appropriate to this century


*) trac
- trac is already readonly, keep content so that search engines can 
still find the it
- edit the trac html templates, adding a note pointing at the 
bug.openwrt.org instance


*) IRC
- add back cloaking
- give people channel ownership/admin rights

*) email accounts
- currently there are around ~20 active openwrt.org mail accounts (the 
3 owrt devs would like to keep theirs active)
- turn all the webmaster@, hostmaster@, ... accounts into aliases that 
anyone with voting rights can be subscribed to
- ask those people that are no longer active to voluntarily give up 
their accounts
- mail addresses may under no conditions be used for any personal 
business, consultancy, applying for jobs, ... purposes
- any mail sent from an openwrt.org account needs to adhere the 
trademark policy and should only be used for FOSS purposes


*) wiki / forum
- TBD
- asking in either forum/wiki will get a biased vote so keep them both 
around

- start a separate discussion regarding these post remerge

*) LF
- find out what doubts folks have about LF
- find out benefits - we would have their hosting and sponsorship ?!
- start a separate discussion regarding these post remerge

*) git trees
- rebrand the lede tree to openwrt
- work out what has happened inside the openwrt tree since the reboot 
and pick up the useful bits (zoltan has done some prior work on this 
already)


*) mailing list
- ask david to add the openwrt-adm and openwrt lists
- send out invitation mails to the new list
- setup redirect/auto-reply for the existing lists

*) trademark policy
- review/ack imres trademark policy (https://openwrt.org/trademark)

*) timeline
- vote / agree on the proposal within the next week
- work on the action items in the 4 weeks after that

John



___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev


___
openwrt-devel mailing list
openwrt-de...@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel


___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev



___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] [OpenWrt-Devel] Remerge logo ideas

[Eric Luehrsen]

On 05/29/2017 07:45 AM, Imre Kaloz wrote:
> On 2017-05-29 13:10, Jamie Stuart wrote:
>> See another iteration, with:
>>
>> - correct capitalisation
>> - antenna to the side (will not work with lowercase ’n’)
>> - open sans typeface (open source)
>> - mockups of website header
>> - accent colours
>>
>> http://i.imgur.com/ZKtcFXo.png
> 
> Nice :) Personally I like the darker color set of the last, but the 
> layout of the first the most (when the "signal" is at the end).
> 
> 
> Imre

Excellent. Many simple picture-and-word logos lead with the picture and 
follow with the word. This may help with recognition. If an individual 
or product maker is advertising support for OpenWrt, then that may 
strengthen their efforts. Also because it is simple, the choice of color 
may warrant more iteration or time to be sure it right.

- Eric
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] [OpenWrt-Devel] Remerge logo ideas

[John Crispin]

On 29/05/17 19:31, Jamie Stuart wrote:

Tried that Moritz - it just wouldn’t work unfortunately. Neither does adding 
the antenna afterwards

All - see another set of designs. I’ve opted for Roboto Condensed as the logo 
typeface.
Personal favorite is the green as OpenWrt is targeted towards low-power devices.

http://imgur.com/a/TfWxr

What’s the next step here? John - could this be added to the remerge proposal 
v3?


Post re-merge owrt will be governed by the lede rules making logo 
changes and so on a trivial thing to do. we can simply vote on it.






On 29 May 2017, at 19:12, Moritz Warning  wrote:

Looks nice.

random idea, merge antenna with O of OpenWrt?

On 05/29/2017 01:10 PM, Jamie Stuart wrote:

See another iteration, with:

- correct capitalisation
- antenna to the side (will not work with lowercase ’n’)
- open sans typeface (open source)
- mockups of website header
- accent colours

http://i.imgur.com/ZKtcFXo.png



On 29 May 2017, at 13:52, John Crispin  wrote:



On 29/05/17 12:11, Jamie Stuart wrote:

Hi,
First of all, I’m glad to hear the process of remerging LEDE with OpenWrt is 
moving forward.
For what it’s worth, if prefer the LEDE name (it’s friendlier - ‘leddy’ - and 
not tied to the name of an old router!)

However, it seems the consensus is that the OpenWrt name should remain. I 
thought that maybe we should take this opportunity to at least give the project 
an updated look?
Maybe a new logo? I’m personally not one for mascots, so I had a quick go at a 
few simple text-based designs:

http://i.imgur.com/9zyXSYR.png

What are you thoughts?

Jamie, onebillion

Hi,

the correct spelling is OpenWrt with a capital O and W. could you add that to 
the proposal aswell please ? ideally with and without the antenna feature

   John

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev


___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev



___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev


___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev



___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] Generic way to disable Generic Receive Offload (GRO)

[rosenp]

Hmm how about driver side? looking at the source code,
register_netdevice enables GSO and GRO by default. Any way to
explicitly disable it?

On Mon, 2017-05-29 at 14:34 -0700, Florian Fainelli wrote:
> Le 05/29/17 à 13:55, ros...@gmail.com a écrit :
> > So LEDE is using fq_codel by default. On the cake homepage is this
> > little sentence:
> > 
> > "Preliminary indications are that not doing GRO “peeling” is where
> > the
> > first generation of fq_codel enabled 802.11ac routers went wrong in
> > their QoS systems."
> > 
> > On my Archer C7v2, I've been able to observe that by disabling GRO
> > using ethtool, I've been able to get a 1-2ms reduction in my
> > overall
> > latency when browsing the internet.
> > 
> > Anyone know if there is a way to disable GRO without having to
> > install
> > ethtool?
> 
> ethtool just send an ioctl so you can write a few lines of C code
> that
> would do the same thing.
> 
> > 
> > On a side note, the ethernet driver for the Archer needs some love.
> > It's not using the correct API for GRO (using netif_receive_skb
> > instead
> > of napi_gro_receive).
> > 
> > ___
> > Lede-dev mailing list
> > Lede-dev@lists.infradead.org
> > http://lists.infradead.org/mailman/listinfo/lede-dev
> > 
> 
> 

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] Generic way to disable Generic Receive Offload (GRO)

[Florian Fainelli]

Le 05/29/17 à 13:55, ros...@gmail.com a écrit :
> So LEDE is using fq_codel by default. On the cake homepage is this
> little sentence:
> 
> "Preliminary indications are that not doing GRO “peeling” is where the
> first generation of fq_codel enabled 802.11ac routers went wrong in
> their QoS systems."
> 
> On my Archer C7v2, I've been able to observe that by disabling GRO
> using ethtool, I've been able to get a 1-2ms reduction in my overall
> latency when browsing the internet.
> 
> Anyone know if there is a way to disable GRO without having to install
> ethtool?

ethtool just send an ioctl so you can write a few lines of C code that
would do the same thing.

> 
> On a side note, the ethernet driver for the Archer needs some love.
> It's not using the correct API for GRO (using netif_receive_skb instead
> of napi_gro_receive).
> 
> ___
> Lede-dev mailing list
> Lede-dev@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/lede-dev
> 


-- 
Florian

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] [OpenWrt-Devel] openwrt and lede - remerge proposal V3

[Hans Dedecker]

On Mon, May 29, 2017 at 9:03 AM, John Crispin  wrote:
> (resend, this time as plain text)
>
>
> Hi,
>
> here is a V3 of the remerge proposal, I tried to fold all the comments
> people made into it, if anything is missing let me know. Please remeber that
> post remerge anything can be voted on, so cluttering the proposal with many
> details will delay the remerge even more.
>
> Ideally we manage to vote during this week.
>
>
> John
>
> *) rules
> - owrt will adopt the lede rules and voting system
>
> *) branding
> - the owrt side sees no option of using the lede brand
> - a (minor) majority voted for openwrt as a name over lede whilst most
> people said they did not care
> - as the last vote had a 100% ACK for a remerge using the owrt brand is the
> only feasible option
>
> *) domain
> - transfer owner ship to SPI for openwrt.org and lede-project.org
> - add them to the pool of urls at digital ocean
> - post remerge build a setup where we have several DNS servers in various
> locations
> - point git.openwrt.org at the lede git server
> - point bugs.openwrt.org to the lede flyspray instance
> - keep both wikis and forums as is (we should decide post remerge how to
> proceed to avoid these issues blocking the progress)
> - update the lede domain entries for build/download/rsync/... servers so
> that the openwrt domain also points at them
>
> *) SPI
> - nominate a new liaison team (imre and john offer to do this, if anyone
> else is interested let us know)
> - inform SPI of the new liaisons, voters and project rules
> - this should be done early in the remerge process s.t. the domains can be
> handed over
>
> *) github
> - start pushing to the openwrt organisation
> - cleanup the list of owners in the openwrt organisation
> - obsolete all issues on the openwrt organisation and close the issue
> tracker
> - go through the open openwrt and lede PRs, pickup whats useful and close
> the rest, asking people to repost (things wont be rebasable anyhow)
> - close the lede PR tracker
> - obsolete the lede github org after a grace period of 3-6 months
>
> *) landing page
> - add a letter of intent / notice to both current landing pages announcing
> the remerge
> - update the lede landing page to represent the openwrt name
> - update the landing page to have the same look & feel as the current
> openwrt landing page
> - point openwrt.org at the lede landing page
> - try to find some design guru that will transform the owrt theme to one
> appropriate to this century
>
> *) trac
> - trac is already readonly, keep content so that search engines can still
> find the it
> - edit the trac html templates, adding a note pointing at the
> bug.openwrt.org instance
>
> *) IRC
> - add back cloaking
> - give people channel ownership/admin rights
>
> *) email accounts
> - currently there are around ~20 active openwrt.org mail accounts (the 3
> owrt devs would like to keep theirs active)
> - turn all the webmaster@, hostmaster@, ... accounts into aliases that
> anyone with voting rights can be subscribed to
> - ask those people that are no longer active to voluntarily give up their
> accounts
> - mail addresses may under no conditions be used for any personal business,
> consultancy, applying for jobs, ... purposes
> - any mail sent from an openwrt.org account needs to adhere the trademark
> policy and should only be used for FOSS purposes
>
> *) wiki / forum
> - TBD
> - asking in either forum/wiki will get a biased vote so keep them both
> around
> - start a separate discussion regarding these post remerge
>
> *) LF
> - find out what doubts folks have about LF
> - find out benefits - we would have their hosting and sponsorship ?!
> - start a separate discussion regarding these post remerge
>
> *) git trees
> - rebrand the lede tree to openwrt
> - work out what has happened inside the openwrt tree since the reboot and
> pick up the useful bits (zoltan has done some prior work on this already)
>
> *) mailing list
> - ask david to add the openwrt-adm and openwrt lists
> - send out invitation mails to the new list
> - setup redirect/auto-reply for the existing lists
>
> *) trademark policy
> - review/ack imres trademark policy (https://openwrt.org/trademark)
>
> *) timeline
> - vote / agree on the proposal within the next week
Ack from my side on all the listed items

Thx for compiling the list John

Hans
> - work on the action items in the 4 weeks after that
>
> John
>
>
>
> ___
> Lede-dev mailing list
> Lede-dev@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/lede-dev
>
>
> ___
> openwrt-devel mailing list
> openwrt-de...@lists.openwrt.org
> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
> ___
> openwrt-devel mailing list
> openwrt-de...@lists.openwrt.org
> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [LEDE-DEV] [OpenWrt-Devel] openwrt and lede - remerge proposal V3

[Daniel Golle]

On Mon, May 29, 2017 at 09:03:57AM +0200, John Crispin wrote:
> (resend, this time as plain text)
> 
> Hi,
> 
> here is a V3 of the remerge proposal, I tried to fold all the comments
> people made into it, if anything is missing let me know. Please remeber that
> post remerge anything can be voted on, so cluttering the proposal with many
> details will delay the remerge even more.
> 
> Ideally we manage to vote during this week.

+1 ACK

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] [OpenWrt-Hackers] openwrt and lede - remerge proposal V3

[Florian Fainelli]

Le 05/29/17 à 00:03, John Crispin a écrit :
> (resend, this time as plain text)
> 
> Hi,
> 
> here is a V3 of the remerge proposal, I tried to fold all the comments
> people made into it, if anything is missing let me know. Please remeber
> that post remerge anything can be voted on, so cluttering the proposal
> with many details will delay the remerge even more.
> 
> Ideally we manage to vote during this week.

Ack on everything, let's get this moving!
-- 
Florian

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] openwrt and lede - remerge proposal V3

[Hauke Mehrtens]

On 05/29/2017 09:03 AM, John Crispin wrote:
> (resend, this time as plain text)
> 
> Hi,
> 
> here is a V3 of the remerge proposal, I tried to fold all the comments
> people made into it, if anything is missing let me know. Please remeber
> that post remerge anything can be voted on, so cluttering the proposal
> with many details will delay the remerge even more.
> 
> Ideally we manage to vote during this week.
> 
> 
> John

Looks good, ack from me.

Hauke

> 
> *) rules
> - owrt will adopt the lede rules and voting system
> 
> *) branding
> - the owrt side sees no option of using the lede brand
> - a (minor) majority voted for openwrt as a name over lede whilst most
> people said they did not care
> - as the last vote had a 100% ACK for a remerge using the owrt brand is
> the only feasible option
> 
> *) domain
> - transfer owner ship to SPI for openwrt.org and lede-project.org
> - add them to the pool of urls at digital ocean
> - post remerge build a setup where we have several DNS servers in
> various locations
> - point git.openwrt.org at the lede git server
> - point bugs.openwrt.org to the lede flyspray instance
> - keep both wikis and forums as is (we should decide post remerge how to
> proceed to avoid these issues blocking the progress)
> - update the lede domain entries for build/download/rsync/... servers so
> that the openwrt domain also points at them
> 
> *) SPI
> - nominate a new liaison team (imre and john offer to do this, if anyone
> else is interested let us know)
> - inform SPI of the new liaisons, voters and project rules
> - this should be done early in the remerge process s.t. the domains can
> be handed over
> 
> *) github
> - start pushing to the openwrt organisation
> - cleanup the list of owners in the openwrt organisation
> - obsolete all issues on the openwrt organisation and close the issue
> tracker
> - go through the open openwrt and lede PRs, pickup whats useful and
> close the rest, asking people to repost (things wont be rebasable anyhow)
> - close the lede PR tracker
> - obsolete the lede github org after a grace period of 3-6 months
> 
> *) landing page
> - add a letter of intent / notice to both current landing pages
> announcing the remerge
> - update the lede landing page to represent the openwrt name
> - update the landing page to have the same look & feel as the current
> openwrt landing page
> - point openwrt.org at the lede landing page
> - try to find some design guru that will transform the owrt theme to one
> appropriate to this century
> 
> *) trac
> - trac is already readonly, keep content so that search engines can
> still find the it
> - edit the trac html templates, adding a note pointing at the
> bug.openwrt.org instance
> 
> *) IRC
> - add back cloaking
> - give people channel ownership/admin rights
> 
> *) email accounts
> - currently there are around ~20 active openwrt.org mail accounts (the 3
> owrt devs would like to keep theirs active)
> - turn all the webmaster@, hostmaster@, ... accounts into aliases that
> anyone with voting rights can be subscribed to
> - ask those people that are no longer active to voluntarily give up
> their accounts
> - mail addresses may under no conditions be used for any personal
> business, consultancy, applying for jobs, ... purposes
> - any mail sent from an openwrt.org account needs to adhere the
> trademark policy and should only be used for FOSS purposes
> 
> *) wiki / forum
> - TBD
> - asking in either forum/wiki will get a biased vote so keep them both
> around
> - start a separate discussion regarding these post remerge
> 
> *) LF
> - find out what doubts folks have about LF
> - find out benefits - we would have their hosting and sponsorship ?!
> - start a separate discussion regarding these post remerge
> 
> *) git trees
> - rebrand the lede tree to openwrt
> - work out what has happened inside the openwrt tree since the reboot
> and pick up the useful bits (zoltan has done some prior work on this
> already)
> 
> *) mailing list
> - ask david to add the openwrt-adm and openwrt lists
> - send out invitation mails to the new list
> - setup redirect/auto-reply for the existing lists
> 
> *) trademark policy
> - review/ack imres trademark policy (https://openwrt.org/trademark)
> 
> *) timeline
> - vote / agree on the proposal within the next week
> - work on the action items in the 4 weeks after that
> 
> John
> 



___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] [OpenWrt-Devel] Remerge logo ideas

[Jamie Stuart]

Tried that Moritz - it just wouldn’t work unfortunately. Neither does adding 
the antenna afterwards

All - see another set of designs. I’ve opted for Roboto Condensed as the logo 
typeface.
Personal favorite is the green as OpenWrt is targeted towards low-power devices.

http://imgur.com/a/TfWxr

What’s the next step here? John - could this be added to the remerge proposal 
v3?



> On 29 May 2017, at 19:12, Moritz Warning  wrote:
> 
> Looks nice.
> 
> random idea, merge antenna with O of OpenWrt?
> 
> On 05/29/2017 01:10 PM, Jamie Stuart wrote:
>> See another iteration, with:
>> 
>> - correct capitalisation
>> - antenna to the side (will not work with lowercase ’n’)
>> - open sans typeface (open source)
>> - mockups of website header
>> - accent colours
>> 
>> http://i.imgur.com/ZKtcFXo.png
>> 
>> 
>>> On 29 May 2017, at 13:52, John Crispin  wrote:
>>> 
>>> 
>>> 
>>> On 29/05/17 12:11, Jamie Stuart wrote:
 Hi,
 First of all, I’m glad to hear the process of remerging LEDE with OpenWrt 
 is moving forward.
 For what it’s worth, if prefer the LEDE name (it’s friendlier - ‘leddy’ - 
 and not tied to the name of an old router!)
 
 However, it seems the consensus is that the OpenWrt name should remain. I 
 thought that maybe we should take this opportunity to at least give the 
 project an updated look?
 Maybe a new logo? I’m personally not one for mascots, so I had a quick go 
 at a few simple text-based designs:
 
 http://i.imgur.com/9zyXSYR.png
 
 What are you thoughts?
 
 Jamie, onebillion
>>> 
>>> Hi,
>>> 
>>> the correct spelling is OpenWrt with a capital O and W. could you add that 
>>> to the proposal aswell please ? ideally with and without the antenna feature
>>> 
>>>   John
 ___
 Lede-dev mailing list
 Lede-dev@lists.infradead.org
 http://lists.infradead.org/mailman/listinfo/lede-dev
>>> 
>> 
>> 
>> ___
>> Lede-dev mailing list
>> Lede-dev@lists.infradead.org
>> http://lists.infradead.org/mailman/listinfo/lede-dev
>> 
> 
> 
> ___
> Lede-dev mailing list
> Lede-dev@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/lede-dev


___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] dropbear & gcc 7.1.0

[Kevin Darbyshire-Bryant]

On 29/05/17 16:54, e9hack wrote:

Am 29.05.2017 um 10:13 schrieb Bastian Bittorf:

* Syrone Wong  [29.05.2017 10:03]:

have you tried to '/etc/init.d/dropbear'?


The problem is you cannot access the router, which means you cannot
execute any commands.


ok, maybe you can execute a command with LuCI?
(i'am not familiar with LuCI)
maybe you can try serial console.
maybe you can put that into /etc/rc.local

i wanted to write: '/etc/init.d/dropbear restart', sorry for that.



I did try it already with custom commands from LuCI. It doesn't help. Dropbear 
is still running but to connect isn't
possible.


Had a really quick play with this and as I suspected it's related to 
compiler optimization flags.  In essence, if I compile with '-Os' then 
dropbear plays dumb, with my usual (but different from default) of '-O2' 
then dropbear, gcc 7 & mips get on fine, irrespective of target -march 
settings.


So as further totally wild guesses and on the basis 'ssh -vvv' shows 
things hanging during the initial ECDH key exchange, I'm going to guess 
this is happening somewhere in the libtommath/crypt libraries.


Kevin

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] [OpenWrt-Hackers] [OpenWrt-Devel] openwrt and lede - remerge proposal V3

[Matteo Croce]

Looks very good to me

2017-05-29 18:38 GMT+02:00 Stijn Tintel :
> On 29-05-17 09:03, John Crispin wrote:
>> (resend, this time as plain text)
>>
>> Hi,
>>
>> here is a V3 of the remerge proposal, I tried to fold all the comments
>> people made into it, if anything is missing let me know. Please
>> remeber that post remerge anything can be voted on, so cluttering the
>> proposal with many details will delay the remerge even more.
>>
>> Ideally we manage to vote during this week.
>>
> Full ACK from me.
>
> Thanks,
> Stijn
> ___
> openwrt-hackers mailing list
> openwrt-hack...@lists.openwrt.org
> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-hackers



-- 
Matteo Croce
OpenWrt Developer

perl -e 'for($t=0;;$t++){print chr($t*($t>>8|$t>>13)&255)}' |aplay

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] [OpenWrt-Devel] openwrt and lede - remerge proposal V3

[Stijn Tintel]

On 29-05-17 09:03, John Crispin wrote:
> (resend, this time as plain text)
>
> Hi,
>
> here is a V3 of the remerge proposal, I tried to fold all the comments
> people made into it, if anything is missing let me know. Please
> remeber that post remerge anything can be voted on, so cluttering the
> proposal with many details will delay the remerge even more.
>
> Ideally we manage to vote during this week.
>
Full ACK from me.

Thanks,
Stijn

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] [PATCH] Adding acct_interval to wireless configuration

[tapper]

Hi there mate thanks for your first patch!I am not a coder or  a dev. I 
just wanted to let you know that OpenWRT and LEDE are in the middle of 
re merging, so if you don't get any feedback for your patch it's because 
people are trying to sort out the re merging not ignoring you. If you 
dont get your patch merged or any feed back in 1-2 weeks then resend 
your mail. I am glad that we are getting new people around so thanks 
again. Tapper


On 29/05/2017 13:04, Yury Shvedov wrote:

Hi, I'm new here and I wonder why there is still no UCI option to configure 
Radius-Accounting-Interim-Interval.
I've made a patch to fix that and like to share it to others and ask is there 
any serious reason for lack of such
option?

Make an ability to configure Accounting-Interim-Interval via UCI

Signed-off-by: Yury Shvedov 
---
  package/network/services/hostapd/files/hostapd.sh | 5 -
  1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/package/network/services/hostapd/files/hostapd.sh 
b/package/network/services/hostapd/files/hostapd.sh
index 6fb902e376..e6bccef39b 100644
--- a/package/network/services/hostapd/files/hostapd.sh
+++ b/package/network/services/hostapd/files/hostapd.sh
@@ -151,6 +151,7 @@ hostapd_common_add_bss_config() {
config_add_string acct_server
config_add_string acct_secret
config_add_int acct_port
+   config_add_int acct_interval
config_add_string dae_client
config_add_string dae_secret
@@ -208,7 +209,7 @@ hostapd_set_bss_options() {
wps_independent wps_device_type wps_device_name 
wps_manufacturer wps_pin \
macfilter ssid wmm uapsd hidden short_preamble rsn_preauth \
iapp_interface eapol_version acct_server acct_secret acct_port \
-   dynamic_vlan ieee80211w
+   acct_interval dynamic_vlan ieee80211w
set_default isolate 0
set_default maxassoc 0
@@ -249,6 +250,8 @@ hostapd_set_bss_options() {
append bss_conf "acct_server_port=$acct_port" "$N"
[ -n "$acct_secret" ] && \
append bss_conf "acct_server_shared_secret=$acct_secret" 
"$N"
+   [ -n "$acct_interval" ] && \
+   append bss_conf "radius_acct_interim_interval=$acct_interval" 
"$N"
}
local vlan_possible=""




___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] [OpenWrt-Devel] Remerge logo ideas

[Moritz Warning]

Looks nice.

random idea, merge antenna with O of OpenWrt?

On 05/29/2017 01:10 PM, Jamie Stuart wrote:

See another iteration, with:

- correct capitalisation
- antenna to the side (will not work with lowercase ’n’)
- open sans typeface (open source)
- mockups of website header
- accent colours

http://i.imgur.com/ZKtcFXo.png



On 29 May 2017, at 13:52, John Crispin  wrote:



On 29/05/17 12:11, Jamie Stuart wrote:

Hi,
First of all, I’m glad to hear the process of remerging LEDE with OpenWrt is 
moving forward.
For what it’s worth, if prefer the LEDE name (it’s friendlier - ‘leddy’ - and 
not tied to the name of an old router!)

However, it seems the consensus is that the OpenWrt name should remain. I 
thought that maybe we should take this opportunity to at least give the project 
an updated look?
Maybe a new logo? I’m personally not one for mascots, so I had a quick go at a 
few simple text-based designs:

http://i.imgur.com/9zyXSYR.png

What are you thoughts?

Jamie, onebillion


Hi,

the correct spelling is OpenWrt with a capital O and W. could you add that to 
the proposal aswell please ? ideally with and without the antenna feature

   John

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev





___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev




___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] dropbear & gcc 7.1.0

[e9hack]

Am 29.05.2017 um 10:13 schrieb Bastian Bittorf:
> * Syrone Wong  [29.05.2017 10:03]:
>>> have you tried to '/etc/init.d/dropbear'?
>>
>> The problem is you cannot access the router, which means you cannot
>> execute any commands.
> 
> ok, maybe you can execute a command with LuCI?
> (i'am not familiar with LuCI)
> maybe you can try serial console.
> maybe you can put that into /etc/rc.local
> 
> i wanted to write: '/etc/init.d/dropbear restart', sorry for that.
> 

I did try it already with custom commands from LuCI. It doesn't help. Dropbear 
is still running but to connect isn't
possible.

Regards,
Hartmut


___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] openwrt and lede - remerge proposal V3

[Matthias Schiffer]

On 05/29/2017 09:03 AM, John Crispin wrote:
> (resend, this time as plain text)
> 
> Hi,
> 
> here is a V3 of the remerge proposal, I tried to fold all the comments
> people made into it, if anything is missing let me know. Please remeber
> that post remerge anything can be voted on, so cluttering the proposal with
> many details will delay the remerge even more.
> 
> Ideally we manage to vote during this week.
> 
> 
> John

The proposal looks very good, and I think all important points have been
discussed over the last weeks. So that's an ACK from my side.

Matthias


> 
> *) rules
> - owrt will adopt the lede rules and voting system
> 
> *) branding
> - the owrt side sees no option of using the lede brand
> - a (minor) majority voted for openwrt as a name over lede whilst most
> people said they did not care
> - as the last vote had a 100% ACK for a remerge using the owrt brand is the
> only feasible option
> 
> *) domain
> - transfer owner ship to SPI for openwrt.org and lede-project.org
> - add them to the pool of urls at digital ocean
> - post remerge build a setup where we have several DNS servers in various
> locations
> - point git.openwrt.org at the lede git server
> - point bugs.openwrt.org to the lede flyspray instance
> - keep both wikis and forums as is (we should decide post remerge how to
> proceed to avoid these issues blocking the progress)
> - update the lede domain entries for build/download/rsync/... servers so
> that the openwrt domain also points at them
> 
> *) SPI
> - nominate a new liaison team (imre and john offer to do this, if anyone
> else is interested let us know)
> - inform SPI of the new liaisons, voters and project rules
> - this should be done early in the remerge process s.t. the domains can be
> handed over
> 
> *) github
> - start pushing to the openwrt organisation
> - cleanup the list of owners in the openwrt organisation
> - obsolete all issues on the openwrt organisation and close the issue tracker
> - go through the open openwrt and lede PRs, pickup whats useful and close
> the rest, asking people to repost (things wont be rebasable anyhow)
> - close the lede PR tracker
> - obsolete the lede github org after a grace period of 3-6 months
> 
> *) landing page
> - add a letter of intent / notice to both current landing pages announcing
> the remerge
> - update the lede landing page to represent the openwrt name
> - update the landing page to have the same look & feel as the current
> openwrt landing page
> - point openwrt.org at the lede landing page
> - try to find some design guru that will transform the owrt theme to one
> appropriate to this century
> 
> *) trac
> - trac is already readonly, keep content so that search engines can still
> find the it
> - edit the trac html templates, adding a note pointing at the
> bug.openwrt.org instance
> 
> *) IRC
> - add back cloaking
> - give people channel ownership/admin rights
> 
> *) email accounts
> - currently there are around ~20 active openwrt.org mail accounts (the 3
> owrt devs would like to keep theirs active)
> - turn all the webmaster@, hostmaster@, ... accounts into aliases that
> anyone with voting rights can be subscribed to
> - ask those people that are no longer active to voluntarily give up their
> accounts
> - mail addresses may under no conditions be used for any personal business,
> consultancy, applying for jobs, ... purposes
> - any mail sent from an openwrt.org account needs to adhere the trademark
> policy and should only be used for FOSS purposes
> 
> *) wiki / forum
> - TBD
> - asking in either forum/wiki will get a biased vote so keep them both around
> - start a separate discussion regarding these post remerge
> 
> *) LF
> - find out what doubts folks have about LF
> - find out benefits - we would have their hosting and sponsorship ?!
> - start a separate discussion regarding these post remerge
> 
> *) git trees
> - rebrand the lede tree to openwrt
> - work out what has happened inside the openwrt tree since the reboot and
> pick up the useful bits (zoltan has done some prior work on this already)
> 
> *) mailing list
> - ask david to add the openwrt-adm and openwrt lists
> - send out invitation mails to the new list
> - setup redirect/auto-reply for the existing lists
> 
> *) trademark policy
> - review/ack imres trademark policy (https://openwrt.org/trademark)
> 
> *) timeline
> - vote / agree on the proposal within the next week
> - work on the action items in the 4 weeks after that
> 
> John



signature.asc
Description: OpenPGP digital signature
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] [PATCH v3 6/6] ipq806x: Enable ubi image for ipq40xx AP-DK04.1-C1 board

[Ram Chandra Jangir]

Thanks John,

Actually this was based on https://patchwork.ozlabs.org/patch/752962/ and it
got failed to apply.  I will resend this last patch. 
Can you please help to merge this https://patchwork.ozlabs.org/patch/752962/
, if it takes some time to review/merge then can you please help to merge
the pinctrl patch(852-ipq4019-pinctrl-Updated-various-Pin-definitions.patch)
available in this.
 It is required for qpic nand pin definitions for nand boot.

Thanks,
Ram

On Monday, May 29, 2017 11:56 AM, John Crispin  wrote:

>Hi Ram,

>thanks for splitting the series up, i merged the first  patches into my
tree, however the final patch fails to apply. could you rebase/resend just
that last one please ?

> John

>On 25/05/17 01:31, Ram Chandra Jangir wrote:
> This change enables ubi image for IPQ40xx AP-DK04.1-C1 board, also add 
> sysupgrage support for AP-DK04.1-C1 and generates a sysupgrade.tar 
> image.
>
> Testing:
>   *Tested on IPQ40xx AP-DK04.1-C1:
> a. NAND boot
> b. ubi sysupgrade
>
> Signed-off-by: Ram Chandra Jangir 
> ---
>
> Changes since v2:
>   *Splitted to individual patches
>
>   target/linux/ipq806x/base-files/lib/upgrade/platform.sh | 1 +
>   target/linux/ipq806x/image/Makefile | 1 +
>   2 files changed, 2 insertions(+)
>
> diff --git a/target/linux/ipq806x/base-files/lib/upgrade/platform.sh 
> b/target/linux/ipq806x/base-files/lib/upgrade/platform.sh
> index 8970285..fd08db3 100644
> --- a/target/linux/ipq806x/base-files/lib/upgrade/platform.sh
> +++ b/target/linux/ipq806x/base-files/lib/upgrade/platform.sh
> @@ -12,6 +12,7 @@ platform_pre_upgrade() {
>   
>   case "$board" in
>   ap148 |\
> + ap-dk04.1-c1 |\
>   d7800 |\
>   nbg6817 |\
>   r7500 |\
> diff --git a/target/linux/ipq806x/image/Makefile 
> b/target/linux/ipq806x/image/Makefile
> index 6ebcde5..c49a73e 100644
> --- a/target/linux/ipq806x/image/Makefile
> +++ b/target/linux/ipq806x/image/Makefile
> @@ -264,6 +264,7 @@ endef
>   
>   define Device/AP-DK04.1-C1
>   $(call Device/FitImage)
> + $(call Device/UbiFit)
>   DEVICE_DTS := qcom-ipq4019-ap.dk04.1-c1
>   KERNEL_LOADADDR := 0x80208000
>   KERNEL_INSTALL := 1



___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

[LEDE-DEV] [PATCH] Adding acct_interval to wireless configuration

[Yury Shvedov]

Hi, I'm new here and I wonder why there is still no UCI option to configure 
Radius-Accounting-Interim-Interval. 
I've made a patch to fix that and like to share it to others and ask is there 
any serious reason for lack of such
option?

Make an ability to configure Accounting-Interim-Interval via UCI

Signed-off-by: Yury Shvedov 
---
 package/network/services/hostapd/files/hostapd.sh | 5 -
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/package/network/services/hostapd/files/hostapd.sh 
b/package/network/services/hostapd/files/hostapd.sh
index 6fb902e376..e6bccef39b 100644
--- a/package/network/services/hostapd/files/hostapd.sh
+++ b/package/network/services/hostapd/files/hostapd.sh
@@ -151,6 +151,7 @@ hostapd_common_add_bss_config() {
config_add_string acct_server
config_add_string acct_secret
config_add_int acct_port
+   config_add_int acct_interval
config_add_string dae_client
config_add_string dae_secret
@@ -208,7 +209,7 @@ hostapd_set_bss_options() {
wps_independent wps_device_type wps_device_name 
wps_manufacturer wps_pin \
macfilter ssid wmm uapsd hidden short_preamble rsn_preauth \
iapp_interface eapol_version acct_server acct_secret acct_port \
-   dynamic_vlan ieee80211w
+   acct_interval dynamic_vlan ieee80211w
set_default isolate 0
set_default maxassoc 0
@@ -249,6 +250,8 @@ hostapd_set_bss_options() {
append bss_conf "acct_server_port=$acct_port" "$N"
[ -n "$acct_secret" ] && \
append bss_conf 
"acct_server_shared_secret=$acct_secret" "$N"
+   [ -n "$acct_interval" ] && \
+   append bss_conf 
"radius_acct_interim_interval=$acct_interval" "$N"
}
local vlan_possible=""
-- 
2.13.0


___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] [OpenWrt-Devel] Remerge logo ideas

[Imre Kaloz]

On 2017-05-29 13:10, Jamie Stuart wrote:

See another iteration, with:

- correct capitalisation
- antenna to the side (will not work with lowercase ’n’)
- open sans typeface (open source)
- mockups of website header
- accent colours

http://i.imgur.com/ZKtcFXo.png


Nice :) Personally I like the darker color set of the last, but the 
layout of the first the most (when the "signal" is at the end).



Imre

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] [OpenWrt-Devel] Remerge logo ideas

[Jamie Stuart]

See another iteration, with:

- correct capitalisation
- antenna to the side (will not work with lowercase ’n’)
- open sans typeface (open source)
- mockups of website header
- accent colours

http://i.imgur.com/ZKtcFXo.png


> On 29 May 2017, at 13:52, John Crispin  wrote:
> 
> 
> 
> On 29/05/17 12:11, Jamie Stuart wrote:
>> Hi,
>> First of all, I’m glad to hear the process of remerging LEDE with OpenWrt is 
>> moving forward.
>> For what it’s worth, if prefer the LEDE name (it’s friendlier - ‘leddy’ - 
>> and not tied to the name of an old router!)
>> 
>> However, it seems the consensus is that the OpenWrt name should remain. I 
>> thought that maybe we should take this opportunity to at least give the 
>> project an updated look?
>> Maybe a new logo? I’m personally not one for mascots, so I had a quick go at 
>> a few simple text-based designs:
>> 
>> http://i.imgur.com/9zyXSYR.png
>> 
>> What are you thoughts?
>> 
>> Jamie, onebillion
> 
> Hi,
> 
> the correct spelling is OpenWrt with a capital O and W. could you add that to 
> the proposal aswell please ? ideally with and without the antenna feature
> 
>John
>> ___
>> Lede-dev mailing list
>> Lede-dev@lists.infradead.org
>> http://lists.infradead.org/mailman/listinfo/lede-dev
> 


___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] [OpenWrt-Devel] Remerge logo ideas

[John Crispin]

On 29/05/17 12:11, Jamie Stuart wrote:

Hi,
First of all, I’m glad to hear the process of remerging LEDE with OpenWrt is 
moving forward.
For what it’s worth, if prefer the LEDE name (it’s friendlier - ‘leddy’ - and 
not tied to the name of an old router!)

However, it seems the consensus is that the OpenWrt name should remain. I 
thought that maybe we should take this opportunity to at least give the project 
an updated look?
Maybe a new logo? I’m personally not one for mascots, so I had a quick go at a 
few simple text-based designs:

http://i.imgur.com/9zyXSYR.png

What are you thoughts?

Jamie, onebillion


Hi,

the correct spelling is OpenWrt with a capital O and W. could you add 
that to the proposal aswell please ? ideally with and without the 
antenna feature


John

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev



___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] [OpenWrt-Devel] Remerge logo ideas

[Martin Tippmann]

On Mon, May 29, 2017 at 12:11 PM, Jamie Stuart  wrote:
> Hi,
> First of all, I’m glad to hear the process of remerging LEDE with OpenWrt is 
> moving forward.
> For what it’s worth, if prefer the LEDE name (it’s friendlier - ‘leddy’ - and 
> not tied to the name of an old router!)
>
> However, it seems the consensus is that the OpenWrt name should remain. I 
> thought that maybe we should take this opportunity to at least give the 
> project an updated look?
> Maybe a new logo? I’m personally not one for mascots, so I had a quick go at 
> a few simple text-based designs:
>
> http://i.imgur.com/9zyXSYR.png
>
> What are you thoughts?

+1

The logo looks great. Is the used font free to use? There could be a
problems if it's a commercial font, depending on the licence?

Maybe LEDE/OpenWRT could create some minimal "corporate identity" like
some base colors and fonts that are used on all websites. I guess it
shouldn't more be than a few CSS rules but having a somewhat unified
look across all websites / pages is a nice thing to have. Arch Linux
is a good example, they also use Flyspray and a Wiki and gitweb but
have a similiar look and feel everywhere.

regards
Martin

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

[LEDE-DEV] [OpenWrt-Devel] Remerge logo ideas

[Jamie Stuart]

Hi,
First of all, I’m glad to hear the process of remerging LEDE with OpenWrt is 
moving forward.
For what it’s worth, if prefer the LEDE name (it’s friendlier - ‘leddy’ - and 
not tied to the name of an old router!)

However, it seems the consensus is that the OpenWrt name should remain. I 
thought that maybe we should take this opportunity to at least give the project 
an updated look?
Maybe a new logo? I’m personally not one for mascots, so I had a quick go at a 
few simple text-based designs:

http://i.imgur.com/9zyXSYR.png

What are you thoughts?

Jamie, onebillion
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

[LEDE-DEV] [PATCH v2] imx6: disable UART dma

[Koen Vandeputte]

Fixes these prints on boot:

[   13.785600] imx-uart 202.serial: DMA transaction error.
[   13.793134] imx-uart 202.serial: DMA transaction error.
[   13.798721] imx-uart 202.serial: DMA transaction error.

Based on following upstream patch by Tim Harvey (Gateworks):

https://github.com/Gateworks/openwrt/commit/80a01b6582f94c4547f39d3a25e0a1e9b6eb9877

TX complete DMA messages are getting missed.
This is also currently an issue in mainline.
For now we will disable DMA in serial/imx.c.

This resolves an issue encountered with RS485 transmit.

Signed-off-by: Koen Vandeputte 
---
 .../imx6/patches-4.9/210-disable-uart-dma.patch| 23 ++
 1 file changed, 23 insertions(+)
 create mode 100644 target/linux/imx6/patches-4.9/210-disable-uart-dma.patch

diff --git a/target/linux/imx6/patches-4.9/210-disable-uart-dma.patch 
b/target/linux/imx6/patches-4.9/210-disable-uart-dma.patch
new file mode 100644
index 000..6abbb93
--- /dev/null
+++ b/target/linux/imx6/patches-4.9/210-disable-uart-dma.patch
@@ -0,0 +1,23 @@
+Based on following upstream patch by Tim Harvey (Gateworks):
+
+https://github.com/Gateworks/openwrt/commit/80a01b6582f94c4547f39d3a25e0a1e9b6eb9877
+
+TX complete DMA messages are getting missed.
+This is also currently an issue in mainline.
+For now we will disable DMA in serial/imx.c.
+
+This resolves an issue encountered with RS485 transmit.
+
+--- a/drivers/tty/serial/imx.c
 b/drivers/tty/serial/imx.c
+@@ -1268,10 +1268,6 @@ static int imx_startup(struct uart_port
+ 
+   writel(temp & ~UCR4_DREN, sport->port.membase + UCR4);
+ 
+-  /* Can we enable the DMA support? */
+-  if (!uart_console(port) && !sport->dma_is_inited)
+-  imx_uart_dma_init(sport);
+-
+   spin_lock_irqsave(>port.lock, flags);
+   /* Reset fifo's and state machines */
+   i = 100;
-- 
2.7.4


___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] [PATCH] bcm53xx: include wpad-mini only on devices with (supported) wireless

[Rafał Miłecki]

On 22 May 2017 at 12:50, Rafał Miłecki  wrote:
> From: Rafał Miłecki 
>
> Don't include wpad-mini when it's useless just like we don't include
> useless wireless drivers.
>
> Signed-off-by: Rafał Miłecki 

I'm going to push this soon (last call for comments).

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

[LEDE-DEV] [PATCH v2] ramips: add support for Ubiquiti EdgeRouter X-SFP

[Sven Roederer]

This patch adds support for the Ubiquiti EdgeRouter X-SFP and
improves support for the EdgeRouter X (PoE-passthrough).

Specification:
- SoC: MediaTek MT7621AT
- Flash: 256 MiB
- RAM: 265 MiB
- Ethernet: 5 x LAN (1000 Mbps)
- UART: 1 x UART on PCB (3.3V, RX, TX, GND) - 57600 8N1
- EdgeRouter X:
  - 1 x PoE-Passtrough (Eth4)
  - powered by Wallwart or passive PoE
- EdgeRouter X-SFP:
  - 5 x PoE-Out (24V, passive)
  - 1 x SFP (unknown status)
  - powered by Wallwart (24V)

Doesn't work:
* SoC has crypto engine but no open driver.
* SoC has nat acceleration, but no open driver.
* This router has 2MB spi flash soldered in but MT
  nand/spi drivers do not support pin sharing,
  so it is not accessable and disabled. Stock
  firmware could read it and it was empty.

Installation

via vendor firmware:
- build an Initrd-image (> 3MiB) and upload the factory-image
- initrd can have luci-mod-failsafe
- flash final firmware via LuCI / sysupgrade on rebooted system

via TFTP:
- stop uboot into tftp-load into option "1"
- upload factory.bin image

Signed-off-by: Sven Roederer 
---
 .../linux/ramips/base-files/etc/board.d/02_network |   1 +
 .../ramips/base-files/etc/board.d/03_gpio_switches |  25 +
 target/linux/ramips/base-files/lib/ramips.sh   |   3 +
 .../ramips/base-files/lib/upgrade/platform.sh  |   9 +-
 target/linux/ramips/dts/UBNT-ER-e50.dtsi   | 106 +
 target/linux/ramips/dts/UBNT-ERX-SFP.dts   |  24 +
 target/linux/ramips/dts/UBNT-ERX.dts   | 103 +---
 target/linux/ramips/image/mt7621.mk|  13 +++
 8 files changed, 179 insertions(+), 105 deletions(-)
 create mode 100755 target/linux/ramips/base-files/etc/board.d/03_gpio_switches
 create mode 100644 target/linux/ramips/dts/UBNT-ER-e50.dtsi
 create mode 100644 target/linux/ramips/dts/UBNT-ERX-SFP.dts

diff --git a/target/linux/ramips/base-files/etc/board.d/02_network 
b/target/linux/ramips/base-files/etc/board.d/02_network
index 9dd5823..3cd7ff6 100755
--- a/target/linux/ramips/base-files/etc/board.d/02_network
+++ b/target/linux/ramips/base-files/etc/board.d/02_network
@@ -170,6 +170,7 @@ ramips_setup_interfaces()
rb750gr3|\
rt-n14u|\
ubnt-erx|\
+   ubnt-erx-sfp|\
ur-326n4g|\
wrtnode|\
wrtnode2p | \
diff --git a/target/linux/ramips/base-files/etc/board.d/03_gpio_switches 
b/target/linux/ramips/base-files/etc/board.d/03_gpio_switches
new file mode 100755
index 000..859dfb3
--- /dev/null
+++ b/target/linux/ramips/base-files/etc/board.d/03_gpio_switches
@@ -0,0 +1,25 @@
+#!/bin/sh
+
+. /lib/functions/uci-defaults.sh
+. /lib/ramips.sh
+
+board_config_update
+
+board=$(ramips_board_name)
+
+case "$board" in
+ubnt-erx)
+   ucidef_add_gpio_switch "poe_passthrough" "PoE Passthrough" "0"
+   ;;
+ubnt-erx-sfp)
+   ucidef_add_gpio_switch "poe_power_port0" "PoE Power Port0" "496"
+   ucidef_add_gpio_switch "poe_power_port1" "PoE Power Port1" "497"
+   ucidef_add_gpio_switch "poe_power_port2" "PoE Power Port2" "498"
+   ucidef_add_gpio_switch "poe_power_port3" "PoE Power Port3" "499"
+   ucidef_add_gpio_switch "poe_power_port4" "PoE Power Port4" "500"
+   ;;
+esac
+
+board_config_flush
+
+exit 0
diff --git a/target/linux/ramips/base-files/lib/ramips.sh 
b/target/linux/ramips/base-files/lib/ramips.sh
index 4b60a07..c8865fc 100755
--- a/target/linux/ramips/base-files/lib/ramips.sh
+++ b/target/linux/ramips/base-files/lib/ramips.sh
@@ -487,6 +487,9 @@ ramips_board_detect() {
*"UBNT-ERX")
name="ubnt-erx"
;;
+   *"UBNT-ERX-SFP")
+   name="ubnt-erx-sfp"
+   ;;
*"UR-326N4G")
name="ur-326n4g"
;;
diff --git a/target/linux/ramips/base-files/lib/upgrade/platform.sh 
b/target/linux/ramips/base-files/lib/upgrade/platform.sh
index 6aad4c9..d814f59 100755
--- a/target/linux/ramips/base-files/lib/upgrade/platform.sh
+++ b/target/linux/ramips/base-files/lib/upgrade/platform.sh
@@ -252,7 +252,8 @@ platform_check_image() {
# these boards use metadata images
return 0
;;
-   ubnt-erx)
+   ubnt-erx|\
+   ubnt-erx-sfp)
nand_do_platform_check "$board" "$1"
return $?;
;;
@@ -274,7 +275,8 @@ platform_nand_pre_upgrade() {
local board=$(ramips_board_name)
 
case "$board" in
-   ubnt-erx)
+   ubnt-erx|\
+   ubnt-erx-sfp)
platform_upgrade_ubnt_erx "$ARGV"
;;
esac
@@ -286,7 +288,8 @@ platform_pre_upgrade() {
case "$board" in
hc5962|\
r6220|\
-   ubnt-erx)
+   ubnt-erx|\
+   ubnt-erx-sfp)
nand_do_upgrade "$ARGV"
;;
esac
diff --git a/target/linux/ramips/dts/UBNT-ER-e50.dtsi 
b/target/linux/ramips/dts/UBNT-ER-e50.dtsi
new file mode 100644
index 

[LEDE-DEV] Question regarding wan6 interface defaults

[Sebastian Moeller]

Sear list, dear Hans,

CONTEXT:
As described in 
https://forum.lede-project.org/t/build-for-wndr3700v1-v2-wndr3800/64/56?u=moeller0
 I had issues with using IPv6 and IPv4 DNS on my home network (deutsche 
Telekom, vdsl2 @BRAS link). The main symptoms were, that a) IPv6 did not work, 
and b) DNS even for IPv4 was very unreliable. Unfortunately, for a long time 
did I spent no time on the IPv6 issue (assuming that missing IPv6 is a more 
cosmetic thing than getting IPv4 DNS working again*). Last weekend I attempted 
to tackle the issue again and found your recommendation to change the wan6 
iface from eth1 to @wan (see 
https://bugs.lede-project.org/index.php?do=details_id=668). And that 
"magically" solved all my issues, IPv6 started to work (at least all my 
internal hosts now get IPv6 addresses with the correct ISP assigned prefix), 
and more unexpected IPv4 DNS seems to work again (and DDNS also automatically 
started working). Jow brought up the information that the wan6 ifname default 
was changed a while back (see http
 
s://forum.lede-project.org/t/build-for-wndr3700v1-v2-wndr3800/64/59?u=moeller0, 
and c118e5edf4301dc303024603dd34d369d9926d6d for the patch and rationale). He 
also advised that I should bring up the issue of the wan6 default ifname with 
you.

So, from my limited understanding, the challenge is to have a default that will 
work out of the box with both native IPv6 (am I right to assume that dslite is 
basically a sub-variant of native IPv6?) and with IPv6 managed via an IPv4 
path, or PPPoE in my case. On the one hand, it makes sense to welcome the 
future and make native IPv6 a well-supported option, on the other hand many 
users, as far as I can tell, are still living in the past and are stuck with 
having to use say PPPoE to get IPv6 up and running. 

QUESTIONS:
0) What do you believe to currently be the best default configuration for wan6 
ifname?

1) From your perspective is there a way to either make the default 
configuration work for both situations gracefully?

2) Say, is there a way to auto detect non-working configurations at run-time 
and print a hint into the syslog, so the user has an idea how to get things 
working again, like changing the wan6 ifname?

3) Or could switching the protocol to PPPoE maybe bring up a help text (in a 
modal dialog?) that informs the user to manually rename the wan6 iface in case 
of connectivity issues?

4) Final question, in your bug tracker response you allude to the option to 
completely delete the wan6 interface to get a (hopefully) working wan_6 
autoconfigured; which of the two options, no wan6 or wan6.ifname set to @wan 
would you recommend?


Best Regards
Sebastian



*) Please note my IPv4 DNS issues might still be unsolved, but now at least 
working IPv6 DNS will pick up the slack mostly.
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] dropbear & gcc 7.1.0

[Bastian Bittorf]

* Syrone Wong  [29.05.2017 10:03]:
> > have you tried to '/etc/init.d/dropbear'?
> 
> The problem is you cannot access the router, which means you cannot
> execute any commands.

ok, maybe you can execute a command with LuCI?
(i'am not familiar with LuCI)
maybe you can try serial console.
maybe you can put that into /etc/rc.local

i wanted to write: '/etc/init.d/dropbear restart', sorry for that.

bye, bastian

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] dropbear & gcc 7.1.0

[Syrone Wong]

> have you tried to '/etc/init.d/dropbear'?

The problem is you cannot access the router, which means you cannot
execute any commands.

Best Regards,
Syrone Wong

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] dropbear & gcc 7.1.0

[Bastian Bittorf]

* e9hack  [29.05.2017 08:59]:
> if I select gcc 7.1.0 instead of gcc 6.3.0, anything seems to be work with 
> exception of dropbear (and a few build fixes
> for some packages are necessary). Dropbear is running, but it isn't possible 
> to connect. The message from WinSCP is
> 'Network error: Connection to "wlan-xyz" refused' or from PuTTY 'Network 
> error: connection refused'. If I copy the
> dropbear image from a previous build with gcc 6.3.0 to the router, it's 
> possible to connect with PuTTY and WinSCP. This
> problem occurs for three builds: TP-Link Archer C7, TP-Link wdr3600 and 
> 8devices carambola. All are using as target the
> ar71xx platform.
> 
> Any ideas?

i have also seen this on a lot of routers:
have you tried to '/etc/init.d/dropbear'?
it seems to work around this problem here,
but i do not fully understand it for now...

bye, bastian

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] openwrt and lede - remerge proposal V3

[Vincenzo Romano]

2017-05-29 9:03 GMT+02:00 John Crispin :
> (resend, this time as plain text)
>
> Hi,
>
> here is a V3 of the remerge proposal, I tried to fold all the comments
> people made into it, if anything is missing let me know. Please remeber that
> post remerge anything can be voted on, so cluttering the proposal with many
> details will delay the remerge even more.
>
> Ideally we manage to vote during this week.
>
>
> John
>
> *) rules
> - owrt will adopt the lede rules and voting system

I agree.

> *) branding
> - the owrt side sees no option of using the lede brand
> - a (minor) majority voted for openwrt as a name over lede whilst most
> people said they did not care
> - as the last vote had a 100% ACK for a remerge using the owrt brand is the
> only feasible option

I agree as I don't mind about the names.

> *) domain
> - transfer owner ship to SPI for openwrt.org and lede-project.org
> - add them to the pool of urls at digital ocean
> - post remerge build a setup where we have several DNS servers in various
> locations
> - point git.openwrt.org at the lede git server
> - point bugs.openwrt.org to the lede flyspray instance
> - keep both wikis and forums as is (we should decide post remerge how to
> proceed to avoid these issues blocking the progress)
> - update the lede domain entries for build/download/rsync/... servers so
> that the openwrt domain also points at them

I agree.

> *) SPI
> - nominate a new liaison team (imre and john offer to do this, if anyone
> else is interested let us know)
> - inform SPI of the new liaisons, voters and project rules
> - this should be done early in the remerge process s.t. the domains can be
> handed over

I agree.

> *) github
> - start pushing to the openwrt organisation
> - cleanup the list of owners in the openwrt organisation
> - obsolete all issues on the openwrt organisation and close the issue
> tracker
> - go through the open openwrt and lede PRs, pickup whats useful and close
> the rest, asking people to repost (things wont be rebasable anyhow)
> - close the lede PR tracker
> - obsolete the lede github org after a grace period of 3-6 months

I agree as long as the reporters of the issues to be obsoleted will be
informed about the change.

> *) landing page
> - add a letter of intent / notice to both current landing pages announcing
> the remerge
> - update the lede landing page to represent the openwrt name
> - update the landing page to have the same look & feel as the current
> openwrt landing page
> - point openwrt.org at the lede landing page
> - try to find some design guru that will transform the owrt theme to one
> appropriate to this century

I agree.

> *) trac
> - trac is already readonly, keep content so that search engines can still
> find the it
> - edit the trac html templates, adding a note pointing at the
> bug.openwrt.org instance

I agree.

> *) IRC
> - add back cloaking
> - give people channel ownership/admin rights


I agree.

> *) email accounts
> - currently there are around ~20 active openwrt.org mail accounts (the 3
> owrt devs would like to keep theirs active)
> - turn all the webmaster@, hostmaster@, ... accounts into aliases that
> anyone with voting rights can be subscribed to
> - ask those people that are no longer active to voluntarily give up their
> accounts
> - mail addresses may under no conditions be used for any personal business,
> consultancy, applying for jobs, ... purposes
> - any mail sent from an openwrt.org account needs to adhere the trademark
> policy and should only be used for FOSS purposes

I agree.

> *) wiki / forum
> - TBD
> - asking in either forum/wiki will get a biased vote so keep them both
> around
> - start a separate discussion regarding these post remerge

I agree as long as this will be a P1 task.
The wiki embodies the project documentation and is the primary source
of information.

> *) LF
> - find out what doubts folks have about LF
> - find out benefits - we would have their hosting and sponsorship ?!
> - start a separate discussion regarding these post remerge

I agree.

> *) git trees
> - rebrand the lede tree to openwrt
> - work out what has happened inside the openwrt tree since the reboot and
> pick up the useful bits (zoltan has done some prior work on this already)

I agree.

> *) mailing list
> - ask david to add the openwrt-adm and openwrt lists
> - send out invitation mails to the new list
> - setup redirect/auto-reply for the existing lists

I agree.

> *) trademark policy
> - review/ack imres trademark policy (https://openwrt.org/trademark)

I agree.

> *) timeline
> - vote / agree on the proposal within the next week
> - work on the action items in the 4 weeks after that

I agree.

>
> John

Enzo

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] [PATCH][procd] ubus: use ubus_auto_connect() logic

[Alexandru Ardelean]

On Mon, May 29, 2017 at 10:19 AM, Felix Fietkau  wrote:
> On 2017-05-19 09:45, Alexandru Ardelean wrote:
>> Admittedly, the semantic is a bit different, in the sense
>> that there are no progressive retry timeouts.
>>
>> ubus_auto_connect() uses 1 second fixed retry intervals.
>> Whereas the old logic would start at 50 millisecs and
>> progress up to 1 second.
>>
>> Other than that, the rest should be the same overall logic.
>> This should cleanup the code a bit.
>>
>> For reference, the `ubus_add_uloop()` call is handled
>> by ubus_auto_connect() as well.
>>
>> Signed-off-by: Alexandru Ardelean 
> procd intentionally uses different semantics, since it's responsible for
> launching ubus in the first place.
>
> This patch causes extra delay and extra error messages, so I don't think
> we should do something like this at all.
>
> - Felix

Fine from me.
Will close.

Thanks :)
Alex

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] Planning v17.01.2

[Julian Labus]

On 05/24/2017 10:34 PM, Jo-Philipp Wich wrote:
> If you want specific fixes cherry-picked/backported to lede-17.01,
> please mention them in a reply to this mail.

Hi,

would be nice to see the following two patches in v17.01.2.

b09ee2dc01ad1bc3f1236e08b998aff072f9bc1f usbmode: update to latest version
a9206ac26c2515c05f85f9690fa56e2b190d73c1 usbmode: update usb-modeswitch-data to 
20170205

Thanks,
Julian



signature.asc
Description: OpenPGP digital signature
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] [PATCH][procd] ubus: use ubus_auto_connect() logic

[Felix Fietkau]

On 2017-05-19 09:45, Alexandru Ardelean wrote:
> Admittedly, the semantic is a bit different, in the sense
> that there are no progressive retry timeouts.
> 
> ubus_auto_connect() uses 1 second fixed retry intervals.
> Whereas the old logic would start at 50 millisecs and
> progress up to 1 second.
> 
> Other than that, the rest should be the same overall logic.
> This should cleanup the code a bit.
> 
> For reference, the `ubus_add_uloop()` call is handled
> by ubus_auto_connect() as well.
> 
> Signed-off-by: Alexandru Ardelean 
procd intentionally uses different semantics, since it's responsible for
launching ubus in the first place.

This patch causes extra delay and extra error messages, so I don't think
we should do something like this at all.

- Felix

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

[LEDE-DEV] openwrt and lede - remerge proposal V3

[John Crispin]

(resend, this time as plain text)

Hi,

here is a V3 of the remerge proposal, I tried to fold all the comments 
people made into it, if anything is missing let me know. Please remeber 
that post remerge anything can be voted on, so cluttering the proposal 
with many details will delay the remerge even more.


Ideally we manage to vote during this week.


John

*) rules
- owrt will adopt the lede rules and voting system

*) branding
- the owrt side sees no option of using the lede brand
- a (minor) majority voted for openwrt as a name over lede whilst most 
people said they did not care
- as the last vote had a 100% ACK for a remerge using the owrt brand is 
the only feasible option


*) domain
- transfer owner ship to SPI for openwrt.org and lede-project.org
- add them to the pool of urls at digital ocean
- post remerge build a setup where we have several DNS servers in 
various locations

- point git.openwrt.org at the lede git server
- point bugs.openwrt.org to the lede flyspray instance
- keep both wikis and forums as is (we should decide post remerge how to 
proceed to avoid these issues blocking the progress)
- update the lede domain entries for build/download/rsync/... servers so 
that the openwrt domain also points at them


*) SPI
- nominate a new liaison team (imre and john offer to do this, if anyone 
else is interested let us know)

- inform SPI of the new liaisons, voters and project rules
- this should be done early in the remerge process s.t. the domains can 
be handed over


*) github
- start pushing to the openwrt organisation
- cleanup the list of owners in the openwrt organisation
- obsolete all issues on the openwrt organisation and close the issue 
tracker
- go through the open openwrt and lede PRs, pickup whats useful and 
close the rest, asking people to repost (things wont be rebasable anyhow)

- close the lede PR tracker
- obsolete the lede github org after a grace period of 3-6 months

*) landing page
- add a letter of intent / notice to both current landing pages 
announcing the remerge

- update the lede landing page to represent the openwrt name
- update the landing page to have the same look & feel as the current 
openwrt landing page

- point openwrt.org at the lede landing page
- try to find some design guru that will transform the owrt theme to one 
appropriate to this century


*) trac
- trac is already readonly, keep content so that search engines can 
still find the it
- edit the trac html templates, adding a note pointing at the 
bug.openwrt.org instance


*) IRC
- add back cloaking
- give people channel ownership/admin rights

*) email accounts
- currently there are around ~20 active openwrt.org mail accounts (the 3 
owrt devs would like to keep theirs active)
- turn all the webmaster@, hostmaster@, ... accounts into aliases that 
anyone with voting rights can be subscribed to
- ask those people that are no longer active to voluntarily give up 
their accounts
- mail addresses may under no conditions be used for any personal 
business, consultancy, applying for jobs, ... purposes
- any mail sent from an openwrt.org account needs to adhere the 
trademark policy and should only be used for FOSS purposes


*) wiki / forum
- TBD
- asking in either forum/wiki will get a biased vote so keep them both 
around

- start a separate discussion regarding these post remerge

*) LF
- find out what doubts folks have about LF
- find out benefits - we would have their hosting and sponsorship ?!
- start a separate discussion regarding these post remerge

*) git trees
- rebrand the lede tree to openwrt
- work out what has happened inside the openwrt tree since the reboot 
and pick up the useful bits (zoltan has done some prior work on this 
already)


*) mailing list
- ask david to add the openwrt-adm and openwrt lists
- send out invitation mails to the new list
- setup redirect/auto-reply for the existing lists

*) trademark policy
- review/ack imres trademark policy (https://openwrt.org/trademark)

*) timeline
- vote / agree on the proposal within the next week
- work on the action items in the 4 weeks after that

John



___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev


___
openwrt-devel mailing list
openwrt-de...@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel


___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] [PATCH v3 6/6] ipq806x: Enable ubi image for ipq40xx AP-DK04.1-C1 board

[John Crispin]

Hi Ram,

thanks for splitting the series up, i merged the first  patches into my 
tree, however the final patch fails to apply. could you rebase/resend 
just that last one please ?


John

On 25/05/17 01:31, Ram Chandra Jangir wrote:

This change enables ubi image for IPQ40xx AP-DK04.1-C1
board, also add sysupgrage support for AP-DK04.1-C1 and
generates a sysupgrade.tar image.

Testing:
  *Tested on IPQ40xx AP-DK04.1-C1:
a. NAND boot
b. ubi sysupgrade

Signed-off-by: Ram Chandra Jangir 
---

Changes since v2:
  *Splitted to individual patches

  target/linux/ipq806x/base-files/lib/upgrade/platform.sh | 1 +
  target/linux/ipq806x/image/Makefile | 1 +
  2 files changed, 2 insertions(+)

diff --git a/target/linux/ipq806x/base-files/lib/upgrade/platform.sh 
b/target/linux/ipq806x/base-files/lib/upgrade/platform.sh
index 8970285..fd08db3 100644
--- a/target/linux/ipq806x/base-files/lib/upgrade/platform.sh
+++ b/target/linux/ipq806x/base-files/lib/upgrade/platform.sh
@@ -12,6 +12,7 @@ platform_pre_upgrade() {
  
  	case "$board" in

ap148 |\
+   ap-dk04.1-c1 |\
d7800 |\
nbg6817 |\
r7500 |\
diff --git a/target/linux/ipq806x/image/Makefile 
b/target/linux/ipq806x/image/Makefile
index 6ebcde5..c49a73e 100644
--- a/target/linux/ipq806x/image/Makefile
+++ b/target/linux/ipq806x/image/Makefile
@@ -264,6 +264,7 @@ endef
  
  define Device/AP-DK04.1-C1

$(call Device/FitImage)
+   $(call Device/UbiFit)
DEVICE_DTS := qcom-ipq4019-ap.dk04.1-c1
KERNEL_LOADADDR := 0x80208000
KERNEL_INSTALL := 1



___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev