Hi!
I was thinking about porting wayland/weston to OpenWrt for a while.
Now I finally searched for that I saw that it has already been done!
I love it when that happens, reaching a goal with no efforts involved :)
Thank you Oskari for rpi-openwrt!
What about merging the weston and related packages
Can someone please give me some feedback as to whether this patch now
meets the canonical standard, and whether it's likely to get applied. I
have a number of others to come and I would like to make sure I get them
right.
Thanks,
Stephen Parry
On 17/08/14 23:30, Stephen Parry wrote:
> Patch to B
Patch to BusyBox Makefile to fix linker errors when PAM support is enabled by
CONFIG_BUSYBOX_CONFIG_PAM=y. Typical errors include:
login.c:(.text.login_main+0x122): undefined reference to `pam_start'
Signed-off-by: Stephen Parry
---
New version of patch - now against trunk and using git
package/
On 08/17/2014 11:08 PM, Rafał Miłecki wrote:
> Signed-off-by: Rafał Miłecki
> ---
> This patch can't be applied yet, because SPI driver depends on the:
> dc6be9f54a4ecb0a09765d1f515ed947d86b7528
> bcma: use NS prefix for names of Northstar specific cores
>
> Hauke: I don't know magic tricks for u
Signed-off-by: Rafał Miłecki
---
This patch can't be applied yet, because SPI driver depends on the:
dc6be9f54a4ecb0a09765d1f515ed947d86b7528
bcma: use NS prefix for names of Northstar specific cores
Hauke: I don't know magic tricks for updating bcma in 6 different
kernels. I won't manage to do t
It it used by brcm47xx and bcm53xx targets, so put patches in generic.
Signed-off-by: Rafał Miłecki
---
V2: Update bcm53xx kernel config
---
target/linux/bcm53xx/config-3.14 | 1 +
.../027-mtd-bcm47xxpart-get-nvram.patch| 4 +-
.../390-mtd-bcm47xxpart-backports-fr
On 15 August 2014 02:54, Roman Yeryomin wrote:
> Compile and run tested.
>
Hi!
Anything wrong with these two?
Should I just add 3.14 support instead of replacing 3.10 (don't see a
reason why though)?
Regards,
Roman
___
openwrt-devel mailing list
openwr
It it used by brcm47xx and bcm53xx targets, so put patches in generic.
Signed-off-by: Rafał Miłecki
---
.../027-mtd-bcm47xxpart-get-nvram.patch| 4 +-
.../390-mtd-bcm47xxpart-backports-from-3.16.patch | 59 +++
...part-find-NVRAM-partitions-in-middle-bloc.patch | 16
On 17 August 2014 15:30, quickbooks office wrote:
> I installed this:
>
> [user@localhost openwrt]$ md5sum *
> 65111512db032e42b581a2041c63d816 openwrt-wnr1000_v3-squashfs.chk
OK
> but now the Power light on the router is Orange. It doesn't turn to green.
OpenWrt doesn't know LEDs or buttons
I installed this:
[user@localhost openwrt]$ md5sum *
65111512db032e42b581a2041c63d816 openwrt-wnr1000_v3-squashfs.chk
[user@localhost openwrt]$
but now the Power light on the router is Orange. It doesn't turn to green.
I connected to LAN port 4, the port lights up to green.
But I do not get a
Hi,
if I create a rule such as:
config rule
option in 'wireless0'
option action 'unreachable'
and have a wireless0 network configured in network and wireless config, the rule
does not show up after a network restart (/etc/init.d/network restart). E.g. ip
rule does not list the rule. If a jus
There are pretty many OpenWrt patches against mtd subsystem resulting
in a bit of mess and growing maintenance cost.
My idea is to use an extra "mtdsplit" directory with OpenWrt specific
files (including Kconfig).
This is the first step to achieve this. This patch adds a "mtdsplit"
directory with K
Hello list,
On my ar71xx/dir-825-c1 Luci is included in rc3. This was not the case
for rc2. Can anybody please point me to the related changeset? I can't
seem to find it.
Kind regards,
Sebastian
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt
13 matches
Mail list logo
