From: Dirk Behme <dirk.behme@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 0/2] SPI flash enhancements: allow default bus and chip-selects
Date: Tue, 31 Jan 2012 17:21:29 +0100 [thread overview]
Message-ID: <4F281509.4040401@googlemail.com> (raw)
In-Reply-To: <201201311016.32376.vapier@gentoo.org>
On 31.01.2012 16:16, Mike Frysinger wrote:
> On Monday 30 January 2012 15:02:24 Eric Nelson wrote:
>> Patch 1 modifies the 'sf' command to allow a default bus and chip-select
>> to be specified by board headers. This allows a bare 'sf' probe command:
>> U-Boot> sf probe
>> instead of the more cumbersome usage when a GPIO is tacked onto
>> the chip-select. Otherwise, this command-line would be needed
>> to specify GP3:19 on SabreLite:
>> U-Boot> sf probe 0x5300
>>
>> Patch 2 provides a description of usage and configuration of CONFIG_CMD_SF.
>
> thanks, i'll merge both into my sf branch and then push to wolfgang for next
> merge window (if he doesn't pick things up directly himself)
As we had the first version of the initial patch series already at the
list while the last merge window was still open, I was hoping for a
chance to get this into v2012.03 ;)
Anyway, many thanks and best regards
Dirk
next prev parent reply other threads:[~2012-01-31 16:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-30 20:02 [U-Boot] [PATCH 0/2] SPI flash enhancements: allow default bus and chip-selects Eric Nelson
2012-01-30 20:02 ` [U-Boot] [PATCH 1/2] sf command: allow default bus and chip selects Eric Nelson
2012-01-31 10:37 ` Matthias Fuchs
2012-01-30 20:02 ` [U-Boot] [PATCH 2/2] README: Add description of SPI Flash (SF) command configuration Eric Nelson
2012-01-31 15:16 ` [U-Boot] [PATCH 0/2] SPI flash enhancements: allow default bus and chip-selects Mike Frysinger
2012-01-31 15:19 ` Eric Nelson
2012-01-31 16:21 ` Dirk Behme [this message]
2012-01-31 18:20 ` Mike Frysinger
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=4F281509.4040401@googlemail.com \
--to=dirk.behme@googlemail.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