From: kaloz@openwrt.org (Imre Kaloz)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: add support for BCM2708/BCM2835 and Raspberry Pi
Date: Sun, 09 Sep 2012 10:46:34 +0200 [thread overview]
Message-ID: <op.wkc1bwjx2s3iss@ecaz> (raw)
In-Reply-To: <1729018.3VWhxcipzn@wuerfel>
On Sun, 09 Sep 2012 03:16:54 +0200, Arnd Bergmann <arnd@arndb.de> wrote:
<snip>
>> so in that case I'm not going to know if anything is broken on an IOP32x
>> kernel until that gets rebooted (which it will do soon because I want to
>> change its disks - but hopefully not before 62 days time.)
>
> I was specifically saying "a port gets started", not "a port is fully
> working". The example I was thinking of is the mach-cns3xxx, which
> was introduced in a very minimal state about 2 years ago. The only
> users I could find on the internet are on OpenWRT, which adds
> support for an actual board file (upstream only has the evaluation
> board) as well as SMP, clock, i2c, ethernet, gpio, and a bunch of
> bug fixes[1]. I'd say we should either find someone who is willing to
> submit the patches upstream and make sure they work with at least
> one version, or we can remove what we have today because it's evidently
> not used.
For some time now you have to have clocks support to be able to get SMP
and co working. Without that and DT it doesn't really make sense to submit
those patches.
<snip>
> * ixp4xx is (as expected) actively used, but a lot of patches are stuck
> in openwrt[2] and not getting submitted.
> Greg also submitted a regression fix, Ben Hutchins promised
> another fix from Debian.
Mostly the same as above. Don't forget that DT support will essentially
get rid of all separate board support files, so those patches will have to
be translated to dts files instead.
Since I'm doing all the OpenWrt work (as well as upstreaming non-ARM
stuff) in my free time, things got stuck and will likely stay that way for
another month or so.
Imre
next prev parent reply other threads:[~2012-09-09 8:46 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-06 5:07 [PATCH] ARM: add support for BCM2708/BCM2835 and Raspberry Pi Stephen Warren
2012-09-06 9:04 ` Arnd Bergmann
2012-09-06 9:47 ` Domenico Andreoli
2012-09-06 15:46 ` Arnd Bergmann
2012-09-08 21:56 ` Russell King - ARM Linux
2012-09-09 0:30 ` Domenico Andreoli
2012-09-09 1:34 ` Arnd Bergmann
2012-09-09 0:52 ` Olof Johansson
2012-09-09 1:16 ` Arnd Bergmann
2012-09-09 8:46 ` Imre Kaloz [this message]
2012-09-07 2:23 ` Stephen Warren
2012-09-07 4:04 ` Arnd Bergmann
2012-09-06 16:53 ` Seth Jennings
2012-09-06 22:10 ` Simon Arlott
2012-09-07 0:56 ` Seth Jennings
2012-09-07 1:52 ` Stephen Warren
2012-09-08 17:12 ` popcornmix
2012-09-08 17:48 ` Stephen Warren
2012-09-08 17:53 ` popcornmix
2012-09-07 1:38 ` Stephen Warren
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=op.wkc1bwjx2s3iss@ecaz \
--to=kaloz@openwrt.org \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).