> On 19 Jul 2018, at 19:52, Mathias Kresin wrote:
>
> 2018-07-19 19:26 GMT+02:00 Thibaut VARÈNE :
>> faf94d926e2810f895f2a98d4a49ee2fe8f673e8 added "support" for a hacked
>> device where the original boot loader (routerboot) has been replaced
>> by u-boot.
>>
>> Support for this device with
2018-07-19 19:12 GMT+02:00 Thibaut VARÈNE :
> This patch improves faf64056ddd46992a75b1e277d94541c7251035c by setting
> the correct partition scheme for the RouterBoot section of the flash.
>
> This section is subdivided in several segments, as they are on ar71xx
> RB devices, albeit with
> On 19 Jul 2018, at 19:46, Mathias Kresin wrote:
>
>
> To get the dt compiler accepting the overlapping partitions without a
> warning, a style was chosen completely different from all other dts
> files in the target [maintenance reason]. Furthermore, nodes sharing
> the same reg are usually
2018-07-19 19:12 GMT+02:00 Thibaut VARÈNE :
> This patch improves 5684d087418d176cfdef4e045e1950ca7ba3b09f by setting
> the correct partition scheme for the RouterBoot section of the flash.
>
> This section is subdivided in several segments, as they are on ar71xx
> RB devices, albeit with
> On 19 Jul 2018, at 19:46, Mathias Kresin wrote:
>
>
> To get the dt compiler accepting the overlapping partitions without a
> warning, a style was chosen completely different from all other dts
> files in the target [maintenance reason]. Furthermore, nodes sharing
> the same reg are usually
2018-07-19 19:26 GMT+02:00 Thibaut VARÈNE :
> faf94d926e2810f895f2a98d4a49ee2fe8f673e8 added "support" for a hacked
> device where the original boot loader (routerboot) has been replaced
> by u-boot.
>
> Support for this device with stock bootloader is possible (as evidenced
> by support for the
[resending properly formatted]
Detailed rationale:
• This code should never have been accepted: it should certainly not be part of
a release and if it accidentally was part of one that should not be reason to
continue what is IMO a mistake.
• This code does not support the stock hardware.
•
faf94d926e2810f895f2a98d4a49ee2fe8f673e8 added "support" for a hacked
device where the original boot loader (routerboot) has been replaced
by u-boot.
Support for this device with stock bootloader is possible (as evidenced
by support for the RBM33G), and conflicts with this code.
Remove code
This patch improves 5684d087418d176cfdef4e045e1950ca7ba3b09f by setting
the correct partition scheme for the RouterBoot section of the flash.
This section is subdivided in several segments, as they are on ar71xx
RB devices, albeit with different offsets and sizes. The naming convention
from
This series fix the DTS files of the MikroTik RouterBOARD M11G and M33G. The
changes are similar in both patches:
- The model name string is updated to match the hardware-stored (in flash)
string that we cannot (yet?) extract at runtime.
- The partition scheme is updated to reflect areas
This patch improves faf64056ddd46992a75b1e277d94541c7251035c by setting
the correct partition scheme for the RouterBoot section of the flash.
This section is subdivided in several segments, as they are on ar71xx
RB devices, albeit with different offsets and sizes. The naming convention
from
The first block(s) of the ubi mtd device might be bad. We need to take
care on our own to skip the bad block(s) and read the next one(s).
Don't treat recoverable read errors as fatal and check for the UBI magic
if the data of a block could be recovered using ECC or similar.
Signed-off-by:
The early return on failed open of the mtd device allows to get rid of
one level of indentation.
Move the put_mtd_device() called on multiple error conditions to a goto
label to use it later for more error conditions.
While at it, make clear that we only check for the UBI magic if the read
from
With a10a204aab26cc ("kernel: make ubi auto-attach check for a tar file
magic") the check for the magic was added without considering a failing
mtd_read(). If the read fails, no check is done and the mount code is
called straight away.
Failing with an error message for such cases seems to me the
All these devices share the exact same image format.
Signed-off-by: Thibaut VARÈNE
---
target/linux/ramips/image/mt7621.mk | 20 +---
1 file changed, 9 insertions(+), 11 deletions(-)
diff --git a/target/linux/ramips/image/mt7621.mk
b/target/linux/ramips/image/mt7621.mk
index
Detailed rationale:
• This code should never have been accepted: it should certainly not be part of
a release and if it accidentally was part of one that should absolutely not be
reason to continue what is IMO a mistake.
• This code does not support the stock hardware
• This code is a
Hi,
On 2018-07-19 08:49, Jo-Philipp Wich wrote:
Hi again,
As a workaround, run the following command once within the IB/SDK directory:
sed -i -e 's,/\(usr\|lib\|etc\)/,/###/,g' ./staging_dir/host/lib/libc.so.6
Executing the above command solves the problem on my system (Manjaro -
similar
Hi again,
As a workaround, run the following command once within the IB/SDK directory:
sed -i -e 's,/\(usr\|lib\|etc\)/,/###/,g' ./staging_dir/host/lib/libc.so.6
This will prevent the bundled glibc from trying to dlopen() libraries on
the host system which is the root cause of the assertion.
Hi,
works for me on Debian 9 und Ubuntu 18. I've got reports that it is
broken on Arch which I am currently trying to install but it seems to be
a pain
~ Jo
signature.asc
Description: OpenPGP digital signature
___
openwrt-devel mailing list
19 matches
Mail list logo
