linux-tegra.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
To: Marc Dietrich <marvin24-Mmb7MZpHnFY@public.gmane.org>
Cc: linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Olof Johansson <olof-nZhT3qVonbNeoWH0uzbU5w@public.gmane.org>,
	Colin Cross <ccross-z5hGa2qSFaRBDgjK7y7TUQ@public.gmane.org>
Subject: Re: [PATCH] ARM: tegra: update defconfig to support more paz00 hardware
Date: Mon, 20 Aug 2012 11:14:16 -0600	[thread overview]
Message-ID: <50327068.6010705@wwwdotorg.org> (raw)
In-Reply-To: <2895bbda75127f208239e07dbbcf79e718cf684f.1345309601.git.marvin24-Mmb7MZpHnFY@public.gmane.org>

On 08/18/2012 11:10 AM, Marc Dietrich wrote:
> This update adds various devices found on the usb bus on PAZ00 boards:
> 
> 	- Wifi chip (rt3070)
> 	- Bluetooth (btusb)
> 	- Camera (uvcvideo)
> 	- 3G modem (acm and wdm)
> 
> These are enabled as modules because they are not needed for boot and
> will not be used on other boards. Wifi also needs to be module because
> of the firmware loader.
> 
> The update also enabled support for the rfkill switch, the Wifi LED and
> the nvec power and led driver which got lost in the past.
> 
> Finally, devtmpfs and tmpfs acls are enabled because they are mandatory
> on modern linux distros.

Thanks, applied to Tegra's for-3.7/defconfig branch.

      parent reply	other threads:[~2012-08-20 17:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-18 17:10 [PATCH] ARM: tegra: update defconfig to support more paz00 hardware Marc Dietrich
     [not found] ` <2895bbda75127f208239e07dbbcf79e718cf684f.1345309601.git.marvin24-Mmb7MZpHnFY@public.gmane.org>
2012-08-20 17:14   ` Stephen Warren [this message]

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=50327068.6010705@wwwdotorg.org \
    --to=swarren-3lzwwm7+weoh9zmkesr00q@public.gmane.org \
    --cc=ccross-z5hGa2qSFaRBDgjK7y7TUQ@public.gmane.org \
    --cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=marvin24-Mmb7MZpHnFY@public.gmane.org \
    --cc=olof-nZhT3qVonbNeoWH0uzbU5w@public.gmane.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).