From: Mason <slash.tmp@free.fr>
To: Linux ARM <linux-arm-kernel@lists.infradead.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Grafting old platform drivers onto a new DT kernel
Date: Thu, 5 Nov 2015 12:02:33 +0100 [thread overview]
Message-ID: <563B3749.50701@free.fr> (raw)
Hello,
My company provides a 3.4 kernel for an ARM-based SoC (there's also a 2.6.32
stashed somewhere for customers refusing to upgrade) along with drivers of
dubious quality written over the past decade.
I was tasked to release a new kernel, and took the opportunity to perform
a massive clean-up by discarding everything, and adding only enough code
on top of a recent kernel to boot to the shell.
I now have a small port with no drivers.
(I do have working serial and ethernet.)
Since I don't have time to rewrite the drivers at the moment, I'm wondering
if it's possible to "graft" old drivers (they're using the platform API, no
trace of DT support) onto my small base?
That way I can make management happy by providing a working new kernel,
and I can start working on converting drivers one-by-one.
Is that a realistic plan? What traps am I likely to fall into?
Regards.
next reply other threads:[~2015-11-05 11:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-05 11:02 Mason [this message]
2015-11-05 15:15 ` Grafting old platform drivers onto a new DT kernel Andrew Lunn
2015-11-05 15:42 ` Javier Martinez Canillas
2015-11-09 15:15 ` Mason
2015-11-09 15:36 ` Marc Zyngier
2016-02-03 15:33 ` Sebastian Frias
2015-11-09 15:40 ` Måns Rullgård
2015-11-09 16:07 ` Mason
2015-11-09 16:12 ` Måns Rullgård
2015-11-09 17:03 ` Mason
2015-11-09 17:13 ` Måns Rullgård
2015-11-10 12:44 ` Mason
2015-11-10 12:56 ` Arnd Bergmann
2015-11-09 16:26 ` Russell King - ARM Linux
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=563B3749.50701@free.fr \
--to=slash.tmp@free.fr \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.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