Welcome! Log In Create A New Profile

Advanced

Linux Kernel 5.13.6 Kirkwood package and Debian rootfs

Posted by bodhi 
Re: Linux Kernel 4.0 (FDT) and 3.16 (non-FDT) Kirkwood package and rootfs
May 06, 2015 03:36PM
gryle Wrote:
-------------------------------------------------------
> Hi bodhi,
>
> Would it be possible to include qmi_wwan as a
> module in your next kernel compilations?
> I need it to be able to use my LTE USB stick as an
> ethernet device, using the libqmi-utils package.
>
> Thank you

Sure. Will do.

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: Linux Kernel 4.0 (FDT) and 3.16 (non-FDT) Kirkwood package and rootfs
May 07, 2015 01:53AM
LeggoMyEggo Wrote:
-------------------------------------------------------
> Maybe it's time to start a new Debian for Kirkwood
> thread in general. This is now 34 pages of packed
> information.

Yes :) Please create a new Debian thread to start any subject discussion that is relevant, but not specific to this kernel.

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: Linux Kernel 4.0 (FDT) and 3.16 (non-FDT) Kirkwood package and rootfs
May 08, 2015 06:01PM
bodhi Wrote:
> Yes :) Please create a new Debian thread to start
> any subject discussion that is relevant, but not
> specific to this kernel.

Could you maybe split the current thread to before dtb / after dtb? The cut off might be a problem to determine I realize as there are probably lots of cross kernel posts intermittently situated. But that would make the most sense to me.
Re: Linux Kernel 4.0 (FDT) and 3.16 (non-FDT) Kirkwood package and rootfs
May 08, 2015 06:29PM
LeggoMyEggo Wrote:
-------------------------------------------------------
> bodhi Wrote:
> > Yes :) Please create a new Debian thread to
> start
> > any subject discussion that is relevant, but
> not
> > specific to this kernel.
>
> Could you maybe split the current thread to before
> dtb / after dtb? The cut off might be a problem
> to determine I realize as there are probably lots
> of cross kernel posts intermittently situated.
> But that would make the most sense to me.

I think that's perhaps not the good cutoff, because all the issues are common to both versions. I think we should just leave this thread as is, and be more aware of the need to start new thread.

-bodhi
===========================
Forum Wiki
bodhi's corner
Hi bodhi,

Your work is very interesting.

I installed your kernel (linux-4.0.0-kirkwood-tld-2-bodhi.tar.bz2) into my Stora (MS2110).
But, MPP assign seems wrong.

I revised DTS file.
It works fine on my Stora.

I hope your merge.



Edited 1 time(s). Last edit at 05/22/2015 10:01AM by Hiro.AK47.
Attachments:
open | download - kirkwood-netgear_stora_ms2000.dts (4.2 KB)
Re: Linux Kernel 4.0 Kirkwood (FDT) and 3.16 Kirkwood (non-FDT) package and rootfs
May 22, 2015 03:38PM
@Hiro.AK47,

Thanks for letting me know! Will take a look and merge it.

-bodhi
===========================
Forum Wiki
bodhi's corner
IMHO
That would not clutter the file /etc/rc.local does not need infoy
and to simplify follow-up support
Change the contents of the file

/etc/rc.local

**********************************
#!/bin/sh

