From: Timur Tabi <timur@freescale.com>
To: Kumar Gala <galak@kernel.crashing.org>,
Scott Wood <scottwood@freescale.com>,
Linuxppc-dev Development <linuxppc-dev@ozlabs.org>
Subject: Re: removing get_immrbase()??
Date: Tue, 28 Apr 2009 08:48:47 -0500 [thread overview]
Message-ID: <49F7093F.1000500@freescale.com> (raw)
In-Reply-To: <20090428041257.GC11265@yookeroo.seuss>
David Gibson wrote:
> On Wed, Apr 22, 2009 at 11:41:31PM -0500, Kumar Gala wrote:
>> Lets say I had an error driver for our MCM (core to soc coherency
>> module). It was getting the base address by using get_immrbase().
>> Today I proposed a proper device node for the MCM block as it doesn't
>> exist in .dts today. We add such a node into .dts and I can clean up my
>> error driver to use proper device node information. However I've just
>> broken any old .dts that didn't have this node. You are saying I need to
>> add code into the kernel to create this new node and we have to keep that
>> code around for ever in the kernel.. why would I ever bother to actually
>> changing anything than.
>
> Well, again. It's a judgement call, balancing the pain of having to
> update the dts files (which depends on how widely deployed the
> platform is) versus the pain of having to keep the bacwards
> compatibility shim in the kernel.
I agree with this sentiment. I'm only asking for a reasonable attempt
at adding backwards compatibility via an isolated code block. Sprinkle
in a few comments, and that should be enough. It won't always be
possible to add such code, but at the very least, I expect the
driver/kernel to clearly indicate what's missing from the device tree.
In Kumar's example above, I expect the kernel to say that the MCM node
is missing.
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2009-04-28 13:50 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-22 18:38 removing get_immrbase()?? Kumar Gala
2009-04-22 19:35 ` Timur Tabi
2009-04-22 20:16 ` Scott Wood
2009-04-22 20:16 ` Timur Tabi
2009-04-22 20:20 ` Scott Wood
2009-04-22 21:31 ` Kumar Gala
2009-04-22 21:33 ` Timur Tabi
2009-04-22 21:39 ` Kumar Gala
2009-04-22 21:46 ` Timur Tabi
2009-04-22 21:54 ` Kumar Gala
2009-04-22 21:57 ` Timur Tabi
2009-04-22 22:07 ` Kumar Gala
2009-04-22 22:00 ` Scott Wood
2009-04-22 22:00 ` Timur Tabi
2009-04-23 13:54 ` Grant Likely
2009-04-22 21:38 ` Scott Wood
2009-04-22 21:55 ` Kumar Gala
2009-04-22 22:33 ` Scott Wood
2009-04-23 0:03 ` Timur Tabi
2009-04-23 2:26 ` David Gibson
2009-04-23 3:36 ` Kumar Gala
2009-04-23 4:06 ` David Gibson
2009-04-23 4:41 ` Kumar Gala
2009-04-28 4:12 ` David Gibson
2009-04-28 13:48 ` Timur Tabi [this message]
2009-04-23 13:07 ` Timur Tabi
2009-04-23 15:56 ` Scott Wood
2009-04-23 13:02 ` Timur Tabi
2009-04-23 13:50 ` Anton Vorontsov
2009-04-23 14:02 ` Timur Tabi
2009-04-23 14:06 ` Kumar Gala
2009-04-23 14:09 ` Timur Tabi
2009-04-24 14:40 ` Wrobel Heinz-R39252
2009-04-23 14:13 ` Anton Vorontsov
2009-04-23 16:00 ` Scott Wood
2009-04-23 16:54 ` Anton Vorontsov
2009-04-23 17:03 ` Scott Wood
2009-04-23 17:26 ` Anton Vorontsov
2009-04-23 17:59 ` Scott Wood
2009-04-28 4:25 ` David Gibson
2009-04-28 4:21 ` David Gibson
2009-04-23 13:53 ` Grant Likely
2009-04-23 14:03 ` Anton Vorontsov
2009-04-28 4:26 ` David Gibson
2009-04-22 19:44 ` Scott Wood
2009-04-22 20:00 ` Kumar Gala
2009-04-22 20:30 ` Scott Wood
2009-04-23 13:53 ` 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=49F7093F.1000500@freescale.com \
--to=timur@freescale.com \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=scottwood@freescale.com \
/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).