From mboxrd@z Thu Jan  1 00:00:00 1970
From: Patrick Wildt <patrick@blueri.se>
Date: Mon, 4 Feb 2019 17:43:09 +0100
Subject: [U-Boot] [PATCH 2/2] efi_loader: set the dhcp ack received flag
In-Reply-To: <12c99515-030e-3cd6-1eca-cb839d47b00b@gmx.de>
References: <20180327122405.GB94872@nyx.local>
 <51ad49ad-05ec-c502-5b16-5abc61418413@gmx.de>
 <141d2897-07ae-f1ef-bb01-83cd49d792fd@suse.de>
 <20190131142525.GA37117@nyx.local>
 <22d7dfc2-6013-00e4-b477-0c7d4151dceb@suse.de>
 <20190131145423.GA37343@nyx.local>
 <12c99515-030e-3cd6-1eca-cb839d47b00b@gmx.de>
Message-ID: <20190204164308.GA5200@nyx.local>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

On Thu, Jan 31, 2019 at 07:29:04PM +0100, Heinrich Schuchardt wrote:
> On 1/31/19 3:54 PM, Patrick Wildt wrote:
> > On Thu, Jan 31, 2019 at 03:31:34PM +0100, Alexander Graf wrote:
> >> Is there any way to pass an object reference in as parameter that allows us
> >> to find the exact efi net object back again? IIRC the network code was
> >> pretty much single target, but maybe we don't have to encode that in every
> >> single place ...
> > 
> > I agree, but I have to say that I don't know the u-boot code enough to
> > know that.
> 
> The current network device can be determined via eth_get_dev().
> In function eth_current_changed() this eth_get_dev() function is used to
> update the ethact environment variable.
> 
> If we have a single update function we can determine the active network
> device there.
> 
> Best regards
> 
> Heinrich

Looks like you know what to do.

Best regards,
Patrick