On 03/25/2018 10:11 PM, Heinrich Schuchardt wrote:
> On 03/25/2018 07:31 PM, Patrick Wildt wrote:
>> On Fri, Mar 23, 2018 at 07:58:07PM +0100, Heinrich Schuchardt wrote:
>>> On 03/23/2018 07:54 PM, Heinrich Schuchardt wrote:
>From c38a011f699cf5a41b48c6fc547f3d0dde3d7cf9 Mon Sep 17 00:00:00 20
On 03/25/2018 10:23 PM, Patrick Wildt wrote:
> On Sun, Mar 25, 2018 at 10:04:55PM +0200, Heinrich Schuchardt wrote:
>> Thank you for the explanation. I think the right way go ahead is to add
>> all missing fields and to do away with unused[].
>>
>> Please, carefully observe the alignment. The spec
Hi Joe,
On Sat, Mar 24, 2018 at 1:11 AM, Joe Hershberger wrote:
> On Thu, Mar 22, 2018 at 9:46 AM, Bin Meng wrote:
>> Hi,
>>
>> On Fri, Feb 2, 2018 at 9:53 PM, Stefan Mavrodiev wrote:
>>> CONFIG_PHY_ADDR is used for old-style configuration. This makes
>>> impossible changing the PHY address, if
On Sat, 2016-12-03 at 11:40 -0700, Simon Glass wrote:
> Hi Mugunthan,
>
> On 17 November 2016 at 02:08, Mugunthan V N
> wrote:
> > Add a TI MUSB peripheral driver with driver model support and the
> > driver will be bound by the MUSB wrapper driver based on the
> > dr_mode device tree entry.
See
On Sun, Mar 25, 2018 at 10:04:55PM +0200, Heinrich Schuchardt wrote:
> Thank you for the explanation. I think the right way go ahead is to add
> all missing fields and to do away with unused[].
>
> Please, carefully observe the alignment. The spec defines BOOLEAN as
> 8bit value. ToS is the 19th b
On 03/25/2018 07:31 PM, Patrick Wildt wrote:
> On Fri, Mar 23, 2018 at 07:58:07PM +0100, Heinrich Schuchardt wrote:
>> On 03/23/2018 07:54 PM, Heinrich Schuchardt wrote:
>>> >From c38a011f699cf5a41b48c6fc547f3d0dde3d7cf9 Mon Sep 17 00:00:00 2001
>>> From: Patrick Wildt
>>> Date: Fri, 23 Mar 2018 1
On 03/25/2018 07:44 PM, Patrick Wildt wrote:
> On Fri, Mar 23, 2018 at 08:04:27PM +0100, Heinrich Schuchardt wrote:
>> On 03/23/2018 08:01 PM, Heinrich Schuchardt wrote:
>>> >From 689ada7663efae5ef13d021f3266e081d1d53293 Mon Sep 17 00:00:00 2001
>>> From: Patrick Wildt
>>> Date: Fri, 23 Mar 2018 1
On 03/25/2018 07:54 PM, Patrick Wildt wrote:
> Since the backing memory for a new device path can contain stale
> data we have to make sure that we zero the buffer. Otherwise some
> code paths that don't set all fields in a structure backed by this
> device path might contain unwanted stale data.
On Sun, Mar 25, 2018 at 3:22 PM, Jagan Teki wrote:
> Now, MX6 has proper CONFIG names so rename the SYS_SOC to
> imx6 from mx6 and also change related files.
>
> Signed-off-by: Jagan Teki
> ---
> .travis.yml| 4 ++--
> arch/arm/Kconfig
Now, we have proper CONFIG_SOC_ names for i.MX6 SOC types,
so use the same for building dtbs.
Signed-off-by: Jagan Teki
---
arch/arm/dts/Makefile | 44 ++--
1 file changed, 26 insertions(+), 18 deletions(-)
diff --git a/arch/arm/dts/Makefile b/arch/arm/dt
u-boot,dm-spl property is specific to U-Boot, so move it into
*u-boot.dtsi files for relevant i.MX6UL files.
This make syncing Linux dts files straight forward.
Also update the MAINTAINERS file for dts files.
Signed-off-by: Jagan Teki
---
arch/arm/dts/imx6ul-geam-kit-u-boot.dtsi | 25 +++
Move usdhc2 node along with pinctrl to imx6ul-isiot.dts
from imx6ul-isiot-emmc.dts
Signed-off-by: Jagan Teki
---
arch/arm/dts/imx6ul-isiot-emmc.dts | 24
arch/arm/dts/imx6ul-isiot.dtsi | 26 ++
2 files changed, 26 insertions(+), 24 deletions(-
u-boot,dm-spl property is specific to U-Boot, so move it into
*u-boot.dtsi files for relevant i.MX6QDL files.
This make syncing Linux dts files straight forward.
Also update the MAINTAINERS file for dts files.
Signed-off-by: Jagan Teki
---
arch/arm/dts/imx6dl-icore-mipi-u-boot.dtsi | 11 ++
Now, MX6 has proper CONFIG names so rename the SYS_SOC to
imx6 from mx6 and also change related files.
Signed-off-by: Jagan Teki
---
.travis.yml| 4 ++--
arch/arm/Kconfig | 2 +-
arch/arm/Makefile
This series add proper CONFIG names for i.MX6 architecture code,
where CONFIG_MX6 become CONFIG_ARCH_IMX6 and rest of SOC types
like CONFIG_MX6Q become CONFIG_SOC_IMX6Q which is similar to Linux.
patch 1: Update new CONFIG names globally to all files for i.MX6 code
patch 2: Change SYS_SOC from mx
From: Duncan Hare
All the code is new, and not copied from any source.
Series-changes
The previous patch was using an old version of net/Kconfig,
which prevented requesting options for a bootp/dhcp request.
A similar issue fixed with a cmd/Kconfig.
Items in include/net.h fixed.
Signed-off-by:
From: Duncan Hare
Why http and wget:
HTTP is the most efficient file retrieval protocol in common
use. The client send a single request, after TCP connection,
to receive a file of any length.
WGET is the application which implements http file transfer
outside browsers as a file transfer protoco
From: Duncan Hare
cover-letter:
Why netboot:
Central management, including logs and change control,
coupled with with enhanced security and unauthorized
change detection and remediation by exposing a
small attack surface.
Why TCP:
Currently file transfer are done using tftp or NFS both
over udp
Since the backing memory for a new device path can contain stale
data we have to make sure that we zero the buffer. Otherwise some
code paths that don't set all fields in a structure backed by this
device path might contain unwanted stale data.
Signed-off-by: Patrick Wildt
---
lib/efi_loader/ef
On Fri, Mar 23, 2018 at 08:04:27PM +0100, Heinrich Schuchardt wrote:
> On 03/23/2018 08:01 PM, Heinrich Schuchardt wrote:
> >>From 689ada7663efae5ef13d021f3266e081d1d53293 Mon Sep 17 00:00:00 2001
> > From: Patrick Wildt
> > Date: Fri, 23 Mar 2018 15:38:48 +0100
> > Subject: [PATCH 2/2] efi_loader
On Fri, Mar 23, 2018 at 07:58:07PM +0100, Heinrich Schuchardt wrote:
> On 03/23/2018 07:54 PM, Heinrich Schuchardt wrote:
> >>From c38a011f699cf5a41b48c6fc547f3d0dde3d7cf9 Mon Sep 17 00:00:00 2001
> > From: Patrick Wildt
> > Date: Fri, 23 Mar 2018 15:36:58 +0100
> > Subject: [PATCH 1/2] efi_loader
On Sun, Mar 25, 2018 at 3:34 PM, Wolfgang Denk wrote:
> Dear Alex,
>
> In message
> you
> wrote:
>>
>> > Why can't you just "env import"
>> > these additional fragments as part of your hard coded startup
>> > sequence?
>>
>> Other than wanting to filter the variables that can come in that way,
Dear Alex,
In message
you wrote:
>
> > Why can't you just "env import"
> > these additional fragments as part of your hard coded startup
> > sequence?
>
> Other than wanting to filter the variables that can come in that way,
> it does everything I need. In fact with sufficient care I probably
On Sun, Mar 25, 2018 at 11:50 AM, Wolfgang Denk wrote:
> Dear Alex,
>
> In message
> you
> wrote:
>> I'm trying to set up a configuration where I've largely got a hardcoded
>> environment (ENV_IS_NOWHERE) with a very small list of variables that come
>> from a loadable environment (ENV_IS_IN_FA
Spam detection software, running on the system "lists.denx.de",
has identified this incoming email as possible spam. The original
message has been attached to this so you can view it or label
similar future email. If you have any questions, see
@@CONTACT_ADDRESS@@ for details.
Content preview:
Spam detection software, running on the system "lists.denx.de",
has identified this incoming email as possible spam. The original
message has been attached to this so you can view it or label
similar future email. If you have any questions, see
@@CONTACT_ADDRESS@@ for details.
Content preview:
Spam detection software, running on the system "lists.denx.de",
has identified this incoming email as possible spam. The original
message has been attached to this so you can view it or label
similar future email. If you have any questions, see
@@CONTACT_ADDRESS@@ for details.
Content preview:
Hi everybody,
sorry for asking stupid questions, but you are my last hope for getting this
working...
What I would like to do, is embedding this script:
https://github.com/rauc/rauc/blob/master/contrib/uboot.sh
Into u-Boot with Yocto: ./mkimage -T script -A arm -C none -n 'Redundant Boot'
-d c
Dear Alex,
In message
you wrote:
> I'm trying to set up a configuration where I've largely got a hardcoded
> environment (ENV_IS_NOWHERE) with a very small list of variables that come
> from a loadable environment (ENV_IS_IN_FAT for my use case) - things like
> serial# and regulatory region. Eve
I'm trying to set up a configuration where I've largely got a hardcoded
environment (ENV_IS_NOWHERE) with a very small list of variables that come
from a loadable environment (ENV_IS_IN_FAT for my use case) - things like
serial# and regulatory region. Even then I want them largely set once in
the f
30 matches
Mail list logo
