On Thu, Jan 03, 2019 at 08:53:18PM +0100, Sam Ravnborg wrote:
> Hi Andreay.
>
> > > > To support bootstrap from SD card run a detect all before
> > > > mounting the SD card.
> > > >
> > > > Signed-off-by: Sam Ravnborg
> > > > ---
> > > > lib/bootstrap/disk.c | 2 ++
> > > > 1 file changed, 2
On Thu, Jan 03, 2019 at 10:00:41PM +0100, Sam Ravnborg wrote:
> Hi Sascha.
>
> Previous mail was written while being disturbed by others - sorry.
>
> > > > Fix lowlevel init to get reset vector.
> > > >
> > > > Add new MACH_AT91SAM9263EK_BOOTSTRAP config entry
> > > > used when building the
On Mon, Dec 31, 2018 at 09:07:23AM +0100, Sam Ravnborg wrote:
> Fix the following warning:
>
> PBLCC arch/arm/boards/at91sam9261ek/pbl-lowlevel_init.o
> arch/arm/boards/at91sam9261ek/lowlevel_init.c:120:26:
> warning: no previous prototype for ‘barebox_arm_reset_vector’
>
On Thu, Jan 3, 2019 at 7:31 AM Roland Hieber wrote:
>
> On Wed, Dec 12, 2018 at 11:03:33PM -0800, Andrey Smirnov wrote:
> > A number of custom error codes used by e1000 driver will be propagated
> > all the way up to generic networking code and will end up being fed to
> > strerror(). As a result
Hi Sascha!
I have some good news and some bad news.
First the good news.
Barebox was used for Day 18 of QEMU 2018 advent
(https://www.qemu-advent-calendar.org/2018/).
Here is a quote:
> This is an image for QEMU's emulated Canon A1100 Arm machine:
> Play 2048 in the Barebox firmware
Hi Sascha.
Previous mail was written while being disturbed by others - sorry.
> > > Fix lowlevel init to get reset vector.
> > >
> > > Add new MACH_AT91SAM9263EK_BOOTSTRAP config entry
> > > used when building the bootstrap variant.
> > > The new config entry is required as we cannot combine
Hi Andreay.
> > > To support bootstrap from SD card run a detect all before
> > > mounting the SD card.
> > >
> > > Signed-off-by: Sam Ravnborg
> > > ---
> > > lib/bootstrap/disk.c | 2 ++
> > > 1 file changed, 2 insertions(+)
> > >
> > > diff --git a/lib/bootstrap/disk.c b/lib/bootstrap/disk.c
On Wed, Dec 12, 2018 at 11:03:33PM -0800, Andrey Smirnov wrote:
> A number of custom error codes used by e1000 driver will be propagated
> all the way up to generic networking code and will end up being fed to
> strerror(). As a result of that, some of the current error codes will
> result in not
Hi Sascha,
thanks a lot!
There's two things I noticed when reviewing the patches:
The commit message of 47866ba5 is a bit misleading since poison.h is no longer
being added in the commit.
861ce6d looks a bit weird, I guess that's a typo (ACTION_SORT | ACTION_SORT).
- Florian
Am Donnerstag,
On Thu, Jan 03, 2019 at 10:22:21AM +0100, Lukasz Madej wrote:
> Access priviledges for AIPS3 bridge have been configured so peripherals
> connected to it (like SDMA, SAI etc.) can work properly.
>
> Signed-off-by: Lukasz Madej
> ---
> arch/arm/mach-imx/imx7.c | 9 +
> 1 file changed, 9
Hi Antony,
On Tue, Dec 18, 2018 at 10:19:33AM +0300, Antony Pavlov wrote:
> This patchseries adds initial RISC-V architecture support for barebox.
>
It's very nice to get RISC-V support for barebox.
The code looks fine from a first glance. I would prefer using multi
image support from the
On Sun, Dec 30, 2018 at 03:18:23AM +0100, Roland Hieber wrote:
> Now that we are moving away from boilerplate code towards SPDX license
> tags in individual file headers, we should have a short note about what
> these tags mean. Also, until now, there was effectively no explicit
> information that
On Thu, Dec 20, 2018 at 12:54:08PM +, Scherer, Thorsten wrote:
> Hallo Sascha,
>
> On Mon, 2018-12-17 at 12:31 +0100, Sascha Hauer wrote:
> > On Mon, Dec 17, 2018 at 02:18:52PM +0300, Antony Pavlov wrote:
> > > On Thu, 13 Dec 2018 07:33:56 +0100
> > > "Thorsten K. Scherer" wrote:
> > >
> >
On Wed, Dec 19, 2018 at 03:07:03PM +0100, Stefan Riedmueller wrote:
> Commit 19a32c0f6bf0 ("nvmem: ocotp: Add support for second mac address
> fuses on imx6ul") added support for correctly reading the second MAC
> address from fuses of the i.MX 6UL/ULL but not for writing. So also fit
> writing of
Hi Florian,
On Wed, Dec 19, 2018 at 02:02:03PM +, Baeuerle, Florian wrote:
> Add a flag to sort directory entries before recursing into them.
>
> Since this part of lib/ is used inside barebox as well as in
> scripts/bareboxenv.c, we cannot easily use stringlists from lib/, which
> would
Hi Sascha.
> > Fix lowlevel init to get reset vector.
> >
> > Add new MACH_AT91SAM9263EK_BOOTSTRAP config entry
> > used when building the bootstrap variant.
> > The new config entry is required as we cannot combine MULTI_IMAGE
> > with a bootstrap variant.
>
> Why can't that be combined?
The
On Sat, Dec 22, 2018 at 09:50:10AM +0100, Oleksij Rempel wrote:
> Signed-off-by: Oleksij Rempel
> ---
Applied, thanks
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str.
On Sat, Dec 22, 2018 at 11:00:46AM +0100, Oleksij Rempel wrote:
> Am 22.12.18 um 10:56 schrieb Sam Ravnborg:
> > Hi Oleksij
> >
> >> i can't build MIPS images after this patch:
> >>
> >> commit 3abeee3e45224c73245e32cb614c241cd195f1c4 (bb/master)
> >> Author: Sascha Hauer
> >> Date: Mon Dec 17
On Mon, Dec 24, 2018 at 09:24:56AM +0300, Alexander Shiyan wrote:
> This patch revises the bits for register MC13892_POWER_MISC.
> - Added definition for one missing bit (0).
> - Changed the name for bit 21 for accordance with the datasheet.
> - Updated affected board that uses these
On Mon, Dec 24, 2018 at 10:16:42AM +, Alexander Kurz wrote:
> From: Alexander Kurz
>
> Limits for the number of clusters were used to determine the FAT fs type.
> This fails e.g. for FAT32 fs with low cluster number that can be found
> in certain Android images.
> Sync the FAT fs type
On Tue, Dec 25, 2018 at 09:59:22AM +0300, Alexander Shiyan wrote:
> If the partition size is too small for imx_bbu_nand_update(),
> this can lead to an infinite loop in the imx_bbu_firmware_fcb_start_page()
> function, because imx_bbu_firmware_max_blocks() returns zero.
> Fix this by place
Access priviledges for AIPS3 bridge have been configured so peripherals
connected to it (like SDMA, SAI etc.) can work properly.
Signed-off-by: Lukasz Madej
---
arch/arm/mach-imx/imx7.c | 9 +
1 file changed, 9 insertions(+)
diff --git a/arch/arm/mach-imx/imx7.c
On Thu, Dec 27, 2018 at 04:57:14PM -0200, Fabio Estevam wrote:
> Passing the full path of the referenced files make the text
> clearer.
>
> Signed-off-by: Fabio Estevam
> ---
> Documentation/boards/imx/nxp-imx8mq-evk.rst | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
Applied,
Hi Masahiro,
On Tue, Jan 01, 2019 at 06:13:06PM +0900, Masahiro Yamada wrote:
> Hi Sam,
>
> On Mon, Dec 31, 2018 at 3:12 PM Sam Ravnborg wrote:
> >
> > Hi Masahiro
> >
> > Thanks for taking your time to sync kconfig up with the kernel, very
> > appreciated!
> >
> > I left a few comments to
On Mon, Dec 31, 2018 at 09:07:22AM +0100, Sam Ravnborg wrote:
> piggy.o would be build for every time barebox was built
> This had the sideeffect that the image(s) would
> always be rebuilt despite no changes
>
> Fix this by adding piggy.o to targets
> and avoid an extra command in the rule to
On Wed, Jan 02, 2019 at 02:35:48PM +0100, Ahmad Fatoum wrote:
> The bootN-partitions binding is barebox-specific, so it shouldn't
> be fixed up into the kernel device tree.
>
> Suggested-by: Sascha Hauer
> Signed-off-by: Ahmad Fatoum
> ---
> drivers/mci/mci-core.c | 7 ++-
> 1 file
Hi Sam,
On Wed, Jan 02, 2019 at 09:26:11PM +0100, Sam Ravnborg wrote:
> Fix lowlevel init to get reset vector.
>
> Add new MACH_AT91SAM9263EK_BOOTSTRAP config entry
> used when building the bootstrap variant.
> The new config entry is required as we cannot combine MULTI_IMAGE
> with a bootstrap
27 matches
Mail list logo