if [ -d /etc/startup_nas.d/ ]; then
for file in /etc/startup_nas.d/*; do
if [ -x $file ]; then
. $file
fi
done
fi

***********************************

content :
---------------------------------------------------------------------------------------------------------
if [ -d /sys/class/leds/dockstar:green:health ]; then
echo default-on > /sys/class/leds/dockstar:green:health/trigger
echo none > /sys/class/leds/dockstar:orange:misc/trigger
fi
----------------------------------------------------------------------------------------------------------

to move not executable file /etc/startup_nas.d/dockstar

content :
------------------------------------------------------------------------------------------------
if [ -d /sys/class/leds/nsa325:green:sys ]; then
echo default-on > /sys/class/leds/nsa325:green:sys/trigger
echo none > /sys/class/leds/nsa325:orange:sys/trigger
fi

if [ -d /sys/class/leds/nsa325:green:sata1 ]; then
echo ide-disk1 > /sys/class/leds/nsa325:green:sata1/trigger
fi

if [ -d /sys/class/leds/nsa325:green:sata2 ]; then
echo ide-disk2 > /sys/class/leds/nsa325:green:sata2/trigger
fi

if [ -d /sys/class/leds/nsa325:green:usb ]; then
echo usb-host > /sys/class/leds/nsa325\:green\:usb/trigger
fi
------------------------------------------------------------------------------------------------------

to move not executable file /etc/startup_nas.d/nas325

and so on for other devices.

by analogy with the command

cat dts/kirkwood-dockstar.dtb >> zImage.fdt

run command for your device :

chmod +x /etc/startup_nas.d/dockstar

Owners of other devices can offer their own versions settings.
Re: Linux Kernel 4.0 Kirkwood (FDT) and 3.16 Kirkwood (non-FDT) package and rootfs
May 27, 2015 03:34PM
balbes150,

Good suggestion! I actually did something similar to this in all my boxes. But I thought I would leave it up to individual installation whether and how they want to do that. Yours is one of the good methods.

-bodhi
===========================
Forum Wiki
bodhi's corner
Please help to check my uboot env setting
June 07, 2015 09:00PM
I downloaded Debian-3.18.5-kirkwood-tld-1-rootfs-bodhi.tar.bz2
followed the instructions to install it on a USB HD formated in ext4.

my uboot env on pogo_e02 (uboot ver: U-Boot 2014.07-tld-1 (Jul 18 2014 - 00:29:52)):
arcNumber=3542
baudrate=115200
bootcmd=run bootcmd_usb; run bootcmd_mmc; run bootcmd_sata; reset
bootcmd_mmc=run mmc_init; run set_bootargs_mmc; run mmc_boot
bootcmd_sata=run sata_init; run set_bootargs_sata; run sata_boot;
bootcmd_usb=run usb_init; run set_bootargs_usb; run usb_boot;
bootdelay=10
console=ttyS0,115200
device=0:1
ethact=egiga0
ethaddr=00:25:31:00:A6:8F
if_netconsole=ping $serverip
ipaddr=192.168.1.18
led_error=orange blinking
led_exit=green off
led_init=green blinking
load_dtb=ext4load usb 0:1 0x1c00000 /boot/dts/kirkwood-pogo_e02.dtb
load_initrd=ext4load usb 0:1 0x1100000 /boot/uInitrd
load_uimage=ext4load usb 0:1 0x800000 /boot/uImage
machid=dd6
mainlineLinux=yes
mmc_boot=mw 0x800000 0 1; run mmc_load_uimage; if run mmc_load_uinitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
mmc_init=mmc rescan
mmc_load_uimage=ext2load mmc $device 0x800000 /boot/uImage
mmc_load_uinitrd=ext2load mmc $device 0x1100000 /boot/uInitrd
mmc_root=/dev/mmcblk0p1
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
partition=nand0,2
preboot_nc=run if_netconsole start_netconsole
rootdelay=10
rootfstype=ext4
sata_boot=mw 0x800000 0 1; run sata_load_uimage; if run sata_load_uinitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
sata_init=ide reset
sata_load_uimage=ext2load ide $device 0x800000 /boot/uImage
sata_load_uinitrd=ext2load ide $device 0x1100000 /boot/uInitrd
sata_root=/dev/sda1
serverip=192.168.1.15
set_bootargs_mmc=setenv bootargs console=$console root=$mmc_root rootdelay=$rootdelay rootfstype=$rootfstype $mtdparts
set_bootargs_sata=setenv bootargs console=$console root=$sata_root rootdelay=$rootdelay rootfstype=$rootfstype $mtdparts
set_bootargs_usb=setenv bootargs console=$console root=$usb_root rootdelay=$rootdelay rootfstype=$rootfstype $mtdparts
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
stderr=serial
stdin=serial
stdout=serial
usb_boot=run load_dtb; run load_uimage; if run load_initrd; then bootm 0x800000 0x1100000 0x1c00000; else bootm 0x800000 - 0x1c00000; fi
usb_init=usb start
usb_load_uimage=ext4load usb 0:1 0x800000 /boot/uImage
usb_load_uinitrd=ext4load usb 0:1 0x1100000 /boot/uInitrd
usb_root=LABEL=rootfs

after power on, booting stopped with these messages:
[    3.234420] Waiting 10 sec before mounting root device...
[   13.240867] VFS: Cannot open root device "sda1" or unknown-block(0,0): error -6
[   13.248212] Please append a correct "root=" boot option; here are the available partitions:
[   13.256658] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

I have tried two other USB thumb drivers and got the same error. I also checked md5 of download rootfs. here is what I did:
sudo su
cd /media/rootfs
tar -xjf /path/to/Debian-3.18.5-kirkwood-tld-1-rootfs-bodhi.tar.bz2
cd boot
cp -a zImage-3.18.5-kirkwood-tld-1  zImage.fdt
cat dts/kirkwood-pogo_e02.dtb  >> zImage.fdt
mv uImage uImage.orig
mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-3.18.5-kirkwood-tld-1 -d zImage.fdt uImage
mkimage -A arm -O linux -T ramdisk -C gzip -a 0x00000000 -e 0x00000000 -n initramfs-3.18.5-kirkwood-tld-1 -d initrd.img-3.18.5-kirkwood-tld-1 uInitrd
sync

What's wrong? why it keeps looking for sda1, not usb drive?
Re: Please help to check my uboot env setting
June 07, 2015 09:28PM
zzbao,

sda1 is what assigned to the USB drive. So that's is always what the kernel looking for to mount rootfs.

A couple things that are possibly wrong:

1. Did you label the USB rootfs as rootfs?

2. Also, this is not right, since you have append the DTB to uImage. This is for booting with a separate DTB:
usb_boot=run load_dtb; run load_uimage; if run load_initrd; then bootm 0x800000 0x1100000 0x1c00000; else bootm 0x800000 - 0x1c00000; fi

In any case, the serial boot log will tell what went wrong at what point. Please post the entire serial console boot log.

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: Please help to check my uboot env setting
June 08, 2015 08:02PM
bodhi Wrote:

> 2. Also, this is not right, since you have append the DTB to uImage. This is for booting with a separate DTB:
>
> usb_boot=run load_dtb; run load_uimage; if run
> load_initrd; then bootm 0x800000 0x1100000
> 0x1c00000; else bootm 0x800000 - 0x1c00000; fi
>

change this to
setenv usb_boot 'mw 0x800000 0 1; run usb_load_uimage; if run usb_load_uinitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi'

it works very well after that. Thank you very much.



Edited 1 time(s). Last edit at 06/08/2015 08:03PM by zzbao.
Hey bodhi,

I have put 3.18.5 on nsa320. Everything looks fine, but the hwmon_nsa3x0 module is missing in this bundle.
Is this module available for download?

many thanks.
Re: Linux Kernel 4.0 Kirkwood (FDT) and 3.16 Kirkwood (non-FDT) package and rootfs
June 10, 2015 12:03AM
leo,

Kernel 4.0 has the module. Do you need to stay with 3.18 or can you update to linux-4.0.0-kirkwood-tld-2 ?

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: Linux Kernel 4.0 Kirkwood (FDT) and 3.16 Kirkwood (non-FDT) package and rootfs
June 10, 2015 08:50AM
Hi,

the nsa3xx-hwmon is included in linux-4.0.0-kirkwood-tld-2, but the problem is, with the kirkwood-nas320.dts description,

the GPIO's for the holtek mcu microprocessor which controls the fan and temperature sensor in the NSA320 are no longer exposed to the outside driver world, i.e mcu_data, mcu_clk, mcu_act

        /* The following pins are currently not assigned to a driver,
           some of them should be configured as inputs.
        pinctrl-0 = <&pmx_mcu_data &pmx_mcu_clk &pmx_mcu_act
                     &pmx_htp &pmx_vid_b1
                     &pmx_power_resume_data &pmx_power_resume_clk>; */

