Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1567488

Re: How to ensure other module/driver is initialized?

Show all headers | View raw

On Tue, Jan 24, 2017 at 5:40 PM, Ian Pilcher <arequipeno@gmail.com> wrote:

> Device tree presents even greater problems.  It's not clear to me that
> device tree even works with x86_64, and even if it does, I'm almost
> positive that none of the "generic" distributions are going to support
> it.
>
> If my understanding of device tree is inaccurate, please do let me
> know.  I'd definitely like to replace the "board" module with a
> device tree description if it's possible.

Sorry for my ignorance. I thought this was some ARM or MIPS thing.

It should indeed come in as a board file for x86 systems,
unless they have ACPI to do what DT does on other platforms,
which modern systems do.

The way on these systems is to put a file in
drivers/platform/x86/* I think, but I know too little about
x86 for that.

I do think it'll be accepted upstream nevertheless, we do not
really count users but rather check whether the code is nice
and maintainable.

Yours,
Linus Walleij

Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

Re: How to ensure other module/driver is initialized? Linus Walleij <linus.walleij@linaro.org> - 2017-01-24 14:10 +0100
  Re: How to ensure other module/driver is initialized? Ian Pilcher <arequipeno@gmail.com> - 2017-01-24 17:50 +0100
    Re: How to ensure other module/driver is initialized? Linus Walleij <linus.walleij@linaro.org> - 2017-01-26 16:00 +0100

csiph-web