Re: [OpenWrt-Devel] Add support for AVM Fritzbox 7360 SL

2016-05-19 Thread Sebastian Ortwein 

Hey Christian

No you can use the avm bootloader. Uboot is not recommend because some 
details about your Fritz Box ist in the AVM bootloader (macadresse, 
eeprom wireless).


You don't need any extra hardware but you must find out the IP Adress of 
your Bootloader in most cases it is 192.168.178.1. Here are some Infos 
http://www.wehavemorefun.de/fritzbox/ADAM2_Shell. in FritzOS you can 
find your variables in /proc/sys/urloader/enviroment.

I recommend a seriel cable to control the bootloader but you don't need one.
You have 5 seconds to make a ftp connection to your Fritzbox on boot.

Here are a short description
login to your fritzbox with

ftp 192.168.178.1
user: adam2
pass: adam2

now do the following commands:

passive
binary
debug 1
quote MEDIA FLSH

its time to flash your image to the box, use the squashfs image because 
the jffs image will not work ! Don't override your bootloader or the 
tffs partions !!!


put bin/lantiq/openwrt-lantiq-xrx200-FRITZ7360SL mtd1

after a time flash is ready an you can start restart your fritzbox with 
openwrt.


Sebastian

Am 16.05.2016 um 11:27 schrieb Christian Mehlis:

Am 15.05.2016 um 22:13 schrieb Martin Blumenstingl:
On Sun, May 15, 2016 at 9:45 PM, Sebastian Ortwein 
 wrote:

Am 15.05.2016 um 17:37 schrieb Martin Blumenstingl:
Okay thank you for support. Now all thinks works fine LAN, WIFI, 
Switch and

USB.
I attach my patch to add the support for OpenWRT.

Great - congratulations :-)


Hi Sebastian,

I'm interested in some details about the flashing procedure.

Did you replace the original avm bootloader with uboot?

   a) YEA: How to replace it, with which uboot version, where to find 
the code?
   b) NO: How to flash openwrt with avm bootloader? Can I flash 
without any extra hardware? Only with serial and the right commands? 
Please name them.


Thanks,
Christian

___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Add support for AVM Fritzbox 7360 SL

2016-05-16 Thread Christian Mehlis 

Am 15.05.2016 um 22:13 schrieb Martin Blumenstingl:

On Sun, May 15, 2016 at 9:45 PM, Sebastian Ortwein  wrote:

Am 15.05.2016 um 17:37 schrieb Martin Blumenstingl:
Okay thank you for support. Now all thinks works fine LAN, WIFI, Switch and
USB.
I attach my patch to add the support for OpenWRT.

Great - congratulations :-)


Hi Sebastian,

I'm interested in some details about the flashing procedure.

Did you replace the original avm bootloader with uboot?

   a) YEA: How to replace it, with which uboot version, where to find 
the code?
   b) NO: How to flash openwrt with avm bootloader? Can I flash without 
any extra hardware? Only with serial and the right commands? Please name 
them.


Thanks,
Christian
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Add support for AVM Fritzbox 7360 SL

2016-05-15 Thread Martin Blumenstingl 
On Sun, May 15, 2016 at 9:45 PM, Sebastian Ortwein  wrote:
> Am 15.05.2016 um 17:37 schrieb Martin Blumenstingl:
> Okay thank you for support. Now all thinks works fine LAN, WIFI, Switch and
> USB.
> I attach my patch to add the support for OpenWRT.
Great - congratulations :-)

> Is there anything to do for including this patch in OpenWRT?
actually you should split your patch into two:
1. adding support for 7360 SL
2. enabling CONFIG_AT803X_PHY saying that it's needed by 7360 SL

Make sure that you commit the patches with "git commit -s" (to add
"signed-off-by") and give them a nice description.
Then send them to this mailing-list (preferrably with git send-email -
see also: [0]).

PS: maybe you could change the LED labels in your patch to have a
"fritz7360sl" prefix, instead of "fritz7360" before sending the patch.


Martin

[0] https://wiki.openwrt.org/doc/patch/using.git
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Add support for AVM Fritzbox 7360 SL

2016-05-15 Thread Sebastian Ortwein 

Am 15.05.2016 um 17:37 schrieb Martin Blumenstingl:

On Sun, May 15, 2016 at 3:44 PM, Sebastian Ortwein  wrote:

USB, WLAN and LAN works now. The only think what would not work is phy0 &
phy1.
I have attached my lastet patch.

if you google around a bit you'll find an AR8035 datasheet: that phy
is from the same series as the AR8030.
It defines that the RST pin is "active low" -> meaning you have to
pull it high to ensure that the PHY is not being reset:
http://lxr.free-electrons.com/source/Documentation/devicetree/bindings/pinctrl/lantiq,pinctrl-xway.txt?v=4.4#L61
This means you should probably use:
lantiq,output = <1>;
lantiq,pull = <2>;
lantiq,open-drain;


[ 0.993675] libphy: lantiq,xrx200-mdio: probed
[1.004257] eth0: attached PHY [Generic PHY] (phy_addr=0:00, irq=-1)
[1.009606] eth0: attached PHY [Generic PHY] (phy_addr=0:01, irq=-1)
[1.079564] eth0: attached PHY [Lantiq XWAY VR9 GPHY 11G v1.4]
(phy_addr=0:11, irq=-1)
[1.147555] eth0: attached PHY [Lantiq XWAY VR9 GPHY 11G v1.4]
(phy_addr=0:13, irq=-1)

"Generic PHY" means that no specific driver for this PHY is loaded.
Make sure you enable CONFIG_AT803X_PHY in target/linux/lantiq/config-4.4

Additionally you should check the phy-mode:
You are setting phy-mode = "rgmii", but Atheros says that the AR8030
is an "Ultra low-power single RMII Fast Ethernet PHY".
Thus you should probably change "rgmii" to "rmii".


Martin


Okay thank you for support. Now all thinks works fine LAN, WIFI, Switch 
and USB.

I attach my patch to add the support for OpenWRT.

Is there anything to do for including this patch in OpenWRT?

Sebastian


On Sun, May 15, 2016 at 3:44 PM, Sebastian Ortwein  wrote:

Am 08.05.2016 um 18:40 schrieb Martin Blumenstingl:

On Sun, May 8, 2016 at 5:49 PM, Sebastian Ortwein 
wrote:

