It turned out that the wifi wasn't working because of a missmatch in the mtd
"art" partition naming. The ath10k caldata hotplug script was expecting it named
"0:ART" instead of "art".
Wifi seems to work fine now.
I will drop those files in the next PR.
On 10/31/19 1:12 PM, Robert Marko wrote:
>
On Thu, 31 Oct 2019 at 13:10, Daniel Danzberger wrote:
>
> Hi Jeff,
> >
> > .../arch/arm/boot/dts/qcom-ipq4019-bus.dtsi | 1142 +
> > .../include/dt-bindings/msm/msm-bus-ids.h | 869 +
> >
> > The sudden appearance of a need the MSM bus and its IDs worries me.
>
Hi Jeff,
>
> .../arch/arm/boot/dts/qcom-ipq4019-bus.dtsi | 1142 +
> .../include/dt-bindings/msm/msm-bus-ids.h | 869 +
>
> The sudden appearance of a need the MSM bus and its IDs worries me.
>
> With 25 devices already on the ipq40xx platform without them, it
Because of old MT29F driver, it was basically a hack just to get
SPI-NANDs working.
On Thu, 31 Oct 2019 at 11:34, Daniel Danzberger wrote:
>
> Well, that makes sense and now it works :)
> I am just wondering why it has been working before with the other driver.
>
> On 10/31/19 11:30 AM, Robert
Well, that makes sense and now it works :)
I am just wondering why it has been working before with the other driver.
On 10/31/19 11:30 AM, Robert Marko wrote:
> On Thu, 31 Oct 2019 at 11:30, Daniel Danzberger wrote:
>>
>> I am already using 'ubi.mtd=rootfs root=/dev/ubiblock0_1', which has
On Thu, 31 Oct 2019 at 11:30, Daniel Danzberger wrote:
>
> I am already using 'ubi.mtd=rootfs root=/dev/ubiblock0_1', which has worked
> before
Well this is the issue, your ubi.mtd needs to be ubi.mtd=ubi
>
> On 10/31/19 11:26 AM, Robert Marko wrote:
> > On Thu, 31 Oct 2019 at 11:25, Daniel
I am already using 'ubi.mtd=rootfs root=/dev/ubiblock0_1', which has worked
before
On 10/31/19 11:26 AM, Robert Marko wrote:
> On Thu, 31 Oct 2019 at 11:25, Daniel Danzberger wrote:
>>
>> On the deprecated staging driver, it somehow directly came up as "rootfs" and
>> not "ubi". Even though it
On Thu, 31 Oct 2019 at 11:25, Daniel Danzberger wrote:
>
> On the deprecated staging driver, it somehow directly came up as "rootfs" and
> not "ubi". Even though it has been named "ubi" in the dts.
> Now the image won't boot because no rootfs is detected:
>
>
> [1.919001] Creating 1 MTD
On the deprecated staging driver, it somehow directly came up as "rootfs" and
not "ubi". Even though it has been named "ubi" in the dts.
Now the image won't boot because no rootfs is detected:
[1.919001] Creating 1 MTD partitions on "spi0.1":
[1.925399] 0x-0x0800
On Thu, 31 Oct 2019 at 11:17, Daniel Danzberger wrote:
>
> Using 'compatible = "spi-nand"' worked and the device got detected by the
> driver. However it won't create and "rootfs" partition like it did before.
>
> ---
> [1.901930] spi-nand spi0.1: GigaDevice SPI NAND was found.
> [
Using 'compatible = "spi-nand"' worked and the device got detected by the
driver. However it won't create and "rootfs" partition like it did before.
---
[1.901930] spi-nand spi0.1: GigaDevice SPI NAND was found.
[1.905266] spi-nand spi0.1: 128 MiB, block size: 128 KiB, page size: 2048,
Hi,
> > + m25p80@0 {
> > + #address-cells = <1>;
> > + #size-cells = <1>;
> > + reg = <0>;
> > + linux,modalias = "m25p80", "n25q128a11";
> > +
On 10/30/19 4:27 AM, Daniel Danzberger wrote:
This device contains 2 flash devices. One NOR (32M) and one NAND (128M).
U-boot and caldata are on the NOR, the firmware on the NAND.
SoC:IPQ4019
CPU:4x 710MHz ARMv7
RAM:256MB
FLASH: NOR:32MB NAND:128MB
[...]
Hi,
just some cosmetical drive-by comments below:
...
> diff --git
> a/target/linux/ipq40xx/base-files/etc/hotplug.d/firmware/11-ath10k-caldata
> b/target/linux/ipq40xx/base-
> files/etc/hotplug.d/firmware/11-ath10k-caldata
> index 2336ef3c7b..b18d17e422 100644
> ---
This device contains 2 flash devices. One NOR (32M) and one NAND (128M).
U-boot and caldata are on the NOR, the firmware on the NAND.
SoC:IPQ4019
CPU:4x 710MHz ARMv7
RAM:256MB
FLASH: NOR:32MB NAND:128MB
ETH:2x GMAC Gigabit
POE:802.3 af/at POE,
15 matches
Mail list logo