whereas in nsa320-setup.c from NSA-320 Setup, by AA666 and also
in bodhis patch for 3.14 these structs are found together with a kirkwood_init
function for nsa320_hwmon,

static struct nsa3xx_hwmon_platform_data nsa320_hwmon_data = {
        /* GPIOs connected to Holtek HT46R065 MCU */
        .act_pin  = 17,
        .clk_pin  = 16,
        .data_pin = 14,
};

static struct platform_device nsa320_hwmon = {
        .name           = "nsa3xx-hwmon",
        .id             = -1,
        .num_resources  = 0,
        .dev            = {
                .platform_data  = &nsa320_hwmon_data,
        },

        kirkwood_init();
.......
        platform_device_register(&nsa320_hwmon);

the linux devs who made the transition from nsa320-setup.c where everything was contained
in the pre dts time simply looked if there is a driver requesting it, as the nsa3xx-hwmon never got upstream,
the GPIO's were not included, but it should be relatively easy to add this, if I have some time, maybe
I'll give it a try,

best wishes pbg4



Edited 2 time(s). Last edit at 06/10/2015 09:04AM by pbg4.
hello bodhi,

thank you for reply. I would rather stay with 3.18 for now (too much to learn ab. upates:)

regards,
Re: Linux Kernel 4.0 Kirkwood (FDT) and 3.16 Kirkwood (non-FDT) package and rootfs
June 10, 2015 02:04PM
leo Wrote:
-------------------------------------------------------
> hello bodhi,
>
> thank you for reply. I would rather stay with 3.18
> for now (too much to learn ab. upates:)
>
> regards,

In that case, I will upload the module and you can modprobe it.

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: Linux Kernel 4.0 Kirkwood (FDT) and 3.16 Kirkwood (non-FDT) package and rootfs
June 10, 2015 02:08PM
pbg4,


> the linux devs who made the transition from
> nsa320-setup.c where everything was contained
> in the pre dts time simply looked if there is a
> driver requesting it, as the nsa3xx-hwmon never
> got upstream,
> the GPIO's were not included, but it should be
> relatively easy to add this, if I have some time,
> maybe
> I'll give it a try,

I don't have the NSA320 so did not notice this difference. Please do correct the DTS if you have time!

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: Linux Kernel 4.0 Kirkwood (FDT) and 3.16 Kirkwood (non-FDT) package and rootfs
June 10, 2015 04:05PM
Hi bodhi,

a quick comparison of kirkwood-nsa320.dts and the more complete kirkwood-nsa325.dts revealed
already most of the differences which have to be adapted for the nsa320 in the dts file, because
both devices have many design similarities,

as you own a nsa325, is the nsa3xx-hwmon included in linux-4.0.0-kirkwood-tld-2driver working for you properly with the
nsa325 ??,.. than it should be relatively easy to generate a patch for kirkwood-nsa320.dts to get this
working also,..

best wishes pbg4
Re: Linux Kernel 4.0 Kirkwood (FDT) and 3.16 Kirkwood (non-FDT) package and rootfs
June 11, 2015 12:03AM
pbg4,

> as you own a nsa325, is the nsa3xx-hwmon included
> in linux-4.0.0-kirkwood-tld-2driver working for
> you properly with the
> nsa325 ??

The NSA325 does not use nsaxx-hwmon module. The sensors are controlled automatically in hardware (e.g. we can't control fan speed). To read the sensors output, we have to use i2c. Hence, I can't verify the hwnmon for other nsaxx boxes after I built the kernel. I'll need others who has this box to verify it. There are quite a few users who have this box, but perhaps they don't use and pay attention to sensors.

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: Linux Kernel 4.0 Kirkwood (FDT) and 3.16 Kirkwood (non-FDT) package and rootfs
June 11, 2015 05:18AM
@leo,

Here is the hwmon module. Extract this ko file and put this in:

/lib/modules/3.18.5-kirkwood-tld-1/kernel/drivers/hwmon

Try to modprobe this and see if you can use it. According to pbg4 above, it lacks some GPIOs so we need to fix the DTS so it will provide full functionality. However, just the module itself might be useful for you to confirm that it is running OK. Once we have the new DTS updated, a new DTB for NSA320 will be uploaded and that will hopefully restore this capabilty like it it was in kernel 3.16.x.

-bodhi
===========================
Forum Wiki
bodhi's corner
Attachments:
open | download - nsa3xx-hwmon.ko.tar.gz (3.3 KB)
Hello bodhi,

thank you for your time.
Unfortunately the module does not load. Here is the verbose output:

root@zyxel:/lib/modules/3.18.5-kirkwood-tld-1/kernel/drivers/hwmon# modprobe -vvv ./nsa3xx-hwmon.ko && lsmod               
modprobe: INFO: ../libkmod/libkmod.c:354 kmod_set_log_fn() custom logging function 0xb6f38acc registered
modprobe: DEBUG: ../libkmod/libkmod-index.c:790 index_mm_open() file=/lib/modules/3.18.5-kirkwood-tld-1/modules.dep.bin
modprobe: DEBUG: ../libkmod/libkmod-index.c:790 index_mm_open() file=/lib/modules/3.18.5-kirkwood-tld-1/modules.alias.bin
modprobe: DEBUG: ../libkmod/libkmod-index.c:790 index_mm_open() file=/lib/modules/3.18.5-kirkwood-tld-1/modules.symbols.bin
modprobe: DEBUG: ../libkmod/libkmod-index.c:790 index_mm_open() file=/lib/modules/3.18.5-kirkwood-tld-1/modules.builtin.bin
modprobe: DEBUG: ../libkmod/libkmod-module.c:540 kmod_module_new_from_lookup() input alias=./nsa3xx-hwmon.ko, normalized=./nsa3xx_hwmon.ko
modprobe: DEBUG: ../libkmod/libkmod-module.c:546 kmod_module_new_from_lookup() lookup modules.dep ./nsa3xx_hwmon.ko
modprobe: DEBUG: ../libkmod/libkmod.c:545 kmod_search_moddep() use mmaped index 'modules.dep' modname=./nsa3xx_hwmon.ko
modprobe: DEBUG: ../libkmod/libkmod-module.c:550 kmod_module_new_from_lookup() lookup modules.symbols ./nsa3xx_hwmon.ko
modprobe: DEBUG: ../libkmod/libkmod-module.c:554 kmod_module_new_from_lookup() lookup install and remove commands ./nsa3xx_hwmon.ko
modprobe: DEBUG: ../libkmod/libkmod-module.c:558 kmod_module_new_from_lookup() lookup modules.aliases ./nsa3xx_hwmon.ko
modprobe: DEBUG: ../libkmod/libkmod.c:424 kmod_lookup_alias_from_alias_bin() use mmaped index 'modules.alias' for name=./nsa3xx_hwmon.ko
modprobe: DEBUG: ../libkmod/libkmod-module.c:562 kmod_module_new_from_lookup() lookup modules.builtin ./nsa3xx_hwmon.ko
modprobe: DEBUG: ../libkmod/libkmod.c:495 kmod_lookup_alias_from_builtin_file() use mmaped index 'modules.builtin' modname=./nsa3xx_hwmon.ko
modprobe: DEBUG: ../libkmod/libkmod-module.c:567 kmod_module_new_from_lookup() lookup ./nsa3xx_hwmon.ko=0, list=(nil)
modprobe: DEBUG: lookup failed - trying to check if it's builtin
modprobe: DEBUG: ../libkmod/libkmod.c:392 kmod_pool_get_module() get module name='' found=(nil)
modprobe: DEBUG: ../libkmod/libkmod.c:400 kmod_pool_add_module() add 0xb8b645a0 key=''
modprobe: DEBUG: ../libkmod/libkmod-module.c:1726 kmod_module_get_initstate() could not open '/sys/module//initstate': No such file or directory
modprobe: DEBUG: ../libkmod/libkmod-module.c:452 kmod_module_unref() kmod_module 0xb8b645a0 released
modprobe: DEBUG: ../libkmod/libkmod.c:408 kmod_pool_del_module() del 0xb8b645a0 key=''
builtin ./nsa3xx-hwmon.ko
modprobe: INFO: ../libkmod/libkmod.c:321 kmod_unref() context 0xb8b63118 released

Module                  Size  Used by
nls_utf8                1053  1 
nls_cp437               4703  1 
vfat                    8412  1 
fat                    48843  1 vfat
ipv6                  301542  50 
md_mod                102466  0 
evdev                   9363  0 
fixed                   2289  0 
orion_wdt               5721  0 
hmac                    2437  0 
mv_cesa                10625  0 
gpio_keys               7576  0 
uio_pdrv_genirq         2857  0 
uio                     6877  1 uio_pdrv_genirq
ext2                   56729  1 
sg                     21795  0 
sd_mod                 33052  8 
uas                    12649  0 
usb_storage            40262  3 uas
sata_mv                25912  3 
libata                149941  1 sata_mv
scsi_mod              170665  5 sg,uas,usb_storage,libata,sd_mod
root@zyxel:/lib/modules/3.18.5-kirkwood-tld-1/kernel/drivers/hwmon#

Thanks & Regards,
Re: Linux Kernel 4.0 Kirkwood (FDT) and 3.16 Kirkwood (non-FDT) package and rootfs
June 11, 2015 11:49PM
@leo,

Sorry this is possibly the kernel headers mistmatched, since the module was from kernel 4.0. The solution is either:

- I have to compile this module in kernel 3.18.5 for you. Or,
- You need to install kernel 4.0

I'm away from my development environment, so I can't do that until at least a couple weeks form now.

I think you should upgrade to kernel 4.0.0-kirwood-tld-2. If you're worry about messing up your current rootfs:

- Use a new USB stick, download the 3.18.5 tarball, extract it to the USB stick and boot with it. Then upgrade the kernel on it. See if you can go through this upgrade successfully. And then repeat it on your current rootfs.

-bodhi
===========================
Forum Wiki
bodhi's corner
hi bodhi,

that sounds reasonable. will do like you say.

Thanks&regards,
Re: Linux Kernel 4.0 Kirkwood (FDT) and 3.16 Kirkwood (non-FDT) package and rootfs
June 15, 2015 03:51PM
hi bodhi

Can you add some option in your next kernel please ?

This :
SPI-NOR device support (under Memory Technology Device (MTD) support)
and then
Support most SPI Flash chips (AT26DF, M25P, W25X, ...) (in Self-contained MTD device drivers)

it's needed by one my NAS.

Thanks.
Re: Linux Kernel 4.0 Kirkwood (FDT) and 3.16 Kirkwood (non-FDT) package and rootfs
June 16, 2015 12:22AM
Val532,

Sure, I'll add it to kernel 4.1.

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: Linux Kernel 4.0 Kirkwood (FDT) and 3.16 Kirkwood (non-FDT) package and rootfs
June 22, 2015 01:48PM
Hi bodhi,

on kernel.org linux kernel 4.1 was finally released today, a first look at the relevant sources
for the dvb-usb-dw2102 kernel module and Integration of various usb dvb-s2 adapters revealed
that most of the changes of Olli Salonen for that driver got upstream,..
so the tt-s2-4600 is supported from now on!!,...

but a small patch is still needed - instead of my big patch included in your kernel now - mostly
concerning secure and fast locking of tt-s2-4600 on dvb-s2-transponders with the latest changes from
Olli Salonen's git, in the next days I am going to prepare a clean patch and send it to you for integration
into your next 4.1 kernel,

best wishes pbg4



Edited 1 time(s). Last edit at 06/22/2015 02:32PM by pbg4.
Re: Linux Kernel 4.0 Kirkwood (FDT) and 3.16 Kirkwood (non-FDT) package and rootfs
June 22, 2015 02:52PM
@pbg4,

> but a small patch is still needed - instead of my
> big patch included in your kernel now - mostly
> concerning secure and fast locking of tt-s2-4600
> on dvb-s2-transponders with the latest changes
> from
> Olli Salonen's git, in the next days I am going to
> prepare a clean patch and send it to you for
> integration
> into your next 4.1 kernel,
>

That would be great!

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: Linux Kernel 4.0 Kirkwood (FDT) and 3.16 Kirkwood (non-FDT) package and rootfs
June 27, 2015 02:28PM
Hi bodhi,

I just send the patch for linux-4.1 for dvb-usb-dw2102 to you per pm, please have a look,
as stated before it is rather small, because most of the changes are upstream and contained in linux 4.1,..

it would also be a good idea to put the newest frontend firmware for m88ds3103 into your next rootfs,
in /lib/firmware, it is also attached in the pm, md5sum should be b31080dd205ce1659ed7aedf2b153e03 for
the firmware dvb-demod-m88ds3103.fw,

best wishes pbg4
Re: Linux Kernel 4.0 Kirkwood (FDT) and 3.16 Kirkwood (non-FDT) package and rootfs
June 27, 2015 06:00PM
pbg4,

Got it.

> it would also be a good idea to put the newest
> frontend firmware for m88ds3103 into your next
> rootfs,
> in /lib/firmware, it is also attached in the pm,
> md5sum should be b31080dd205ce1659ed7aedf2b153e03
> for
> the firmware dvb-demod-m88ds3103.fw,

Good idea! this also reminded me that I should add the Iogear BT 4.0 firmware to the rootfs, too.

Thanks!

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: Linux Kernel 4.0 Kirkwood (FDT) and 3.16 Kirkwood (non-FDT) package and rootfs
June 29, 2015 03:01AM
@Hiro.AK47,

> I revised DTS file.
> It works fine on my Stora.

I've reviewed your version of the DTS. Everything looks good to me, including the trigger name changes (I think the trigger names are now consistent with the other Kirkwood trigger naming convention).

One thing that stands out and needs to be confirmed. The reset button was 37 in the orginal non-FDT setup code (kernel 3.16 and earlier). Are you sure the reset button is 38?
ocp@f1000000 {
		pinctrl: pin-controller@10000 {
			pmx_button_power: pmx-button-power {
				marvell,pins = "mpp36";
				marvell,function = "gpio";
			};

			pmx_button_reset: pmx-button-reset {
				marvell,pins = "mpp38"; /* should be 37 ? */
				marvell,function = "gpio";

-bodhi
===========================
Forum Wiki
bodhi's corner
Sorry, you can't reply to this topic. It has been closed.