From: Linus Walleij <linus.walleij@linaro.org>
To: Arnd Bergmann <arnd@arndb.de>,
Ladislav Michl <ladis@linux-mips.org>,
github@hilscher.com
Cc: Olof Johansson <olof@lixom.net>,
Robert Schwebel <r.schwebel@pengutronix.de>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Pengutronix Kernel Team <kernel@pengutronix.de>
Subject: Re: Hilscher NetX mach-netx refactorings
Date: Sun, 13 Jan 2019 13:14:36 +0100 [thread overview]
Message-ID: <CACRpkdZ7KSmgTYP8a_RUJAWKzuc652OZ420Lq4ZnzkCuESLZ2Q@mail.gmail.com> (raw)
In-Reply-To: <CAK8P3a08TV+sQhsCPjkXh6wOKEpLfGLqVo9+FHoXzDVXs_bY7A@mail.gmail.com>
On Sat, Jan 12, 2019 at 1:03 PM Arnd Bergmann <arnd@arndb.de> wrote:
> On Sat, Jan 12, 2019 at 9:35 AM Linus Walleij <linus.walleij@linaro.org> wrote:
> >
> > Hi Sascha, Robert,
> >
> > I am looking at refactoring mach-netx to use the new PL11x
> > DRM driver for the graphics.
> >
> > I need to make sure that patches get tested on the hardware
> > and just want to ascertain that there is an active maintainer that
> > will be able to test patches I make for this and work on getting
> > it migrated to DRM before I start spending time on it.
> >
> > Are you/pengutronix still actively maintaining this machine and
> > testing new kernels on netx?
> >
> > I guess the second question is whether you have plans to migrate
> > it to device tree and multiplatform, but I'm mainly thinking about
> > my own little patches now.
>
>
> On a related note, there does appear to be active work on
> newer netx machines that were never upstreamed, see
> https://github.com/Hilscher/netx4000-linux/commits/v4.9-netx4000-stable
That RS485 addition to PL011 using GPIOs is a bit hacky but
looks like very useful for industrial applications.
Ladislav, have you been in contact with Hilscher?
> I wonder if anyone has contacts into the company so we can
> work together with them to include them into mainline Linux.
They have a mail address github@hilscher.com, let's knock
on the door and see if somebody answers it :D
I'd personally be able to take a stab at converting this machine
to device tree and multiplatform if I only had access to the
hardware, as it seems to be in the same class as EP93xx
and MOXA ART: deployed in industrial systems as we speak.
Yours,
Linus Walleij
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-01-13 12:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-12 8:35 Hilscher NetX mach-netx refactorings Linus Walleij
2019-01-12 12:03 ` Arnd Bergmann
2019-01-13 12:14 ` Linus Walleij [this message]
2019-01-13 15:50 ` Ladislav Michl
2019-01-13 22:39 ` Linus Walleij
2019-01-14 11:26 ` Michael Trensch
2019-01-14 14:22 ` Linus Walleij
2019-01-15 7:05 ` Michael Trensch
2019-01-15 10:11 ` Arnd Bergmann
2019-01-15 10:14 ` Arnd Bergmann
2019-01-14 10:35 ` Sascha Hauer
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=CACRpkdZ7KSmgTYP8a_RUJAWKzuc652OZ420Lq4ZnzkCuESLZ2Q@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=arnd@arndb.de \
--cc=github@hilscher.com \
--cc=kernel@pengutronix.de \
--cc=ladis@linux-mips.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=olof@lixom.net \
--cc=r.schwebel@pengutronix.de \
/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).