From: Miaoqing Pan
Signed-off-by: Miaoqing Pan
---
.../linux/ar71xx/files/arch/mips/ath79/dev-i2c.c | 33 ++
.../linux/ar71xx/files/arch/mips/ath79/dev-i2c.h | 24
...915-MIPS-ath79-add-gpio-based-i2c-support.patch | 22 +++
3 files changed,
From: Miaoqing Pan
Signed-off-by: Miaoqing Pan
---
...PS-ath79-add-giga-device-spi-nand-support.patch | 40 ++
1 file changed, 40 insertions(+)
create mode 100644
target/linux/ar71xx/patches-3.18/916-MIPS-ath79-add-giga-device-spi-nand-support.patch
diff --git
a/target/l
From: Miaoqing Pan
Derived from 'drivers/staging/mt29f_spinand'.
Only support Giga Device SPI NAND device now,
- GD5F1GQ4U 1G 3.3V 8-bit
- GD5F2GQ4U 2G 3.3V 8-bit
- GD5F1GQ4R 1G 1.8V 8-bit
- GD5F2GQ4R 2G 1.8V 8-bit
Signed-off-by: Miaoqing Pan
---
.../ar71xx/files/drivers/mtd/n
Otherwise uloop will delete the fd and the ustream will receive no
notification of the error.
Signed-off-by: Philip Craig
---
ustream-fd.c | 8 +++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/ustream-fd.c b/ustream-fd.c
index 5ffca53..2c15b42 100644
--- a/ustream-fd.c
+++ b
Hi,
can you first send this patch upstream please ?
John
On 10/07/2015 09:18, miaoq...@qti.qualcomm.com wrote:
> From: Miaoqing Pan
>
> Signed-off-by: Miaoqing Pan
> ---
> ...PS-ath79-add-giga-device-spi-nand-support.patch | 40
> ++
> 1 file changed, 40 insertio
Hi,
lots of comments inline. please check all you error paths. right now on
various places when an error occurs you simply continue as if nothing
happened.
also move all the dev_err calls into the functions where the error
happens. please also review the actual error messages.
John
On 1
Hi,
I'm trying to integrate a new hardware connected via I2C into OpenWRT.
I already integrated the according driver so that it shows up in the menuconfig
under "Kernel Modules -> Other modules".
To get I2C working I also activated the modules () kmod-i2c-bcm2708 and
kmod-i2c-core.
Now I
Hi Varka Bhadram,
>6LoWPAN over IEEE-802.15.4 support available in OpenWRT from the kernel
version 4.0 [1]
As I see this version doesn't support all Processors, I'm using :
openwrt-at91-legacy-9g25ek-uImage
So can you please inform me if it's supported with version 4.0 and if you
please provi
Hi,
On Fri, Jul 10, 2015 at 9:18 AM, wrote:
> From: Miaoqing Pan
>
> Derived from 'drivers/staging/mt29f_spinand'.
>
> Only support Giga Device SPI NAND device now,
> - GD5F1GQ4U 1G 3.3V 8-bit
> - GD5F2GQ4U 2G 3.3V 8-bit
> - GD5F1GQ4R 1G 1.8V 8-bit
> - GD5F2GQ4R 2G 1.8V 8-bit
>
Agree with you, I investigated this, tried to merge two into one. E.g.
Implement the common core for spinand, separate vendors related codes, but
give up finally as no device to verify mt29f:( So I only add it to support for
ath79 platform.
Thanks,
Miaoqing
-Original Message-
Fr
Hi list,
I've flashed yesterday's EnGenius EPG5000 image from
https://downloads.openwrt.org/snapshots/trunk/ar71xx/generic/openwrt-ar71xx-generic-epg5000-squashfs-sysupgrade.bin
which went fine. Thing is 'firstboot' in failsafe mode via telnet just simply
hang without outputting anything (erasing
On 2015-07-10 09:23, Philip Craig wrote:
> Otherwise uloop will delete the fd and the ustream will receive no
> notification of the error.
>
> Signed-off-by: Philip Craig
I think this fix is incomplete. When an error occurs, ustream-fd should
delete the fd after setting the error flags to avoid g
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Isn't this normally called the "OYE-0001" ? not "OY-0001" ? The website
and all literature I've seen uses the "OYE-0001" name...
Regardless, in many places, you have not followed the existing
alphabetical order.
LiWeijian wrote:
> From: Tom Deng <2
On 10/07/2015 13:27, Karl Palsson wrote:
> Isn't this normally called the "OYE-0001" ? not "OY-0001" ? The website
> and all literature I've seen uses the "OYE-0001" name...
>
> Regardless, in many places, you have not followed the existing
> alphabetical order.
>
there never has been an alpha
Hi，
Thanks very much for your comments and taking time to check the name. Regarding
the 'OY-0001', it's for business reason to use 'OY-0001' but not 'OYE-0001'.
The 'old' name in the website also will be updated afterward.
Regards,
Weijian
> Subject: Re: [OpenWrt-Devel] [PATCH] ramips: adding s
Bastian,
I just saw this reply now. I think that's a great idea! We'll make sure to
do introductions next time!
Eric
On Fri, Jun 26, 2015 at 10:25 AM, Bastian Bittorf
wrote:
> * Javier Domingo Cansino [26.06.2015 17:22]:
> > Thanks for sharing!!
>
> short comment from myself (for the next han
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
John Crispin wrote:
>
>
> On 10/07/2015 13:27, Karl Palsson wrote:
> > Isn't this normally called the "OYE-0001" ? not "OY-0001" ? The website
> > and all literature I've seen uses the "OYE-0001" name...
> >
> > Regardless, in many places, you hav
On 07/09/2015 06:44 AM, John Crispin wrote:
>> I have the below change to add rudimentary support for sysupgrade on the
>> Raspberry Pi. I looked at the way platform_copy_config() is implemented
>> for x86 and tried to do the same, but I get the following error on mount:
>>
>> mount: mounting /dev/
Hello Martin,
I've just applied your patch against trunk (r46292) and flashed this
firmware. Unfortunately linked patch did not apply cleanly because
some of your changes were accepted into openwrt trunk. I was able to
fix it locally but I hope you will update your patch for others to
test it. So
On 07/08/2015 07:42 PM, Bruno Randolf wrote:
> Hi!
>
> I have the below change to add rudimentary support for sysupgrade on the
> Raspberry Pi. I looked at the way platform_copy_config() is implemented
> for x86 and tried to do the same, but I get the following error on mount:
>
> mount: mounting
On 10/07/2015 17:19, Karl Palsson wrote:
> John Crispin wrote:
>
>
>> On 10/07/2015 13:27, Karl Palsson wrote:
>>> Isn't this normally called the "OYE-0001" ? not "OY-0001" ? The website
>>> and all literature I've seen uses the "OYE-0001" name...
>>>
>>> Regardless, in many places, you have
On 10/07/2015 21:31, John Crispin wrote:
>
>
> On 10/07/2015 17:19, Karl Palsson wrote:
>> John Crispin wrote:
>>
>>
>>> On 10/07/2015 13:27, Karl Palsson wrote:
Isn't this normally called the "OYE-0001" ? not "OY-0001" ? The website
and all literature I've seen uses the "OYE-0001"
On 10/07/15 02:54, Pan, Miaoqing wrote:
> Agree with you, I investigated this, tried to merge two into one. E.g.
> Implement the common core for spinand, separate vendors related codes, but
> give up finally as no device to verify mt29f:( So I only add it to support
> for ath79 platform.
Since the /dev filesystem is tiny, /dev/shm needs to live somewhere
else.
Signed-off-by: Daniel Gimpelevich
--- a/initd/early.c 2015-06-19 14:01:25.0 -0700
+++ b/initd/early.c 2015-07-10 15:04:23.270143065 -0700
@@ -66,16 +66,20 @@
mount("sysfs", "/sys", "sysfs", MS_NOATIM
Signed-off-by: Daniel Gimpelevich
---
include/target.mk | 1 +
target/linux/x86/kvm_guest/config-default | 15 ++-
target/linux/x86/kvm_guest/target.mk | 1 +
target/linux/x86/xen_domu/target.mk | 1 +
4 files changed, 17 insertions(+), 1 deletion
On 10 July 2015 at 05:07, camden lindsay
wrote:
> I'm sorry, i said ath9k in the subject but the above seems more likely
> to be ath10k.
>
> On Thu, Jul 9, 2015 at 7:03 PM, camden lindsay
> wrote:
>> Hello-
>>
>> Thought I should report this, since there was so much discussion and
>> confusion on
26 matches
Mail list logo
