> On Aug 16, 2021, at 9:11 AM, Michael van Elst wrote:
>
> On Mon, Aug 16, 2021 at 06:46:17AM -0700, Jason Thorpe wrote:
>>
>>> On Aug 16, 2021, at 2:31 AM, Michael van Elst wrote:
>>> Isn't that what we do today? Have a common name and value format,
>>> copied/translated from various
On Mon, Aug 16, 2021 at 06:46:17AM -0700, Jason Thorpe wrote:
>
> > On Aug 16, 2021, at 2:31 AM, Michael van Elst wrote:
> > Isn't that what we do today? Have a common name and value format,
> > copied/translated from various sources and stored in the MI device
> > dictionary.
>
> We sort of
> On Aug 16, 2021, at 2:31 AM, Michael van Elst wrote:
>
> j...@coris.org.uk (Julian Coleman) writes:
>
>> We can decide on the name that we'll use (e.g. `ethernet_address') and
>> use that in all the drivers.
>
> Isn't that what we do today? Have a common name and value format,
>
j...@coris.org.uk (Julian Coleman) writes:
>We can decide on the name that we'll use (e.g. `ethernet_address') and
>use that in all the drivers.
Isn't that what we do today? Have a common name and value format,
copied/translated from various sources and stored in the MI device
dictionary.
Hi,
> How do I know what properties are going to be available in a driver?
> Is it part of an internal kernel<->kernel interface like device
> properties, or just whatever is passed through the OF/FDT or ACPI
> firmware?
I think that we need a standard form for each type of information. The
