All of lore.kernel.org
 help / color / mirror / Atom feed
From: Darren Hart <dvhart@linux.intel.com>
To: poky@yoctoproject.org,bruce.ashfield@windriver.com,tom.zanussi@intel.com
Subject: [PATCH 0/3] linux-2.6-windriver: Beagleboard revision detection and gpio write-protect mapping
Date: Fri, 21 Jan 2011  8:37:23 -0800	[thread overview]
Message-ID: <cover.1295627451.git.dvhart@linux.intel.com> (raw)

The existing board detection doesn't work for all board types. The GPIO pins are
mapped differently, particularly the SD card write-protect lines. These patches
fix a boot hang on the Beagleboard xM due to the xM using a micro SD which
doesn't have WP lines.

The following patches already exist in mainline and apply without modification
to the linux-2.6-windriver git tree.

Please merge dvhart/beagleboard-standard with beagleboard-standard.

Pull URL: git://git.pokylinux.org/linux-2.6-windriver-contrib.git
  Branch: dvhart/beagleboard-standard
  Browse: http://git.pokylinux.org/cgit.cgi/linux-2.6-windriver-contrib/log/?h=dvhart/beagleboard-standard

Thanks,
    Darren Hart <dvhart@linux.intel.com>
---


Robert Nelson (3):
  omap: Beagle: revision detection
  omap: Beagle: only Cx boards use pin 23 for write protect
  omap: Beagle: no gpio_wp pin connection on xM

 arch/arm/mach-omap2/board-omap3beagle.c |   93 ++++++++++++++++++++++++++++++-
 1 files changed, 92 insertions(+), 1 deletions(-)



             reply	other threads:[~2011-01-21 16:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-21 16:37 Darren Hart [this message]
2011-01-21 16:37 ` [PATCH 1/3] omap: Beagle: revision detection Robert Nelson
2011-01-21 16:37 ` [PATCH 2/3] omap: Beagle: only Cx boards use pin 23 for write protect Robert Nelson
2011-01-21 16:37 ` [PATCH 3/3] omap: Beagle: no gpio_wp pin connection on xM Robert Nelson
2011-01-21 18:05 ` [PATCH 0/3] linux-2.6-windriver: Beagleboard revision detection and gpio write-protect mapping Bruce Ashfield

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=cover.1295627451.git.dvhart@linux.intel.com \
    --to=dvhart@linux.intel.com \
    --cc=bruce.ashfield@windriver.com \
    --cc=poky@yoctoproject.org \
    --cc=tom.zanussi@intel.com \
    /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.