On Wed, Feb 24, 2021 at 05:14:10PM -0600, Frank Rowand wrote:
> On 2/24/21 7:00 AM, Enrico Weigelt, metux IT consult wrote:
> > On 15.02.21 02:12, Frank Rowand wrote:
> >
> >> Why not compile in ACPI data (tables?) instead of devicetree description?
> >
> > The problem is a bit more complex than
On 2/24/21 7:00 AM, Enrico Weigelt, metux IT consult wrote:
> On 15.02.21 02:12, Frank Rowand wrote:
>
>> Why not compile in ACPI data (tables?) instead of devicetree description?
>
> The problem is a bit more complex than it might seem.
>
> Let's take the APU2/37/4 boards as an example.
On 15.02.21 02:12, Frank Rowand wrote:
Why not compile in ACPI data (tables?) instead of devicetree description?
The problem is a bit more complex than it might seem.
Let's take the APU2/37/4 boards as an example. They've got some aux
devices, eg. some gpio controller, and some things (leds,
On Mon, Feb 15, 2021 at 3:15 AM Frank Rowand wrote:
> On 2/8/21 5:48 PM, Rob Herring wrote:
> > On Mon, Feb 8, 2021 at 4:22 PM Enrico Weigelt, metux IT consult
> > wrote:
> >>
> >> Hello folks,
> >>
> >> here's an RFC for using compiled-in dtb's for initializing board devices
> >> that can't be
On 2/8/21 5:48 PM, Rob Herring wrote:
> +Johan H
>
> On Mon, Feb 8, 2021 at 4:22 PM Enrico Weigelt, metux IT consult
> wrote:
>>
>> Hello folks,
>>
>> here's an RFC for using compiled-in dtb's for initializing board devices
>> that can't be probed via bus'es or firmware.
I've just been
On 11.02.21 12:41, Andy Shevchenko wrote:
Hi,
On Thu, Feb 11, 2021 at 1:15 PM Enrico Weigelt, metux IT consult
wrote:
On 10.02.21 11:30, Andy Shevchenko wrote:
Use cases are boards with non-oftree firmware (ACPI, etc) where certain
platform devices can't be directly enumerated via
On Thu, Feb 11, 2021 at 1:15 PM Enrico Weigelt, metux IT consult
wrote:
> On 10.02.21 11:30, Andy Shevchenko wrote:
> >> Use cases are boards with non-oftree firmware (ACPI, etc) where certain
> >> platform devices can't be directly enumerated via firmware. Traditionally
> >> we had to write
On 10.02.21 11:30, Andy Shevchenko wrote:
Hi,
Use cases are boards with non-oftree firmware (ACPI, etc) where certain
platform devices can't be directly enumerated via firmware. Traditionally
we had to write board specific drivers that check for board identification
(DMI strings, etc), then
On 09.02.21 00:48, Rob Herring wrote:
Hi,
here's an RFC for using compiled-in dtb's for initializing board devices
that can't be probed via bus'es or firmware.
I'm not convinced compiled in is the mechanism we want.
To make it clear, I'm talking of DTBs compiled into the ofboard driver
On Tue, Feb 9, 2021 at 12:25 AM Enrico Weigelt, metux IT consult
wrote:
>
> Hello folks,
>
> here's an RFC for using compiled-in dtb's for initializing board devices
> that can't be probed via bus'es or firmware.
>
> Use cases are boards with non-oftree firmware (ACPI, etc) where certain
>
+Johan H
On Mon, Feb 8, 2021 at 4:22 PM Enrico Weigelt, metux IT consult
wrote:
>
> Hello folks,
>
> here's an RFC for using compiled-in dtb's for initializing board devices
> that can't be probed via bus'es or firmware.
I'm not convinced compiled in is the mechanism we want.
> Use cases are
Hello folks,
here's an RFC for using compiled-in dtb's for initializing board devices
that can't be probed via bus'es or firmware.
Use cases are boards with non-oftree firmware (ACPI, etc) where certain
platform devices can't be directly enumerated via firmware. Traditionally
we had to write
12 matches
Mail list logo