can I add it the following way ?
  mdio@0 {
  #address-cells = <1>;
  #size-cells = <0>;
  compatible = "lantiq,xrx200-mdio";
  phy0: ethernet-phy@0 {
  reg = <0x0>;
  compatible = "lantiq,phy11g",
"ethernet-phy-ieee802.3-c22";
  gpios = < 37 0>;
  };
  phy1: ethernet-phy@1 {
  reg = <0x1>;
  compatible = "lantiq,phy11g",
"ethernet-phy-ieee802.3-c22";
  gpios = < 44 0>;
  };
  phy11: ethernet-phy@11 {
  reg = <0x11>;
  compatible = "lantiq,phy11g",
"ethernet-phy-ieee802.3-c22";
  };
  phy13: ethernet-phy@13 {
  reg = <0x13>;
  compatible = "lantiq,phy11g",
"ethernet-phy-ieee802.3-c22";
  };

I think you have to name the property "reset-gpios", but apart from
that it looks good.

I have try it like you sayed. But without success.
I think the gpios are defined here, but it won't working.

 phy-rst {
 lantiq,pins = "io37", "io44";
 lantiq,pull = <0>;
 lantiq,open-drain = <0>;
 lantiq,output = <1>;
 };


I cannot see any ath9k messages in your kernel log - are you sure it's
being installed (/lib/modules/*/ath9k.ko)?
Your first patch lists kmod-ath9k, but if you added that after you
generated your .config then you're probably still missing it.
Please check "grep kmod-ath9k .config" and enable (set it to
=y/built-in) it if it's missing.

I have not disable the ath9k driver. it is present and loaded.

I think I see the problem after looking at your .dts again:
you *must* specify the ath,pci-slot property, otherwise the fixup is
not executed.
It seems that the wifi part is similar to the TD-W8980 (AR9287 behind
the PCIe-to-PCI bridge), so "0" should be the right value.
(otherwise it's pretty easy to find out by looking at sysfs:
/sys/bus/pci/devices/\:00\:0e.0/ -> that's where the ath9k device
on HH5A can be found, there we use ath,pci-slot = <0xe>;)


Martin


[0]
https://github.com/openwrt/openwrt/blob/master/target/linux/lantiq/patches-4.4/0035-owrt-lantiq-wifi-and-ethernet-eeprom-handling.patch#L178


USB, WLAN and LAN works now. The only think what would not work is phy0 &
phy1.
I have attached my lastet patch.

dmesg

[0.00] Linux version 4.4.7 (sebastian@sebastian-desktop) (gcc
version 5.3.0 (OpenWrt GCC 5.3.0 r49377) ) #1 Sun May 15 13:18:03 UTC 2016
[0.00] SoC: xRX200 rev 1.1
[0.00] bootconsole [early0] enabled
[0.00] CPU0 revision is: 00019555 (MIPS 34Kc)
[0.00] MIPS: machine is FRITZ7360SL - 1&1 HomeServer
[0.00] Determined physical RAM map:
[0.00]  memory: 0800 @  (usable)
[

Re: [OpenWrt-Devel] Add support for AVM Fritzbox 7360 SL

2016-05-15 Thread Martin Blumenstingl 
On Sun, May 15, 2016 at 3:44 PM, Sebastian Ortwein  wrote:
> USB, WLAN and LAN works now. The only think what would not work is phy0 &
> phy1.
> I have attached my lastet patch.
if you google around a bit you'll find an AR8035 datasheet: that phy
is from the same series as the AR8030.
It defines that the RST pin is "active low" -> meaning you have to
pull it high to ensure that the PHY is not being reset:
http://lxr.free-electrons.com/source/Documentation/devicetree/bindings/pinctrl/lantiq,pinctrl-xway.txt?v=4.4#L61
This means you should probably use:
lantiq,output = <1>;
lantiq,pull = <2>;
lantiq,open-drain;

> [ 0.993675] libphy: lantiq,xrx200-mdio: probed
> [1.004257] eth0: attached PHY [Generic PHY] (phy_addr=0:00, irq=-1)
> [1.009606] eth0: attached PHY [Generic PHY] (phy_addr=0:01, irq=-1)
> [1.079564] eth0: attached PHY [Lantiq XWAY VR9 GPHY 11G v1.4]
> (phy_addr=0:11, irq=-1)
> [1.147555] eth0: attached PHY [Lantiq XWAY VR9 GPHY 11G v1.4]
> (phy_addr=0:13, irq=-1)
"Generic PHY" means that no specific driver for this PHY is loaded.
Make sure you enable CONFIG_AT803X_PHY in target/linux/lantiq/config-4.4

Additionally you should check the phy-mode:
You are setting phy-mode = "rgmii", but Atheros says that the AR8030
is an "Ultra low-power single RMII Fast Ethernet PHY".
Thus you should probably change "rgmii" to "rmii".


Martin

On Sun, May 15, 2016 at 3:44 PM, Sebastian Ortwein  wrote:
> Am 08.05.2016 um 18:40 schrieb Martin Blumenstingl:
>>
>> On Sun, May 8, 2016 at 5:49 PM, Sebastian Ortwein 
>> wrote:
>>>
>>> can I add it the following way ?
>>>  mdio@0 {
>>>  #address-cells = <1>;
>>>  #size-cells = <0>;
>>>  compatible = "lantiq,xrx200-mdio";
>>>  phy0: ethernet-phy@0 {
>>>  reg = <0x0>;
>>>  compatible = "lantiq,phy11g",
>>> "ethernet-phy-ieee802.3-c22";
>>>  gpios = < 37 0>;
>>>  };
>>>  phy1: ethernet-phy@1 {
>>>  reg = <0x1>;
>>>  compatible = "lantiq,phy11g",
>>> "ethernet-phy-ieee802.3-c22";
>>>  gpios = < 44 0>;
>>>  };
>>>  phy11: ethernet-phy@11 {
>>>  reg = <0x11>;
>>>  compatible = "lantiq,phy11g",
>>> "ethernet-phy-ieee802.3-c22";
>>>  };
>>>  phy13: ethernet-phy@13 {
>>>  reg = <0x13>;
>>>  compatible = "lantiq,phy11g",
>>> "ethernet-phy-ieee802.3-c22";
>>>  };
>>
>> I think you have to name the property "reset-gpios", but apart from
>> that it looks good.
>
> I have try it like you sayed. But without success.
> I think the gpios are defined here, but it won't working.
>
> phy-rst {
> lantiq,pins = "io37", "io44";
> lantiq,pull = <0>;
> lantiq,open-drain = <0>;
> lantiq,output = <1>;
> };
>
 I cannot see any ath9k messages in your kernel log - are you sure it's
 being installed (/lib/modules/*/ath9k.ko)?
 Your first patch lists kmod-ath9k, but if you added that after you
 generated your .config then you're probably still missing it.
 Please check "grep kmod-ath9k .config" and enable (set it to
 =y/built-in) it if it's missing.
>>>
>>> I have not disable the ath9k driver. it is present and loaded.
>>
>> I think I see the problem after looking at your .dts again:
>> you *must* specify the ath,pci-slot property, otherwise the fixup is
>> not executed.
>> It seems that the wifi part is similar to the TD-W8980 (AR9287 behind
>> the PCIe-to-PCI bridge), so "0" should be the right value.
>> (otherwise it's pretty easy to find out by looking at sysfs:
>> /sys/bus/pci/devices/\:00\:0e.0/ -> that's where the ath9k device
>> on HH5A can be found, there we use ath,pci-slot = <0xe>;)
>>
>>
>> Martin
>>
>>
>> [0]
>> https://github.com/openwrt/openwrt/blob/master/target/linux/lantiq/patches-4.4/0035-owrt-lantiq-wifi-and-ethernet-eeprom-handling.patch#L178
>
>
> USB, WLAN and LAN works now. The only think what would not work is phy0 &
> phy1.
> I have attached my lastet patch.
>
> dmesg
>
> [0.00] Linux version 4.4.7 (sebastian@sebastian-desktop) (gcc
> version 5.3.0 (OpenWrt GCC 5.3.0 r49377) ) #1 Sun May 15 13:18:03 UTC 2016
> [0.00] SoC: xRX200 rev 1.1
> [0.00] bootconsole [early0] enabled
> [0.00] CPU0 revision is: 00019555 (MIPS 34Kc)
> [0.00] MIPS: machine is FRITZ7360SL - 1&1 HomeServer
> [0.00] Determined physical RAM map:
> [0.00]  memory: 0800 @  (usable)
> [0.00] Initrd not

Re: [OpenWrt-Devel] Add support for AVM Fritzbox 7360 SL

2016-05-15 Thread Sebastian Ortwein 

Am 08.05.2016 um 18:40 schrieb Martin Blumenstingl:

On Sun, May 8, 2016 at 5:49 PM, Sebastian Ortwein  wrote:

can I add it the following way ?
 mdio@0 {
 #address-cells = <1>;
 #size-cells = <0>;
 compatible = "lantiq,xrx200-mdio";
 phy0: ethernet-phy@0 {
 reg = <0x0>;
 compatible = "lantiq,phy11g",
"ethernet-phy-ieee802.3-c22";
 gpios = < 37 0>;
 };
 phy1: ethernet-phy@1 {
 reg = <0x1>;
 compatible = "lantiq,phy11g",
"ethernet-phy-ieee802.3-c22";
 gpios = < 44 0>;
 };
 phy11: ethernet-phy@11 {
 reg = <0x11>;
 compatible = "lantiq,phy11g",
"ethernet-phy-ieee802.3-c22";
 };
 phy13: ethernet-phy@13 {
 reg = <0x13>;
 compatible = "lantiq,phy11g",
"ethernet-phy-ieee802.3-c22";
 };

I think you have to name the property "reset-gpios", but apart from
that it looks good.

I have try it like you sayed. But without success.
I think the gpios are defined here, but it won't working.

phy-rst {
lantiq,pins = "io37", "io44";
lantiq,pull = <0>;
lantiq,open-drain = <0>;
lantiq,output = <1>;
};


I cannot see any ath9k messages in your kernel log - are you sure it's
being installed (/lib/modules/*/ath9k.ko)?
Your first patch lists kmod-ath9k, but if you added that after you
generated your .config then you're probably still missing it.
Please check "grep kmod-ath9k .config" and enable (set it to
=y/built-in) it if it's missing.

I have not disable the ath9k driver. it is present and loaded.

I think I see the problem after looking at your .dts again:
you *must* specify the ath,pci-slot property, otherwise the fixup is
not executed.
It seems that the wifi part is similar to the TD-W8980 (AR9287 behind
the PCIe-to-PCI bridge), so "0" should be the right value.
(otherwise it's pretty easy to find out by looking at sysfs:
/sys/bus/pci/devices/\:00\:0e.0/ -> that's where the ath9k device
on HH5A can be found, there we use ath,pci-slot = <0xe>;)


Martin


[0] 
https://github.com/openwrt/openwrt/blob/master/target/linux/lantiq/patches-4.4/0035-owrt-lantiq-wifi-and-ethernet-eeprom-handling.patch#L178


USB, WLAN and LAN works now. The only think what would not work is phy0 
& phy1.

I have attached my lastet patch.

dmesg

[0.00] Linux version 4.4.7 (sebastian@sebastian-desktop) (gcc 
version 5.3.0 (OpenWrt GCC 5.3.0 r49377) ) #1 Sun May 15 13:18:03 UTC 2016

[0.00] SoC: xRX200 rev 1.1
[0.00] bootconsole [early0] enabled
[0.00] CPU0 revision is: 00019555 (MIPS 34Kc)
[0.00] MIPS: machine is FRITZ7360SL - 1&1 HomeServer
[0.00] Determined physical RAM map:
[0.00]  memory: 0800 @  (usable)
[0.00] Initrd not found or empty - disabling initrd
[0.00] Zone ranges:
[0.00]   Normal   [mem 0x-0x07ff]
[0.00] Movable zone start for each node
[0.00] Early memory node ranges
[0.00]   node   0: [mem 0x-0x07ff]
[0.00] Initmem setup node 0 [mem 
0x-0x07ff]

[0.00] On node 0 totalpages: 32768
[0.00] free_area_init_node: node 0, pgdat 804d6390, node_mem_map 
81007b60

[0.00]   Normal zone: 256 pages used for memmap
[0.00]   Normal zone: 0 pages reserved
[0.00]   Normal zone: 32768 pages, LIFO batch:7
[0.00] Primary instruction cache 32kB, VIPT, 4-way, linesize 32 
bytes.
[0.00] Primary data cache 32kB, 4-way, VIPT, cache aliases, 
linesize 32 bytes

[0.00] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
[0.00] pcpu-alloc: [0] 0
[0.00] Built 1 zonelists in Zone order, mobility grouping on.  
Total pages: 32512

[0.00] Kernel command line: console=ttyLTQ0,115200 init=/etc/preinit
[0.00] PID hash table entries: 512 (order: -1, 2048 bytes)
[0.00] Dentry cache hash table entries: 16384 (order: 4, 65536 
bytes)

[0.00] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
[0.00] Writing ErrCtl register=00074200
[0.00] Readback ErrCtl register=00074200
[0.00] Memory: 123372K/131072K available (3764K kernel code, 
164K rwdata, 1144K rodata, 1184K init, 211K bss, 7700K reserved, 0K 
cma-reserved)

[0.00] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[0.00] NR_IRQS:256
[0.00] CPU Clock: 500MHz
[0.00]

Re: [OpenWrt-Devel] Add support for AVM Fritzbox 7360 SL

2016-05-08 Thread Martin Blumenstingl 
On Sun, May 8, 2016 at 5:49 PM, Sebastian Ortwein  wrote:
> can I add it the following way ?
> mdio@0 {
> #address-cells = <1>;
> #size-cells = <0>;
> compatible = "lantiq,xrx200-mdio";
> phy0: ethernet-phy@0 {
> reg = <0x0>;
> compatible = "lantiq,phy11g",
> "ethernet-phy-ieee802.3-c22";
> gpios = < 37 0>;
> };
> phy1: ethernet-phy@1 {
> reg = <0x1>;
> compatible = "lantiq,phy11g",
> "ethernet-phy-ieee802.3-c22";
> gpios = < 44 0>;
> };
> phy11: ethernet-phy@11 {
> reg = <0x11>;
> compatible = "lantiq,phy11g",
> "ethernet-phy-ieee802.3-c22";
> };
> phy13: ethernet-phy@13 {
> reg = <0x13>;
> compatible = "lantiq,phy11g",
> "ethernet-phy-ieee802.3-c22";
> };
I think you have to name the property "reset-gpios", but apart from
that it looks good.

>> I cannot see any ath9k messages in your kernel log - are you sure it's
>> being installed (/lib/modules/*/ath9k.ko)?
>> Your first patch lists kmod-ath9k, but if you added that after you
>> generated your .config then you're probably still missing it.
>> Please check "grep kmod-ath9k .config" and enable (set it to
>> =y/built-in) it if it's missing.
>
> I have not disable the ath9k driver. it is present and loaded.
I think I see the problem after looking at your .dts again:
you *must* specify the ath,pci-slot property, otherwise the fixup is
not executed.
It seems that the wifi part is similar to the TD-W8980 (AR9287 behind
the PCIe-to-PCI bridge), so "0" should be the right value.
(otherwise it's pretty easy to find out by looking at sysfs:
/sys/bus/pci/devices/\:00\:0e.0/ -> that's where the ath9k device
on HH5A can be found, there we use ath,pci-slot = <0xe>;)


Martin


[0] 
https://github.com/openwrt/openwrt/blob/master/target/linux/lantiq/patches-4.4/0035-owrt-lantiq-wifi-and-ethernet-eeprom-handling.patch#L178
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Add support for AVM Fritzbox 7360 SL

2016-05-08 Thread Sebastian Ortwein 

Am 08.05.2016 um 14:56 schrieb Martin Blumenstingl:

On Sun, May 8, 2016 at 10:33 AM, Sebastian Ortwein  wrote:

I get the eeprom from the ath9k driver working, but wifi will not showed.
First, I get a error message that from the ath9k driver that the eeprom
couldn't load. After PCI Bus is initialize the eeprom is loaded.

That is "normal" - nothing to worry about here.


[1.16] found entry name -> annex=B
[1.192650] found entry name -> maca=BC:05:43:D7:1E:7C
[1.197738] found entry name -> macb=BC:05:43:D7:1E:7D
[1.202875] found entry name -> macwlan=BC:05:43:D7:1E:7E
[1.208269] found entry name -> macdsl=BC:05:43:D7:1E:7F
[1.213632] found entry name -> macwlan2=BC:05:43:D7:1E:81
[1.219063] found entry name -> wlan_key=4004584479108575
[1.227509] ath9k,eeprom ath9k_eep: endian check enabled.
[1.231483] ath9k,eeprom ath9k_eep: using random mac
[1.236475] ath9k,eeprom ath9k_eep: loaded ath9k eeprom
[1.246508] UBIFS error (pid: 1): cannot open "ubi0:rootfs", error -19
[1.257496] VFS: Mounted root (squashfs filesystem) readonly on device
31:3.
[1.265035] Freeing unused kernel memory: 1224K (804fe000 - 8063)
[2.475280] init: Console is alive
.

As you can see OpenWrt will find the mac-adesses from all devices, how can I
asign it in the dts file?

I think you can't (at least not with the current tffs driver). All it
currently does is printing the mac addresses: [0]
My fritz_tffs_read tool is userspace only. The only downside is that
you currently cannot userspace tools to set the mac address in the
ath9k calibration data. We would need a solution like Christian's
OWL-loader, see [1] (or another TFFS kernel driver).


The wiki is right. I will upload some images to the openwrt Wiki when the
box is working.
But phy0 and phy1 works only somtimes. In my dts file I assigned the reset
GPIO's like in the FRITZ3370.dts file.
I have take GPIO config from the AVM GPL sources. Is there anything I forgot
orwrong in my new DTS file ?

I think the GPIOs definition is in the wrong place - it has to be per
PHY (thus you should put it into the mdio@0 section below).

can I add it the following way ?
mdio@0 {
#address-cells = <1>;
#size-cells = <0>;
compatible = "lantiq,xrx200-mdio";
phy0: ethernet-phy@0 {
reg = <0x0>;
compatible = "lantiq,phy11g", 
"ethernet-phy-ieee802.3-c22";

gpios = < 37 0>;
};
phy1: ethernet-phy@1 {
reg = <0x1>;
compatible = "lantiq,phy11g", 
"ethernet-phy-ieee802.3-c22";

gpios = < 44 0>;
};
phy11: ethernet-phy@11 {
reg = <0x11>;
compatible = "lantiq,phy11g", 
"ethernet-phy-ieee802.3-c22";

};
phy13: ethernet-phy@13 {
reg = <0x13>;
compatible = "lantiq,phy11g", 
"ethernet-phy-ieee802.3-c22";

};


I cannot see any ath9k messages in your kernel log - are you sure it's
being installed (/lib/modules/*/ath9k.ko)?
Your first patch lists kmod-ath9k, but if you added that after you
generated your .config then you're probably still missing it.
Please check "grep kmod-ath9k .config" and enable (set it to
=y/built-in) it if it's missing.

I have not disable the ath9k driver. it is present and loaded.

root@OpenWrt:/# ls /lib/modules/*/ath9k.ko
/lib/modules/4.4.7/ath9k.ko


root@OpenWrt:/# lsmod
act_connmark1712  0
act_mirred  2800  0
act_skbedit 1744  0
aead3649  0
ath21317  3 ath9k
ath9k 101900  0
ath9k_common   20142  1 ath9k
ath9k_hw  348113  2 ath9k
atm37986  2 pppoatm
br2684  6544  0
cfg80211  230563  4 ath9k

Sebastian



Martin


[0] 
https://github.com/openwrt/openwrt/blob/master/target/linux/lantiq/patches-4.4/0007-MIPS-lantiq-add-basic-tffs-driver.patch
[1] https://lists.openwrt.org/pipermail/openwrt-devel/2016-April/040755.html

___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Add support for AVM Fritzbox 7360 SL

2016-05-08 Thread Martin Blumenstingl 
On Sun, May 8, 2016 at 10:33 AM, Sebastian Ortwein  wrote:
> I get the eeprom from the ath9k driver working, but wifi will not showed.
> First, I get a error message that from the ath9k driver that the eeprom
> couldn't load. After PCI Bus is initialize the eeprom is loaded.
That is "normal" - nothing to worry about here.

> [1.16] found entry name -> annex=B
> [1.192650] found entry name -> maca=BC:05:43:D7:1E:7C
> [1.197738] found entry name -> macb=BC:05:43:D7:1E:7D
> [1.202875] found entry name -> macwlan=BC:05:43:D7:1E:7E
> [1.208269] found entry name -> macdsl=BC:05:43:D7:1E:7F
> [1.213632] found entry name -> macwlan2=BC:05:43:D7:1E:81
> [1.219063] found entry name -> wlan_key=4004584479108575
> [1.227509] ath9k,eeprom ath9k_eep: endian check enabled.
> [1.231483] ath9k,eeprom ath9k_eep: using random mac
> [1.236475] ath9k,eeprom ath9k_eep: loaded ath9k eeprom
> [1.246508] UBIFS error (pid: 1): cannot open "ubi0:rootfs", error -19
> [1.257496] VFS: Mounted root (squashfs filesystem) readonly on device
> 31:3.
> [1.265035] Freeing unused kernel memory: 1224K (804fe000 - 8063)
> [2.475280] init: Console is alive
> .
>
> As you can see OpenWrt will find the mac-adesses from all devices, how can I
> asign it in the dts file?
I think you can't (at least not with the current tffs driver). All it
currently does is printing the mac addresses: [0]
My fritz_tffs_read tool is userspace only. The only downside is that
you currently cannot userspace tools to set the mac address in the
ath9k calibration data. We would need a solution like Christian's
OWL-loader, see [1] (or another TFFS kernel driver).

> The wiki is right. I will upload some images to the openwrt Wiki when the
> box is working.
> But phy0 and phy1 works only somtimes. In my dts file I assigned the reset
> GPIO's like in the FRITZ3370.dts file.
> I have take GPIO config from the AVM GPL sources. Is there anything I forgot
> orwrong in my new DTS file ?
I think the GPIOs definition is in the wrong place - it has to be per
PHY (thus you should put it into the mdio@0 section below).

I cannot see any ath9k messages in your kernel log - are you sure it's
being installed (/lib/modules/*/ath9k.ko)?
Your first patch lists kmod-ath9k, but if you added that after you
generated your .config then you're probably still missing it.
Please check "grep kmod-ath9k .config" and enable (set it to
=y/built-in) it if it's missing.


Martin


[0] 
https://github.com/openwrt/openwrt/blob/master/target/linux/lantiq/patches-4.4/0007-MIPS-lantiq-add-basic-tffs-driver.patch
[1] https://lists.openwrt.org/pipermail/openwrt-devel/2016-April/040755.html
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Add support for AVM Fritzbox 7360 SL

2016-05-08 Thread Sebastian Ortwein 

Am 07.05.2016 um 19:26 schrieb Sylwek ScApi:

W dniu 2016-05-07 o 09:53, Martin Blumenstingl pisze:

On Sat, May 7, 2016 at 12:40 AM, Sebastian Ortwein  wrote:

Hey

I have tried do get openwrt working on my Fritzbox. Openwrt will start
Network and VDSL Modem is working. But WLAN ist not working. The Chip is
supported bei the ath9k driver. Any hint how I can get Wifi working ?

I see you already got most things working - see my comments inline.
I get the eeprom from the ath9k driver working, but wifi will not 
showed. First, I get a error message that from the ath9k driver that the 
eeprom couldn't load. After PCI Bus is initialize the eeprom is loaded.

..
[0.332504] ath9k,eeprom ath9k_eep: failed to load eeprom address
[0.353603] usbcore: registered new interface driver usbfs
[0.359114] usbcore: registered new interface driver hub
[0.364465] usbcore: registered new device driver usb
[0.369845] PCI host bridge to bus :00
[0.373843] pci_bus :00: root bus resource [mem 
0x1c00-0x1cff]

[0.380756] pci_bus :00: root bus resource [io 0x1d80-0x1d8f]
[0.387699] pci_bus :00: root bus resource [??? 0x flags 0x0]
[0.394553] pci_bus :00: No busn resource found for root bus, 
will use [bus 00-ff]

[0.402584] pci :00:00.0: [15d1:0011] type 01 class 0x06
[0.402621] ifx_pcie_rc_class_early_fixup: fixed pcie host bridge to 
pci-pci bridge
[0.420266] ifx_pcie_fixup_resource: fixup host controller 
:00:00.0 (15d1:0011)

[0.427855] pci :00:00.0: PME# supported from D0 D3hot
[0.428422] pci :01:00.0: [168c:ff1c] type 00 class 0x02
[0.428512] pci :01:00.0: reg 0x10: [mem 0x-0x 64bit]
[0.428665] pci :01:00.0: supports D1
[0.428686] pci :01:00.0: PME# supported from D0 D1 D3hot
[0.428975] pci_bus :01: busn_res: [bus 01-ff] end is updated to 01
[0.429015] pci_bus :00: busn_res: [bus 00-ff] end is updated to 01
[0.429072] pci :00:00.0: BAR 8: assigned [mem 0x1c00-0x1c0f]
[0.435760] pci :01:00.0: BAR 0: assigned [mem 
0x1c00-0x1c00 64bit]

[0.443120] pci :00:00.0: PCI bridge to [bus 01]
[0.448137] pci :00:00.0:   bridge window [mem 0x1c00-0x1c0f]
...
[1.16] found entry name -> annex=B
[1.192650] found entry name -> maca=BC:05:43:D7:1E:7C
[1.197738] found entry name -> macb=BC:05:43:D7:1E:7D
[1.202875] found entry name -> macwlan=BC:05:43:D7:1E:7E
[1.208269] found entry name -> macdsl=BC:05:43:D7:1E:7F
[1.213632] found entry name -> macwlan2=BC:05:43:D7:1E:81
[1.219063] found entry name -> wlan_key=4004584479108575
[1.227509] ath9k,eeprom ath9k_eep: endian check enabled.
[1.231483] ath9k,eeprom ath9k_eep: using random mac
[1.236475] ath9k,eeprom ath9k_eep: loaded ath9k eeprom
[1.246508] UBIFS error (pid: 1): cannot open "ubi0:rootfs", error -19
[1.257496] VFS: Mounted root (squashfs filesystem) readonly on 
device 31:3.

[1.265035] Freeing unused kernel memory: 1224K (804fe000 - 8063)
[2.475280] init: Console is alive
.

As you can see OpenWrt will find the mac-adesses from all devices, how 
can I asign it in the dts file?

root@OpenWrt:/# dmesg
[0.00] Linux version 4.4.7 (sebastian@sebastian-desktop) (gcc
version 5.3.0 (OpenWrt GCC 5.3.0 r49296) ) #1 Fri May 6 22:23:36 UTC 2016
[0.00] SoC: xRX200 rev 1.1
[0.00] bootconsole [early0] enabled
[0.00] CPU0 revision is: 00019555 (MIPS 34Kc)
[0.00] MIPS: machine is FRITZ7360SL - 1&1 HomeServer
[0.00] Determined physical RAM map:
[0.00]  memory: 0800 @  (usable)
[0.00] Initrd not found or empty - disabling initrd
[0.00] Zone ranges:
[0.00]   Normal   [mem 0x-0x07ff]
[0.00] Movable zone start for each node
[0.00] Early memory node ranges
[0.00]   node   0: [mem 0x-0x07ff]
[0.00] Initmem setup node 0 [mem
0x-0x07ff]
[0.00] On node 0 totalpages: 32768
[0.00] free_area_init_node: node 0, pgdat 804d6390, node_mem_map
81007a80
[0.00]   Normal zone: 256 pages used for memmap
[0.00]   Normal zone: 0 pages reserved
[0.00]   Normal zone: 32768 pages, LIFO batch:7
[0.00] Primary instruction cache 32kB, VIPT, 4-way, linesize 32
bytes.
[0.00] Primary data cache 32kB, 4-way, VIPT, cache aliases, linesize
32 bytes
[0.00] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
[0.00] pcpu-alloc: [0] 0
[0.00] Built 1 zonelists in Zone order, mobility grouping on.  Total
pages: 32512
[0.00] Kernel command line: console=ttyLTQ0,115200 init=/etc/preinit
[0.00] PID hash table entries: 512 (order: -1, 2048 bytes)
[0.00] Dentry cache hash table entries: 16384 (order: 4,

Re: [OpenWrt-Devel] Add support for AVM Fritzbox 7360 SL

2016-05-07 Thread Sylwek ScApi 

W dniu 2016-05-07 o 09:53, Martin Blumenstingl pisze:

On Sat, May 7, 2016 at 12:40 AM, Sebastian Ortwein  wrote:

Hey

I have tried do get openwrt working on my Fritzbox. Openwrt will start
Network and VDSL Modem is working. But WLAN ist not working. The Chip is
supported bei the ath9k driver. Any hint how I can get Wifi working ?

I see you already got most things working - see my comments inline.


root@OpenWrt:/# dmesg
[0.00] Linux version 4.4.7 (sebastian@sebastian-desktop) (gcc
version 5.3.0 (OpenWrt GCC 5.3.0 r49296) ) #1 Fri May 6 22:23:36 UTC 2016
[0.00] SoC: xRX200 rev 1.1
[0.00] bootconsole [early0] enabled
[0.00] CPU0 revision is: 00019555 (MIPS 34Kc)
[0.00] MIPS: machine is FRITZ7360SL - 1&1 HomeServer
[0.00] Determined physical RAM map:
[0.00]  memory: 0800 @  (usable)
[0.00] Initrd not found or empty - disabling initrd
[0.00] Zone ranges:
[0.00]   Normal   [mem 0x-0x07ff]
[0.00] Movable zone start for each node
[0.00] Early memory node ranges
[0.00]   node   0: [mem 0x-0x07ff]
[0.00] Initmem setup node 0 [mem
0x-0x07ff]
[0.00] On node 0 totalpages: 32768
[0.00] free_area_init_node: node 0, pgdat 804d6390, node_mem_map
81007a80
[0.00]   Normal zone: 256 pages used for memmap
[0.00]   Normal zone: 0 pages reserved
[0.00]   Normal zone: 32768 pages, LIFO batch:7
[0.00] Primary instruction cache 32kB, VIPT, 4-way, linesize 32
bytes.
[0.00] Primary data cache 32kB, 4-way, VIPT, cache aliases, linesize
32 bytes
[0.00] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
[0.00] pcpu-alloc: [0] 0
[0.00] Built 1 zonelists in Zone order, mobility grouping on.  Total
pages: 32512
[0.00] Kernel command line: console=ttyLTQ0,115200 init=/etc/preinit
[0.00] PID hash table entries: 512 (order: -1, 2048 bytes)
[0.00] Dentry cache hash table entries: 16384 (order: 4, 65536
bytes)
[0.00] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
[0.00] Writing ErrCtl register=00064202
[0.00] Readback ErrCtl register=00064202
[0.00] Memory: 123376K/131072K available (3764K kernel code, 164K
rwdata, 1144K rodata, 1184K init, 211K bss, 7696K reserved, 0K cma-reserved)
[0.00] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[0.00] NR_IRQS:256
[0.00] CPU Clock: 500MHz
[0.00] clocksource: MIPS: mask: 0x max_cycles: 0x,
max_idle_ns: 7645041786 ns
[0.12] sched_clock: 32 bits at 250MHz, resolution 4ns, wraps every
8589934590ns
[0.007862] Calibrating delay loop... 332.54 BogoMIPS (lpj=665088)
[0.042318] pid_max: default: 32768 minimum: 301
[0.047171] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[0.053731] Mountpoint-cache hash table entries: 1024 (order: 0, 4096
bytes)
[0.03] clocksource: jiffies: mask: 0x max_cycles:
0x, max_idle_ns: 764504178510 ns
[0.076441] pinctrl core: initialized pinctrl subsystem
[0.082322] NET: Registered protocol family 16
[0.091448] pinctrl-xway 1e100b10.pinmux: Init done
[0.096999] dma-xway 1e104100.dma: Init done - hw rev: 7, ports: 7,
channels: 28
[ 0.206470] dcdc-xrx200 1f106a00.dcdc: Core Voltage : 1016 mV
[ 0.347018] usbcore: registered new interface driver usbfs
[ 0.352523] usbcore: registered new interface driver hub
[ 0.357878] usbcore: registered new device driver usb
[ 0.363254] PCI host bridge to bus :00
[ 0.367244] pci_bus :00: root bus resource [mem 0x1c00-0x1cff]
[ 0.374158] pci_bus :00: root bus resource [io 0x1d80-0x1d8f]
[ 0.381101] pci_bus :00: root bus resource [??? 0x flags 0x0]
[ 0.387957] pci_bus :00: No busn resource found for root bus, will use
[bus 00-ff]
[ 0.395990] pci :00:00.0: [15d1:0011] type 01 class 0x06
[ 0.396028] ifx_pcie_rc_class_early_fixup: fixed pcie host bridge to pci-pci
bridge
[ 0.413669] ifx_pcie_fixup_resource: fixup host controller :00:00.0
(15d1:0011)
[ 0.421261] pci :00:00.0: PME# supported from D0 D3hot
[ 0.421831] pci :01:00.0: [168c:ff1c] type 00 class 0x02

ff1c means that the calibration data was not loaded yet - see
FRITZ3370.dts for example.

Agreed.

[ 0.421921] pci :01:00.0: reg 0x10: [mem 0x-0x 64bit]
[ 0.422076] pci :01:00.0: supports D1
[ 0.422096] pci :01:00.0: PME# supported from D0 D1 D3hot
[ 0.422408] pci_bus :01: busn_res: [bus 01-ff] end is updated to 01
[ 0.422448] pci_bus :00: busn_res: [bus 00-ff] end is updated to 01
[ 0.422506] pci :00:00.0: BAR 8: assigned [mem 0x1c00-0x1c0f]
[ 0.429195] pci :01:00.0: BAR 0: assigned [mem 0x1c00-0x1c00
64bit]
[ 0.436557] pci :00:00.0: PCI bridge to [bus 01]
[

Re: [OpenWrt-Devel] Add support for AVM Fritzbox 7360 SL

2016-05-07 Thread Martin Blumenstingl 
On Sat, May 7, 2016 at 12:40 AM, Sebastian Ortwein  wrote:
> Hey
>
> I have tried do get openwrt working on my Fritzbox. Openwrt will start
> Network and VDSL Modem is working. But WLAN ist not working. The Chip is
> supported bei the ath9k driver. Any hint how I can get Wifi working ?
I see you already got most things working - see my comments inline.

> root@OpenWrt:/# dmesg
> [0.00] Linux version 4.4.7 (sebastian@sebastian-desktop) (gcc
> version 5.3.0 (OpenWrt GCC 5.3.0 r49296) ) #1 Fri May 6 22:23:36 UTC 2016
> [0.00] SoC: xRX200 rev 1.1
> [0.00] bootconsole [early0] enabled
> [0.00] CPU0 revision is: 00019555 (MIPS 34Kc)
> [0.00] MIPS: machine is FRITZ7360SL - 1&1 HomeServer
> [0.00] Determined physical RAM map:
> [0.00]  memory: 0800 @  (usable)
> [0.00] Initrd not found or empty - disabling initrd
> [0.00] Zone ranges:
> [0.00]   Normal   [mem 0x-0x07ff]
> [0.00] Movable zone start for each node
> [0.00] Early memory node ranges
> [0.00]   node   0: [mem 0x-0x07ff]
> [0.00] Initmem setup node 0 [mem
> 0x-0x07ff]
> [0.00] On node 0 totalpages: 32768
> [0.00] free_area_init_node: node 0, pgdat 804d6390, node_mem_map
> 81007a80
> [0.00]   Normal zone: 256 pages used for memmap
> [0.00]   Normal zone: 0 pages reserved
> [0.00]   Normal zone: 32768 pages, LIFO batch:7
> [0.00] Primary instruction cache 32kB, VIPT, 4-way, linesize 32
> bytes.
> [0.00] Primary data cache 32kB, 4-way, VIPT, cache aliases, linesize
> 32 bytes
> [0.00] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
> [0.00] pcpu-alloc: [0] 0
> [0.00] Built 1 zonelists in Zone order, mobility grouping on.  Total
> pages: 32512
> [0.00] Kernel command line: console=ttyLTQ0,115200 init=/etc/preinit
> [0.00] PID hash table entries: 512 (order: -1, 2048 bytes)
> [0.00] Dentry cache hash table entries: 16384 (order: 4, 65536
> bytes)
> [0.00] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
> [0.00] Writing ErrCtl register=00064202
> [0.00] Readback ErrCtl register=00064202
> [0.00] Memory: 123376K/131072K available (3764K kernel code, 164K
> rwdata, 1144K rodata, 1184K init, 211K bss, 7696K reserved, 0K cma-reserved)
> [0.00] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
> [0.00] NR_IRQS:256
> [0.00] CPU Clock: 500MHz
> [0.00] clocksource: MIPS: mask: 0x max_cycles: 0x,
> max_idle_ns: 7645041786 ns
> [0.12] sched_clock: 32 bits at 250MHz, resolution 4ns, wraps every
> 8589934590ns
> [0.007862] Calibrating delay loop... 332.54 BogoMIPS (lpj=665088)
> [0.042318] pid_max: default: 32768 minimum: 301
> [0.047171] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
> [0.053731] Mountpoint-cache hash table entries: 1024 (order: 0, 4096
> bytes)
> [0.03] clocksource: jiffies: mask: 0x max_cycles:
> 0x, max_idle_ns: 764504178510 ns
> [0.076441] pinctrl core: initialized pinctrl subsystem
> [0.082322] NET: Registered protocol family 16
> [0.091448] pinctrl-xway 1e100b10.pinmux: Init done
> [0.096999] dma-xway 1e104100.dma: Init done - hw rev: 7, ports: 7,
> channels: 28
> [ 0.206470] dcdc-xrx200 1f106a00.dcdc: Core Voltage : 1016 mV
> [ 0.347018] usbcore: registered new interface driver usbfs
> [ 0.352523] usbcore: registered new interface driver hub
> [ 0.357878] usbcore: registered new device driver usb
> [ 0.363254] PCI host bridge to bus :00
> [ 0.367244] pci_bus :00: root bus resource [mem 0x1c00-0x1cff]
> [ 0.374158] pci_bus :00: root bus resource [io 0x1d80-0x1d8f]
> [ 0.381101] pci_bus :00: root bus resource [??? 0x flags 0x0]
> [ 0.387957] pci_bus :00: No busn resource found for root bus, will use
> [bus 00-ff]
> [ 0.395990] pci :00:00.0: [15d1:0011] type 01 class 0x06
> [ 0.396028] ifx_pcie_rc_class_early_fixup: fixed pcie host bridge to pci-pci
> bridge
> [ 0.413669] ifx_pcie_fixup_resource: fixup host controller :00:00.0
> (15d1:0011)
> [ 0.421261] pci :00:00.0: PME# supported from D0 D3hot
> [ 0.421831] pci :01:00.0: [168c:ff1c] type 00 class 0x02
ff1c means that the calibration data was not loaded yet - see
FRITZ3370.dts for example.

> [ 0.421921] pci :01:00.0: reg 0x10: [mem 0x-0x 64bit]
> [ 0.422076] pci :01:00.0: supports D1
> [ 0.422096] pci :01:00.0: PME# supported from D0 D1 D3hot
> [ 0.422408] pci_bus :01: busn_res: [bus 01-ff] end is updated to 01
> [ 0.422448] pci_bus :00: busn_res: [bus 00-ff] end is updated to 01
> [ 0.422506] pci :00:00.0: BAR 8: assigned [mem 0x1c00-0x1c0f]
> [ 0.429195] pci :01:00.0: BAR 0:

[OpenWrt-Devel] Add support for AVM Fritzbox 7360 SL

2016-05-06 Thread Sebastian Ortwein 

Hey

I have tried do get openwrt working on my Fritzbox. Openwrt will start 
Network and VDSL Modem is working. But WLAN ist not working. The Chip is 
supported bei the ath9k driver. Any hint how I can get Wifi working ?


The board is based on a Lantiq vr9 soc.

Here are my bootlogs and patches against Openwrt.

root@OpenWrt:/# dmesg
[0.00] Linux version 4.4.7 (sebastian@sebastian-desktop) (gcc 
version 5.3.0 (OpenWrt GCC 5.3.0 r49296) ) #1 Fri May 6 22:23:36 UTC 2016

[0.00] SoC: xRX200 rev 1.1
[0.00] bootconsole [early0] enabled
[0.00] CPU0 revision is: 00019555 (MIPS 34Kc)
[0.00] MIPS: machine is FRITZ7360SL - 1&1 HomeServer
[0.00] Determined physical RAM map:
[0.00]  memory: 0800 @  (usable)
[0.00] Initrd not found or empty - disabling initrd
[0.00] Zone ranges:
[0.00]   Normal   [mem 0x-0x07ff]
[0.00] Movable zone start for each node
[0.00] Early memory node ranges
[0.00]   node   0: [mem 0x-0x07ff]
[0.00] Initmem setup node 0 [mem 
0x-0x07ff]

[0.00] On node 0 totalpages: 32768
[0.00] free_area_init_node: node 0, pgdat 804d6390, node_mem_map 
81007a80

[0.00]   Normal zone: 256 pages used for memmap
[0.00]   Normal zone: 0 pages reserved
[0.00]   Normal zone: 32768 pages, LIFO batch:7
[0.00] Primary instruction cache 32kB, VIPT, 4-way, linesize 32 
bytes.
[0.00] Primary data cache 32kB, 4-way, VIPT, cache aliases, 
linesize 32 bytes

[0.00] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
[0.00] pcpu-alloc: [0] 0
[0.00] Built 1 zonelists in Zone order, mobility grouping on.  
Total pages: 32512

[0.00] Kernel command line: console=ttyLTQ0,115200 init=/etc/preinit
[0.00] PID hash table entries: 512 (order: -1, 2048 bytes)
[0.00] Dentry cache hash table entries: 16384 (order: 4, 65536 
bytes)

[0.00] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
[0.00] Writing ErrCtl register=00064202
[0.00] Readback ErrCtl register=00064202
[0.00] Memory: 123376K/131072K available (3764K kernel code, 
164K rwdata, 1144K rodata, 1184K init, 211K bss, 7696K reserved, 0K 
cma-reserved)

[0.00] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[0.00] NR_IRQS:256
[0.00] CPU Clock: 500MHz
[0.00] clocksource: MIPS: mask: 0x max_cycles: 
0x, max_idle_ns: 7645041786 ns
[0.12] sched_clock: 32 bits at 250MHz, resolution 4ns, wraps 
every 8589934590ns

[0.007862] Calibrating delay loop... 332.54 BogoMIPS (lpj=665088)
[0.042318] pid_max: default: 32768 minimum: 301
[0.047171] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[0.053731] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 
bytes)
[0.03] clocksource: jiffies: mask: 0x max_cycles: 
0x, max_idle_ns: 764504178510 ns

[0.076441] pinctrl core: initialized pinctrl subsystem
[0.082322] NET: Registered protocol family 16
[0.091448] pinctrl-xway 1e100b10.pinmux: Init done
[0.096999] dma-xway 1e104100.dma: Init done - hw rev: 7, ports: 7, 
channels: 28

[0.206470] dcdc-xrx200 1f106a00.dcdc: Core Voltage : 1016 mV
[0.347018] usbcore: registered new interface driver usbfs
[0.352523] usbcore: registered new interface driver hub
[0.357878] usbcore: registered new device driver usb
[0.363254] PCI host bridge to bus :00
[0.367244] pci_bus :00: root bus resource [mem 
0x1c00-0x1cff]

[0.374158] pci_bus :00: root bus resource [io 0x1d80-0x1d8f]
[0.381101] pci_bus :00: root bus resource [??? 0x flags 0x0]
[0.387957] pci_bus :00: No busn resource found for root bus, 
will use [bus 00-ff]

[0.395990] pci :00:00.0: [15d1:0011] type 01 class 0x06
[0.396028] ifx_pcie_rc_class_early_fixup: fixed pcie host bridge to 
pci-pci bridge
[0.413669] ifx_pcie_fixup_resource: fixup host controller 
:00:00.0 (15d1:0011)

[0.421261] pci :00:00.0: PME# supported from D0 D3hot
[0.421831] pci :01:00.0: [168c:ff1c] type 00 class 0x02
[0.421921] pci :01:00.0: reg 0x10: [mem 0x-0x 64bit]
[0.422076] pci :01:00.0: supports D1
[0.422096] pci :01:00.0: PME# supported from D0 D1 D3hot
[0.422408] pci_bus :01: busn_res: [bus 01-ff] end is updated to 01
[0.422448] pci_bus :00: busn_res: [bus 00-ff] end is updated to 01
[0.422506] pci :00:00.0: BAR 8: assigned [mem 0x1c00-0x1c0f]
[0.429195] pci :01:00.0: BAR 0: assigned [mem 
0x1c00-0x1c00 64bit]

[0.436557] pci :00:00.0: PCI bridge to [bus 01]
[0.441574] pci :00:00.0:   bridge window [mem 0x1c00-0x1c0f]
[0.448451] ifx_pcie_bios_map_irq port