Hi Heinrich,
On Wed, Jul 4, 2018 at 3:39 AM, Heinrich Schuchardt wrote:
> On 07/03/2018 06:51 PM, Bin Meng wrote:
>> Hi Alex,
>>
>> On Tue, Jul 3, 2018 at 11:05 PM, Alexander Graf wrote:
>>> On 07/03/2018 04:56 PM, Bin Meng wrote:
Hi Alex,
On Tue, Jul 3, 2018 at 10:32 PM,
On Tue, Jul 3, 2018 at 5:45 PM, André Przywara wrote:
>>
>> I tried enabling DM for MMC on A64 recently and unfortunately it results in
>> SPL exceeding 32kb size limit.
>
> Mmh, worked for me with this preliminary branch:
> [1] https://github.com/apritzel/u-boot/commits/sunxi-dm-WIP
> (which I
On 07/04/2018 01:25 AM, Vasily Khoruzhick wrote:
> On Tue, Jul 3, 2018 at 2:22 PM, André Przywara wrote:
>
>>> Adding a few more people to the list. It looks like b62cdbddedc3 was in
>>> response to fef73766d9ad. So, this close to the release, what do we
>>> need to do to get things back to
The same basic parsing was implemented in tftp and nfs, so add a helper
function to do the work once.
Signed-off-by: Joe Hershberger
---
include/net.h | 11 +++
net/net.c | 20
net/nfs.c | 15 ++-
net/tftp.c| 13 +
4 files
Instead of depending on a env callback for bootfile, read it explicitly.
We do this because the bootfile can be specified on the command line and
if it is, we will overwrite the internal variable. If a netboot_common()
is called again with no bootfile parameter, we want to use the one in
the
Rather than crashing, check the src ptr and set dst to empty string.
Signed-off-by: Joe Hershberger
---
net/net.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/net/net.c b/net/net.c
index 42a50e60f8..333102ea79 100644
--- a/net/net.c
+++ b/net/net.c
@@ -1522,12
For net_boot_common, we allow the serverip to be specified as part of
the boot file name. For net commands that require serverip, include that
source as a valid specification of serverip.
Signed-off-by: Joe Hershberger
---
include/net.h | 3 +++
net/net.c | 7 ++-
2 files changed, 9
With net autoload, we check the prerequisites for the initial command,
but the greater prerequisites when autoloading are not checked.
If we would attempt to autoload, check those prerequisites too.
If we are not expecting a serverip from the server, then don't worry
about it not being set, but
On Tue, Jul 3, 2018 at 2:22 PM, André Przywara wrote:
>> Adding a few more people to the list. It looks like b62cdbddedc3 was in
>> response to fef73766d9ad. So, this close to the release, what do we
>> need to do to get things back to the state things were in for v2018.05?
>> And then what
The check for sending to the gateway was not using the correct variable
for comparison, so it was reporting that packets are sent to the gateway
when they were not.
Signed-off-by: Joe Hershberger
---
Changes in v2: None
net/nfs.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
nfs was only printing basic info about the transfer in the case of a
DEBUG build. Print the same level of detail as tftp always.
Signed-off-by: Joe Hershberger
---
Changes in v2: None
net/nfs.c | 26 +-
1 file changed, 13 insertions(+), 13 deletions(-)
diff --git
Reported-by: Coverity (CID: 152888)
Signed-off-by: Joe Hershberger
---
Changes in v2:
- Take into account the attributes that could be there
- Tested with v2 and v3
net/nfs.h | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/net/nfs.h b/net/nfs.h
index
On the A64 the clock for the first USB controller is actually the parent
of the clock for the second controller, so turning them off in that order
makes the system hang.
Fix this by *not* turning off any clock for OHCI0, but both clocks when
OHCI1 is brought down.
Signed-off-by: Andre Przywara
On 7/3/2018 9:08 AM, Marek Vasut wrote:
> On 07/03/2018 03:58 PM, Jason Rush wrote:
>> On 6/29/2018 10:17 AM, Marek Vasut wrote:
>>> On 06/29/2018 05:06 PM, Jason Rush wrote:
On 6/29/2018 9:52 AM, Marek Vasut wrote:
> On 06/29/2018 04:44 PM, Jason Rush wrote:
>> On 6/29/2018 9:34 AM,
Hi Alberto,
> While downloading or uploading megabytes of data we had thousands of
> dummy lines like:
>
> transfer 0x1 bytes done
> OR
> Uploading 0x1000 bytes
>
> even on non-debug builds. This because transfers are chunked and
> code running on target does not have any clue about when
Hi Alberto,
> This command is part of the write LBA sector sequence performed by
> rkdeveloptool
You mentioned the LBA sector and the need of erasing it.
AFAIK, block devices (eMMC) perform internally erase on write.
Is this protocol also supposed to work with NAND flash? If yes, please
adjust
Hi Alberto,
> It is now possible to read from block device al logic layer.
^^^ - what do you
mean by logic layer?
I suppose this code is to read N blocks (512B) from eMMC device?
NOTE:
On 07/03/2018 09:59 PM, Alexander Graf wrote:
>
>
>> Am 03.07.2018 um 22:51 schrieb Andreas Färber :
>>
>>> Am 03.07.2018 um 01:08 schrieb Andreas Färber:
Am 02.07.2018 um 10:01 schrieb Jagan Teki:
> On Wed, Jun 27, 2018 at 6:12 AM, Andre Przywara
> wrote:
> At the moment we
Hi Alberto,
> Chip Version is a string saved in BOOTROM address space Little Endian.
>
> Ex for rk3288: 0x33323041 0x32303134 0x30383133 0x56323030
> which brings: 320A20140813V200
>
> Note that memory version do invert MSB/LSB so printing the char
> buffer will show: A02341023180002V
>
>
Hi Alberto,
> Two consecutive rockusb_tx_write without waiting for request complete
> do results in transfer reset of first request and thus no or
> incomplete data transfer. This because rockusb_tx_write do use just
> une request to keep serialization.
>
> So calls like:
>
On 07/03/2018 03:52 PM, Tom Rini wrote:
> On Tue, Jul 03, 2018 at 06:06:37PM +0530, Jagan Teki wrote:
>> On Tue, Jul 3, 2018 at 3:10 AM, Tom Rini wrote:
>>> On Mon, Jul 02, 2018 at 11:27:58PM +0200, Marek Vasut wrote:
On 07/02/2018 10:53 PM, Jagan Teki wrote:
> During usb shutdown or
> Am 03.07.2018 um 22:51 schrieb Andreas Färber :
>
>> Am 03.07.2018 um 01:08 schrieb Andreas Färber:
>>> Am 02.07.2018 um 10:01 schrieb Jagan Teki:
On Wed, Jun 27, 2018 at 6:12 AM, Andre Przywara
wrote:
At the moment we have the workaround for the Freescale arch timer
Am 03.07.2018 um 01:08 schrieb Andreas Färber:
> Am 02.07.2018 um 10:01 schrieb Jagan Teki:
>> On Wed, Jun 27, 2018 at 6:12 AM, Andre Przywara
>> wrote:
>>> At the moment we have the workaround for the Freescale arch timer
>>> erratum A-008585 merged into the generic timer_read_counter()
Speedup transfers increasing the max chunk size.
Buffers are allocated with memalign thus developer is noticed when heap is
full and in current configuration a buffer allocation of 64K till now
is safe.
Signed-off-by: Alberto Panizzo
---
arch/arm/include/asm/arch-rockchip/f_rockusb.h | 2 +-
1
Chip Version is a string saved in BOOTROM address space Little Endian.
Ex for rk3288: 0x33323041 0x32303134 0x30383133 0x56323030
which brings: 320A20140813V200
Note that memory version do invert MSB/LSB so printing the char
buffer will show: A02341023180002V
Signed-off-by: Alberto Panizzo
This allows rockusb code to reply correctly to K_FW_GET_CHIP_VER
command.
On RK3288 chip version is at 0x4ff0 and on tested hardware it
corresponds at the string "320A20140813V200"
Signed-off-by: Alberto Panizzo
---
arch/arm/mach-rockchip/rk3288/Makefile | 1 +
While downloading or uploading megabytes of data we had thousands of
dummy lines like:
transfer 0x1 bytes done
OR
Uploading 0x1000 bytes
even on non-debug builds. This because transfers are chunked and
code running on target does not have any clue about when the current
chunk is the last
It is now possible to read from block device al logic layer.
Corresponding command on workstation is:
rkdeveloptool rl
Signed-off-by: Alberto Panizzo
---
arch/arm/include/asm/arch-rockchip/f_rockusb.h | 2 +
drivers/usb/gadget/f_rockusb.c | 102 -
2
This command is part of the write LBA sector sequence performed by
rkdeveloptool
Signed-off-by: Alberto Panizzo
---
arch/arm/include/asm/arch-rockchip/f_rockusb.h | 1 +
drivers/usb/gadget/f_rockusb.c | 46 ++
2 files changed, 47 insertions(+)
diff
Two consecutive rockusb_tx_write without waiting for request complete
do results in transfer reset of first request and thus no or incomplete
data transfer. This because rockusb_tx_write do use just une request
to keep serialization.
So calls like:
rockusb_tx_write_str(emmc_id);
rockusb protocol has been introduced by Eddie Cai in U-Boot mainline
allowing to write internal eMMC of RK3288 based boards (and potentially
all other Rockchip's CPUs).
On workstation side the open source project rkdeveloptool do implement
the rockusb protocol. You can find it on GitHub here:
> From: Alexander Graf
> Date: Tue, 3 Jul 2018 22:08:05 +0200
>
> It's only ever been tested on ARM, so maybe the x86 Linux EFI stub
> behaves differently. If set_virtual_address_map needs to be intact after
> exiting boot services, we need to move all of the relocation information
> and
On 03.07.18 21:39, Heinrich Schuchardt wrote:
> On 07/03/2018 06:51 PM, Bin Meng wrote:
>> Hi Alex,
>>
>> On Tue, Jul 3, 2018 at 11:05 PM, Alexander Graf wrote:
>>> On 07/03/2018 04:56 PM, Bin Meng wrote:
Hi Alex,
On Tue, Jul 3, 2018 at 10:32 PM, Alexander Graf wrote:
>
On 07/03/2018 06:51 PM, Bin Meng wrote:
> Hi Alex,
>
> On Tue, Jul 3, 2018 at 11:05 PM, Alexander Graf wrote:
>> On 07/03/2018 04:56 PM, Bin Meng wrote:
>>>
>>> Hi Alex,
>>>
>>> On Tue, Jul 3, 2018 at 10:32 PM, Alexander Graf wrote:
On 07/03/2018 04:24 PM, Bin Meng wrote:
>
>
On 07/02/2018 04:10 PM, Joe Hershberger wrote:
On Thu, Jun 28, 2018 at 2:47 PM, Grygorii Strashko
wrote:
Now the UCLASS_ETH device "node" field is owerwritten by some network drivers in
case of Ethernet PHYs which are linked to UCLASS_ETH device using
"phy-handle" DT property and when
On Tue, Jul 3, 2018 at 11:46 PM, Marek Vasut wrote:
> On 07/03/2018 08:02 PM, Jagan Teki wrote:
>> On Tue, Jul 3, 2018 at 11:26 PM, Marek Vasut wrote:
>>> On 07/03/2018 07:09 PM, Jagan Teki wrote:
On Tue, Jul 3, 2018 at 10:14 PM, Marek Vasut wrote:
> On 07/03/2018 05:22 PM, Andre
On 07/03/2018 08:02 PM, Jagan Teki wrote:
> On Tue, Jul 3, 2018 at 11:26 PM, Marek Vasut wrote:
>> On 07/03/2018 07:09 PM, Jagan Teki wrote:
>>> On Tue, Jul 3, 2018 at 10:14 PM, Marek Vasut wrote:
On 07/03/2018 05:22 PM, Andre Przywara wrote:
> Hi,
>
> On 02/07/18 22:57, Marek
On Tue, Jul 3, 2018 at 11:26 PM, Marek Vasut wrote:
> On 07/03/2018 07:09 PM, Jagan Teki wrote:
>> On Tue, Jul 3, 2018 at 10:14 PM, Marek Vasut wrote:
>>> On 07/03/2018 05:22 PM, Andre Przywara wrote:
Hi,
On 02/07/18 22:57, Marek Vasut wrote:
> On 07/02/2018 11:40 PM, Tom Rini
On 07/03/2018 07:09 PM, Jagan Teki wrote:
> On Tue, Jul 3, 2018 at 10:14 PM, Marek Vasut wrote:
>> On 07/03/2018 05:22 PM, Andre Przywara wrote:
>>> Hi,
>>>
>>> On 02/07/18 22:57, Marek Vasut wrote:
On 07/02/2018 11:40 PM, Tom Rini wrote:
> On Mon, Jul 02, 2018 at 11:27:58PM +0200, Marek
On Tue, Jul 3, 2018 at 10:14 PM, Marek Vasut wrote:
> On 07/03/2018 05:22 PM, Andre Przywara wrote:
>> Hi,
>>
>> On 02/07/18 22:57, Marek Vasut wrote:
>>> On 07/02/2018 11:40 PM, Tom Rini wrote:
On Mon, Jul 02, 2018 at 11:27:58PM +0200, Marek Vasut wrote:
> On 07/02/2018 10:53 PM, Jagan
On 07/03/2018 05:10 PM, See, Chin Liang wrote:
> On Sat, 2018-06-23 at 06:23 +0200, Marek Vasut wrote:
>> On 06/23/2018 05:55 AM, Marek Vasut wrote:
>>>
>>> On 06/06/2018 08:47 PM, Marek Vasut wrote:
On 05/31/2018 12:00 PM, Marek Vasut wrote:
>
> On 05/31/2018 11:52 AM, See, Chin
Hi Alex,
On Tue, Jul 3, 2018 at 11:05 PM, Alexander Graf wrote:
> On 07/03/2018 04:56 PM, Bin Meng wrote:
>>
>> Hi Alex,
>>
>> On Tue, Jul 3, 2018 at 10:32 PM, Alexander Graf wrote:
>>>
>>> On 07/03/2018 04:24 PM, Bin Meng wrote:
Hi Alex, Heinrich,
At present not all
On 07/03/2018 06:25 PM, Jagan Teki wrote:
> On Tue, Jul 3, 2018 at 8:52 PM, Andre Przywara wrote:
>> Hi,
>>
>> On 02/07/18 22:57, Marek Vasut wrote:
>>> On 07/02/2018 11:40 PM, Tom Rini wrote:
On Mon, Jul 02, 2018 at 11:27:58PM +0200, Marek Vasut wrote:
> On 07/02/2018 10:53 PM, Jagan
On 07/03/2018 05:22 PM, Andre Przywara wrote:
> Hi,
>
> On 02/07/18 22:57, Marek Vasut wrote:
>> On 07/02/2018 11:40 PM, Tom Rini wrote:
>>> On Mon, Jul 02, 2018 at 11:27:58PM +0200, Marek Vasut wrote:
On 07/02/2018 10:53 PM, Jagan Teki wrote:
> During usb shutdown or 'usb reset' all the
Hi Tom,
Please pull this PR.
thanks,
Jagan.
The following changes since commit f58e779513be36e30ce46838fb467e12ac6a5539:
Merge tag 'arc-updates-for-2018.07-rc2' of git://git.denx.de/u-boot-arc
(2018-06-15 09:38:16 -0400)
are available in the Git repository at:
On Tue, Jul 3, 2018 at 5:20 PM, Guillaume Gardet
wrote:
>
>
> Le 03/07/2018 à 01:08, Andreas Färber a écrit :
>>
>> Am 02.07.2018 um 10:01 schrieb Jagan Teki:
>>>
>>> On Wed, Jun 27, 2018 at 6:12 AM, Andre Przywara
>>> wrote:
At the moment we have the workaround for the Freescale arch
On Tue, Jul 3, 2018 at 8:52 PM, Andre Przywara wrote:
> Hi,
>
> On 02/07/18 22:57, Marek Vasut wrote:
>> On 07/02/2018 11:40 PM, Tom Rini wrote:
>>> On Mon, Jul 02, 2018 at 11:27:58PM +0200, Marek Vasut wrote:
On 07/02/2018 10:53 PM, Jagan Teki wrote:
> During usb shutdown or 'usb reset'
From: Willy Tarreau
When kwboot is attached to a terminal which disappears such as one
connected via an unplugged USB cable, read() returns 0, making kwboot
loop until a key is pressed in the terminal. The only case where read()
may return 0 here is when the terminal is closed anyway, so let's
From: Willy Tarreau
Commit 84899e2 ("tools/kwboot: Sync with latest barebox version to
support Armada XP") accidently broke the terminal-only mode (-t) by
removing the test on the bootmsg. Thus even when trying to use kwboot
as a plain terminal, it asks to reboot the target.
This commit simply
On Mon, Jul 02, 2018 at 11:00:05AM +0100, Alex Kiernan wrote:
> On Mon, Jul 2, 2018 at 3:25 AM Tom Rini wrote:
> >
> > On Fri, Jun 29, 2018 at 09:19:34PM -0700, Simon Glass wrote:
> > > +Tom
> > >
> > > Hi Alex,
> > >
> > > On 29 June 2018 at 02:31, Alex Kiernan wrote:
> > > >
> > > > I've just
Hi Bharat,
Thanks for the review! Comments inline.
On 03.07.2018 17:09, Bharat Bhushan wrote:
>
>
>> -Original Message-
>> From: upstream-release-boun...@linux.freescale.net [mailto:upstream-
>> release-boun...@linux.freescale.net] On Behalf Of Laurentiu Tudor
>> Sent: Tuesday, July 3,
On 06/06/2018 04:16 AM, Pramod Kumar wrote:
> LS1012A-FRDM and LS1012A-FRWY board.
>
> 1-Move all common files applicable for both boards LS1012A-FRDM
> and LS1012A-FRWY into board directory ls1012afrx.
> 2-Restructure LS1012A-FRDM code. Only board specific files are
> in LS1012A-FRDM board
Hi,
On 02/07/18 22:57, Marek Vasut wrote:
> On 07/02/2018 11:40 PM, Tom Rini wrote:
>> On Mon, Jul 02, 2018 at 11:27:58PM +0200, Marek Vasut wrote:
>>> On 07/02/2018 10:53 PM, Jagan Teki wrote:
During usb shutdown or 'usb reset' all the necessary clocks
on the specific controller will
On Sat, 2018-06-23 at 06:23 +0200, Marek Vasut wrote:
> On 06/23/2018 05:55 AM, Marek Vasut wrote:
> >
> > On 06/06/2018 08:47 PM, Marek Vasut wrote:
> > >
> > > On 05/31/2018 12:00 PM, Marek Vasut wrote:
> > > >
> > > > On 05/31/2018 11:52 AM, See, Chin Liang wrote:
> > > > >
> > > > > On
On 07/03/2018 04:56 PM, Bin Meng wrote:
Hi Alex,
On Tue, Jul 3, 2018 at 10:32 PM, Alexander Graf wrote:
On 07/03/2018 04:24 PM, Bin Meng wrote:
Hi Alex, Heinrich,
At present not all interfaces in lib/efi_loader/efi_runtime.c are
declared as __efi_runtime. But only declaring those as
Hi Andy,
On Tue, Jul 3, 2018 at 6:42 PM, Andy Shevchenko
wrote:
> On Tue, 2018-07-03 at 02:48 -0700, Bin Meng wrote:
>> This converts all x86 boards over to DM sysreset.
>
>> -int do_reset(cmd_tbl_t *cmdtp, int flag, int argc, char * const
>> argv[])
>> -{
>> - printf("resetting ...\n");
>>
Hi Alex,
On Tue, Jul 3, 2018 at 10:32 PM, Alexander Graf wrote:
> On 07/03/2018 04:24 PM, Bin Meng wrote:
>>
>> Hi Alex, Heinrich,
>>
>> At present not all interfaces in lib/efi_loader/efi_runtime.c are
>> declared as __efi_runtime. But only declaring those as __efi_runtime
>> is not enough. The
On Tue, Jul 03, 2018 at 06:06:37PM +0530, Jagan Teki wrote:
> On Tue, Jul 3, 2018 at 3:10 AM, Tom Rini wrote:
> > On Mon, Jul 02, 2018 at 11:27:58PM +0200, Marek Vasut wrote:
> >> On 07/02/2018 10:53 PM, Jagan Teki wrote:
> >> > During usb shutdown or 'usb reset' all the necessary clocks
> >> >
Hi Prabhakar,
On Mon, Jul 2, 2018 at 11:27 PM, Prabhakar Kushwaha
wrote:
> Dear Bin,
>
> Coming back to x86 example.
>
>> -Original Message-
>> From: Bin Meng [mailto:bmeng...@gmail.com]
>> Sent: Friday, June 29, 2018 7:03 AM
>> To: York Sun
>> Cc: Simon Glass ; Prabhakar Kushwaha
>> ;
Hi Bharat,
Thanks for the review! Comments inline.
On 03.07.2018 16:38, Bharat Bhushan wrote:
>
>
>> -Original Message-
>> From: upstream-release-boun...@linux.freescale.net [mailto:upstream-
>> release-boun...@linux.freescale.net] On Behalf Of Laurentiu Tudor
>> Sent: Tuesday, July 3,
On 07/03/2018 04:24 PM, Bin Meng wrote:
Hi Alex, Heinrich,
At present not all interfaces in lib/efi_loader/efi_runtime.c are
declared as __efi_runtime. But only declaring those as __efi_runtime
is not enough. The data these interfaces use should be declared as
__efi_runtime_data too. More
Hi Alex, Heinrich,
At present not all interfaces in lib/efi_loader/efi_runtime.c are
declared as __efi_runtime. But only declaring those as __efi_runtime
is not enough. The data these interfaces use should be declared as
__efi_runtime_data too. More worse, any U-Boot APIs called by these
> -Original Message-
> From: upstream-release-boun...@linux.freescale.net [mailto:upstream-
> release-boun...@linux.freescale.net] On Behalf Of Laurentiu Tudor
> Sent: Tuesday, July 3, 2018 5:42 PM
> To: York Sun ; Prabhakar Kushwaha
> ; u-boot@lists.denx.de
> Cc: Laurentiu Tudor
>
On 07/03/2018 03:58 PM, Jason Rush wrote:
> On 6/29/2018 10:17 AM, Marek Vasut wrote:
>> On 06/29/2018 05:06 PM, Jason Rush wrote:
>>> On 6/29/2018 9:52 AM, Marek Vasut wrote:
On 06/29/2018 04:44 PM, Jason Rush wrote:
> On 6/29/2018 9:34 AM, Marek Vasut wrote:
>> On 06/29/2018 04:31
On 6/29/2018 10:17 AM, Marek Vasut wrote:
> On 06/29/2018 05:06 PM, Jason Rush wrote:
>> On 6/29/2018 9:52 AM, Marek Vasut wrote:
>>> On 06/29/2018 04:44 PM, Jason Rush wrote:
On 6/29/2018 9:34 AM, Marek Vasut wrote:
> On 06/29/2018 04:31 PM, Jason Rush wrote:
>> Dinh,
> Hi,
>
> -Original Message-
> From: upstream-release-boun...@linux.freescale.net [mailto:upstream-
> release-boun...@linux.freescale.net] On Behalf Of Laurentiu Tudor
> Sent: Tuesday, July 3, 2018 5:42 PM
> To: York Sun ; Prabhakar Kushwaha
> ; u-boot@lists.denx.de
> Cc: Laurentiu Tudor
>
On Tue, Jul 03, 2018 at 02:32:28PM +0200, Stefan Agner wrote:
> Hi Tom, Hi Stefano,
>
> On 02.07.2018 11:08, Patrick DELAUNAY wrote:
> > Hi Stefan
> >
> >> From: Stefan Agner [mailto:ste...@agner.ch]
> >> Sent: mercredi 27 juin 2018 10:36
> >> Subject: Re: [PATCH v1 1/5] ARM: PSCI: initialize
On Tue, Jul 3, 2018 at 3:10 AM, Tom Rini wrote:
> On Mon, Jul 02, 2018 at 11:27:58PM +0200, Marek Vasut wrote:
>> On 07/02/2018 10:53 PM, Jagan Teki wrote:
>> > During usb shutdown or 'usb reset' all the necessary clocks
>> > on the specific controller will disable. Usually this shutdown
>> >
Hi Tom, Hi Stefano,
On 02.07.2018 11:08, Patrick DELAUNAY wrote:
> Hi Stefan
>
>> From: Stefan Agner [mailto:ste...@agner.ch]
>> Sent: mercredi 27 juin 2018 10:36
>> Subject: Re: [PATCH v1 1/5] ARM: PSCI: initialize stack pointer on secondary
>> CPUs
>>
>> On 24.06.2018 21:09, Stefan Agner
Add support for ICID setting of qman portals and
the required device tree fixups.
Also fix an endiness issue in portal setup code.
Signed-off-by: Laurentiu Tudor
---
.../arm/cpu/armv8/fsl-layerscape/ls1046_ids.c | 16 +++
.../asm/arch-fsl-layerscape/fsl_portals.h | 23 ++
QMAN_BAR{E} register setup was disabled on ARM platforms,
however the register does need to be set. Add code that
sets it up on ARMs.
Signed-off-by: Laurentiu Tudor
---
drivers/misc/fsl_portals.c | 7 ++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git
Add infrastructure for ICID setup and device tree
fixup on ARM platforms. This include basic ICID setup
for several devices.
Signed-off-by: Laurentiu Tudor
---
arch/arm/cpu/armv8/fsl-layerscape/Makefile| 1 +
arch/arm/cpu/armv8/fsl-layerscape/icid.c | 111 ++
Add support for ICID setting of fman ports and
the required device tree fixups.
Signed-off-by: Laurentiu Tudor
---
arch/arm/cpu/armv8/fsl-layerscape/icid.c | 82 +++
.../arm/cpu/armv8/fsl-layerscape/ls1046_ids.c | 30 +++
.../asm/arch-fsl-layerscape/fsl_icid.h|
Add a define with a value for the missing debug stream ID.
Signed-off-by: Laurentiu Tudor
---
arch/arm/include/asm/arch-fsl-layerscape/stream_id_lsch2.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/include/asm/arch-fsl-layerscape/stream_id_lsch2.h
The QMan IP block in this SoC is version 3.2 so advertise
this in the SoC configuration header.
Signed-off-by: Laurentiu Tudor
---
arch/arm/include/asm/arch-fsl-layerscape/config.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/include/asm/arch-fsl-layerscape/config.h
Add defines for the edma and qdma register block base addresses.
Signed-off-by: Laurentiu Tudor
---
arch/arm/include/asm/arch-fsl-layerscape/immap_lsch2.h | 4
1 file changed, 4 insertions(+)
diff --git a/arch/arm/include/asm/arch-fsl-layerscape/immap_lsch2.h
This patch series adds the required devices setup and device tree
fixups for SMMU enablement on LS1046A chips. The approach taken tries
to mimic the implementation of PAMU LIODN setup on booke powerpc.
First 4 patches contain some fixes and add some missing bits & pieces.
Last 3 patches add the
Le 03/07/2018 à 01:08, Andreas Färber a écrit :
Am 02.07.2018 um 10:01 schrieb Jagan Teki:
On Wed, Jun 27, 2018 at 6:12 AM, Andre Przywara wrote:
At the moment we have the workaround for the Freescale arch timer
erratum A-008585 merged into the generic timer_read_counter() routine.
Split
Dear Andy,
In message <18255ae55e4faa5733fb8e93dc8ebbc1559a3694.ca...@linux.intel.com> you
wrote:
...
> > This converts all x86 boards over to DM sysreset.
>
> > -int do_reset(cmd_tbl_t *cmdtp, int flag, int argc, char * const
> > argv[])
> > -{
> > - printf("resetting ...\n");
> > -
> > -
On Tue, 2018-07-03 at 02:48 -0700, Bin Meng wrote:
> This converts all x86 boards over to DM sysreset.
> -int do_reset(cmd_tbl_t *cmdtp, int flag, int argc, char * const
> argv[])
> -{
> - printf("resetting ...\n");
> -
> - /* wait 50 ms */
> - udelay(5);
> -
On 07/03/2018 12:08 PM, Andre Przywara wrote:
> Hi,
Hi,
> On 03/07/18 09:24, Marek Vasut wrote:
>> On 07/03/2018 01:44 AM, Andre Przywara wrote:
>>> The USB host controllers on the H3, H5 and A64 have the oddity of
>>> sharing some clock and reset gates, so both the OHCI and EHCI bits have
>>>
On 07/03/2018 12:11 PM, Andre Przywara wrote:
> Hi,
>
> On 03/07/18 07:19, Jagan Teki wrote:
>> On Tue, Jul 3, 2018 at 5:14 AM, Andre Przywara
>> wrote:
>>> The USB host controllers on the H3, H5 and A64 have the oddity of
>>> sharing some clock and reset gates, so both the OHCI and EHCI bits
On Tue, Jul 3, 2018 at 3:41 PM, Andre Przywara wrote:
> Hi,
>
> On 03/07/18 07:19, Jagan Teki wrote:
>> On Tue, Jul 3, 2018 at 5:14 AM, Andre Przywara
>> wrote:
>>> The USB host controllers on the H3, H5 and A64 have the oddity of
>>> sharing some clock and reset gates, so both the OHCI and
Hello Tom,
Am 03.07.2018 um 05:25 schrieb Tom Rini:
Hey all,
It's a week until release and I've put out v2018.07-rc3. I think things
are looking good for release, but I do want to see what we can / can't
Yes, my tbot tests last night looking good (Ok, just the last 2 boards
got the rc3
Hi,
On 03/07/18 07:19, Jagan Teki wrote:
> On Tue, Jul 3, 2018 at 5:14 AM, Andre Przywara wrote:
>> The USB host controllers on the H3, H5 and A64 have the oddity of
>> sharing some clock and reset gates, so both the OHCI and EHCI bits have
>> to be enabled to make only one of them working. We
Hi,
On 03/07/18 09:24, Marek Vasut wrote:
> On 07/03/2018 01:44 AM, Andre Przywara wrote:
>> The USB host controllers on the H3, H5 and A64 have the oddity of
>> sharing some clock and reset gates, so both the OHCI and EHCI bits have
>> to be enabled to make only one of them working. We take care
On Tue, Jul 3, 2018 at 1:54 PM, Marek Vasut wrote:
> On 07/03/2018 01:44 AM, Andre Przywara wrote:
>> The USB host controllers on the H3, H5 and A64 have the oddity of
>> sharing some clock and reset gates, so both the OHCI and EHCI bits have
>> to be enabled to make only one of them working. We
This converts all x86 boards over to DM sysreset.
Signed-off-by: Bin Meng
---
arch/Kconfig | 2 ++
arch/x86/cpu/baytrail/valleyview.c| 6 --
arch/x86/cpu/braswell/braswell.c | 6 --
arch/x86/cpu/cpu.c
In preparation for the reset driver conversion, eliminate the
reset_cpu() call in the FSP init path as it's too early for the
reset driver to work.
Signed-off-by: Bin Meng
---
arch/x86/lib/fsp/fsp_common.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
This adds a generic reset driver for x86 processor.
Signed-off-by: Bin Meng
---
drivers/sysreset/Kconfig| 6 +
drivers/sysreset/Makefile | 1 +
drivers/sysreset/sysreset_x86.c | 49 +
3 files changed, 56 insertions(+)
create mode
This adds full reset bit in the reset register value in the ACPI FADT
table, so that kernel can do a thorough reboot.
Signed-off-by: Bin Meng
---
arch/x86/cpu/quark/acpi.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/cpu/quark/acpi.c b/arch/x86/cpu/quark/acpi.c
Hi Peng
Ok I have fixed it :)
Michael
On Mon, Jul 2, 2018 at 4:26 PM, Michael Nazzareno Trimarchi
wrote:
> Hi Peng
>
> I'm working to make persistent the uboot logo on imx6ull platform but
> I have some problem with the framebuffer. Now this is the main idea
>
> I use this to recalculate
On 07/03/2018 01:44 AM, Andre Przywara wrote:
> The USB host controllers on the H3, H5 and A64 have the oddity of
> sharing some clock and reset gates, so both the OHCI and EHCI bits have
> to be enabled to make only one of them working. We take care of this, and
> initialisation works fine (due
On Mon, Jul 02, 2018 at 11:57:45PM +0200, Marek Vasut wrote:
> On 07/02/2018 11:40 PM, Tom Rini wrote:
> > On Mon, Jul 02, 2018 at 11:27:58PM +0200, Marek Vasut wrote:
> >> On 07/02/2018 10:53 PM, Jagan Teki wrote:
> >>> During usb shutdown or 'usb reset' all the necessary clocks
> >>> on the
On Tue, Jul 3, 2018 at 5:14 AM, Andre Przywara wrote:
> The USB host controllers on the H3, H5 and A64 have the oddity of
> sharing some clock and reset gates, so both the OHCI and EHCI bits have
> to be enabled to make only one of them working. We take care of this, and
> initialisation works
On 07/03/2018 07:29 AM, Takahiro AKASHI wrote:
> On Tue, Jul 03, 2018 at 04:07:31AM +0200, Heinrich Schuchardt wrote:
>> On 07/03/2018 01:51 AM, Takahiro AKASHI wrote:
>>> On Mon, Jul 02, 2018 at 07:07:55PM +0300, Tuomas Tynkkynen wrote:
Hi Heinrich,
On 06/29/2018 01:34 AM, Heinrich
96 matches
Mail list logo
