linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: green@linuxhacker.ru
To: linux-omap@vger.kernel.org
Subject: Initial B&N Nook Color support, take five
Date: Mon,  6 Jun 2011 02:05:02 -0400	[thread overview]
Message-ID: <1307340305-1252-1-git-send-email-green@linuxhacker.ru> (raw)

Hello!

 Next attempt at B&N Nook Color board file submission.
 USB peripheral mode is fully operational as is serial console and
 MMC/SDCard.

 Changes
 since v4:
 Rebased to devel-fixes
 A few more style fixes with regulators
 dropped board_mux define if CONFIG_OMAP_MUX is not set
 since v3:
 Separated mach-types change into a separate patch (already got RMK approval)
 Dramatically cut number of includes in the board file again.
 No longer set voltage regulator dev, just device name in the supply.
 Style fixes
 Serial in uncompress.h sorted by name
 Corrected MUX package to CBP in board file.
 omap_i2c_init now has no return since it's unused anyway.
 Fixed keypad definition.

 since v2:
 rebased on devel-cleanup branch

 since v1:
 Threw away all the android stuff as suggested 
 Cleaned up voltage regulators and removed the ones our twl chip actually
   does not have
 Changed the split of the patches to board file + twl update

Bye,
  Oleg


             reply	other threads:[~2011-06-06  6:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-06  6:05 green [this message]
2011-06-06  6:05 ` [PATCH 1/3] Initial B&N Nook Color (encore) support green
2011-06-14 10:09   ` Igor Grinberg
2011-06-06  6:05 ` [PATCH 2/3] Add tps65921 chip green
2011-06-06  6:05 ` [PATCH 3/3] Update Nook Color machine 3284 to common Encore name green
2011-06-14  8:13 ` Initial B&N Nook Color support, take five Tony Lindgren

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=1307340305-1252-1-git-send-email-green@linuxhacker.ru \
    --to=green@linuxhacker.ru \
    --cc=linux-omap@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).