openbmc Digest, Vol 32, Issue 32

Wang, Haiyue at
Fri Apr 13 15:11:23 AEST 2018

On 2018-04-13 12:43, Benjamin Herrenschmidt wrote:
> On Thu, 2018-04-12 at 16:42 +0800, Wang, Haiyue wrote:
>> I means the device tree merge time, putting things in kernel need long time
>> to be passed code review. And people may want to export different range of
>> registers, then they need to change the device tree, the development cycle
>> may be long.
> But that's not a big issue in practice though, you don't*need*  all
> your device-trees to be upstream and up to date especially if it's
> stored separately from the kernel.
> Keep in mind this should be strictly limited to a few registers that
> need that sort of manipulation, maybe a handful or two, that's it.
> Most things need proper kernel drivers.
Understood, NOT exposing like /dev/mem makes sense for security.


More information about the openbmc mailing list