On Fri, Apr 12, 2019 at 03:51:52PM -0600, Simon Glass wrote:
> Hi Tom,
>
> Build result at https://travis-ci.org/sglass68/u-boot/builds/519059521
>
>
> The following changes since commit 02f173ca156cee8526dff87603d5e446b443cde3:
>
> Merge branch 'master' of git://git.denx.de/u-boot-usb
On Fri, Apr 12, 2019 at 10:32:24PM +0200, Daniel Schwierzeck wrote:
> Hi Tom,
>
> please pull MIPS updates for 2019.07
>
> https://travis-ci.org/danielschwierzeck/u-boot/builds/519324026
>
>
> The following changes since commit 02f173ca156cee8526dff87603d5e446b443cde3:
>
> Merge branch
On Sat, Apr 13, 2019 at 11:50 PM Pierre Bourdon wrote:
>
> ROOT_ITEMs in btrfs are referenced without knowing their actual "offset"
> value. To perform these searches using only two items from the key, the
> btrfs driver uses a special "btrfs_search_tree_key_type" function.
>
> The algorithm used
ROOT_ITEMs in btrfs are referenced without knowing their actual "offset"
value. To perform these searches using only two items from the key, the
btrfs driver uses a special "btrfs_search_tree_key_type" function.
The algorithm used by that function to transform a 3-tuple search into a
2-tuple
On 11/04/2019 13:09, Anatolij Gustschin wrote:
Hi Anatolij,
thanks for the heads up!
> On Tue, 9 Apr 2019 23:05:11 +0200
> Anatolij Gustschin ag...@denx.de wrote:
> ...
>>> drivers/video/vidconsole-uclass.c | 37
>>> +
>>> 1 file changed, 37 insertions(+)
Hi Fabio,
Le 13/04/2019 à 18:31, Fabio Estevam a écrit :
Hi Pierre-Jean,
On Sat, Apr 13, 2019 at 11:38 AM Pierre-Jean Texier
wrote:
-int board_usb_phy_mode(int port)
-{
- return USB_INIT_DEVICE;
-}
-
It seems that #include can also be removed now.
I still see uart related code in
On Sat, Apr 13, 2019 at 1:31 PM Fabio Estevam wrote:
> It seems that #include can also be removed now.
>
> I still see uart related code in the warp7.c board file.
>
> Can they also be removed?
>
> Could #define CONFIG_MXC_UART_BASE UART1_IPS_BASE_ADDR be removed from
> include/configs/warp7.h?
Hi Pierre-Jean,
On Sat, Apr 13, 2019 at 11:38 AM Pierre-Jean Texier
wrote:
>
> -int board_usb_phy_mode(int port)
> -{
> - return USB_INIT_DEVICE;
> -}
> -
It seems that #include can also be removed now.
I still see uart related code in the warp7.c board file.
Can they also be removed?
I updated my local git source tree, but now I get this error
with stock Lamobo_R1_defconfig and w/o any changes to .config:
arm-linux-gnueabihf-ld.bfd: u-boot-spl section `.rodata' will not fit in
region `.sram'
arm-linux-gnueabihf-ld.bfd: region `.sram' overflowed by 1176 bytes
This commit switches to DM USB and SERIAL for warp7 and warp7_bl33 defconfigs.
Signed-off-by: Pierre-Jean Texier
Signed-off-by: Joris Offouga
---
arch/arm/dts/imx7s-warp.dts | 5 +
board/warp7/warp7.c | 5 -
configs/warp7_bl33_defconfig | 2 ++
configs/warp7_defconfig |
On Fri, Apr 12, 2019 at 4:42 PM Stefan Roese wrote:
> Testing has shown that the current DM implementation of a platform /
> board specific translation offset, as its needed for the SPL on MVEBU
> platforms is buggy. The translation offset is confingured too late,
> after the driver bind
On Thu, Apr 11, 2019 at 11:26 AM Stefan Roese wrote:
> With the new DM enabled MMC driver (thanks again), we should probably
> better select DM_MMC in arch/arm/Kconfig for ARCH_MVEBU. This way, all
> those boards will get moved to the new driver version.
>
> What do you think?
I've only tested
On Fri, Apr 12, 2019 at 12:52:16PM +0200, Marek Vasut wrote:
> On 4/12/19 12:51 PM, Alex Kiernan wrote:
> > Migrate support for disable MUSB bulk split/combine to Kconfig
> >
> > Green Travis build:
> >
> > https://travis-ci.org/akiernan/u-boot/builds/519101867
> >
> > Signed-off-by: Alex
On Fri, Apr 12, 2019 at 12:08:14PM +0530, Keerthy wrote:
> The series adds the support for hardware leveling. This needs the
> kernel to be patched with hardware leveling support and the
> kernel support is already in linux-next:
>
>
On Fri, Apr 12, 2019 at 07:08:40PM +1200, Chris Packham wrote:
> On Thu, 11 Apr 2019, 10:33 PM Stefan Roese, wrote:
>
> > We have run now multiple times into size issues with the openrd
> > board port. To finally fix this, this patch now moves the U-Boot size
> > from 0x6. to 0x8.,
as a final(?) example of one of my originally Linux kernel-related
Kbuild cleanup scripts, i have one that identifies Makefile entries
that refer to Kbuild options that are not defined in any Kconfig file
(IIRC, they might be defined manually in a defconfig file, i'll have
to refresh my memory,
On Sat, 13 Apr 2019, Chris Packham wrote:
> Robert points out that we have code selecting CRC32 but nothing that
> actually defines this config option. Similarly image.h #defines
> CONFIG_CRC32 but nothing tests for it.
... snip ...
thanks for all that effort ... my script can *find* stuff
There is no check for CONFIG_CRC32 so the #define in image.h does
nothing. Remove it.
Reported-by: Robert P. J. Day
Signed-off-by: Chris Packham
---
include/image.h | 1 -
1 file changed, 1 deletion(-)
diff --git a/include/image.h b/include/image.h
index 765ffecee0a7..6b2661ed0bd6 100644
---
There are no longer any references to this in the code so this can be
removed.
Signed-off-by: Chris Packham
---
scripts/config_whitelist.txt | 1 -
1 file changed, 1 deletion(-)
diff --git a/scripts/config_whitelist.txt b/scripts/config_whitelist.txt
index 48622b12bb64..634bb8d53b57 100644
There is no 'config CRC32' remove the select that was attempting to use
it.
Reported-by: Robert P. J. Day
Signed-off-by: Chris Packham
---
drivers/mtd/ubi/Kconfig | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/mtd/ubi/Kconfig b/drivers/mtd/ubi/Kconfig
index
There is no 'config CRC32', remove the select that was attempting to use
it.
Reported-by: Robert P. J. Day
Signed-off-by: Chris Packham
---
cmd/Kconfig | 2 --
1 file changed, 2 deletions(-)
diff --git a/cmd/Kconfig b/cmd/Kconfig
index 2bdbfcb3d091..71a7f1cc83c5 100644
--- a/cmd/Kconfig
+++
Robert points out that we have code selecting CRC32 but nothing that
actually defines this config option. Similarly image.h #defines
CONFIG_CRC32 but nothing tests for it.
lib/Makefile has had obj-y += crc32.o for some time. I can't find any
evidence that u-boot ever had CONFIG_CRC32.
I suspect
On Sat, Apr 13, 2019 at 8:43 AM Robert P. J. Day wrote:
>
>
> rather than go to the trouble of whipping up a wiki page, i can
> present this in a short post to the list. here's the list of what my
> script identified as "badref selects" -- those identifiers for which
> there is a Kconfig line
CONFIG_GPIO does not exist. There is one hit for it in tegra_gpio.c but
it is a variable name.
Signed-off-by: Chris Packham
---
scripts/config_whitelist.txt | 1 -
1 file changed, 1 deletion(-)
diff --git a/scripts/config_whitelist.txt b/scripts/config_whitelist.txt
index
CONFIG_GPIO does not exist. sysreset_gpio.c uses the DM gpio APIs so the
correct option to select is DM_GPIO.
Reported-by: Robert P. J. Day
Signed-off-by: Chris Packham
---
drivers/sysreset/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/sysreset/Kconfig
Switch to the driver model for USB on the db-88f6281-bp board.
CONFIG_BLK can't be enabled yet because mvebu_mmc.c needs converting.
Signed-off-by: Chris Packham
Reviewed-by: Stefan Roese
---
In my original patch series having this separate made sense as this
wouldn't be possible without the
Correct CPU_ARM926EJS1 to CPU_ARM926EJS.
Reported-by: Robert P. J. Day
Signed-off-by: Chris Packham
---
arch/arm/mach-imx/mx2/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/mach-imx/mx2/Kconfig b/arch/arm/mach-imx/mx2/Kconfig
index
This is Marvell's Kirkwood development board. It has the following
features
- 512M DDR2
- 2 PCI connectors
- 1 x1 PCI-e interface
- 1 Gigabit Ethernet Port
- 2 SATA Ports
- USB 2.0 Interface
- SDIO
- 128M NAND Flash
- 16M SPI Flash
It can be strapped to boot from SPI or NAND so there
28 matches
Mail list logo
