From: Andrew Lunn <andrew@lunn.ch>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: Jason Cooper <jason@lakedaemon.net>,
ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [CORE TOPIC] hobbyist recruiting
Date: Mon, 12 May 2014 15:58:36 +0200 [thread overview]
Message-ID: <20140512135836.GD3378@lunn.ch> (raw)
In-Reply-To: <20140512083825.GB2665@katana>
> Agree. That is why I point people to OpenWRT which has tons of hardware
> support which is not mainline. And old routers can quite easily be
> obtained. Yet, one must be willing enough to get support of a mostly
> outdated HW into the kernel, just for the fun of it.
I've had some success contacting the authors of kirkwood SoC based
board ports that are in OpenWRT and asking them to contribute there
patches to mainline. It has not been too much effort helping them
clean up the contribution to get the code in mainline. Nobody has made
the transition to a regular contributer, but they do tend to help with
testing when patches affect there board and you ask for tests.
arch/arm/boot/dts$ ls -1 *.dts | cut -f 1 -d - | sort | uniq -c| sort -rn
57 kirkwood
33 omap3
19 imx6q
18 imx28
14 armada
12 imx6dl
10 tegra20
9 ste
9 imx53
7 sun4i
7 omap4
6 am335x
5 imx27
With the usual declaimer of lies, damn lies, and statistics, it looks
like we are doing something right. And kirkwood is mostly hobbyist
maintained.
Andrew
next prev parent reply other threads:[~2014-05-12 14:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-11 5:30 Jason Cooper
2014-05-11 17:57 ` Sebastian Hesselbarth
2014-05-11 19:16 ` Levente Kurusa
2014-05-11 19:26 ` Greg KH
2014-05-11 19:50 ` Levente Kurusa
2014-05-11 20:33 ` Hans Verkuil
2014-05-11 21:35 ` Theodore Ts'o
2014-05-12 8:19 ` Wolfram Sang
2014-05-12 8:38 ` Wolfram Sang
2014-05-12 9:08 ` Li Zefan
2014-05-12 9:40 ` Hans Verkuil
2014-05-12 9:54 ` Wolfram Sang
2014-05-12 13:58 ` Andrew Lunn [this message]
2014-05-12 16:08 ` Stephen Hemminger
2014-05-21 14:32 ` Dan Carpenter
2014-05-12 16:38 ` Jason Cooper
2014-05-12 23:23 ` Greg KH
2014-05-16 3:47 ` Jason Cooper
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=20140512135836.GD3378@lunn.ch \
--to=andrew@lunn.ch \
--cc=jason@lakedaemon.net \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=wsa@the-dreams.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