All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
To: Marc Dietrich <marvin24-Mmb7MZpHnFY@public.gmane.org>
Cc: Wei Ni <wni-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>,
	swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org,
	olof-nZhT3qVonbNeoWH0uzbU5w@public.gmane.org,
	ccross-z5hGa2qSFaRBDgjK7y7TUQ@public.gmane.org,
	linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org,
	linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org,
	arnd-r2nGTMty4D4@public.gmane.org,
	grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org,
	cjb-2X9k7bc8m7Mdnm+yROfE0A@public.gmane.org
Subject: Re: [PATCH 5/5] ARM: tegra: enable wireless in defconfig
Date: Thu, 05 Jul 2012 14:42:33 -0600	[thread overview]
Message-ID: <4FF5FC39.3090402@wwwdotorg.org> (raw)
In-Reply-To: <2114579.sqTp7XiW3H@ax5200p>

On 07/05/2012 02:35 PM, Marc Dietrich wrote:
> On Thursday 05 July 2012 13:59:11 Stephen Warren wrote:
>> On 07/04/2012 03:34 AM, Wei Ni wrote:
>>> New options enabled:
>>> * WIRELESS: (dependency)
>>> * CFG80211: (dependency)
>>> * WLAN: (dependency)
>>> * BRCMFMAC: wlan driver, enable as module.
>>>
>>> diff --git a/arch/arm/configs/tegra_defconfig
>>> b/arch/arm/configs/tegra_defconfig
>>>
>>> +CONFIG_BRCMFMAC=m
>>
>> Why does this need to be a module? Everything else in tegra_defconfig is
>> built-in, and it'd be nice to be consistent here. Built-in makes
>> net-booting new kernels from U-Boot much easier, since there aren't any
>> modules to copy.
> 
> network drivers (especially wifi) are often modules because they need firmwares. 

So I certainly see that WiFi modules may need firmware.

But I don't see why that should imply they must be modules; they should
be able to defer their firmware loading until the firmware is available.

> I'm not sure if the kernel can compile them in every case. Our RT2x00 is an 
> example (which also needs a defconfig entry btw) but brcmfmac also needs it as 
> modinfo shows. Beside that, I don't think you want to netboot using wifi and u-
> boot because this needs a huge wireless framework which u-boot doesn't have.

I net-boot using a USB wired Ethernet adapter. The issue isn't that I
want to use wireless from U-Boot, but rather than it's easy to download
the zImage and .dtb using U-Boot since they're just copied to RAM, but
getting a bunch of modules into a filesystem on the target before
booting the kernel is more painful.

WARNING: multiple messages have this Message-ID (diff)
From: swarren@wwwdotorg.org (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 5/5] ARM: tegra: enable wireless in defconfig
Date: Thu, 05 Jul 2012 14:42:33 -0600	[thread overview]
Message-ID: <4FF5FC39.3090402@wwwdotorg.org> (raw)
In-Reply-To: <2114579.sqTp7XiW3H@ax5200p>

On 07/05/2012 02:35 PM, Marc Dietrich wrote:
> On Thursday 05 July 2012 13:59:11 Stephen Warren wrote:
>> On 07/04/2012 03:34 AM, Wei Ni wrote:
>>> New options enabled:
>>> * WIRELESS: (dependency)
>>> * CFG80211: (dependency)
>>> * WLAN: (dependency)
>>> * BRCMFMAC: wlan driver, enable as module.
>>>
>>> diff --git a/arch/arm/configs/tegra_defconfig
>>> b/arch/arm/configs/tegra_defconfig
>>>
>>> +CONFIG_BRCMFMAC=m
>>
>> Why does this need to be a module? Everything else in tegra_defconfig is
>> built-in, and it'd be nice to be consistent here. Built-in makes
>> net-booting new kernels from U-Boot much easier, since there aren't any
>> modules to copy.
> 
> network drivers (especially wifi) are often modules because they need firmwares. 

So I certainly see that WiFi modules may need firmware.

But I don't see why that should imply they must be modules; they should
be able to defer their firmware loading until the firmware is available.

> I'm not sure if the kernel can compile them in every case. Our RT2x00 is an 
> example (which also needs a defconfig entry btw) but brcmfmac also needs it as 
> modinfo shows. Beside that, I don't think you want to netboot using wifi and u-
> boot because this needs a huge wireless framework which u-boot doesn't have.

I net-boot using a USB wired Ethernet adapter. The issue isn't that I
want to use wireless from U-Boot, but rather than it's easy to download
the zImage and .dtb using U-Boot since they're just copied to RAM, but
getting a bunch of modules into a filesystem on the target before
booting the kernel is more painful.

WARNING: multiple messages have this Message-ID (diff)
From: Stephen Warren <swarren@wwwdotorg.org>
To: Marc Dietrich <marvin24@gmx.de>
Cc: Wei Ni <wni@nvidia.com>,
	swarren@nvidia.com, olof@lixom.net, ccross@android.com,
	linux@arm.linux.org.uk, linux-tegra@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, ldewangan@nvidia.com,
	arnd@arndb.de, grant.likely@secretlab.ca, cjb@laptop.org
Subject: Re: [PATCH 5/5] ARM: tegra: enable wireless in defconfig
Date: Thu, 05 Jul 2012 14:42:33 -0600	[thread overview]
Message-ID: <4FF5FC39.3090402@wwwdotorg.org> (raw)
In-Reply-To: <2114579.sqTp7XiW3H@ax5200p>

