lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Tue, 1 Sep 2020 14:30:30 +0200
From:   Andrew Lunn <andrew@...n.ch>
To:     Marco Felsch <m.felsch@...gutronix.de>
Cc:     Florian Fainelli <f.fainelli@...il.com>, davem@...emloft.net,
        kuba@...nel.org, robh+dt@...nel.org, hkallweit1@...il.com,
        linux@...linux.org.uk, zhengdejin5@...il.com,
        richard.leitner@...data.com, netdev@...r.kernel.org,
        devicetree@...r.kernel.org, kernel@...gutronix.de
Subject: Re: [PATCH 4/5] net: phy: smsc: add phy refclk in support

> Yes, I got this.
> 
> > , or assuming a prior state,
> 
> This is the our case. Isn't it the purpose of the bootloader to setup
> the HW?

This is a bit of a philosophical discussion. For PCs developers would
definitely agree, the firmware should be setting up most of the
hardware. And the firmware is involved in driving the hardware, via
ACPI. That works because you mostly cannot replaces the firmware.

In the ARM world we tend to take the opposite view. The bootloader
does the minimum to get the OS running, and the OS then setups up
everything. Often there are a choice of bootloaders, you have no idea
if the vendor bootload has been replaced by a mainline one with extra
features, etc. And we have no idea what the bootloader is actually
doing, so we try to assume nothing.

       Andrew

Powered by blists - more mailing lists