linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: cavokz@gmail.com (Domenico Andreoli)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: add support for BCM2708/BCM2835 and Raspberry Pi
Date: Thu, 6 Sep 2012 11:47:03 +0200	[thread overview]
Message-ID: <20120906094703.GA7308@glitch> (raw)
In-Reply-To: <201209060904.14903.arnd@arndb.de>

On Thu, Sep 06, 2012 at 09:04:14AM +0000, Arnd Bergmann wrote:
> On Thursday 06 September 2012, Stephen Warren wrote:
> 
> > Questions:
> > * It is asserted (I believe by Broadcom) that the BCM2835 is the only SoC
> >   in the series likely to see Linux support. Irrespective, those working
> >   on BCM2835 support downstream (see git URL above) have chosen to name
> >   the kernel support after the primary SoC (BCM2708) rather than the
> >   particular instance in use on the Raspberry Pi (BCM2835). I've followed
> >   that here, although I wonder if it's really the correct thing to do?
> 
> Doesn't matter too much. Depending on how different the various broadcom
> SoCs actually are, we might even name this mach-bcm and eventually try to
> merge the existing bcmring into it.

I've some stuff for the BCM4760. Working at clean-room patches, which is
easy because the reference published GPL sources [0] are based on 2.6.28 and
may look scary (190k lines of register definitions header file, completely
broken and unused monster to manage clocks, no pinctrl, old-style gpios,
reimplementation of pl011, pl080 - old style dma, to say a few).

Moreover many IP blocks are already in the kernel (PL011, PL081, sdhci,
dwc-usb2 in the device-only implementation of s3c-hsotg).

It's incomplete, has a lot of issues. sdhci and usb not working. PMU
BCM59040 is barely implemented, only regulators. But it can boot from
initramfs, minimal user space works. Yeah... a side project, mostly a
continous-study project.

I could find some similarities with something in bcmring, while grepping,
but I've never dig into it. I also quickly looked into the Raspberry PI
SoC but I could not find anything familiar.  However there could be some
code to share. I'll manage a first post of these patches if interested.

Regards,
Domenico

[0] http://www.tomtom.com/page.php?Page=gpl

  reply	other threads:[~2012-09-06  9:47 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 [this message]
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
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=20120906094703.GA7308@glitch \
    --to=cavokz@gmail.com \
    --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).