linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: andrew@lunn.ch (Andrew Lunn)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] maintainership update for the Marvell Orion family of SOCs
Date: Tue, 1 May 2012 10:48:29 +0200	[thread overview]
Message-ID: <20120501084829.GF15541@lunn.ch> (raw)
In-Reply-To: <201204302217.35958.arnd@arndb.de>

> Well, there is no reason to rush this at all, it could live in parallel
> for a couple of years. But at one point we can decide that if nobody has
> bothered to write the .dts file for one board and tested it that nobody
> cares about that board any more and it can just get removed and possibly
> added back in dts form when someone does complain.

Probably a FAQ, but maybe somebody can point me in the right
direction. How will Debian, Ubuntu, etc, deal with old machines who's
u-boot does not support DT, yet the kernel has moved on and only has
DT support for a board? Will the kernel install process need to
determine what board the machine is and append the DT to the end of
the kernel? Or do we envisage a process where all DT are appended to
the kernel, and the machine ID, as passed by the old uboot, is used to
pick the correct DT?

    Thanks
	Andrew

  reply	other threads:[~2012-05-01  8:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-30 17:44 [PATCH] maintainership update for the Marvell Orion family of SOCs Nicolas Pitre
2012-04-30 17:48 ` Jason Cooper
2012-04-30 18:33   ` Arnd Bergmann
2012-04-30 18:38     ` Andrew Lunn
2012-04-30 20:48 ` Arnaud Patard (Rtp)
2012-04-30 21:24   ` Arnd Bergmann
2012-04-30 21:53     ` Arnaud Patard (Rtp)
2012-04-30 22:17       ` Arnd Bergmann
2012-05-01  8:48         ` Andrew Lunn [this message]
2012-05-02 13:05           ` Arnd Bergmann
2012-04-30 21:25 ` Arnd Bergmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20120501084829.GF15541@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).