From: Mike Frysinger <vapier@gentoo.org>
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 10:16:29 -0500 [thread overview]
Message-ID: <201201311016.32376.vapier@gentoo.org> (raw)
In-Reply-To: <1327953746-4368-1-git-send-email-eric.nelson@boundarydevices.com>
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)
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20120131/f5824209/attachment.pgp>
next prev parent reply other threads:[~2012-01-31 15:16 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 ` Mike Frysinger [this message]
2012-01-31 15:19 ` [U-Boot] [PATCH 0/2] SPI flash enhancements: allow default bus and chip-selects Eric Nelson
2012-01-31 16:21 ` Dirk Behme
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=201201311016.32376.vapier@gentoo.org \
--to=vapier@gentoo.org \
--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