From: Oleksandr Tymoshenko <gonzo@bluezbox.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/2] mmc: add bcm2835 driver
Date: Fri, 26 Oct 2012 10:48:06 -0700 [thread overview]
Message-ID: <508ACCD6.5050609@bluezbox.com> (raw)
In-Reply-To: <20121026173202.GB31793@bill-the-cat>
On 10/26/2012 10:32 AM, Tom Rini wrote:
> On Tue, Oct 23, 2012 at 10:50:47PM -0600, Stephen Warren wrote:
>> This adds a simple driver for the BCM2835's SD controller.
>>
>> Workarounds are implemented for:
>> * Register writes can't be too close to each-other in time, or they will
>> be lost.
>> * Register accesses must all be 32-bit, so implement custom accessors.
>>
>> This code was extracted from:
>> git://github.com/gonzoua/u-boot-pi.git master
>> which was created by Oleksandr Tymoshenko.
>>
>> Portions of the code there were obviously based on the Linux kernel at:
>> git://github.com/raspberrypi/linux.git rpi-3.2.27
>>
>> No s-o-b tags were present in either location.
> Um, that's a bit worrying to me. Wolfgang?
I didn't have much experience with s-o-b stuff, so excuse my ignorance.
Is there official procedure, or is it enough to state that I sign off on
everything in git://github.com/gonzoua/u-boot-pi.git master
authored by me?
next prev parent reply other threads:[~2012-10-26 17:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-24 4:50 [U-Boot] [PATCH 1/2] mmc: add bcm2835 driver Stephen Warren
2012-10-24 4:50 ` [U-Boot] [PATCH 2/2] ARM: rpi_b: enable SD controller, add related env/cmds Stephen Warren
2012-10-26 11:33 ` [U-Boot] [PATCH 1/2] mmc: add bcm2835 driver Vikram Narayanan
2012-10-28 3:28 ` Stephen Warren
2012-10-28 17:06 ` Vikram Narayanan
2012-11-04 15:32 ` Albert ARIBAUD
2012-11-04 17:15 ` Stephen Warren
2012-10-26 17:32 ` Tom Rini
2012-10-26 17:48 ` Oleksandr Tymoshenko [this message]
2012-10-26 18:05 ` Tom Rini
2012-10-26 18:21 ` Stephen Warren
2012-10-26 18:10 ` Greg KH
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=508ACCD6.5050609@bluezbox.com \
--to=gonzo@bluezbox.com \
--cc=u-boot@lists.denx.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