This change enables support to select phy4 in RGMII mode and
enables RGMII TX/RX clock internal delays.
Signed-off-by: Ram Chandra Jangir
---
.../linux/ipq806x/files-4.14/arch/arm/boot/dts/qcom-ipq8064-ap161.dts | 3 +++
1 file changed, 3 insertions(+)
diff --git
a/target/linux/ipq806x/files
ff-by: Ram Chandra Jangir
---
Changes since v1:
* Added RGMII properties as bool
.../linux/generic/files/drivers/net/phy/ar8216.c | 15 +++-
.../linux/generic/files/drivers/net/phy/ar8216.h | 4 ++
.../linux/generic/files/drivers/net/phy/ar8327.c | 44 ++
.../linux/gen
On 11/26/2018 3:15 PM, John Crispin wrote:
On 19/10/2018 13:17, Ram Chandra Jangir wrote:
We have IPQ8064 AP161 board which has three GMAC's
* RGMII x2
* SGMII x1.
The existing ar8327 driver does not have support for
three GMAC's connection, hence this change adds support
fo
ff-by: Ram Chandra Jangir
---
.../linux/generic/files/drivers/net/phy/ar8216.c | 15 +++-
.../linux/generic/files/drivers/net/phy/ar8216.h | 4 ++
.../linux/generic/files/drivers/net/phy/ar8327.c | 43 ++
.../linux/generic/files/drivers/net/phy/ar8327.h | 7
4 fil
) ethernet, 2G and 5G WiFi
6) ubi sysupgrade
Signed-off-by: Ram Chandra Jangir
---
.../ipq806x/base-files/etc/board.d/02_network | 5 +
.../ipq806x/base-files/lib/upgrade/platform.sh | 1 +
.../arch/arm/boot/dts/qcom-ipq8064-ap161.dts | 277 +
target/linux
Signed-off-by: Ram Chandra Jangir
---
...ctrl-Fixed-missing-RGMII-pincontrol-defin.patch | 54 ++
1 file changed, 54 insertions(+)
create mode 100644
target/linux/ipq806x/patches-4.14/0075-ipq8064-pinctrl-Fixed-missing-RGMII-pincontrol-defin.patch
diff --git
a/target
:
1) NOR boot and NAND boot
2) Tested USB and PCIe interfaces
3) WDOG test
4) cpu frequency scaling
5) ethernet, 2G and 5G WiFi
6) ubi sysupgrade
The ap-dk07.1-c1 board is already available in upstream
linux v4.17
Signed-off-by: Ram Chandra Jangir
On 9/12/2018 4:52 AM, Christian Lamparter wrote:
> On Monday, September 10, 2018 5:50:53 PM CEST Ram Chandra Jangir wrote:
>> On Friday, September 07, 2018 8:36 PM CEST Christian Lamparter wrote:
>>> On Friday, September 7, 2018 2:10:30 PM CEST Ram Chandra Jangir wrote:
>&
Thanks Christian Lamparter,
On Friday, September 07, 2018 8:36 PM CEST Christian Lamparter wrote:
> On Friday, September 7, 2018 2:10:30 PM CEST Ram Chandra Jangir wrote:
> * SoC: QCA IPQ4019
> * RAM: 512 MiB
> * Flash: 32 MiB of SPI NOR and 128 MiB NAND
> * Wireless: 2.4-GH
:
1) NOR boot and NAND boot
2) Tested USB and PCIe interfaces
3) WDOG test
4) cpu frequency scaling
5) ethernet, 2G and 5G WiFi
The ap-dk07.1-c1 board is already available in upstream
linux v4.17
Signed-off-by: Ram Chandra Jangir
---
Changes since v1:
Fixed
12:22 AM
> To: Ram Chandra Jangir
> Cc: openwrt-devel@lists.openwrt.org; nar...@codeaurora.org
> Subject: Re: [OpenWrt-Devel] [PATCH] ipq40xx: Add support for IPQ4019
ap-dk07.1-c1
>
> is this correct information? Wireless: 2.4-GHz 802.11ac
>
> On 31/08/2018, Ram Chandra Jangir
:
1) NOR boot and NAND boot
2) Tested USB and PCIe interfaces
3) WDOG test
4) cpu frequency scaling
5) ethernet, 2G and 5G WiFi
The ap-dk07.1-c1 board is already available in upstream
linux v4.17
Signed-off-by: Ram Chandra Jangir
---
.../etc/hotplug.d/firmware
, cgdisk, sgdisk, and fixparts programs).
Thanks,
Ram
-Original Message-
From: Josua Mayer [mailto:josua.maye...@gmail.com]
Sent: Wednesday, May 04, 2016 6:13 PM
To: Ram Chandra Jangir ; openwrt-devel@lists.openwrt.org
Subject: Re: [OpenWrt-Devel] [PATCH v2 2/3] ext4_part_match: fix bug that
Thanks Josua Mayer.
Devname and partname both are different. Devname is holding the device node(ex.
mmcblkXpY) and given name(or partname) is the partition name(ex. rootfs or
rootfs_data).
For below uevent sysfs entries, it tries to populate the device
node(mmcblkXpY) in devname variable and
: 'Arjen de Korte' ;
openwrt-devel@lists.openwrt.org
Cc: 'Ram Chandra Jangir'
Subject: RE: [OpenWrt-Devel] stdout and putchar() behavior in musl
Thanks for your comments. Unfortunately flush(stdout) didn't help.
Thanks,
Naresh
-Original Message-
From: openwrt-devel [
Hi,
Did anyone observed stdout and putchar() behavior differences between musl &
uClibc?
I have below code snippet :
int main(void){
int c;
while((c=getchar())!= 'e') {
putchar(c+1);
}
return 0;
}
When I use uClibc/gcc, I can see writing c+1 f
This change will enables eMMC (ext4 fs) boot support, when we try to boot
from eMMC card then it will read partition names from
/sys/block/mmcblkX/mmcblkXY/uevent
file and will mount the rootfs_data partition as ext4fs overlay.
Signed-off-by: Ram Chandra Jangir
---
change in v2:
fixed space
switch from tmpfs to ext4fs overlay.
Signed-off-by: Ram Chandra Jangir
---
CMakeLists.txt | 1 +
libfstools/ext4.c | 192
libfstools/find.c | 3 +-
libfstools/libfstools.h | 1 +
libfstools/overlay.c| 22
18 matches
Mail list logo
