[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190625035313.GA13239@kroah.com>
Date: Tue, 25 Jun 2019 11:53:13 +0800
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Sandeep Patil <sspatil@...roid.com>
Cc: Saravana Kannan <saravanak@...gle.com>,
Rob Herring <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....com>,
"Rafael J. Wysocki" <rafael@...nel.org>,
Frank Rowand <frowand.list@...il.com>,
David Collins <collinsd@...eaurora.org>,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
kernel-team@...roid.com
Subject: Re: [RESEND PATCH v1 0/5] Solve postboot supplier cleanup and
optimize probe ordering
On Mon, Jun 24, 2019 at 03:37:07PM -0700, Sandeep Patil wrote:
> We are trying to make sure that all (most) drivers in an Aarch64 system can
> be kernel modules for Android, like any other desktop system for
> example. There are a number of problems we need to fix before that happens
> ofcourse.
I will argue that this is NOT an android-specific issue. If the goal of
creating an arm64 kernel that will "just work" for a wide range of
hardware configurations without rebuilding is going to happen, we need
to solve this problem with DT. This goal was one of the original wishes
of the arm64 development effort, let's not loose sight of it as
obviously, this is not working properly just yet.
It just seems that Android is the first one to actually try and
implement that goal :)
thanks,
greg k-h
Powered by blists - more mailing lists