Hi Ian,
On Thu, Jan 24 2019 at 16:28 +0100, Ian Abbott wrote:
> Back when I was determining how to partition the spi-nor flash on my
> embedded device, I reserved two erase blocks (each of size 65536) for
> use as a barebox state partition. I wasn't using it for anything at the
> time. Now I wa
Mark sparse_seek() as static to avoid -Wmissing-prototypes warnings
Signed-off-by: Andrey Smirnov
---
lib/image-sparse.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lib/image-sparse.c b/lib/image-sparse.c
index 7137d15fd..0c31742ab 100644
--- a/lib/image-sparse.c
+++ b/li
On Thu, Jan 24, 2019 at 12:48 AM Sascha Hauer wrote:
>
> On Tue, Jan 22, 2019 at 05:13:37PM -0800, Andrey Smirnov wrote:
> > On 64-bit platforms /dev/mem exceeds the size supported by loff_t and
> > needs special treatment within the rest of FS API. Specifically
> > lseek() needs to be modified to
On Wed, Jan 23, 2019 at 11:52 PM Sascha Hauer wrote:
>
> On Tue, Jan 22, 2019 at 05:13:36PM -0800, Andrey Smirnov wrote:
> > Calculate new position before validtiy check in lseek() to simplify
> > code a bit as well as make following commit simpler. This should be
> > harmless thing to do, since w
On Wed, Jan 23, 2019 at 11:44 PM Sascha Hauer wrote:
>
> On Tue, Jan 22, 2019 at 05:13:35PM -0800, Andrey Smirnov wrote:
> > On 32-bit systems, cheking for IS_ERR_VALUE(pos) is not
> > correct. Expanding that code we get (loff_t cast is added for clarity):
> >
> > (loff_t)pos >= (unsigned long)-M
I took the new raspi hw rev definitions from
https://www.raspberrypi.org/documentation/hardware/raspberrypi/revision-codes/README.md
and completed rpi_models_old_scheme and rpi_models_new_scheme.
Lookint at the "New-style revision codes in use:" list you can see that
there is a22042 2B (with BCM
Hi,
Back when I was determining how to partition the spi-nor flash on my
embedded device, I reserved two erase blocks (each of size 65536) for
use as a barebox state partition. I wasn't using it for anything at the
time. Now I want to use it to hold bootstate information for barebox
bootcho
Hello.
I successfully use the barebox with custom board based on CC-i.MX51 module.
I am using 30MB UBI volume as initrd for root filesystem. This configuration is
works fine for me.
I decided to change the size of the UBI volume for the root file system to 60
MB.
Now I get a weird OOM error. Tur
On Tue, Jan 22, 2019 at 05:13:37PM -0800, Andrey Smirnov wrote:
> On 64-bit platforms /dev/mem exceeds the size supported by loff_t and
> needs special treatment within the rest of FS API. Specifically
> lseek() needs to be modified to make sure it does the right thing.
>
> Prievious attempt at fi
