* Sven Roederer [27.04.2016 08:30]:
> So finally, as this change will come, so it comes already inside this release
> and some derived projects also adapted the change.
We also adapted this change and it makes the world better.
bye, bastian
___
openwr
Hi Alexandru,
pushed to master - thanks!
~ Jo
On 27.04.2016 08:16, Alexandru Ardelean wrote:
> From: Alexandru Ardelean
>
> Since commit 60f1444 , this struct is no longer used.
>
> Signed-off-by: Alexandru Ardelean
> ---
> defaults.c | 7 ---
> 1 file changed, 7 deletions(-)
>
> diff
From: Alexandru Ardelean
Since commit 60f1444 , this struct is no longer used.
Signed-off-by: Alexandru Ardelean
---
defaults.c | 7 ---
1 file changed, 7 deletions(-)
diff --git a/defaults.c b/defaults.c
index e246949..3d210f9 100644
--- a/defaults.c
+++ b/defaults.c
@@ -164,13 +164,6 @@
From: Alexandru Ardelean
Since commit 60f1444 , this struct is no longer used.
Signed-off-by: Alexandru Ardelean
---
defaults.c | 7 ---
1 file changed, 7 deletions(-)
diff --git a/defaults.c b/defaults.c
index e246949..3d210f9 100644
--- a/defaults.c
+++ b/defaults.c
@@ -164,13 +164,6 @@
PATCHv1:
This patch adds support for the SamKnows version 8.0 Whitebox, built
around the MT7621 platform. 2.4GHz appears to be working, albeit
poorly; 5GHz not working yet.
PATCHv2:
- Fixed LED name in DTS.
PATCHv3:
DTS: Syntax error fixed, LEDs and buttons mapped correctly now
- diag.sh updated
Documented everything that led to this here:
https://wiki.openwrt.org/inbox/samknows/samknows_sk-wb8
On Wed, Apr 27, 2016 at 1:59 AM, Andrew Yong wrote:
> PATCHv1:
> This patch adds support for the SamKnows version 8.0 Whitebox, built
> around the MT7621 platform. 2.4GHz appears to be working, al
On Fri, Mar 11, 2016 at 11:19 AM, Matthias Schiffer
wrote:
> As I wrote, "bullet" is the correct image for all XM devices with one
> ethernet port and no USB.
Finally had a chance to play with the Bullet and Nanostation images this week.
What I found is that the Nano M image includes the switch dr
PATCHv1:
This patch adds support for the SamKnows version 8.0 Whitebox, built
around the MT7621 platform. 2.4GHz appears to be working, albeit
poorly; 5GHz not working yet.
PATCHv2:
- Fixed LED name in DTS.
PATCHv3:
DTS: Syntax error fixed, LEDs and buttons mapped correctly now
- diag.sh updated
Am 23.04.2016 um 22:15 schrieb Heiner Kallweit:
> OpenWRT has own support for the memory-mapped fast SPI flash read on ath79.
> With mainline kernel 4.6/4.7 more elegant generic support for this feature
> was added upstream consisting of these two commits:
>
> 556351f14e74 "spi: introduce accelera
Hi John,
On Tue, Apr 26, 2016 at 3:33 PM, John Crispin wrote:
>
>
> On 26/04/2016 11:48, Helmut Schaa wrote:
>> The Freescale T4240 is a 12 core (24 threads) SoC.
>> Add a sub-target to the mpc85xx target to build images for the T4240
>> Reference Design Board.
>>
>> Currently CPU thread support
On 26/04/2016 11:48, Helmut Schaa wrote:
> The Freescale T4240 is a 12 core (24 threads) SoC.
> Add a sub-target to the mpc85xx target to build images for the T4240
> Reference Design Board.
>
> Currently CPU thread support is only available in 64bit kernel builds,
> hence the sub-target uses th
Hostapd allows more than one RADIUS server to be added in case the main server
goes down.
This allows netifd to load a list of RADIUS servers from the wireless confid
file and add them to hostapd.
The format of the list in the config file is as follow:
list auth_servers 'secret@server_add
On 26/04/2016 15:02, Sven Roederer wrote:
> Am Monday 25 April 2016, 09:06:38 schrieb John Crispin:
>> On 25/04/2016 08:54, Bastian Bittorf wrote:
>>> * John Crispin [25.04.2016 07:39]:
> The changed image name breaks compatibility for derived projects and
> that's something which should
Am Monday 25 April 2016, 09:06:38 schrieb John Crispin:
> On 25/04/2016 08:54, Bastian Bittorf wrote:
> > * John Crispin [25.04.2016 07:39]:
> >>> The changed image name breaks compatibility for derived projects and
> >>> that's something which should only happen if there is a really good
> >>> re
PATCHv1:
This patch adds support for the SamKnows version 8.0 Whitebox, built
around the MT7621 platform. 2.4GHz appears to be working, albeit
poorly; 5GHz not working yet.
PATCHv2:
- Fixed LED name in DTS.
PATCHv3:
DTS: Syntax error fixed, LEDs and buttons mapped correctly now
- diag.sh updated
On Tuesday, April 26, 2016 07:20:32 AM Valo, Kalle wrote:
> Christian Lamparter writes:
> > On Monday, April 25, 2016 10:53:41 AM David Hutchison wrote:
> >> So with some modifications to pci.c, hw.h and core.c I was able to get
> >> the radio initialized! :)
> >
> > Hey, that's nice! Can you make
PATCHv1:
This patch adds support for the SamKnows version 8.0 Whitebox, built
around the MT7621 platform. 2.4GHz appears to be working, albeit
poorly; 5GHz not working yet.
PATCHv2:
- Fixed LED name in DTS.
PATCHv3:
DTS: Syntax error fixed, LEDs and buttons mapped correctly now
- diag.sh updated
On Tue, 26 Apr 2016 13:09:15 +0200, John Crispin
wrote:
On 26/04/2016 13:07, Imre Kaloz wrote:
On Tue, 26 Apr 2016 13:00:40 +0200, John Crispin
wrote:
On 26/04/2016 12:59, Imre Kaloz wrote:
On Tue, 26 Apr 2016 12:55:50 +0200, John Crispin
wrote:
the maintainer of the target does n
On 26/04/2016 13:07, Imre Kaloz wrote:
> On Tue, 26 Apr 2016 13:00:40 +0200, John Crispin
> wrote:
>
>>
>>
>> On 26/04/2016 12:59, Imre Kaloz wrote:
>>> On Tue, 26 Apr 2016 12:55:50 +0200, John Crispin
>>> wrote:
>>>
the maintainer of the target does not use patchwork. so they are not
>>>
On Tue, 26 Apr 2016 13:00:40 +0200, John Crispin
wrote:
On 26/04/2016 12:59, Imre Kaloz wrote:
On Tue, 26 Apr 2016 12:55:50 +0200, John Crispin
wrote:
the maintainer of the target does not use patchwork. so they are not
applicable to be listed in patchwork. sorry i normally send an emai
On 26/04/2016 12:52, Alexander Couzens wrote:
>> The following patches (submitted by you) have been updated in
>> patchwork:
>>
>> * openwrt: [OpenWrt-Devel,1/4] omap: add sdcard creation script
>> - http://patchwork.ozlabs.org/patch/614748/
>> - for: OpenWrt development
>> was: Ne
On 26/04/2016 12:59, Imre Kaloz wrote:
> On Tue, 26 Apr 2016 12:55:50 +0200, John Crispin
> wrote:
>
>> the maintainer of the target does not use patchwork. so they are not
>> applicable to be listed in patchwork. sorry i normally send an email to
>> the submitter informing him of this. i forgo
On Tue, 26 Apr 2016 12:55:50 +0200, John Crispin
wrote:
the maintainer of the target does not use patchwork. so they are not
applicable to be listed in patchwork. sorry i normally send an email to
the submitter informing him of this. i forgot to do so last night
"the maintainer" was told to
On 26/04/2016 12:52, Alexander Couzens wrote:
>> The following patches (submitted by you) have been updated in
>> patchwork:
>>
>> * openwrt: [OpenWrt-Devel,1/4] omap: add sdcard creation script
>> - http://patchwork.ozlabs.org/patch/614748/
>> - for: OpenWrt development
>> was: Ne
> The following patches (submitted by you) have been updated in
> patchwork:
>
> * openwrt: [OpenWrt-Devel,1/4] omap: add sdcard creation script
> - http://patchwork.ozlabs.org/patch/614748/
> - for: OpenWrt development
> was: New
> now: Not Applicable
>
> * openwrt: [OpenWrt-
The Freescale T4240 is a 12 core (24 threads) SoC.
Add a sub-target to the mpc85xx target to build images for the T4240
Reference Design Board.
Currently CPU thread support is only available in 64bit kernel builds,
hence the sub-target uses the powerpc64 feature flag.
Using musl libc doesn't comp
libbpf fails to build.
perf just emits a warning and carries on.
This is a collision between linux's and musl's
when building for powerpc.
For powerpc, EDEADLOCK has value 58.
The initial definition in the kernel
include/uapi/asm-generic/errno.h : #define EDEADLOCK EDEADLK
Then this gets over
On 04/26/2016 09:52 AM, John Crispin wrote:
>
>
> On 26/04/2016 09:37, kwadronaut wrote:
>> On 26/04/16 09:28, John Crispin wrote:
>>
>>> i fail to extract from your mail what you are trying to tell us
>>
>> Common sense: don't change names within a stable release.
>
> others may claim the commo
On 26/04/2016 09:37, kwadronaut wrote:
> On 26/04/16 09:28, John Crispin wrote:
>
>> i fail to extract from your mail what you are trying to tell us
>
> Common sense: don't change names within a stable release.
others may claim the common sense is to polish it even more and make it
consistent.
On 04/26/2016 10:37 AM, kwadronaut wrote:
On 26/04/16 09:28, John Crispin wrote:
i fail to extract from your mail what you are trying to tell us
Common sense: don't change names within a stable release.
Hi, i watched this conversation from the beginning and even if what you
are saying ma
On 26/04/16 09:28, John Crispin wrote:
> i fail to extract from your mail what you are trying to tell us
Common sense: don't change names within a stable release.
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/c
On 26/04/2016 09:22, kwadronaut wrote:
> On 25/04/16 09:06, John Crispin wrote:
>> On 25/04/2016 08:54, Bastian Bittorf wrote:
>>> * John Crispin [25.04.2016 07:39]:
> The changed image name breaks compatibility for derived projects and
> that's something which should only happen if ther
On 25/04/16 09:06, John Crispin wrote:
> On 25/04/2016 08:54, Bastian Bittorf wrote:
>> * John Crispin [25.04.2016 07:39]:
The changed image name breaks compatibility for derived projects and
that's something which should only happen if there is a really good
reason (e.g. security f
Christian Lamparter writes:
> Hello,
>
> On Monday, April 25, 2016 10:53:41 AM David Hutchison wrote:
>> So with some modifications to pci.c, hw.h and core.c I was able to get
>> the radio initialized! :)
>
> Hey, that's nice! Can you make and post a patch for that?
> I'm sure if it's just a mat
34 matches
Mail list logo
