Hi Marek,
On 1 September 2018 at 16:45, Marek Vasut wrote:
>
> On 09/01/2018 11:50 PM, Simon Glass wrote:
> > Hi Marek,
> >
> > On 30 August 2018 at 07:42, Marek Vasut wrote:
> >> On 08/30/2018 03:32 PM, Bin Meng wrote:
> >>> Hi Marek,
> >>>
> >>> On Thu, Aug 30, 2018 at 1:07 AM Marek Vasut
Hi,
On 1 September 2018 at 16:41, Marek Vasut wrote:
> On 09/01/2018 11:45 PM, Simon Glass wrote:
>> Hi Marek,
>>
>> On 30 August 2018 at 04:20, Marek Vasut wrote:
>>> On 08/30/2018 02:29 AM, Simon Glass wrote:
Hi Marek,
>>>
>>> Hi,
>>>
On 24 August 2018 at 12:27, Marek Vasut wrote:
Hi Marek,
On 1 September 2018 at 16:43, Marek Vasut wrote:
> On 09/01/2018 11:45 PM, Simon Glass wrote:
>> Hi Marek,
>>
>> On 30 August 2018 at 03:25, Marek Vasut wrote:
>>>
>>> On 08/30/2018 02:29 AM, Simon Glass wrote:
Hi Marek,
>>>
>>> Hi,
>>>
>>> [...]
>>>
>> If you have both EHCI
On 09/01/2018 11:45 PM, Simon Glass wrote:
> Hi Marek,
>
> On 30 August 2018 at 03:25, Marek Vasut wrote:
>>
>> On 08/30/2018 02:29 AM, Simon Glass wrote:
>>> Hi Marek,
>>
>> Hi,
>>
>> [...]
>>
> If you have both EHCI and a xHCI controller which can occupy the same
> BFD, then how would
On 09/01/2018 11:50 PM, Simon Glass wrote:
> Hi Marek,
>
> On 30 August 2018 at 07:42, Marek Vasut wrote:
>> On 08/30/2018 03:32 PM, Bin Meng wrote:
>>> Hi Marek,
>>>
>>> On Thu, Aug 30, 2018 at 1:07 AM Marek Vasut wrote:
On 08/29/2018 05:15 PM, Bin Meng wrote:
> +Simon
>
On 09/01/2018 11:45 PM, Simon Glass wrote:
> Hi Marek,
>
> On 30 August 2018 at 04:20, Marek Vasut wrote:
>> On 08/30/2018 02:29 AM, Simon Glass wrote:
>>> Hi Marek,
>>
>> Hi,
>>
>>> On 24 August 2018 at 12:27, Marek Vasut wrote:
Reword the documentation to make it clear the compatible
Hi Marek,
On 30 August 2018 at 07:42, Marek Vasut wrote:
> On 08/30/2018 03:32 PM, Bin Meng wrote:
>> Hi Marek,
>>
>> On Thu, Aug 30, 2018 at 1:07 AM Marek Vasut wrote:
>>>
>>> On 08/29/2018 05:15 PM, Bin Meng wrote:
+Simon
Hi Marek,
On Wed, Aug 29, 2018 at 10:22 PM
Hi,
On 30 August 2018 at 23:22, Jagdish Gediya wrote:
> Hi,
>
>> -Original Message-
>> From: s...@google.com On Behalf Of Simon Glass
>> Sent: Thursday, August 30, 2018 8:21 AM
>> To: Jagdish Gediya
>> Cc: U-Boot Mailing List ; Prabhakar Kushwaha
>> ; York Sun ; Poonam
>> Aggrwal ; Bin
Hi Marek,
On 30 August 2018 at 04:20, Marek Vasut wrote:
> On 08/30/2018 02:29 AM, Simon Glass wrote:
>> Hi Marek,
>
> Hi,
>
>> On 24 August 2018 at 12:27, Marek Vasut wrote:
>>> Reword the documentation to make it clear the compatible string is now
>>> optional, yet still matching on it takes
Hi Marek,
On 30 August 2018 at 03:25, Marek Vasut wrote:
>
> On 08/30/2018 02:29 AM, Simon Glass wrote:
> > Hi Marek,
>
> Hi,
>
> [...]
>
> >>> If you have both EHCI and a xHCI controller which can occupy the same
> >>> BFD, then how would you supply in the DT options needed by the
> >>>
From: Fabio Estevam
Add an entry for mx7dsabresd_qspi_defconfig to avoid the following
warnings:
WARNING: no status info for 'mx7dsabresd_qspi'
WARNING: no maintainers for 'mx7dsabresd_qspi'
Reported-by: Tom Rini
Signed-off-by: Fabio Estevam
---
board/freescale/mx7dsabresd/MAINTAINERS | 1 +
On Fri, Aug 31, 2018 at 03:04:31PM +0200, Stefano Babic wrote:
> Hi Tom,
>
> please pull from u-boot-imx, thanks !
>
> The following changes since commit 11ed312896c5f5814064c5d45dcb2f53dc121437:
>
> configs: am57xx: change default board name to beagle_x15 (2018-08-26
> 12:26:16 -0400)
>
>
Hi there,
On Tue, Aug 28, 2018 at 08:42:01AM +0200, Eugeniu Rosca wrote:
> Hi Bin,
>
> cc: Masahiro, Andrey
>
> On Tue, Aug 28, 2018 at 10:05:51AM +0800, Bin Meng wrote:
> > Hi Eugeniu,
> >
> > On Mon, Aug 27, 2018 at 7:19 AM Eugeniu Rosca
> > wrote:
> > >
> > > Fix the following UBSAN
On 31.08.18 20:45, Mark Kettenis wrote:
>> From: Heinrich Schuchardt
>> Date: Fri, 31 Aug 2018 19:37:25 +0200
>>
>> On 06/14/2018 12:41 AM, Mark Kettenis wrote:
>>> If desired (and possible) switch into HYP mode or non-secure SVC mode
>>> before calling the entry point of an EFI application.
On 01.09.18 11:43, Alexander Graf wrote:
>
>
> On 31.08.18 21:31, Heinrich Schuchardt wrote:
>> This patch provides a define to initialize a table that maps lower to
>> capital letters for Unicode code point 0x - 0x.
>>
>> Signed-off-by: Heinrich Schuchardt
>> ---
>> v2
>> add
On 31.08.18 21:31, Heinrich Schuchardt wrote:
> Provide unit tests for utf_to_lower() utf_to_upper().
>
> Signed-off-by: Heinrich Schuchardt
> ---
> v2:
> use ut_assert*() for testing
> ---
> test/unicode_ut.c | 30 ++
> 1 file changed, 30 insertions(+)
>
>
On 31.08.18 21:31, Heinrich Schuchardt wrote:
> This patch provides a define to initialize a table that maps lower to
> capital letters for Unicode code point 0x - 0x.
>
> Signed-off-by: Heinrich Schuchardt
> ---
> v2
> add shorter tables for code pages 437 and 1250
> ---
>
On 31.08.18 21:31, Heinrich Schuchardt wrote:
> The width and precision of the printf() function refer to the number of
> characters not to the number of bytes printed.
>
> Signed-off-by: Heinrich Schuchardt
> ---
> v2:
> use library function utf16_utf8_strncpy() for string16()
> ---
>
On 31.08.2018 16:57, Miquel Raynal wrote:
The 'mtdparts' command is not needed anymore. While the environment
variable is still valid (and useful), the command has been replaced by
'mtd' which is much more close to the MTD stack and do not add its own
specific glue. The 'mtdids' variable, only
On 31.08.2018 16:57, Miquel Raynal wrote:
UBI should not mess with MTD partitions, now that the partitions are
handled in a clean way, clean the ubi command and avoid using this
uneeded extra-glue to reference the devices.
Signed-off-by: Miquel Raynal
---
cmd/Kconfig | 2 ++
cmd/ubi.c |
On 31.08.2018 16:57, Miquel Raynal wrote:
Current implementation of mtdparts command errors out if the desired MTD
device is not found. Fallback to the new probe function in this case
before erroring out.
This will the save the user the need to call something like 'mtd list'
before mtdparts.
On 31.08.2018 16:57, Miquel Raynal wrote:
There should not be a 'nand' command, a 'sf' command and certainly not
a new 'spi-nand' command. Write a 'mtd' command instead to manage all
MTD devices/partitions at once. This should be the preferred way to
access any MTD device.
Signed-off-by: Miquel
On 31.08.2018 16:57, Miquel Raynal wrote:
Instead of collecting partitions in a flat list, create a hierarchy
within the mtd_info structure: use a partitions list to keep track of
the partitions of an MTD device (which might be itself a partition of
another MTD device), a pointer to the parent
On 31.08.2018 16:57, Miquel Raynal wrote:
Using an MTD device (resp. partition) name in mtdparts is simple and
straightforward. However, for a long time already, another name was
given in mtdparts to indicate a device (resp. partition) so the
"mtdids" environment variable was created to do the
On 31.08.2018 16:57, Miquel Raynal wrote:
The current parser is very specific to U-Boot mtdparts implementation.
It does not use MTD structures like mtd_info and mtd_partition. Copy
and adapt the current parser in drivers/mtd/mtd-uclass.c (to not break
the current use of mtdparts.c itself) and
On 31.08.2018 16:57, Miquel Raynal wrote:
The user might want to trigger the probe of any MTD device, export these
functions so they can be called from a command source file.
Signed-off-by: Miquel Raynal
Acked-by: Jagan Teki
---
drivers/mtd/mtd-uclass.c | 16
include/mtd.h
On 31.08.2018 16:57, Miquel Raynal wrote:
All U-Boot users must define the mtdparts environment variable with:
setenv mtdparts mtdparts=...
While this may ease the partition declaration job to be passed to
Linux, this is a pure software limitation and forcing this prefix is a
complete
On 31.08.2018 16:57, Miquel Raynal wrote:
MTD_PARTITIONS is declared twice. Remove the redundant entry with no
help associated.
Signed-off-by: Miquel Raynal
---
drivers/mtd/Kconfig | 3 ---
1 file changed, 3 deletions(-)
diff --git a/drivers/mtd/Kconfig b/drivers/mtd/Kconfig
index
On 31.08.2018 16:57, Miquel Raynal wrote:
Let spi-nand devices be recognized by mtdparts. This is superfluous
but a full mtdparts rework would be very time-consuming.
Signed-off-by: Miquel Raynal
Acked-by: Jagan Teki
Reviewed-by: Boris Brezillon
---
cmd/mtdparts.c | 13
On 31.08.2018 16:57, Miquel Raynal wrote:
While 1kB or 1kiB will be parsed correctly, 1k will return the right
amount, but the metric suffix will not be escaped once the char
pointer updated. Fix this situation by simplifying the move of the
endp pointer.
Signed-off-by: Miquel Raynal
---
On 31.08.2018 16:57, Miquel Raynal wrote:
Both ustrtoul and ustrtoull interpret 1k but not 1m or 1g. Even if the
SI symbols for Mega and Giga are 'M' and 'G', certain entries of
eg. mtdparts also use (wrongly) the metric prefix 'm' and 'g'.
I do not see how parsing lowercase prefixes could
On 31.08.2018 16:28, Quentin Schulz wrote:
The SSP2 clock is at bit 6 in the register, so the value is 0x40 unlike
the current 0x70 which enables the clock of UART2, SSP1 and SSP2.
Signed-off-by: Quentin Schulz
---
added in v2
@Stefan: I think you'd want to test the FPGA on x600 again as
32 matches
Mail list logo