Dear Tom,
Could you these patches on u-boot/master, plz?
The following changes since commit 29e0cfb4f77f7aa369136302cee14a91e22dca71:
Prepare v2016.11 (2016-11-14 11:27:11 -0500)
are available in the git repository at:
http://git.denx.de/u-boot-mmc.git master
for you to fetch changes up
Hi Hans,
On 12/11/2016 11:22, Hans de Goede wrote:
Hi,
On 11-11-16 19:33, Mylene Josserand wrote:
Hi everyone,
I am currently using FEL and Fastboot to flash a sunxi-device with SPL
and u-boot.
In my board, I have two MMC devices: a MMC slot and an eMMC.
My use-case is to flash an empty
On 16.11.2016 01:26, Masahiro Yamada wrote:
> Hi Michal
>
> 2016-11-16 2:59 GMT+09:00 Michal Simek :
>> Hi Tom,
>>
>> please pull these changes to your tree.
>> There are several things in this PR like
>> DTS cleanups, Topic NL board with extending mkimage format and nand
On 16.11.2016 01:34, Masahiro Yamada wrote:
> Hi.
>
>
> 2016-11-16 4:01 GMT+09:00 Michal Simek :
>> On 15.11.2016 15:22, Tom Rini wrote:
>>> On Tue, Nov 15, 2016 at 03:16:51PM +0100, Michal Simek wrote:
On 11.11.2016 18:33, Tom Rini wrote:
> On Fri, Nov 11, 2016 at
Hi Stefan
>From: Stefan Agner
>This patchset cleans up the SPL USB Gadget Kconfig and Makfile.
>The first two patches are actual fixes and we might consider to add these two
>for the v2016.11 release. The third one adds a new config option >for cleaner
>structure. I
Hi Stephen
>>Adding this:
> >config SPL_DFU_SUPPORT
> > bool "Support DFU (Device Firmware Upgarde)"
>- depends on SPL_GADGET_SUPPORT
>+ depends on SPL_USB_GADGET_SUPPORT
>select SPL_HASH_SUPPORT
> help
> This feature enables the DFU (Device Firmware
Hi,
> -Original Message-
> From: Jagan Teki [mailto:ja...@openedev.com]
> Sent: Wednesday, November 16, 2016 9:33 AM
> To: u-boot@lists.denx.de
> Cc: Jagan Teki ; Bin Meng ;
> York Sun ; Vignesh R ; Mugunthan V
> N
Hi,
> -Original Message-
> From: U-Boot [mailto:u-boot-boun...@lists.denx.de] On Behalf Of Jagan Teki
> Sent: Wednesday, November 16, 2016 9:33 AM
> To: u-boot@lists.denx.de
> Cc: Jagan Teki
> Subject: [U-Boot] [PATCH v6 21/21] sf: Fix s25fs512s id param table
>
>
Hi,
> -Original Message-
> From: Jagan Teki [mailto:ja...@openedev.com]
> Sent: Wednesday, November 16, 2016 9:33 AM
> To: u-boot@lists.denx.de
> Cc: Jagan Teki ; Bin Meng ;
> York Sun ; Vignesh R ; Mugunthan V
> N
Hi,
> -Original Message-
> From: Jagan Teki [mailto:ja...@openedev.com]
> Sent: Wednesday, November 16, 2016 9:33 AM
> To: u-boot@lists.denx.de
> Cc: Jagan Teki ; Simon Glass ;
> Bin Meng ; York Sun ; Vignesh
> R
Hi,
> -Original Message-
> From: Jagan Teki [mailto:ja...@openedev.com]
> Sent: Wednesday, November 16, 2016 9:33 AM
> To: u-boot@lists.denx.de
> Cc: Jagan Teki ; Yunhui Cui
> ; Bin Meng ; York Sun
> ;
On 16.11.2016 07:34, Michal Simek wrote:
> Hi,
>
> On 16.11.2016 01:50, Andre Przywara wrote:
>> It seems pretty odd that the minimum supported SDHCI frequency is
>> the maximum frequency shifted _left_ by 9 bits.
>> Shifting it right by that amount seems to make much more sense.
>>
>> Pointed
Hi,
> -Original Message-
> From: Jagan Teki [mailto:ja...@openedev.com]
> Sent: Wednesday, November 16, 2016 9:33 AM
> To: u-boot@lists.denx.de
> Cc: Jagan Teki ; Bin Meng ;
> York Sun ; Vignesh R ; Mugunthan V
> N
Hi,
> -Original Message-
> From: Jagan Teki [mailto:ja...@openedev.com]
> Sent: Wednesday, November 16, 2016 9:33 AM
> To: u-boot@lists.denx.de
> Cc: Jagan Teki ; Bin Meng ;
> York Sun ; Vignesh R ; Mugunthan V
> N
Hi,
> -Original Message-
> From: Jagan Teki [mailto:ja...@openedev.com]
> Sent: Wednesday, November 16, 2016 9:33 AM
> To: u-boot@lists.denx.de
> Cc: Jagan Teki ; Bin Meng ;
> York Sun ; Vignesh R ; Mugunthan V
> N
Hi,
> -Original Message-
> From: Jagan Teki [mailto:ja...@openedev.com]
> Sent: Wednesday, November 16, 2016 9:33 AM
> To: u-boot@lists.denx.de
> Cc: Jagan Teki ; Bin Meng ;
> York Sun ; Vignesh R ; Mugunthan V
> N
Hi,
On 16.11.2016 01:50, Andre Przywara wrote:
> It seems pretty odd that the minimum supported SDHCI frequency is
> the maximum frequency shifted _left_ by 9 bits.
> Shifting it right by that amount seems to make much more sense.
>
> Pointed out by GCC 6.2 as the value needs more than 32 bits.
Hi,
> -Original Message-
> From: Jagan Teki [mailto:ja...@openedev.com]
> Sent: Wednesday, November 16, 2016 9:33 AM
> To: u-boot@lists.denx.de
> Cc: Jagan Teki ; Yunhui Cui ;
> Bin Meng ; York Sun ; Vignesh
> R
Hi,
> -Original Message-
> From: Jagan Teki [mailto:ja...@openedev.com]
> Sent: Wednesday, November 16, 2016 9:33 AM
> To: u-boot@lists.denx.de
> Cc: Jagan Teki ; Bin Meng ;
> York Sun ; Vignesh R ; Mugunthan V
> N
Hi,
> -Original Message-
> From: Jagan Teki [mailto:ja...@openedev.com]
> Sent: Wednesday, November 16, 2016 9:33 AM
> To: u-boot@lists.denx.de
> Cc: Jagan Teki ; Bin Meng ;
> York Sun ; Vignesh R ; Mugunthan V
>
Hi,
> -Original Message-
> From: Jagan Teki [mailto:ja...@openedev.com]
> Sent: Wednesday, November 16, 2016 9:33 AM
> To: u-boot@lists.denx.de
> Cc: Jagan Teki ; Bin Meng ;
> York Sun ; Vignesh R ; Mugunthan V
> N
Hi,
> -Original Message-
> From: Jagan Teki [mailto:ja...@openedev.com]
> Sent: Wednesday, November 16, 2016 9:33 AM
> To: u-boot@lists.denx.de
> Cc: Jagan Teki ; Bin Meng ;
> York Sun ; Vignesh R ; Mugunthan V
> N
Hi,
> -Original Message-
> From: Jagan Teki [mailto:ja...@openedev.com]
> Sent: Wednesday, November 16, 2016 9:33 AM
> To: u-boot@lists.denx.de
> Cc: Jagan Teki ; Simon Glass ;
> Bin Meng ; York Sun ; Vignesh
> R
Hi,
> -Original Message-
> From: Jagan Teki [mailto:ja...@openedev.com]
> Sent: Wednesday, November 16, 2016 9:33 AM
> To: u-boot@lists.denx.de
> Cc: Jagan Teki ; Bin Meng ;
> York Sun ; Vignesh R ; Mugunthan V
> N
Hi,
> -Original Message-
> From: U-Boot [mailto:u-boot-boun...@lists.denx.de] On Behalf Of Jagan Teki
> Sent: Wednesday, November 16, 2016 9:33 AM
> To: u-boot@lists.denx.de
> Cc: Jagan Teki
> Subject: [U-Boot] [PATCH v6 03/21] sf: sandbox: Use JEDEC_MFR|ID in id
>
Hi: york
There is a bit of change for MSI node of kernel , so I will update this patch
on next version and with new comments you mentioned.
Best Regards
Wenbin Song
> -Original Message-
> From: york sun
> Sent: Tuesday, November 15, 2016 5:36 AM
> To: Wenbin Song
s25fs512s and s25fl512s_256k have common id information
till 5 bytes and 6th byte have different family id
like FS and FL-S as 0x81 and 0x80.
Reported-by: Vignesh R
Signed-off-by: Jagan Teki
---
drivers/mtd/spi/spi_flash_ids.c | 2 +-
1 file changed, 1
- fix single line comments
- remove unneeded spaces
- ascending order of include files
- rename SPI DATAFLASH to dataflash
- rename SPI DataFlash to dataflash
- return NULL replaced with error code
Cc: Bin Meng
Cc: York Sun
Signed-off-by: Jagan Teki
This patch fixed the add_dataflash return logic,
so-that it can handle both jedec and older chips
same as Linux.
Cc: Bin Meng
Cc: York Sun
Signed-off-by: Jagan Teki
Reviewed-by: Simon Glass
Reviewed-by: Jagan Teki
Dual flash code in spi are usually take the spi controller
to work with dual connected flash devices. Usually these
dual connection operation's are referred to flash controller
protocol rather with spi controller protocol, these are still
present in flash side for the usage of spi-nor controllers.
dataflash doesn't require options, memory_map from spi.
Cc: Bin Meng
Cc: Simon Glass
Cc: York Sun
Signed-off-by: Jagan Teki
Reviewed-by: Simon Glass
Reviewed-by: Jagan Teki
Flash id detection should be the first step to enumerate
the connected flash on the board, once ie done checking
with respective id codes locally in the driver all this
should be part of jedec_probe instead of id detection and
validated through flash_info{} table separatly.
Cc: Bin Meng
Use small 'd' in s25s512s ext_jedec
Cc: Bin Meng
Cc: York Sun
Cc: Vignesh R
Cc: Mugunthan V N
Cc: Michal Simek
Cc: Siva Durga Prasad Paladugu
Signed-off-by: Jagan Teki
spi_flash_write_bar-> write_bar
spi_flash_write_bar -> read_bar
spi_flash_cmd_wait_ready -> spi_flash_wait_till_ready
Cc: Bin Meng
Cc: York Sun
Cc: Vignesh R
Cc: Mugunthan V N
Cc: Michal Simek
For readability use small letter's with flash name.
Cc: Bin Meng
Cc: York Sun
Cc: Vignesh R
Cc: Mugunthan V N
Cc: Michal Simek
Cc: Siva Durga Prasad Paladugu
Remove unneeded/non-meaningful commit message on
params and flash.
Cc: Bin Meng
Cc: York Sun
Cc: Vignesh R
Cc: Mugunthan V N
Cc: Michal Simek
Cc: Siva Durga Prasad Paladugu
Now the flash params table as renamed to spi_flash_ids structure,
so rename the sf_params.c to spi_flash_ids.c and remove the legacy.
Cc: Bin Meng
Cc: York Sun
Cc: Vignesh R
Cc: Mugunthan V N
Cc: Michal Simek
From: Jagan Teki
Since flash detection code is more mature to
detect even with 6 bytes id length devices
removed old code and related references.
Cc: Yunhui Cui
Cc: Bin Meng
Cc: York Sun
Cc: Vignesh R
INFO6 is for tabulating 6 byte flash parts, Ex: S25FS256S_64K
Cc: Bin Meng
Cc: York Sun
Cc: Vignesh R
Cc: Mugunthan V N
Cc: Michal Simek
Cc: Siva Durga Prasad Paladugu
Add id length of 5 bytes numerical value to macro.
Cc: Bin Meng
Cc: York Sun
Cc: Vignesh R
Cc: Mugunthan V N
Cc: Michal Simek
Cc: Siva Durga Prasad Paladugu
Add Spansion S25FS256S_64K spi flash to the list of spi_flash_ids.
In spansion S25FS-S family the physical sectors are grouped as
normal and parameter sectors. Parameter sectors are 4kB in size
with 8 set located at the bottom or top address of a device.
Normal sectors are similar to other flash
So, now SPI_FLASH_ID_MAX_LEN is 6 bytes useful for
few spansion flash families S25FS-S
Cc: Bin Meng
Cc: York Sun
Cc: Vignesh R
Cc: Mugunthan V N
Cc: Michal Simek
Cc: Siva Durga Prasad
Rename nr_sectors as n_sectors to sync with Linux.
Cc: Bin Meng
Cc: York Sun
Cc: Vignesh R
Cc: Mugunthan V N
Cc: Michal Simek
Cc: Siva Durga Prasad Paladugu
Instead of extracting id's separately better
to use JEDEC_MFR|ID for code simplicity.
Cc: Bin Meng
Signed-off-by: Jagan Teki
Reviewed-by: Simon Glass
Reviewed-by: Jagan Teki
Tested-by: Jagan Teki
- Proper tabs spaces
- Removed unnecessary
- Added meaningful comments
Cc: Simon Glass
Cc: Bin Meng
Cc: York Sun
Cc: Vignesh R
Cc: Mugunthan V N
Cc: Michal Simek
Cc: Siva
Simplify the flash_lock ops detection code and added
meaningful comment.
Cc: Bin Meng
Cc: York Sun
Cc: Vignesh R
Cc: Mugunthan V N
Cc: Michal Simek
Cc: Siva Durga Prasad Paladugu
INFO macro make flash table entries more adjustable like
adding new flash_info attributes, update ID length bytes
and so on and more over it will sync to Linux way of defining
flash_info attributes.
- Add JEDEC_ID
- Add JEDEC_EXT macro
- Add JEDEC_MFR
- spi_flash_params => spi_flash_info
- params
From: Jagan Teki
Updated spi_flash_info table in sync with Linux, and removed
legacy and unsupported code.
Changes for v6:
- Fix few comments from Simon
- Rebase to master
Changes for v5:
- Add dataflash fixes in this series
- Rebase to master
Changes for v4:
-
Hi Hongbo,
> -Original Message-
> From: Hongbo Zhang [mailto:macro.wav...@gmail.com]
> Sent: 2016年11月15日 18:29
> To: Z.Q. Hou
> Cc: york sun ; u-boot@lists.denx.de; tr...@konsulko.com;
> w...@csie.org; H.B. Zhang
> Subject:
York,
Please test again?
On Tue, Nov 8, 2016 at 10:59 PM, york sun wrote:
> On 11/07/2016 08:52 PM, york@nxp.com wrote:
>> On 10/30/2016 10:47 AM, Jagan Teki wrote:
>>> INFO macro make flash table entries more adjustable like
>>> adding new flash_info attributes, update
On Tue, Nov 15, 2016 at 11:53 AM, Andy Shevchenko
wrote:
> Perhaps it was discussed somewhere, but...
>
> Which obviously show that double quote is ignored. Was it previous
> behaviour that has been altered by custom patches? Or this is a
> regression/feature of newer
From: Philipp Tomsich
To send a parametrized command to the PHY over MDIO, we should write
the data first, the trigger the execution by the command register
write. Fix the access pattern in our MDIO write routine.
Apparently this doesn't really matter with
The final line with the linefeeds should obviously only printed once
(what the code actually does), but the indentation suggests otherwise.
Fix the indentation to avoid compiler warnings and puzzled readers.
Pointed out by GCC 6.2's -Wmisleading-indentation warning.
Signed-off-by: Andre
Apparently the indentation is wrong in this case, as the second message
should be printed indepdently of the if statement.
Fix this indentation to avoid both compiler warnings and puzzled readers.
Pointed out by GCC 6.2's -Wmisleading-indentation warning.
Signed-off-by: Andre Przywara
The error checking makes only sense if the previous line has been
executed, so add block braces around the _whole_ then clause.
Pointed out by GCC 6.2's -Wmisleading-indentation warning.
Signed-off-by: Andre Przywara
---
drivers/net/phy/micrel.c | 3 ++-
1 file changed,
The shortname variable isn't referenced anywhere in the code, so just
remove it.
Pointed out by a GCC 6.2 default warning option.
Signed-off-by: Andre Przywara
---
drivers/usb/gadget/ether.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/usb/gadget/ether.c
It seems pretty odd that the minimum supported SDHCI frequency is
the maximum frequency shifted _left_ by 9 bits.
Shifting it right by that amount seems to make much more sense.
Pointed out by GCC 6.2 as the value needs more than 32 bits.
Signed-off-by: Andre Przywara
Apparently the indentation is wrong here, fix this to avoid compiler
warnings and puzzled readers.
Pointed out by GCC 6.2's -Wmisleading-indentation warning.
Signed-off-by: Andre Przywara
---
drivers/usb/eth/r8152_fw.c | 8
1 file changed, 4 insertions(+), 4
Obviously the mask for the rx and tx select field cannot be right,
as it would overlap in one and exceed the 32-bit register in the other
case. From looking at the neighbouring bits it looks like the mask
should be really 4 bits wide instead of 8.
Pointed out by a GCC 6.2 (default) warning.
The error checking makes only sense if the previous line has been
executed, so add block braces around the _whole_ then clause.
Pointed out by GCC 6.2's -Wmisleading-indentation warning.
Signed-off-by: Andre Przywara
---
drivers/net/ldpaa_eth/ldpaa_eth.c | 3 ++-
1 file
The rtl8169_intr_mask variable isn't used anywhere in the code, so
just remove it to avoid a GCC 6.2 compiler warning.
Signed-off-by: Andre Przywara
---
drivers/net/rtl8169.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/drivers/net/rtl8169.c
The whole error message should be within the else clause, not just
the first part.
Pointed out by GCC 6.2's -Wmisleading-indentation warning.
Signed-off-by: Andre Przywara
---
board/freescale/ls2080aqds/eth.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff
More or less by accident I ran buildman the other day on a box with
GCC 6.2.0 cross-compilers. By default it seems that the 6.x series enables
more (and new) warnings, so the results were non-clean builds for about
two thirds of the armv8 defconfigs.
Some of the warnings are cosmectic, but some
Apparently the indentation is off here, for the IGB model just want to
bail out early.
Fix this to avoid both compiler warnings and puzzled readers.
Pointed out by GCC 6.2's -Wmisleading-indentation warning.
Signed-off-by: Andre Przywara
---
drivers/net/e1000.c | 5
The indentation is misleading here and suggests that the write command
will be only executed in the else clause.
It seems like this is not intended, so fix the indentation to avoid
both compiler warnings and puzzled readers.
Pointed out by GCC 6.2's -Wmisleading-indentation warning.
Hi.
2016-11-16 4:01 GMT+09:00 Michal Simek :
> On 15.11.2016 15:22, Tom Rini wrote:
>> On Tue, Nov 15, 2016 at 03:16:51PM +0100, Michal Simek wrote:
>>> On 11.11.2016 18:33, Tom Rini wrote:
On Fri, Nov 11, 2016 at 06:32:15PM +0100, Michal Simek wrote:
> Hi,
>
>
Hi Michal
2016-11-16 2:59 GMT+09:00 Michal Simek :
> Hi Tom,
>
> please pull these changes to your tree.
> There are several things in this PR like
> DTS cleanups, Topic NL board with extending mkimage format and nand driver.
>
> I have run buildman over it and there is not an
Hi Bin,
On 2 November 2016 at 22:11, Bin Meng wrote:
> Hi Simon,
>
> On Fri, Oct 7, 2016 at 4:59 AM, Simon Glass wrote:
>> It is sometimes useful to be able to reference configuration options in a
>> device tree source file. Add the necessary includes so
Hi Bin,
On 2 November 2016 at 22:11, Bin Meng wrote:
> Hi Simon,
>
> On Fri, Oct 7, 2016 at 4:59 AM, Simon Glass wrote:
>> Change x86 boards to use binman to produce the ROM. This involves adding the
>> image definition to the device tree and using it in
Hi Marcel,
On 1 November 2016 at 16:19, Marcel Ziswiler
wrote:
> Hi Simon
>
> That sounds somewhat similar to the new OpenEmbedded Image Creator tool
> called WIC (e.g. see slide 27ff here https://www.yoctoproject.org/sites
>
Hi Tom,
On 5 October 2016 at 20:04, Tom Rini wrote:
> On Wed, Oct 05, 2016 at 10:51:04AM -0600, Simon Glass wrote:
>> Hi Masahiro,
>>
>> On 4 October 2016 at 21:51, Masahiro Yamada
>> wrote:
>> >
>> > 2016-10-05 9:25 GMT+09:00 Simon Glass
Hi Andrew,
On 15 November 2016 at 10:07, Andrew F. Davis wrote:
>
> On 11/14/2016 06:34 PM, Simon Glass wrote:
> > Hi Andrew,
> >
> > On 14 November 2016 at 14:55, Andrew F. Davis wrote:
> >> On 11/14/2016 02:44 PM, Simon Glass wrote:
> >>> Hi Andrew,
> >>>
> >>> On 14
Hi,
On 15 November 2016 at 00:20, Y.T. Tang wrote:
> Hi Simon,
>
> Please see my reply inline.
>
>> -Original Message-
>> From: s...@google.com [mailto:s...@google.com] On Behalf Of Simon Glass
>> Sent: Saturday, November 12, 2016 12:18 AM
>> To: Y.T. Tang
Hi Andreas,
On 15 November 2016 at 10:07, Andreas Färber wrote:
> Hi Simon,
>
> Am 28.10.2016 um 03:52 schrieb Simon Glass:
>> On 27 October 2016 at 05:44, Andreas Färber wrote:
>>> Am 26.10.2016 um 21:19 schrieb Simon Glass:
On 26 October 2016 at 09:02,
At present buildman leaves behind a few characters during its progress
updates, which looks odd. Fix it.
Signed-off-by: Simon Glass
---
tools/buildman/builder.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/buildman/builder.py
On 15/11/2016 23:11, york sun wrote:
On 11/15/2016 12:36 PM, Alexander Graf wrote:
Hi York,
Do you want to take that patch set?
Yes, I can. I saw it assigned to you in patchwork so I didn't act.
I think since it's really hardware enablement for your platform, I'd
prefer if you pull
On 11/15/2016 12:36 PM, Alexander Graf wrote:
> Hi York,
>
> Do you want to take that patch set?
>
Yes, I can. I saw it assigned to you in patchwork so I didn't act.
York
___
U-Boot mailing list
U-Boot@lists.denx.de
On Dienstag, 15. November 2016 13:02:45 CET Stefan Agner wrote:
> From: Stefan Agner
>
> diff --git a/common/spl/Kconfig b/common/spl/Kconfig
> index bb99f1f..54bcba3 100644
> --- a/common/spl/Kconfig
> +++ b/common/spl/Kconfig
> @@ -497,6 +497,32 @@ config
From: Stefan Agner
Introduce USB Gadget config option. This allows to combine Makefile
entries for SPL_USBETH_SUPPORT and SPL_DFU_SUPPORT.
Signed-off-by: Stefan Agner
---
Changes in v3:
- Fix depends on SPL_USB_GADGET_SUPPORT and use if
From: Stefan Agner
Some devices (e.g. dra7xx) support loading to RAM using DFU without
having direct boot from RAM support. Make sure the linker list
does not contain BOOT_DEVICE_RAM if CONFIG_SPL_RAM_SUPPORT is not
enabled.
Fixes: 98136b2f26fa ("spl: Convert
From: Stefan Agner
The DFU Kconfig menu entries should be part of the SPL
Kconfig file. Also avoid using the top level Makefile by
moving the config dependent build artifacts to the driver/
and driver/usb/gadget/ Makfiles.
With that, DFU can be built again in SPL if
From: Stefan Agner
This patchset cleans up the SPL USB Gadget Kconfig and Makfile.
The first two patches are actual fixes and we might consider to
add these two for the v2016.11 release. The third one adds a new
config option for cleaner structure. I plan to add
On 2016-11-15 00:52, B, Ravi wrote:
> Stefan
>
>> From: Stefan Agner
>
>>This patchset cleans up the SPL USB Gadget Kconfig and Makfile.
>>The first two patches are actual fixes and we might consider to add these two
>>for the v2016.11 release. The third one adds a
Hi York,
Do you want to take that patch set?
Thanks,
Alex
On 19/10/2016 16:31, Alexander Graf wrote:
We now have EFI support in U-Boot which worked out of the box on all systems
that I tried it on so far. Except for the LS2080ARDB. With this patch set
I can successfully boot grub2 and Linux
Hi Michal,
On 15 November 2016 at 12:07, Michal Simek wrote:
> Hi guys,
>
> I just found today with playing with clock drivers that the patch
> clk: convert API to match reset/mailbox style
> (sha1: 135aa95002646c46e89de93fa36adad1b010548f)
>
> added this part of code to fixed
Hi guys,
I just found today with playing with clock drivers that the patch
clk: convert API to match reset/mailbox style
(sha1: 135aa95002646c46e89de93fa36adad1b010548f)
added this part of code to fixed clock driver
-static ulong clk_fixed_rate_get_rate(struct udevice *dev)
+static ulong
On 15.11.2016 15:22, Tom Rini wrote:
> On Tue, Nov 15, 2016 at 03:16:51PM +0100, Michal Simek wrote:
>> On 11.11.2016 18:33, Tom Rini wrote:
>>> On Fri, Nov 11, 2016 at 06:32:15PM +0100, Michal Simek wrote:
Hi,
2016-11-11 17:04 GMT+01:00 Tom Rini :
> On
On 2016-11-14 21:30, Scott Wood wrote:
> On Wed, 2016-10-26 at 17:18 -0700, Stefan Agner wrote:
>> From: Stefan Agner
>>
>> Commit 35c204d8a9d0 ("nand: reinstate lazy bad block scanning")
>> introduced lazy BBT scanning. However, some controller do parts
>> of the
From: Stefan Agner
Specify standard padding for payload to 68KB. This is derived from
the maximum header size plus maximum SPL size. It matches the
already defined offset for SD/eMMC devices (69KB) too. This allows
to use the u-boot-with-spl.imx build target to generate
On 2016-11-15 10:04, Marek Vasut wrote:
> On 11/15/2016 06:42 PM, Stefan Agner wrote:
>> On 2016-11-15 08:12, Tom Rini wrote:
>>> On Tue, Nov 15, 2016 at 09:59:22AM +, Max Krummenacher wrote:
Hi Stefan
On Mon, 2016-11-14 at 18:06 -0800, Stefan Agner wrote:
> From: Stefan
On 11/15/2016 06:42 PM, Stefan Agner wrote:
> On 2016-11-15 08:12, Tom Rini wrote:
>> On Tue, Nov 15, 2016 at 09:59:22AM +, Max Krummenacher wrote:
>>> Hi Stefan
>>>
>>> On Mon, 2016-11-14 at 18:06 -0800, Stefan Agner wrote:
From: Stefan Agner
When
Hi Tom,
please pull these changes to your tree.
There are several things in this PR like
DTS cleanups, Topic NL board with extending mkimage format and nand driver.
I have run buildman over it and there is not an issue.
./tools/buildman/buildman -b master zynq -C
Thanks,
Michal
The following
On 2016-11-15 08:12, Tom Rini wrote:
> On Tue, Nov 15, 2016 at 09:59:22AM +, Max Krummenacher wrote:
>> Hi Stefan
>>
>> On Mon, 2016-11-14 at 18:06 -0800, Stefan Agner wrote:
>> > From: Stefan Agner
>> >
>> > When building SPL with eMMC boot support, specify standard
On 11/14/2016 06:34 PM, Simon Glass wrote:
> Hi Andrew,
>
> On 14 November 2016 at 14:55, Andrew F. Davis wrote:
>> On 11/14/2016 02:44 PM, Simon Glass wrote:
>>> Hi Andrew,
>>>
>>> On 14 November 2016 at 12:49, Andrew F. Davis wrote:
To help automate the loading
Hi Simon,
Am 28.10.2016 um 03:52 schrieb Simon Glass:
> On 27 October 2016 at 05:44, Andreas Färber wrote:
>> Am 26.10.2016 um 21:19 schrieb Simon Glass:
>>> On 26 October 2016 at 09:02, Andreas Färber wrote:
On a Raspberry Pi 2 disagreements on cell
Joe, All,
On 2016-11-14 21:15 -0600, Joe Hershberger spake thusly:
> On Sun, Nov 13, 2016 at 2:59 PM, Yann E. MORIN
> wrote:
> > Currently, CMD_PXE is forcibly enabled in config_distro_defaults.h, so
> > that general purpose distributions can rely on it being defined.
On 11/15/2016 01:55 AM, Michal Simek wrote:
> Hi Andrew,
>
> On 14.11.2016 20:49, Andrew F. Davis wrote:
>> To help automate the loading of a TEE image during the boot we add a new
>> FIT section type 'tee', when we see this type while loading the loadable
>> sections we automatically call the
On Tue, Nov 15, 2016 at 09:59:22AM +, Max Krummenacher wrote:
> Hi Stefan
>
> On Mon, 2016-11-14 at 18:06 -0800, Stefan Agner wrote:
> > From: Stefan Agner
> >
> > When building SPL with eMMC boot support, specify standard padding
> > for payload to match the load
On Tue, Nov 15, 2016 at 03:16:51PM +0100, Michal Simek wrote:
> On 11.11.2016 18:33, Tom Rini wrote:
> > On Fri, Nov 11, 2016 at 06:32:15PM +0100, Michal Simek wrote:
> >> Hi,
> >>
> >> 2016-11-11 17:04 GMT+01:00 Tom Rini :
> >>
> >>> On Fri, Nov 11, 2016 at 01:26:05PM +0100,
On 11.11.2016 18:33, Tom Rini wrote:
> On Fri, Nov 11, 2016 at 06:32:15PM +0100, Michal Simek wrote:
>> Hi,
>>
>> 2016-11-11 17:04 GMT+01:00 Tom Rini :
>>
>>> On Fri, Nov 11, 2016 at 01:26:05PM +0100, Michal Simek wrote:
>>>
DTC 1.2 reports these warnings:
Warning
1 - 100 of 152 matches
Mail list logo