All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
To: Alexandre Courbot <gnurou-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Alexandre Courbot
	<acourbot-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>,
	Thierry Reding
	<thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	"linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	"linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
	<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
	Linux Kernel Mailing List
	<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH 1/2] ARM: tegra: joystick input in tegra_defconfig
Date: Tue, 13 May 2014 09:39:02 -0600	[thread overview]
Message-ID: <53723C96.5020203@wwwdotorg.org> (raw)
In-Reply-To: <CAAVeFuLZ_wrxipYn2pfNzuyDiTvAPWH4aSWfonrG+YQsm4tM_g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

On 05/12/2014 09:45 PM, Alexandre Courbot wrote:
> On Tue, May 13, 2014 at 1:32 AM, Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org> wrote:
>> On 05/12/2014 02:26 AM, Alexandre Courbot wrote:
>>> NVIDIA SHIELD embeds a USB controller. Compile the corresponding support
>>> as a module in tegra_defconfig.
>>
>> Why make this a module rather than built-in. Almost everything else in
>> tegra_defconfig is built-in, except brcmfmac since it doesn't handle
>> lack of firmware availability at probe time.
> 
> Goal is to minimize the image size, especially since this is not a
> feature I expect to be used much outside of SHIELD. If you prefer it
> built-in, I'm fine with it too.

Yes, built-in for everything makes most sense to me, except for code
that doesn't actually work unless it's a module.

WARNING: multiple messages have this Message-ID (diff)
From: swarren@wwwdotorg.org (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ARM: tegra: joystick input in tegra_defconfig
Date: Tue, 13 May 2014 09:39:02 -0600	[thread overview]
Message-ID: <53723C96.5020203@wwwdotorg.org> (raw)
In-Reply-To: <CAAVeFuLZ_wrxipYn2pfNzuyDiTvAPWH4aSWfonrG+YQsm4tM_g@mail.gmail.com>

On 05/12/2014 09:45 PM, Alexandre Courbot wrote:
> On Tue, May 13, 2014 at 1:32 AM, Stephen Warren <swarren@wwwdotorg.org> wrote:
>> On 05/12/2014 02:26 AM, Alexandre Courbot wrote:
>>> NVIDIA SHIELD embeds a USB controller. Compile the corresponding support
>>> as a module in tegra_defconfig.
>>
>> Why make this a module rather than built-in. Almost everything else in
>> tegra_defconfig is built-in, except brcmfmac since it doesn't handle
>> lack of firmware availability at probe time.
> 
> Goal is to minimize the image size, especially since this is not a
> feature I expect to be used much outside of SHIELD. If you prefer it
> built-in, I'm fine with it too.

Yes, built-in for everything makes most sense to me, except for code
that doesn't actually work unless it's a module.

WARNING: multiple messages have this Message-ID (diff)
From: Stephen Warren <swarren@wwwdotorg.org>
To: Alexandre Courbot <gnurou@gmail.com>
Cc: Alexandre Courbot <acourbot@nvidia.com>,
	Thierry Reding <thierry.reding@gmail.com>,
	"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] ARM: tegra: joystick input in tegra_defconfig
Date: Tue, 13 May 2014 09:39:02 -0600	[thread overview]
Message-ID: <53723C96.5020203@wwwdotorg.org> (raw)
In-Reply-To: <CAAVeFuLZ_wrxipYn2pfNzuyDiTvAPWH4aSWfonrG+YQsm4tM_g@mail.gmail.com>

On 05/12/2014 09:45 PM, Alexandre Courbot wrote:
> On Tue, May 13, 2014 at 1:32 AM, Stephen Warren <swarren@wwwdotorg.org> wrote:
>> On 05/12/2014 02:26 AM, Alexandre Courbot wrote:
>>> NVIDIA SHIELD embeds a USB controller. Compile the corresponding support
>>> as a module in tegra_defconfig.
>>
>> Why make this a module rather than built-in. Almost everything else in
>> tegra_defconfig is built-in, except brcmfmac since it doesn't handle
>> lack of firmware availability at probe time.
> 
> Goal is to minimize the image size, especially since this is not a
> feature I expect to be used much outside of SHIELD. If you prefer it
> built-in, I'm fine with it too.

Yes, built-in for everything makes most sense to me, except for code
that doesn't actually work unless it's a module.


  parent reply	other threads:[~2014-05-13 15:39 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-12  8:26 [PATCH 0/2] ARM: tegra: basic support for NVIDIA SHIELD Alexandre Courbot
2014-05-12  8:26 ` Alexandre Courbot
2014-05-12  8:26 ` Alexandre Courbot
2014-05-12  8:26 ` [PATCH 1/2] ARM: tegra: joystick input in tegra_defconfig Alexandre Courbot
2014-05-12  8:26   ` Alexandre Courbot
2014-05-12  8:26   ` Alexandre Courbot
2014-05-12 16:32   ` Stephen Warren
2014-05-12 16:32     ` Stephen Warren
     [not found]     ` <5370F794.2020800-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2014-05-13  3:45       ` Alexandre Courbot
2014-05-13  3:45         ` Alexandre Courbot
2014-05-13  3:45         ` Alexandre Courbot
     [not found]         ` <CAAVeFuLZ_wrxipYn2pfNzuyDiTvAPWH4aSWfonrG+YQsm4tM_g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-05-13 15:39           ` Stephen Warren [this message]
2014-05-13 15:39             ` Stephen Warren
2014-05-13 15:39             ` Stephen Warren
2014-05-12  8:26 ` [PATCH 2/2] ARM: tegra: add device tree for SHIELD Alexandre Courbot
2014-05-12  8:26   ` Alexandre Courbot
2014-05-12  8:26   ` Alexandre Courbot
     [not found]   ` <1399883209-31169-3-git-send-email-acourbot-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2014-05-12 16:41     ` Stephen Warren
2014-05-12 16:41       ` Stephen Warren
2014-05-12 16:41       ` Stephen Warren

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=53723C96.5020203@wwwdotorg.org \
    --to=swarren-3lzwwm7+weoh9zmkesr00q@public.gmane.org \
    --cc=acourbot-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
    --cc=gnurou-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@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 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.