From: simon@fire.lp0.eu (Simon Arlott)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: add support for BCM2708/BCM2835 and Raspberry Pi
Date: Thu, 06 Sep 2012 23:10:45 +0100 [thread overview]
Message-ID: <50491F65.2020302@simon.arlott.org.uk> (raw)
In-Reply-To: <CAG-w=x77y6ykh3FcyTtVAN85eOk1RP2CZ=ZG-_1091i5jYDF2A@mail.gmail.com>
On 06/09/12 17:53, Seth Jennings wrote:
> (sorry for the dup Stephen, forgot to reply all :-/)
>
> On Thu, Sep 6, 2012 at 12:07 AM, Stephen Warren <swarren@wwwdotorg.org> wrote:
>>
>> The BCM2708 is an ARM SoC from Broadcom. It is the primary SoC in a
>> series which contains the BCM2835 amongst other variants. This patch
>> adds very basic support for this series of SoCs, under the BCM2708 name.
>
> Great work! I'm glad to see this heading upstream :)
>
>> This series was extracted from git://github.com/lp0/linux.git branch
>> rpi-next or rpi-linear from 3-4 months ago, and significantly stripped
>> down and modified since.
I don't know why you're using the rpi-linear branch when the rpi-split
branch has the same content but everything already split into separate
patches...
> I've used Simon's tree before and it will boot up all the way with UART
> support (no graphics, usb, network). I also think it has a fully
> populated device tree.
It has supported graphics for a while:
https://github.com/raspberrypi/linux/wiki/How-to-boot-using-device-tree#wiki-Configuration
I've been waiting over 3 months now for device tree support to be added
to the GPU-based bootloader and it still hasn't appeared.
> Why, in particular, did you strip it down?
>
> I'm new to the ARM SoC upstreaming scene so there might be a obvious
> reason of which I'm not aware.
>
> --
> Seth
--
Simon Arlott
next prev parent reply other threads:[~2012-09-06 22:10 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
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 [this message]
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=50491F65.2020302@simon.arlott.org.uk \
--to=simon@fire.lp0.eu \
--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 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.