From: Paul Bolle <pebolle@tiscali.nl>
To: Yannick GICQUEL <yannick.gicquel@open.eurogiciel.org>
Cc: Steven King <sfking@fdwdc.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
linux-m68k <linux-m68k@lists.linux-m68k.org>,
Gilles DOFFE <gdoffe.pro@gmail.com>,
Baptiste Durand <baptiste.durand@open.eurogiciel.org>
Subject: Re: m68knommu: CONFIG_I2C_COLDFIRE and CONFIG_RTC_DRV_M5441x
Date: Wed, 21 May 2014 17:55:33 +0200 [thread overview]
Message-ID: <1400687733.1122.4.camel@x220> (raw)
In-Reply-To: <537CCA66.1050502@open.eurogiciel.org>
Yannick,
On Wed, 2014-05-21 at 17:46 +0200, Yannick GICQUEL wrote:
> The MCF5441x support is quite a hot topic today for our company.
> This Soc family is seducing some of our customers, especially for it's
> long term support from Freescale.
>
> We have worked on this target since past few weeks, using a Tower Kit
> hardware and JTag, and just about to prepare a full integration of this
> device on recent kernel release.
> As a part of the open-source department, we have also planned to deliver
> this work to the community and propose some patches to refresh this
> target support.
>
> Some informations we observe on this target to be refreshed:
> - NAND controller needs to be integrated again,
> - UART controller as well,
>
> Also :
> - This chip contains a MMU and can be unlink from the !MMU dependency
>
> This is for the big lines, if the community is ok for a patch receipt,
> some other feature can be also pushed.
> BTW, what about this patches proposal ? Is there some time slot for
> patch proposal ?
The patch discussed (but not yet submitted) would remove all code
currently hidden behind
#if IS_ENABLED(CONFIG_RTC_DRV_M5441x)
in the kernel tree. Now, I'm guessing the (new) code you're working on
doesn't care about CONFIG_RTC_DRV_M5441x. So chances are you could not
care less if that code gets removed.
Paul Bolle
next prev parent reply other threads:[~2014-05-21 15:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-20 19:28 m68knommu: CONFIG_I2C_COLDFIRE and CONFIG_RTC_DRV_M5441x Paul Bolle
2014-05-20 20:19 ` Geert Uytterhoeven
2014-05-20 20:50 ` Steven King
2014-05-20 21:01 ` Paul Bolle
2014-05-20 21:16 ` Steven King
2014-05-21 15:46 ` Yannick GICQUEL
2014-05-21 15:55 ` Paul Bolle [this message]
2014-05-21 21:47 ` Steven King
2014-05-23 8:19 ` Yannick GICQUEL
2014-05-22 1:04 ` Greg Ungerer
2014-05-23 6:44 ` Yannick GICQUEL
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=1400687733.1122.4.camel@x220 \
--to=pebolle@tiscali.nl \
--cc=baptiste.durand@open.eurogiciel.org \
--cc=gdoffe.pro@gmail.com \
--cc=geert@linux-m68k.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=sfking@fdwdc.com \
--cc=yannick.gicquel@open.eurogiciel.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