From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] maintainership update for the Marvell Orion family of SOCs
Date: Wed, 2 May 2012 13:05:17 +0000 [thread overview]
Message-ID: <201205021305.18248.arnd@arndb.de> (raw)
In-Reply-To: <20120501084829.GF15541@lunn.ch>
On Tuesday 01 May 2012, Andrew Lunn wrote:
> > 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?
I think that is the most likely scenario. Another option would be
to provide a replacement or second-stage boot loader that actually
understands DT and that gets loaded instead of the kernel by the
first-stage boot loader.
> 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?
This has been discussed in the past, but IIRC we decided against putting
that logic into the kernel. Folks on devicetree-discuss at l.o.o might remember
the details better than me.
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>
To: linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Cc: Andrew Lunn <andrew-g2DYL2Zd6BY@public.gmane.org>,
Jason Cooper <jason-NLaQJdtUoK4Be96aLqz0jA@public.gmane.org>,
devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
arm-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
Lennert Buytenhek
<kernel-OLH4Qvv75CYX/NnBR394Jw@public.gmane.org>,
Arnaud Patard
<arnaud.patard-dQbF7i+pzddAfugRpC6u6w@public.gmane.org>
Subject: Re: [PATCH] maintainership update for the Marvell Orion family of SOCs
Date: Wed, 2 May 2012 13:05:17 +0000 [thread overview]
Message-ID: <201205021305.18248.arnd@arndb.de> (raw)
In-Reply-To: <20120501084829.GF15541-g2DYL2Zd6BY@public.gmane.org>
On Tuesday 01 May 2012, Andrew Lunn wrote:
> > 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?
I think that is the most likely scenario. Another option would be
to provide a replacement or second-stage boot loader that actually
understands DT and that gets loaded instead of the kernel by the
first-stage boot loader.
> 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?
This has been discussed in the past, but IIRC we decided against putting
that logic into the kernel. Folks on devicetree-discuss@l.o.o might remember
the details better than me.
Arnd
next prev parent reply other threads:[~2012-05-02 13:05 UTC|newest]
Thread overview: 12+ 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
2012-05-02 13:05 ` Arnd Bergmann [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=201205021305.18248.arnd@arndb.de \
--to=arnd@arndb.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.