Re: [PATCH 1/2] net: rt8169: WAR for DHCP not getting IP after kernel boot/reboot

2020-06-12 Thread Tom Rini
On Thu, Mar 26, 2020 at 03:59:13PM -0700, tomcwarren3...@gmail.com wrote: > From: Tom Warren > > This is a WAR for DHCP failure after rebooting from the L4T kernel. The > r8169.c kernel driver is setting bit 19 of the rt816x HW register 0xF0, > which goes by FuncEvent and MISC in various driver

RE: [PATCH 1/2] net: rt8169: WAR for DHCP not getting IP after kernel boot/reboot

2020-03-19 Thread Tom Warren
-Original Message- From: Thierry Reding Sent: Thursday, March 19, 2020 1:04 AM To: Tom Warren Cc: u-boot@lists.denx.de; Stephen Warren ; Jonathan Hunter ; tomcwarren3...@gmail.com Subject: Re: [PATCH 1/2] net: rt8169: WAR for DHCP not getting IP after kernel boot/reboot On Tue, Mar

Re: [PATCH 1/2] net: rt8169: WAR for DHCP not getting IP after kernel boot/reboot

2020-03-19 Thread Thierry Reding
On Tue, Mar 17, 2020 at 01:07:15PM -0700, twar...@nvidia.com wrote: > From: Tom Warren > > This is a WAR for DHCP failure after rebooting from the L4T kernel. The > r8169.c kernel driver is setting bit 19 of the rt816x HW register 0xF0, > which goes by FuncEvent and MISC in various driver source/

RE: [PATCH 1/2] net: rt8169: WAR for DHCP not getting IP after kernel boot/reboot

2020-03-18 Thread Tom Warren
-Original Message- From: Stephen Warren Sent: Wednesday, March 18, 2020 4:30 PM To: Tom Warren Cc: u-boot@lists.denx.de; Stephen Warren ; Thierry Reding ; Jonathan Hunter ; tomcwarren3...@gmail.com Subject: Re: [PATCH 1/2] net: rt8169: WAR for DHCP not getting IP after kernel boot

Re: [PATCH 1/2] net: rt8169: WAR for DHCP not getting IP after kernel boot/reboot

2020-03-18 Thread Stephen Warren
On 3/17/20 2:07 PM, twar...@nvidia.com wrote: > From: Tom Warren > > This is a WAR for DHCP failure after rebooting from the L4T kernel. The > r8169.c kernel driver is setting bit 19 of the rt816x HW register 0xF0, > which goes by FuncEvent and MISC in various driver source/datasheets. > That bit