| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Buffalo WCR-1166DS uses trx-fomatted firmware and the custom magic
number (0x5C436F74, "\Cot") is required for OpenWrt installation from
OEM WebUI.
But the current mtdsplit_trx doesn't support the custom magic number and
fail to parse and split to kernel and rootfs when the factory image is
flashed. Then, the kernel fails to mount rootfs automatically and panics.
Before the commit fddc78bc116bc043fb5cd92dbc45cfd054c21af8, mtdsplit_trx
was patched in ramips target and the device-specific magic number was
supported only for WCR-1166DS[1].
But the patch was not inherited to the later version of the kernel and
deleted by the above commit, then, the custom magic number support was
broken.
[1]: https://github.com/openwrt/openwrt/blob/05d6e92594c507dcd1f4be6c1bcb2282fe1abe1f/target/linux/ramips/patches-4.4/0400-mtd-mtdsplit-add-support-for-custom-trx-magic-for-Buffalo-WCR-1166DS.patch#L27
log (factory image):
[ 1.165312] spi-mt7621 10000b00.spi: sys_freq: 193333333
[ 1.195782] spi-nor spi0.0: w25q128 (16384 Kbytes)
[ 1.205353] 7 fixed-partitions partitions found on MTD device spi0.0
[ 1.217938] Creating 7 MTD partitions on "spi0.0":
[ 1.227436] 0x000000000000-0x000000030000 : "u-boot"
[ 1.238427] 0x000000030000-0x000000040000 : "u-boot-env"
[ 1.250123] 0x000000040000-0x000000050000 : "factory"
[ 1.261306] 0x000000050000-0x000000810000 : "firmware"
[ 1.282051] 0x000000810000-0x000000fd0000 : "firmware2"
[ 1.293594] 0x000000fd0000-0x000000fe0000 : "glbcfg"
[ 1.304719] 0x000000fe0000-0x000000ff0000 : "board_data"
...
[ 1.452424] /dev/root: Can't open blockdev
[ 1.460619] VFS: Cannot open root device "(null)" or unknown-block(0,0): error -6
[ 1.475434] Please append a correct "root=" boot option; here are the available partitions:
[ 1.491986] 1f00 192 mtdblock0
[ 1.491989] (driver?)
[ 1.504938] 1f01 64 mtdblock1
[ 1.504941] (driver?)
[ 1.517885] 1f02 64 mtdblock2
[ 1.517888] (driver?)
[ 1.530831] 1f03 7936 mtdblock3
[ 1.530834] (driver?)
[ 1.543777] 1f04 7936 mtdblock4
[ 1.543781] (driver?)
[ 1.556724] 1f05 64 mtdblock5
[ 1.556727] (driver?)
[ 1.569672] 1f06 64 mtdblock6
[ 1.569675] (driver?)
[ 1.582617] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[ 1.598976] Rebooting in 1 seconds..
This patch fixes this issue by using parser_trx with specifying custom
magic number in dts instead of mtdsplit_trx.
log (fixed factory image):
[ 1.202044] spi-mt7621 10000b00.spi: sys_freq: 193333333
[ 1.225369] spi-nor spi0.0: w25q128 (16384 Kbytes)
[ 1.235015] 7 fixed-partitions partitions found on MTD device spi0.0
[ 1.247603] Creating 7 MTD partitions on "spi0.0":
[ 1.257106] 0x000000000000-0x000000030000 : "u-boot"
[ 1.269447] 0x000000030000-0x000000040000 : "u-boot-env"
[ 1.281192] 0x000000040000-0x000000050000 : "factory"
[ 1.294208] 0x000000050000-0x000000810000 : "firmware"
[ 1.305774] 2 trx partitions found on MTD device firmware
[ 1.316540] Creating 2 MTD partitions on "firmware":
[ 1.326399] 0x00000000001c-0x000000214754 : "linux"
[ 1.336063] mtd: partition "linux" doesn't start on an erase/write block boundary -- force read-only
[ 1.357070] 0x000000214754-0x0000007c0000 : "rootfs"
[ 1.366994] mtd: partition "rootfs" doesn't start on an erase/write block boundary -- force read-only
[ 1.386368] mtd: device 5 (rootfs) set to be root filesystem
[ 1.398700] 1 squashfs-split partitions found on MTD device rootfs
[ 1.411027] 0x000000520000-0x0000007c0000 : "rootfs_data"
[ 1.422841] 0x000000810000-0x000000fd0000 : "firmware2"
[ 1.436282] 0x000000fd0000-0x000000fe0000 : "glbcfg"
[ 1.447408] 0x000000fe0000-0x000000ff0000 : "board_data"
...
[ 1.611216] VFS: Mounted root (squashfs filesystem) readonly on device 31:5.
Signed-off-by: INAGAKI Hiroshi <musashino.open@gmail.com>
|
|
|
|
|
|
|
| |
Use higher frequency than current and up the speed to access to the
flash on WCR-1166DS.
Signed-off-by: INAGAKI Hiroshi <musashino.open@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The mt76x8 subtarget is the only one in ramips that stores the
mediatek,mtd-eeprom property directly in the "root" mt7628an.dtsi.
This is not optimal for a few different reasons:
* If you don't really know it or are used to other (sub)targets,
the property will be set somewhat magically.
* The property is set based on &factory partition before (if at all)
this partition is defined.
* There are several devices that have different offset or even
different partitions to read from, which will then be overwritten
in the DTS files. Thus, definitions are scattered between root
DTSI and individual files.
Based on these circumstances, the "root" definition is removed and
the property is added to the device-based DTS(I) files where needed
and applicable. This should be easier to grasp for unexperienced
developers and will move the property closer to the partition
definitions.
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Like in the previous patch for ath79 target, this will remove the
"devicename" from LED labels in ramips as well.
The devicename is removed in DTS files and 01_leds, consolidation
of definitions into DTSI files is done where (easily) possible,
and migration scripts are updated.
For the latter, all existing definitions were actually just
devicename migrations anyway. Therefore, those are removed and
a common migration file is created in target base-files. This is
actually another example of how the devicename removal makes things
easier.
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The "/dts-v1/;" identifier is supposed to be present once at the
top of a device tree file after the includes have been processed.
In ramips, we therefore requested to have in the DTS files so far,
and omit it in the DTSI files. However, essentially the syntax of
the parent mtxxxx/rtxxxx DTSI files already determines the DTS
version, so putting it into the DTS files is just a useless repetition.
Consequently, this patch puts the dts-v1 statement into the top-level
SoC-based DTSI files, and removes all other occurences.
Since the dts-v1 statement needs to be before any other definitions,
this also moves the includes accordingly where necessary.
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In DTS Checklist[1] we're now demanding proper generic node names, as
the name of a node should reflect the function of the device and use
generic name for that[2]. Everybody seems to be copy&pasting from DTS
files available in the repository today, so let's unify that naming
there as well and provide proper examples.
While at it, remove unused m25p80 label.
Tested on rt5350 (for spi-nor) and rt3662 (for cfi-flash).
1. https://openwrt.org/submitting-patches#dts_checklist
2. https://github.com/devicetree-org/devicetree-specification/blob/master/source/devicetree-basics.rst#generic-names-recommendation
Signed-off-by: Sungbo Eo <mans0n@gorani.run>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Upstream pinctrl driver in drivers/staging uses
groups/function/ralink,num-gpios instead of
ralink,group/ralink,function/ralink,nr-gpio
Replace these properties in dts as well as the pinctrl driver in
patches-4.14.
This commit is created using:
sed -i 's/ralink,group/groups/g'
sed -i 's/ralink,function/function/g'
sed -i 's/ralink,nr-gpio/ralink,num-gpios/g'
Signed-off-by: Chuanhong Guo <gch981213@gmail.com>
|
|
|
|
|
|
|
|
|
|
| |
upstream driver merged 3 separated gpio banks into one gpio node.
and gpioX Y in our local driver should be replaced with gpio X*32+Y.
This patch is created using the following sed command:
sed -i -r 's/(.*)gpio([0-9]) ([0-9]+)(.*)/echo "\1gpio $((\2*32+\3))\4"/ge'
Signed-off-by: Chuanhong Guo <gch981213@gmail.com>
|
|
|
|
|
|
|
|
|
| |
The node pinctrl0 is already set up in the SOC DTSI files, but
defined again as member of pinctrl in most of the device DTS(I)
files. This patch removes this redundancy for the entire ramips
target.
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
|
|
|
|
|
|
|
|
|
|
|
| |
This converts all remaining devices to use interrupt-driven
gpio-keys compatible instead of gpio-keys-polled.
The poll-interval is removed.
While at it, add/remove newlines in keys and leds node where
necessary.
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
|
|
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
|