Hi Anup,
On Mon, Dec 3, 2018 at 3:44 PM Anup Patel wrote:
>
> On Mon, Dec 3, 2018 at 1:08 PM Bin Meng wrote:
> >
> > Hi Anup,
> >
> > On Mon, Dec 3, 2018 at 3:31 PM Anup Patel wrote:
> > >
> > > On Mon, Dec 3, 2018 at 12:56 PM Bin Meng wrote:
> > > >
> > > > Hi Anup,
> > > >
> > > > On Mon, De
On Mon, Dec 03, 2018 at 12:53:41AM +0100, Alexander Graf wrote:
>
>
> On 05.11.18 10:06, AKASHI Takahiro wrote:
> > "run -e" allows for executing EFI application with a specific "Boot"
> > variable. If no "Boot" is specified or "BootOrder" is specified,
> > it tries to run an EFI applicat
Simon,
On Tue, Nov 27, 2018 at 6:45 AM Simon Goldschmidt
wrote:
>
> On Tue, Nov 27, 2018 at 2:02 AM Simon Glass wrote:
> >
> > Hi Simon,
> >
> > On Sat, 17 Nov 2018 at 05:25, Simon Goldschmidt
> > wrote:
> > >
> > > This series fixes CVE-2018-18440 ("insufficient boundary checks in
> > > filesy
On Mon, Dec 3, 2018 at 1:08 PM Bin Meng wrote:
>
> Hi Anup,
>
> On Mon, Dec 3, 2018 at 3:31 PM Anup Patel wrote:
> >
> > On Mon, Dec 3, 2018 at 12:56 PM Bin Meng wrote:
> > >
> > > Hi Anup,
> > >
> > > On Mon, Dec 3, 2018 at 3:19 PM Anup Patel wrote:
> > > >
> > > > On Mon, Dec 3, 2018 at 12:32
On Mon, Dec 3, 2018 at 8:27 AM Kever Yang wrote:
>
> Hi Tom,
>
> With this merge, my boards can't work correctly in SPL, the console
> output is mess up.
>
> I have test on rk3229 and rk3399 boards, and finally I identify that
> below patch is the root cause:
>
> 6f57c34473 serial: ns16550: fi
On Sun, Dec 2, 2018 at 10:26 PM Alexander Graf wrote:
>
>
>
> On 02.12.18 23:07, Heinrich Schuchardt wrote:
> > On 12/2/18 10:47 PM, Alexander Graf wrote:
> >>
> >>
> >> On 16.07.18 20:06, Heinrich Schuchardt wrote:
> >>> On 06/14/2018 10:46 PM, Guillaume GARDET wrote:
> As used on some distr
Hi Anup,
On Mon, Dec 3, 2018 at 3:31 PM Anup Patel wrote:
>
> On Mon, Dec 3, 2018 at 12:56 PM Bin Meng wrote:
> >
> > Hi Anup,
> >
> > On Mon, Dec 3, 2018 at 3:19 PM Anup Patel wrote:
> > >
> > > On Mon, Dec 3, 2018 at 12:32 PM Bin Meng wrote:
> > > >
> > > > Hi Anup,
> > > >
> > > > On Mon, D
On Mon, Dec 03, 2018 at 12:50:04AM +0100, Alexander Graf wrote:
>
>
> On 05.11.18 10:06, AKASHI Takahiro wrote:
> > The current way how command parameters, particularly "fdt addr," are
> > handled makes it a bit complicated to add a subcommand-specific parameter.
> > So just refactor the code and
On Mon, Dec 3, 2018 at 12:56 PM Bin Meng wrote:
>
> Hi Anup,
>
> On Mon, Dec 3, 2018 at 3:19 PM Anup Patel wrote:
> >
> > On Mon, Dec 3, 2018 at 12:32 PM Bin Meng wrote:
> > >
> > > Hi Anup,
> > >
> > > On Mon, Dec 3, 2018 at 2:43 PM Anup Patel wrote:
> > > >
> > > > On Mon, Dec 3, 2018 at 12:0
Hi Tom,
With this merge, my boards can't work correctly in SPL, the console
output is mess up.
I have test on rk3229 and rk3399 boards, and finally I identify that
below patch is the root cause:
6f57c34473 serial: ns16550: fix debug uart putc called before init
Thanks,
- Kever
On 11/16/201
Hi Anup,
On Mon, Dec 3, 2018 at 3:19 PM Anup Patel wrote:
>
> On Mon, Dec 3, 2018 at 12:32 PM Bin Meng wrote:
> >
> > Hi Anup,
> >
> > On Mon, Dec 3, 2018 at 2:43 PM Anup Patel wrote:
> > >
> > > On Mon, Dec 3, 2018 at 12:06 PM Bin Meng wrote:
> > > >
> > > > Hi Anup,
> > > >
> > > > On Mon, D
On Mon, Dec 3, 2018 at 12:32 PM Bin Meng wrote:
>
> Hi Anup,
>
> On Mon, Dec 3, 2018 at 2:43 PM Anup Patel wrote:
> >
> > On Mon, Dec 3, 2018 at 12:06 PM Bin Meng wrote:
> > >
> > > Hi Anup,
> > >
> > > On Mon, Dec 3, 2018 at 1:28 PM Anup Patel wrote:
> > > >
> > > > When running in S-mode, we
On Mon, Dec 03, 2018 at 12:48:28AM +0100, Alexander Graf wrote:
>
>
> On 05.11.18 10:06, AKASHI Takahiro wrote:
> > "memmap" command prints uefi-specific memory map information.
> > => efi memmap
> > Type StartEnd Attributes
> > ==
Hi Anup,
On Mon, Dec 3, 2018 at 2:43 PM Anup Patel wrote:
>
> On Mon, Dec 3, 2018 at 12:06 PM Bin Meng wrote:
> >
> > Hi Anup,
> >
> > On Mon, Dec 3, 2018 at 1:28 PM Anup Patel wrote:
> > >
> > > When running in S-mode, we can use rdtime and rdtimeh instructions
> > > for reading timer ticks (j
On Mon, Dec 03, 2018 at 12:46:20AM +0100, Alexander Graf wrote:
>
>
> On 05.11.18 10:06, AKASHI Takahiro wrote:
> > "devices" command prints all the uefi variables on the system.
> > => efishell devices
> > Device Name
> >
> > /VenHw(e61d73b9-a384-4acc
On Mon, Dec 3, 2018 at 12:06 PM Bin Meng wrote:
>
> Hi Anup,
>
> On Mon, Dec 3, 2018 at 1:28 PM Anup Patel wrote:
> >
> > When running in S-mode, we can use rdtime and rdtimeh instructions
> > for reading timer ticks (just like Linux). The frequency of timer
> > ticks is passed by prior booting s
On Mon, Dec 03, 2018 at 12:42:43AM +0100, Alexander Graf wrote:
>
>
> On 05.11.18 10:06, AKASHI Takahiro wrote:
> > Currently, there is no easy way to add or modify UEFI variables.
> > In particular, bootmgr supports BootOrder/Boot variables, it is
> > quite hard to define them as u-boot vari
Hi Anup,
On Mon, Dec 3, 2018 at 1:28 PM Anup Patel wrote:
>
> When running in S-mode, we can use rdtime and rdtimeh instructions
> for reading timer ticks (just like Linux). The frequency of timer
> ticks is passed by prior booting stages in "timebase-frequency" DT
> property of the "/cpus" DT no
When running in S-mode, we can use rdtime and rdtimeh instructions
for reading timer ticks (just like Linux). The frequency of timer
ticks is passed by prior booting stages in "timebase-frequency" DT
property of the "/cpus" DT node.
This patch provides a generic timer implementation for U-Boot
run
When u-boot runs in S-mode, the M-mode runtime firmware
(BBL or equivalent) uses memory range in 0x8000 to
0x8020. Due to this, we cannot use 0x8000 as
SYS_TEXT_BASE when running in S-mode. Instead for S-mode,
we use 0x8020 as SYS_TEXT_BASE.
Even Linux RISC-V kernel ignores/reserve
This patch adds S-mode defconfigs for QEMU virt machine so
that we can run u-boot in S-mode on QEMU using M-mode runtime
firmware (BBL or equivalent).
Signed-off-by: Anup Patel
Reviewed-by: Bin Meng
Tested-by: Bin Meng
Reviewed-by: Lukas Auer
---
board/emulation/qemu-riscv/MAINTAINERS | 2 ++
This patch adds kconfig option RISCV_SMODE to run U-Boot in
S-mode. When this opition is enabled we use s CSRs instead
of m CSRs.
It is important to note that there is no equivalent S-mode CSR
for misa and mhartid CSRs so we expect M-mode runtime firmware
(BBL or equivalent) to emulate misa and mh
This patchset allows us runing u-boot in S-mode which is
useful on platforms where M-mode runtime firmware is an
independent firmware and u-boot is used as last stage OS
bootloader.
The patchset based upon git://git.denx.de/u-boot-riscv.git
and is tested on QEMU in both M-mode and S-mode.
For S-m
On 30/11/18 10:41 PM, Andrew F. Davis wrote:
Add a new defconfig file for the AM57xx High Security EVM. This config
is specific for the case of UART/USB booting.
Can you share the steps on how you verified uart boot?
Thanks and regards,
Lokesh
Signed-off-by: Andrew F. Davis
---
MAINTAI
On 30/11/18 10:41 PM, Andrew F. Davis wrote:
Add a new defconfig file for the DRA7xx High Security EVM. This config
is specific for the case of UART/USB booting.
How did you test UART boot on dra7 hs evm? IIRC, UART1 is routed out on the
board. But ROM uses UART3 for loading uart images.
T
The U-Boot eMMC does not need to care about the power for Rockchip
SoC, because if the board is using eMMC, the power will default on
(for bootrom), and we do not do power management for it like kernel,
so the 'vmmc', 'vqmmc' is only useful for SD in U-Boot.
Signed-off-by: Kever Yang
---
arch/a
Hello,
I noticed two issues with Das U-Boot on the Raspberry Pi 3 Model B in
combination with Debian (stretch).
I'm running the Raspberry Pi in arm64 mode.
The boot process is as follows: The Raspberry Pi's firmware loads Das
U-Boot which in turn loads the Linux kernel and initramfs.
The issues
Update email address
Signed-off-by: Jorge Ramirez-Ortiz
---
board/qualcomm/dragonboard820c/MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/board/qualcomm/dragonboard820c/MAINTAINERS
b/board/qualcomm/dragonboard820c/MAINTAINERS
index 56c997e..a157033 100644
--- a/
On Debian Buster with gcc 8.2.0
commit d814ff34a1ffb1e60059c964ad692c5c8fc8564b
$ make mrproper
$ make sandbox_defconfig
$ ./u-boot -D
Error binding driver 'sandbox_tpm': -12
Error binding driver 'serial_sandbox': -12
Some drivers failed to bind
initcall sequence 55af34e45860 failed at call 0
The flash_read function is a wrapper over spi_flash_read, which enables
the env to read multiple flash page size from flash until '\0\0' is read
or the end of env partition is reached. Instead of reading the entire env
size. When it reads '\0\0', it stops reading further the env and assumes
that th
On Mon, Dec 03, 2018 at 12:22:37AM +0100, Alexander Graf wrote:
>
>
> On 05.11.18 10:06, AKASHI Takahiro wrote:
> > With an extra argument, efi_bootmgr_load() can now load an efi binary
> > based on a "Boot" variable specified.
> >
> > Signed-off-by: AKASHI Takahiro
>
> I don't see you cha
Hi Stefan,
On Fri, Nov 30, 2018 at 3:25 PM Stefan Roese wrote:
>
> On 30.11.18 09:14, Aditya Prayoga wrote:
> > Hi Stefan,
> >
> > On Fri, Nov 30, 2018 at 2:44 PM Stefan Roese wrote:
> >>
> >> On 30.11.18 03:54, Aditya Prayoga wrote:
> >>> Similar to Clearfog rev 2.1, GPIO 19 also used to reset
On Sun, Dec 02, 2018 at 11:58:45PM +0100, Alexander Graf wrote:
>
>
> On 27.11.18 01:33, AKASHI Takahiro wrote:
> > The current scenario for default UEFI booting, scan_dev_for_efi, has
> > several issues:
> > * load dtb dynamically even if its loacation (device) is not the same
> > as BOOTEFI_N
Hi All,
I had a faulty board to debug at $dayjob. Part of that involved trying the
latest DDR training code from Marvell. That didn't fix by problem (I
suspect a manufacturing issue with that board).
Since I've done the work anyway I figured I'd send this out. Most of the
delta is code movement a
Hi Stefan,
Gmail seems to have started marking some u-boot email as spam so I
didn't see this earlier.
On Thu, Nov 29, 2018 at 11:35 PM Stefan Roese wrote:
>
> Hi Chris,
>
> On 29.11.18 04:16, Chris Packham wrote:
> > I had a faulty board to debug at $dayjob. Part of that involved trying the
> >
On 05.11.18 10:06, AKASHI Takahiro wrote:
> Those function will be used for integration with 'env' command
> so as to handle uefi variables.
>
> Signed-off-by: AKASHI Takahiro
> ---
> cmd/efishell.c| 4 ++--
> include/command.h | 2 ++
> 2 files changed, 4 insertions(+), 2 deletions(-)
>
On 05.11.18 10:06, AKASHI Takahiro wrote:
> "run -e" allows for executing EFI application with a specific "Boot"
> variable. If no "Boot" is specified or "BootOrder" is specified,
> it tries to run an EFI application specified in the order of "bootOrder."
>
> Signed-off-by: AKASHI Takahi
On 05.11.18 10:06, AKASHI Takahiro wrote:
> The current way how command parameters, particularly "fdt addr," are
> handled makes it a bit complicated to add a subcommand-specific parameter.
> So just refactor the code and extract efi_handle_fdt().
>
> This commit is a preparatory change for enha
On 05.11.18 10:06, AKASHI Takahiro wrote:
> "memmap" command prints uefi-specific memory map information.
> => efi memmap
> Type StartEnd Attributes
> ==
> CONVENTIONAL 4000-7de
On 05.11.18 10:06, AKASHI Takahiro wrote:
> "devices" command prints all the uefi variables on the system.
> => efishell devices
> Device Name
>
> /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)
> /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)/SD(0)/SD(0)
>
On 05.11.18 10:06, AKASHI Takahiro wrote:
> Currently, there is no easy way to add or modify UEFI variables.
> In particular, bootmgr supports BootOrder/Boot variables, it is
> quite hard to define them as u-boot variables because they are represented
> in a complicated and encoded format.
>
On 05.11.18 10:06, AKASHI Takahiro wrote:
> With an extra argument, efi_bootmgr_load() can now load an efi binary
> based on a "Boot" variable specified.
>
> Signed-off-by: AKASHI Takahiro
I don't see you changing the caller, so this hunk won't compile on its own?
Please make sure that ev
On 27.11.18 01:33, AKASHI Takahiro wrote:
> The current scenario for default UEFI booting, scan_dev_for_efi, has
> several issues:
> * load dtb dynamically even if its loacation (device) is not the same
> as BOOTEFI_NAME binary's, (reported by Alex)
> * invoke 'bootmgr' only if BOOTEFI_NAME bin
On 12.10.18 02:55, AKASHI Takahiro wrote:
> On Thu, Oct 11, 2018 at 04:18:33PM +0200, Heinrich Schuchardt wrote:
>> On 10/11/2018 01:11 PM, AKASHI Takahiro wrote:
>>> Currently, image's image_base points to an address where the image was
>>> temporarily uploaded for further loading. Since efi_loa
On 02.12.18 23:33, Otavio Salvador wrote:
> On Sun, Dec 2, 2018 at 8:00 PM Alexander Graf wrote:
>>
>>> The most generic way of having a stable boot behavior is to rely on
>>> UUID instead of device names for root partition, so the order of
>>> probing does not cause issues with booting.
>>>
>>>
On Sun, Dec 2, 2018 at 8:00 PM Alexander Graf wrote:
>
> > The most generic way of having a stable boot behavior is to rely on
> > UUID instead of device names for root partition, so the order of
> > probing does not cause issues with booting.
> >
> > This enables the `CMD_FS_UUID` for following d
On 02.12.18 23:07, Heinrich Schuchardt wrote:
> On 12/2/18 10:47 PM, Alexander Graf wrote:
>>
>>
>> On 16.07.18 20:06, Heinrich Schuchardt wrote:
>>> On 06/14/2018 10:46 PM, Guillaume GARDET wrote:
As used on some distro, such as openSUSE.
Signed-off-by: Guillaume GARDET
Cc:
Hi Fabio,
> [Adding Stefan and Marcel in case they could help reviewing/testing
> this series]
There is also a started thread regarding GTDL:
https://community.nxp.com/thread/490391
On which I'm now also working.
>
> On Sun, Dec 2, 2018 at 6:42 PM Lukasz Majewski wrote:
> >
> > This patch ser
On 12/2/18 10:47 PM, Alexander Graf wrote:
>
>
> On 16.07.18 20:06, Heinrich Schuchardt wrote:
>> On 06/14/2018 10:46 PM, Guillaume GARDET wrote:
>>> As used on some distro, such as openSUSE.
>>> Signed-off-by: Guillaume GARDET
>>>
>>> Cc: Tom Rini
>>> ---
>>> include/config_distro_bootcmd.h |
> Replace various third party lists of Raspberry Pi revision codes in a
> comment with the list on raspberrypi.org.
>
> Signed-off-by: Jonathan Gray
Thanks, applied to rpi-next
Alex
___
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/l
> Add Raspberry Pi 3 Model A+ to list of models, the revision code is 0xE
> according to the list on raspberrypi.org.
>
> Signed-off-by: Jonathan Gray
Thanks, applied to rpi-next
Alex
___
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de
> This patch enables the bmp command (with gzip support enabled) on all
> Raspberry Pi boards.
>
> The value of CONFIG_SYS_VIDEO_LOGO_MAX_SIZE (required by
> CONFIG_VIDEO_BMP_GZIP) is set to match resolution of the "official"
> 7 inch LCD.
>
> Signed-off-by: Adam Heinrich
> Cc: Alexander Graf
> The most generic way of having a stable boot behavior is to rely on
> UUID instead of device names for root partition, so the order of
> probing does not cause issues with booting.
>
> This enables the `CMD_FS_UUID` for following defconfig files:
>
> - rpi_0_w_defconfig
> - rpi_2_defconfig
>
On 04.07.18 09:34, Emmanuel Vadot wrote:
> On Wed, 4 Jul 2018 09:25:16 +0200
> Alexander Graf wrote:
>
>> On 07/04/2018 09:08 AM, Emmanuel Vadot wrote:
>>> When running with special configuration (OF_BOARD and mmc overlay)
>>> RPI have the SD card as id 1.
>>> This make device enumeration fails
On 16.07.18 20:06, Heinrich Schuchardt wrote:
> On 06/14/2018 10:46 PM, Guillaume GARDET wrote:
>> As used on some distro, such as openSUSE.
>> Signed-off-by: Guillaume GARDET
>>
>> Cc: Tom Rini
>> ---
>> include/config_distro_bootcmd.h | 3 ++-
>> 1 file changed, 2 insertions(+), 1 deletion(-
On 29.03.18 06:02, Joe Hershberger wrote:
> Hi Patrick,
>
> On Wed, Mar 28, 2018 at 4:54 PM, Fabio Estevam wrote:
>> Adding Joe in case he has some ideas.
>>
>> On Tue, Mar 27, 2018 at 9:12 AM, Patrick Wildt wrote:
>>> Hi,
>>>
>>> I have been debugging network issues when running an EFI Applic
[Adding Stefan and Marcel in case they could help reviewing/testing this series]
On Sun, Dec 2, 2018 at 6:42 PM Lukasz Majewski wrote:
>
> This patch series provides code to perform read leveling - RDLVL, which
> is adjusting the DQS strobe in relation to the DQ signals so that the
> strobe edge
On 27.03.18 18:05, Heinrich Schuchardt wrote:
> On 03/27/2018 02:24 PM, Patrick Wildt wrote:
>> The PXE object contains a flag that specifies whether or not a DHCP
>> ACK has been received. This can be used by EFI Applications to find
>> out whether or not it is worth to read the DHCP informatio
> The UEFI spec mandates that runtime sections are 64kb aligned to enable
> support for 64kb page size OSs.
>
> This patch ensures that we extend the runtime section to 64kb to be spec
> compliant.
>
> Signed-off-by: Alexander Graf
Thanks, applied to efi-next
Alex
This patch provides the code to calibrate the DDR's
DQS to DQ signals (RDLVL).
It is based on:
VFxxx Controller Reference Manual, Rev. 0, 10/2016, page 1600
10.1.6.16.4.1 "Software Read Leveling in MC Evaluation Mode"
and NXP's community thread:
"Vybrid: About DDR leveling feature on DDRMC."
http
This patch extends the vf610 DDR memory controller code to support SW
leveling.
Signed-off-by: Lukasz Majewski
---
arch/arm/mach-imx/ddrmc-vf610.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/arch/arm/mach-imx/ddrmc-vf610.c b/arch/arm/mach-imx/ddrmc-vf610.c
index ea6a49e0fa..8474
This commit provides extra defines needed for DDR memory controller
calibration (read leveling performing).
Signed-off-by: Lukasz Majewski
---
arch/arm/include/asm/arch-vf610/imx-regs.h | 6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm/include/asm/arch-vf610/imx-regs.h
b/arch/
This patch series provides code to perform read leveling - RDLVL, which
is adjusting the DQS strobe in relation to the DQ signals so that the
strobe edge is centered in the window of valid read data.
The code is based on Vybrid's Reference Manual's:
"VFxxx Controller Reference Manual, Rev. 0, 10/2
attached Patch to check if active menuitem is inside menu
regards Frank
> Gesendet: Samstag, 01. Dezember 2018 um 13:41 Uhr
> Von: "Frank Wunderlich"
> An: "Tom Rini"
> Cc: u-boot@lists.denx.de
> Betreff: Re: [U-Boot] add default-option to bootmenu
>
> thank you
>
> as a small improvement (i'v
Right, i test on bananapi-r2. 2gb ram with 0x8000 base-adress
Seems you need (unsigned) int64 for calculations
Am 2. Dezember 2018 18:14:19 MEZ schrieb Simon Goldschmidt
:
>Am 02.12.2018 um 16:48 schrieb Frank Wunderlich:
>> lmb_init: base: 0x8000, size: 0x8000
>
>Ok, so I don't know
Am 02.12.2018 um 16:48 schrieb Frank Wunderlich:
lmb_init: base: 0x8000, size: 0x8000
Ok, so I don't know your board, is that correct? Do you have 2 GByte
starting at 0x8000?
If so, that would result in an overflow to 0 on a 32-bit platform and
would explain why it doesn't work.
seems like strings breaks my (older 2014-04) uboot:
BPI-IoT> tftp ${loadaddr} 192.168.0.10:files.lst
Using mtk_eth device
TFTP from server 192.168.0.10; our IP address is 192.168.0.11
Filename 'files.lst'.
Load address: 0x8400
Loading: #
43 KiB/s
done
Bytes transferred = 89 (59 hex)
B
> Gesendet: Sonntag, 02. Dezember 2018 um 16:48 Uhr
> Von: "Frank Wunderlich"
> An: "Simon Goldschmidt"
> Betreff: Aw: Re: [U-Boot] [PATCH v4 0/7] Fix CVE-2018-18440 and CVE-2018-18439
>
> lmb_init: base: 0x8000, size: 0x8000
>
> https://github.com/frank-w/u-boot/commit/e0763252a8e135f
Hi Alexander,
Alexander Graf writes:
> On some systems, not all RAM may be usable within U-Boot. Maybe the
> memory maps are incomplete, maybe it's used as workaround for broken
> DMA. But whatever the reason may be, a platform can say that it does
> not wish to have its RAM accessed above a cert
On Sat, Dec 01, 2018 at 01:48:18AM +0100, Philipp Tomsich wrote:
> Hi Tom,
>
> A summary of improvements and fixes is below.
>
> Thanks,
> Philipp.
>
>
> The following changes since commit 6d4a3ff2649faa2cf2739e332557f256cc34831e:
>
> Merge branch 'master' of git://git.denx.de/u-boot-socfpg
On Fri, Nov 30, 2018 at 12:29:18PM -0700, Simon Glass wrote:
> Hi Tom,
>
> See:
>
> https://travis-ci.org/sglass68/u-boot/builds/461837218?utm_medium=notification&utm_source=email
>
>
> The following changes since commit e16c888fab5014b022d5781dc534f204460a073b:
>
> Merge branch '2018-11-28
On Fri, Nov 30, 2018 at 10:50:28PM +0100, Daniel Schwierzeck wrote:
> Hi Tom,
>
> please pull some minor updates for MIPS.
>
> https://travis-ci.org/danielschwierzeck/u-boot/builds/461866534
>
>
> The following changes since commit 6d4a3ff2649faa2cf2739e332557f256cc34831e:
>
> Merge branch
Am 02.12.2018 um 10:33 schrieb Frank Wunderlich:
can you give me an example how to download and display it, seems i only have
tftpboot which runs kernel directly?
also found no strings-command in https://www.denx.de/wiki/DULG/Manual
=> tftp ${loadaddr} 192.168.1.1:list.txt
Speed: 100, full du
i've walked through code and it seems i've found it in cmd/strings.c
strings
display strings
[byte count]
- display strings at for at least [byte count] or first
double NUL
does tftp add the "double NUL" if i do this:
tftp 0x8020 filelist.txt
strings 0x8020
The mtdparts variable might contain partition definitions for several
MTD devices. Each partition layout is separated by a ';', so let's
make sure we don't pick a wrong name when mtdparts is malformed.
Fixes: 5db66b3aee6f ("cmd: mtd: add 'mtd' command")
Signed-off-by: Boris Brezillon
Tested-by: H
MTD partition creation code is a bit tricky. It tries to figure out
when things have changed (either MTD dev list or mtdparts/mtdids vars)
and when that happens it first deletes all the partitions that had been
previously created and then creates the new ones based on the new
mtdparts/mtdids values
SPI flash based MTD devs can be registered/unregistered at any time
through the sf probe command or the spi_flash_free() function.
This commit does not try to fix the root cause as it would probably
require rewriting most of the code and have an mtd_info object
instance per spi_flash object (not t
The DM implementation of spi_flash_free() does not unregister the MTD
device before removing the spi dev object. This leads to a use-after-free
bug when the MTD device is later accessed by a MTD user (observed when
attaching the device to UBI after env_sf_load() has called
spi_flash_free()).
Imple
spi_flash_mtd_register() can be called several times and each time it
will register the same mtd_info instance like if it was a new one.
The MTD ID allocation gets crazy when that happens, so let's track the
status of the sf_mtd_info object to avoid that.
Fixes: 9fe6d8716e09 ("mtd, spi: Add MTD la
strstr() does not guarantee that the string we're searching for is
placed at the beginning. Use strncmp() instead.
Fixes: 5db66b3aee6f ("cmd: mtd: add 'mtd' command")
Signed-off-by: Boris Brezillon
Tested-by: Heiko Schocher
---
Changes in v4:
- Add T-b tag
Changes in v3:
- None
Changes in v2:
The environment is not guaranteed to contain a valid mtdids variable
when called from mtd_search_alternate_name(). Call get_mtdids() instead
of env_get("mtdids").
Fixes: ff4afa8a981e ("mtd: uboot: search for an equivalent MTD name with the
mtdids")
Signed-off-by: Boris Brezillon
Reviewed-by: Miq
The local mtd_name[] variable is limited in size. Return an error if
the name passed in mtdparts does not fit in this local var.
Fixes: 5db66b3aee6f ("cmd: mtd: add 'mtd' command")
Signed-off-by: Boris Brezillon
Tested-by: Heiko Schocher
---
Changes in v4:
- Add T-b tag
Changes in v3:
- None
C
We need to parse mtdparts/mtids again everytime a device has been
added/removed from the MTD list, but there's currently no way to know
when such an update has been done.
Add an ->updated field to the idr struct that we set to true every time
a device is added/removed and expose a function returni
If we don't do that, partitions might still be exposed while the
underlying device is gone.
Fixes: 2a74930da57f ("mtd: mtdpart: implement proper partition handling")
Signed-off-by: Boris Brezillon
Tested-by: Heiko Schocher
---
Changes in v4:
- Test the del_mtd_partitions() ret code and propagate
Updates to the MTD device list should trigger a new parsing of the
mtdids/mtdparts vars even if those vars haven't changed.
Fixes: 5db66b3aee6f ("cmd: mtd: add 'mtd' command")
Signed-off-by: Boris Brezillon
Tested-by: Heiko Schocher
---
Changes in v4:
- Add T-b tag
Changes in v3:
- None
Change
Hello,
This is the 4th version of the mtd / sf fixes patchset. This v4 just
adds a new check in del_mtd_device() (and a debug() when
del_mtd_partitions() fails).
Regards,
Boris
P.S.: travis-ci results =>
https://travis-ci.org/bbrezillon/u-boot/builds/461943011
Boris Brezillon (11):
mtd
can you give me an example how to download and display it, seems i only have
tftpboot which runs kernel directly?
also found no strings-command in https://www.denx.de/wiki/DULG/Manual
Frank
> Gesendet: Montag, 19. November 2018 um 12:29 Uhr
> Von: "Simon Goldschmidt"
> An: "Frank Wunderlich"
Am 01.12.2018 um 12:07 schrieb Frank Wunderlich:
forgot error-message and detailed command:
fatload ${device} ${partition} ${scriptaddr}
${bpi}/${board}/${service}/${bootenv}
** Reading file would overwrite reserved memory **
echo ${device} ${partition} ${scriptaddr} ${bpi}/${board}/${service}/
The BITMAP related operations can now be moved to ./include/linux/bitmap.h
file to mimic the Linux kernel directory tree.
This change also allows removing the lin_gadget_compat.h header file
(which is a legacy code only for composite U-boot layer).
It was also possible to remove #includes from sev
89 matches
Mail list logo
