From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Michael Welling <mwelling@ieee.org>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] RT FEC net driver for IMX6Q
Date: Wed, 3 Feb 2016 16:33:41 +0100 [thread overview]
Message-ID: <20160203153341.GG32138@hermes.click-hack.org> (raw)
In-Reply-To: <20160203151802.GC25464@deathstar>
On Wed, Feb 03, 2016 at 09:18:02AM -0600, Michael Welling wrote:
> On Wed, Feb 03, 2016 at 04:04:48PM +0100, Gilles Chanteperdrix wrote:
> > On Wed, Feb 03, 2016 at 08:51:46AM -0600, Michael Welling wrote:
> > > Is there any specific reason why the fec driver is restricted to the PPC
> > > arcitecture?
> >
> > In its current state, the driver does not compile for IMX6. A broken
> > patch has been proposed, my idea is to work on RTnet core before
> > tackling the drivers, but if a patch fixing the build for imx6 is
> > proposed, it could be re-enabled.
> >
>
> What are the issues with the RTnet core?
The main issue is that it predates many factorizations in the Linux
kernel code and so could be made simpler by relying on them. It open
codes linked lists for instance, this is just a random example.
Another issue is that keeping the drivers synchronized with their
mainline counter-part requires a big maintenance effort.
>
> I just found out the hard way that the driver does not compile.
> I will try my best to update the IMX drivers so that they build
> with 3.18.20.
A patch has been posted here:
https://xenomai.org/pipermail/xenomai/2016-January/035756.html
--
Gilles.
https://click-hack.org
next prev parent reply other threads:[~2016-02-03 15:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-03 14:51 [Xenomai] RT FEC net driver for IMX6Q Michael Welling
2016-02-03 15:04 ` Gilles Chanteperdrix
2016-02-03 15:18 ` Michael Welling
2016-02-03 15:33 ` Gilles Chanteperdrix [this message]
2016-02-04 19:58 ` Michael Welling
2016-02-04 22:07 ` Gilles Chanteperdrix
2016-02-04 22:20 ` Michael Welling
2016-02-04 23:56 ` Michael Welling
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=20160203153341.GG32138@hermes.click-hack.org \
--to=gilles.chanteperdrix@xenomai.org \
--cc=mwelling@ieee.org \
--cc=xenomai@xenomai.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.