On 07/05/2012 02:35 PM, Marc Dietrich wrote:
> On Thursday 05 July 2012 13:59:11 Stephen Warren wrote:
>> On 07/04/2012 03:34 AM, Wei Ni wrote:
>>> New options enabled:
>>> * WIRELESS: (dependency)
>>> * CFG80211: (dependency)
>>> * WLAN: (dependency)
>>> * BRCMFMAC: wlan driver, enable as module.
>>>
>>> diff --git a/arch/arm/configs/tegra_defconfig
>>> b/arch/arm/configs/tegra_defconfig
>>>
>>> +CONFIG_BRCMFMAC=m
>>
>> Why does this need to be a module? Everything else in tegra_defconfig is
>> built-in, and it'd be nice to be consistent here. Built-in makes
>> net-booting new kernels from U-Boot much easier, since there aren't any
>> modules to copy.
> 
> network drivers (especially wifi) are often modules because they need firmwares. 

So I certainly see that WiFi modules may need firmware.

But I don't see why that should imply they must be modules; they should
be able to defer their firmware loading until the firmware is available.

> I'm not sure if the kernel can compile them in every case. Our RT2x00 is an 
> example (which also needs a defconfig entry btw) but brcmfmac also needs it as 
> modinfo shows. Beside that, I don't think you want to netboot using wifi and u-
> boot because this needs a huge wireless framework which u-boot doesn't have.

I net-boot using a USB wired Ethernet adapter. The issue isn't that I
want to use wireless from U-Boot, but rather than it's easy to download
the zImage and .dtb using U-Boot since they're just copied to RAM, but
getting a bunch of modules into a filesystem on the target before
booting the kernel is more painful.

  reply	other threads:[~2012-07-05 20:42 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-04  9:34 [PATCH 0/5] ARM: tegra: enable wlan for t20 and t30 Wei Ni
2012-07-04  9:34 ` Wei Ni
2012-07-04  9:34 ` Wei Ni
     [not found] ` <1341394488-13169-1-git-send-email-wni-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-07-04  9:34   ` [PATCH 1/5] ARM: tegra: set up wlan clocks for tegra dt Wei Ni
2012-07-04  9:34     ` Wei Ni
2012-07-04  9:34     ` Wei Ni
     [not found]     ` <1341394488-13169-2-git-send-email-wni-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-07-04 10:43       ` Marc Dietrich
2012-07-04 10:43         ` Marc Dietrich
2012-07-04 10:43         ` Marc Dietrich
2012-07-04 11:23         ` Wei Ni
2012-07-04 11:23           ` Wei Ni
2012-07-04 11:23           ` Wei Ni
2012-07-04 11:51           ` Marc Dietrich
2012-07-04 11:51             ` Marc Dietrich
2012-07-04 11:51             ` Marc Dietrich
2012-07-05  3:18             ` Wei Ni
2012-07-05  3:18               ` Wei Ni
2012-07-05  3:18               ` Wei Ni
2012-07-05  8:39               ` Marc Dietrich
2012-07-05  8:39                 ` Marc Dietrich
2012-07-04  9:34   ` [PATCH 5/5] ARM: tegra: enable wireless in defconfig Wei Ni
2012-07-04  9:34     ` Wei Ni
2012-07-04  9:34     ` Wei Ni
     [not found]     ` <1341394488-13169-6-git-send-email-wni-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-07-05 19:59       ` Stephen Warren
2012-07-05 19:59         ` Stephen Warren
2012-07-05 19:59         ` Stephen Warren
     [not found]         ` <4FF5F20F.2050005-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-07-05 20:35           ` Marc Dietrich
2012-07-05 20:35             ` Marc Dietrich
2012-07-05 20:35             ` Marc Dietrich
2012-07-05 20:42             ` Stephen Warren [this message]
2012-07-05 20:42               ` Stephen Warren
2012-07-05 20:42               ` Stephen Warren
     [not found]               ` <4FF5FC39.3090402-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-07-06  3:19                 ` Wei Ni
2012-07-06  3:19                   ` Wei Ni
2012-07-06  3:19                   ` Wei Ni
2012-07-06  3:08           ` Wei Ni
2012-07-06  3:08             ` Wei Ni
2012-07-06  3:08             ` Wei Ni
2012-07-06 15:42             ` Stephen Warren
2012-07-06 15:42               ` Stephen Warren
2012-07-06 15:42               ` Stephen Warren
2012-07-04  9:34 ` [PATCH 2/5] ARM: dt: t20 seaboard: add pinmux, gpio for wlan Wei Ni
2012-07-04  9:34   ` Wei Ni
2012-07-04  9:34   ` Wei Ni
2012-07-04  9:34 ` [PATCH 3/5] ARM: dt: t20 ventana: " Wei Ni
2012-07-04  9:34   ` Wei Ni
2012-07-04  9:34   ` Wei Ni
2012-07-04  9:34 ` [PATCH 4/5] ARM: dt: t30 cardhu: " Wei Ni
2012-07-04  9:34   ` Wei Ni
2012-07-04  9:34   ` Wei Ni

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=4FF5FC39.3090402@wwwdotorg.org \
    --to=swarren-3lzwwm7+weoh9zmkesr00q@public.gmane.org \
    --cc=arnd-r2nGTMty4D4@public.gmane.org \
    --cc=ccross-z5hGa2qSFaRBDgjK7y7TUQ@public.gmane.org \
    --cc=cjb-2X9k7bc8m7Mdnm+yROfE0A@public.gmane.org \
    --cc=grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org \
    --cc=ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
    --cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org \
    --cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=marvin24-Mmb7MZpHnFY@public.gmane.org \
    --cc=olof-nZhT3qVonbNeoWH0uzbU5w@public.gmane.org \
    --cc=swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
    --cc=wni-DDmLM1+adcrQT0dZR+AlfA@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.