I'm struggling a bit to build compat-wireless in a cross-build environment.
I normally don't build kernels in-tree, rather I use a build tree, e.g.
% cd <linux-source>
% mkdir /tmp/kernel_build
% make O=/tmp/kernel_build <some_config>
% make O=/tmp/kernel_build uImage
I can't see how to use this setup with the compat-wireless package.
I tried [all the combinations I could think of] something like this:
% cd <compat-wireless>
% make KLIB=<linux-source> KLIB_BUILD=/tmp/kernel_build
However, this seems to not work as all I get are errors like this:
/local/compat-wireless-2012-02-28/config.mk:242: "WARNING: CONFIG_CFG80211_WEXT will be deactivated or not working because kernel was compiled with CONFIG_WIRELESS_EXT=n. Tools
using wext interface like iwconfig will not work. To activate it build your kernel e.g. with CONFIG_LIBIPW=m."
Does this process work in my workflow? What do I need to do to
get it going?
Thanks
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
On 2012-02-29 12:59, Thomas Pedersen wrote:
> Hi Gary,
>
> On Wed, Feb 29, 2012 at 11:44 AM, Gary Thomas<[email protected]> wrote:
>> On 2012-02-29 11:48, Gary Thomas wrote:
>>>
>>> On 2012-02-29 08:43, Gary Thomas wrote:
>>>>
>>>> I'm struggling a bit to build compat-wireless in a cross-build
>>>> environment.
>>>> I normally don't build kernels in-tree, rather I use a build tree, e.g.
>>>> % cd<linux-source>
>>>> % mkdir /tmp/kernel_build
>>>> % make O=/tmp/kernel_build<some_config>
>>>> % make O=/tmp/kernel_build uImage
>>>>
>>>> I can't see how to use this setup with the compat-wireless package.
>>>> I tried [all the combinations I could think of] something like this:
>>>> % cd<compat-wireless>
>>>> % make KLIB=<linux-source> KLIB_BUILD=/tmp/kernel_build
>>>> However, this seems to not work as all I get are errors like this:
>>>> /local/compat-wireless-2012-02-28/config.mk:242: "WARNING:
>>>> CONFIG_CFG80211_WEXT will be deactivated or not working because kernel was
>>>> compiled with CONFIG_WIRELESS_EXT=n. Tools
>>>> using wext interface like iwconfig will not work. To activate it build
>>>> your kernel e.g. with CONFIG_LIBIPW=m."
>>>>
>>>> Does this process work in my workflow? What do I need to do to
>>>> get it going?
>>>
>>>
>>> I managed to get past this, using this
>>> % make KLIB=/tmp/kernel_build KLIB_BUILD=/tmp/kernel_build
>>> but to get it to actually build anything, I had to append the
>>> 'modules' target, e.g.
>>> % make KLIB=/tmp/kernel_build KLIB_BUILD=/tmp/kernel_build modules
>>>
>>> Next problems:
>>> * How do I select sub-options? I only want WL12xx support with SDIO, but
>>> that requires some sub-options to be set that don't appear to happen.
>>> I get the main wl12xx module, but not wl12xx_sdio or wl12xx_platform_data
>>> * There are a number of files which don't build against my 2.6.37 kernel,
>>> but none of these are important to me (they are in the bluetooth driver
>>> which I don't need, but nonetheless it gets built)
>>> * The make/install is terribly broken for cross-builds.
>>>
>>> I hacked my way past these problems and finally got some modules which
>>> I can try. Sadly, they don't work at all:
>>> # modprobe wl12xx_sdio
>>> wl12xx: loaded
>>> # ifconfig wlan0 up
>>> wl1271_sdio mmc1:0001:2: sdio write failed (-110)
>>> wl1271_sdio mmc1:0001:2: sdio write failed (-110)
>>> ...
>>
>>
>> Sadly, this one was my fault - one of my build hacks got in the way :-(
>>
>> Now, I'm getting this error:
>> wl12xx: ERROR could not get firmware ti-connectivity/wl127x-fw-4-sr.bin: -2
>> But this file is not available at the Linux firmware tree
>> (git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git)
>>
>> Where can I find it?
>>
>
> Try here: git://github.com/TI-OpenLink/firmwares.git
Thanks. Do you know if these will be moving to kernel.org anytime soon?
My build recipes expect that to be the official home for firmware.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
On 2012-02-29 08:43, Gary Thomas wrote:
> I'm struggling a bit to build compat-wireless in a cross-build environment.
> I normally don't build kernels in-tree, rather I use a build tree, e.g.
> % cd <linux-source>
> % mkdir /tmp/kernel_build
> % make O=/tmp/kernel_build <some_config>
> % make O=/tmp/kernel_build uImage
>
> I can't see how to use this setup with the compat-wireless package.
> I tried [all the combinations I could think of] something like this:
> % cd <compat-wireless>
> % make KLIB=<linux-source> KLIB_BUILD=/tmp/kernel_build
> However, this seems to not work as all I get are errors like this:
> /local/compat-wireless-2012-02-28/config.mk:242: "WARNING: CONFIG_CFG80211_WEXT will be deactivated or not working because kernel was compiled with CONFIG_WIRELESS_EXT=n. Tools
> using wext interface like iwconfig will not work. To activate it build your kernel e.g. with CONFIG_LIBIPW=m."
>
> Does this process work in my workflow? What do I need to do to
> get it going?
I managed to get past this, using this
% make KLIB=/tmp/kernel_build KLIB_BUILD=/tmp/kernel_build
but to get it to actually build anything, I had to append the
'modules' target, e.g.
% make KLIB=/tmp/kernel_build KLIB_BUILD=/tmp/kernel_build modules
Next problems:
* How do I select sub-options? I only want WL12xx support with SDIO, but
that requires some sub-options to be set that don't appear to happen.
I get the main wl12xx module, but not wl12xx_sdio or wl12xx_platform_data
* There are a number of files which don't build against my 2.6.37 kernel,
but none of these are important to me (they are in the bluetooth driver
which I don't need, but nonetheless it gets built)
* The make/install is terribly broken for cross-builds.
I hacked my way past these problems and finally got some modules which
I can try. Sadly, they don't work at all:
# modprobe wl12xx_sdio
wl12xx: loaded
# ifconfig wlan0 up
wl1271_sdio mmc1:0001:2: sdio write failed (-110)
wl1271_sdio mmc1:0001:2: sdio write failed (-110)
...
Note: This driver in my kernel tree gets much farther than this - it
will actually download firmware and talk to the device, so I'm pretty
perplexed by this failure.
Any help greatly appreciated
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
Hi Gary,
On Wed, Feb 29, 2012 at 11:44 AM, Gary Thomas <[email protected]> wrote:
> On 2012-02-29 11:48, Gary Thomas wrote:
>>
>> On 2012-02-29 08:43, Gary Thomas wrote:
>>>
>>> I'm struggling a bit to build compat-wireless in a cross-build
>>> environment.
>>> I normally don't build kernels in-tree, rather I use a build tree, e.g.
>>> % cd <linux-source>
>>> % mkdir /tmp/kernel_build
>>> % make O=/tmp/kernel_build <some_config>
>>> % make O=/tmp/kernel_build uImage
>>>
>>> I can't see how to use this setup with the compat-wireless package.
>>> I tried [all the combinations I could think of] something like this:
>>> % cd <compat-wireless>
>>> % make KLIB=<linux-source> KLIB_BUILD=/tmp/kernel_build
>>> However, this seems to not work as all I get are errors like this:
>>> /local/compat-wireless-2012-02-28/config.mk:242: "WARNING:
>>> CONFIG_CFG80211_WEXT will be deactivated or not working because kernel was
>>> compiled with CONFIG_WIRELESS_EXT=n. Tools
>>> using wext interface like iwconfig will not work. To activate it build
>>> your kernel e.g. with CONFIG_LIBIPW=m."
>>>
>>> Does this process work in my workflow? What do I need to do to
>>> get it going?
>>
>>
>> I managed to get past this, using this
>> % make KLIB=/tmp/kernel_build KLIB_BUILD=/tmp/kernel_build
>> but to get it to actually build anything, I had to append the
>> 'modules' target, e.g.
>> % make KLIB=/tmp/kernel_build KLIB_BUILD=/tmp/kernel_build modules
>>
>> Next problems:
>> * How do I select sub-options? I only want WL12xx support with SDIO, but
>> that requires some sub-options to be set that don't appear to happen.
>> I get the main wl12xx module, but not wl12xx_sdio or wl12xx_platform_data
>> * There are a number of files which don't build against my 2.6.37 kernel,
>> but none of these are important to me (they are in the bluetooth driver
>> which I don't need, but nonetheless it gets built)
>> * The make/install is terribly broken for cross-builds.
>>
>> I hacked my way past these problems and finally got some modules which
>> I can try. Sadly, they don't work at all:
>> # modprobe wl12xx_sdio
>> wl12xx: loaded
>> # ifconfig wlan0 up
>> wl1271_sdio mmc1:0001:2: sdio write failed (-110)
>> wl1271_sdio mmc1:0001:2: sdio write failed (-110)
>> ...
>
>
> Sadly, this one was my fault - one of my build hacks got in the way :-(
>
> Now, I'm getting this error:
> ?wl12xx: ERROR could not get firmware ti-connectivity/wl127x-fw-4-sr.bin: -2
> But this file is not available at the Linux firmware tree
> (git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git)
>
> Where can I find it?
>
Try here: git://github.com/TI-OpenLink/firmwares.git
Thomas
On 2012-02-29 11:48, Gary Thomas wrote:
> On 2012-02-29 08:43, Gary Thomas wrote:
>> I'm struggling a bit to build compat-wireless in a cross-build environment.
>> I normally don't build kernels in-tree, rather I use a build tree, e.g.
>> % cd <linux-source>
>> % mkdir /tmp/kernel_build
>> % make O=/tmp/kernel_build <some_config>
>> % make O=/tmp/kernel_build uImage
>>
>> I can't see how to use this setup with the compat-wireless package.
>> I tried [all the combinations I could think of] something like this:
>> % cd <compat-wireless>
>> % make KLIB=<linux-source> KLIB_BUILD=/tmp/kernel_build
>> However, this seems to not work as all I get are errors like this:
>> /local/compat-wireless-2012-02-28/config.mk:242: "WARNING: CONFIG_CFG80211_WEXT will be deactivated or not working because kernel was compiled with CONFIG_WIRELESS_EXT=n. Tools
>> using wext interface like iwconfig will not work. To activate it build your kernel e.g. with CONFIG_LIBIPW=m."
>>
>> Does this process work in my workflow? What do I need to do to
>> get it going?
>
> I managed to get past this, using this
> % make KLIB=/tmp/kernel_build KLIB_BUILD=/tmp/kernel_build
> but to get it to actually build anything, I had to append the
> 'modules' target, e.g.
> % make KLIB=/tmp/kernel_build KLIB_BUILD=/tmp/kernel_build modules
>
> Next problems:
> * How do I select sub-options? I only want WL12xx support with SDIO, but
> that requires some sub-options to be set that don't appear to happen.
> I get the main wl12xx module, but not wl12xx_sdio or wl12xx_platform_data
> * There are a number of files which don't build against my 2.6.37 kernel,
> but none of these are important to me (they are in the bluetooth driver
> which I don't need, but nonetheless it gets built)
> * The make/install is terribly broken for cross-builds.
>
> I hacked my way past these problems and finally got some modules which
> I can try. Sadly, they don't work at all:
> # modprobe wl12xx_sdio
> wl12xx: loaded
> # ifconfig wlan0 up
> wl1271_sdio mmc1:0001:2: sdio write failed (-110)
> wl1271_sdio mmc1:0001:2: sdio write failed (-110)
> ...
Sadly, this one was my fault - one of my build hacks got in the way :-(
Now, I'm getting this error:
wl12xx: ERROR could not get firmware ti-connectivity/wl127x-fw-4-sr.bin: -2
But this file is not available at the Linux firmware tree (git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git)
Where can I find it?
>
> Note: This driver in my kernel tree gets much farther than this - it
> will actually download firmware and talk to the device, so I'm pretty
> perplexed by this failure.
>
> Any help greatly appreciated
>
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
On Wed, 2012-02-29 at 16:08 -0800, Thomas Pedersen wrote:
> On Wed, Feb 29, 2012 at 12:18 PM, Gary Thomas <[email protected]> wrote:
> > On 2012-02-29 12:59, Thomas Pedersen wrote:
> >>
> >> Hi Gary,
> >>
> >> On Wed, Feb 29, 2012 at 11:44 AM, Gary Thomas<[email protected]> wrote:
> >>>
> >>> On 2012-02-29 11:48, Gary Thomas wrote:
> >>>>
> >>>>
> >>>> On 2012-02-29 08:43, Gary Thomas wrote:
> >>>>>
> >>>>>
> >>>>> I'm struggling a bit to build compat-wireless in a cross-build
> >>>>> environment.
> >>>>> I normally don't build kernels in-tree, rather I use a build tree, e.g.
> >>>>> % cd<linux-source>
> >>>>> % mkdir /tmp/kernel_build
> >>>>> % make O=/tmp/kernel_build<some_config>
> >>>>> % make O=/tmp/kernel_build uImage
> >>>>>
> >>>>> I can't see how to use this setup with the compat-wireless package.
> >>>>> I tried [all the combinations I could think of] something like this:
> >>>>> % cd<compat-wireless>
> >>>>> % make KLIB=<linux-source> KLIB_BUILD=/tmp/kernel_build
> >>>>> However, this seems to not work as all I get are errors like this:
> >>>>> /local/compat-wireless-2012-02-28/config.mk:242: "WARNING:
> >>>>> CONFIG_CFG80211_WEXT will be deactivated or not working because kernel
> >>>>> was
> >>>>> compiled with CONFIG_WIRELESS_EXT=n. Tools
> >>>>> using wext interface like iwconfig will not work. To activate it build
> >>>>> your kernel e.g. with CONFIG_LIBIPW=m."
> >>>>>
> >>>>> Does this process work in my workflow? What do I need to do to
> >>>>> get it going?
> >>>>
> >>>>
> >>>>
> >>>> I managed to get past this, using this
> >>>> % make KLIB=/tmp/kernel_build KLIB_BUILD=/tmp/kernel_build
> >>>> but to get it to actually build anything, I had to append the
> >>>> 'modules' target, e.g.
> >>>> % make KLIB=/tmp/kernel_build KLIB_BUILD=/tmp/kernel_build modules
> >>>>
> >>>> Next problems:
> >>>> * How do I select sub-options? I only want WL12xx support with SDIO, but
> >>>> that requires some sub-options to be set that don't appear to happen.
> >>>> I get the main wl12xx module, but not wl12xx_sdio or
> >>>> wl12xx_platform_data
> >>>> * There are a number of files which don't build against my 2.6.37
> >>>> kernel,
> >>>> but none of these are important to me (they are in the bluetooth driver
> >>>> which I don't need, but nonetheless it gets built)
> >>>> * The make/install is terribly broken for cross-builds.
> >>>>
> >>>> I hacked my way past these problems and finally got some modules which
> >>>> I can try. Sadly, they don't work at all:
> >>>> # modprobe wl12xx_sdio
> >>>> wl12xx: loaded
> >>>> # ifconfig wlan0 up
> >>>> wl1271_sdio mmc1:0001:2: sdio write failed (-110)
> >>>> wl1271_sdio mmc1:0001:2: sdio write failed (-110)
> >>>> ...
> >>>
> >>>
> >>>
> >>> Sadly, this one was my fault - one of my build hacks got in the way :-(
> >>>
> >>> Now, I'm getting this error:
> >>> wl12xx: ERROR could not get firmware ti-connectivity/wl127x-fw-4-sr.bin:
> >>> -2
> >>> But this file is not available at the Linux firmware tree
> >>>
> >>> (git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git)
> >>>
> >>> Where can I find it?
> >>>
> >>
> >> Try here: git://github.com/TI-OpenLink/firmwares.git
> >
> >
> > Thanks. Do you know if these will be moving to kernel.org anytime soon?
> > My build recipes expect that to be the official home for firmware.
> >
>
> I believe Luciano submitted these a few weeks back, so all in good time :)
Yes, I sent a pull request for this to be included in
linux-firmware.git, but Ben hasn't pulled it yet. Hopefully soon. :)
--
Cheers,
Luca.
On Wed, Feb 29, 2012 at 12:18 PM, Gary Thomas <[email protected]> wrote:
> On 2012-02-29 12:59, Thomas Pedersen wrote:
>>
>> Hi Gary,
>>
>> On Wed, Feb 29, 2012 at 11:44 AM, Gary Thomas<[email protected]> ?wrote:
>>>
>>> On 2012-02-29 11:48, Gary Thomas wrote:
>>>>
>>>>
>>>> On 2012-02-29 08:43, Gary Thomas wrote:
>>>>>
>>>>>
>>>>> I'm struggling a bit to build compat-wireless in a cross-build
>>>>> environment.
>>>>> I normally don't build kernels in-tree, rather I use a build tree, e.g.
>>>>> % cd<linux-source>
>>>>> % mkdir /tmp/kernel_build
>>>>> % make O=/tmp/kernel_build<some_config>
>>>>> % make O=/tmp/kernel_build uImage
>>>>>
>>>>> I can't see how to use this setup with the compat-wireless package.
>>>>> I tried [all the combinations I could think of] something like this:
>>>>> % cd<compat-wireless>
>>>>> % make KLIB=<linux-source> ?KLIB_BUILD=/tmp/kernel_build
>>>>> However, this seems to not work as all I get are errors like this:
>>>>> /local/compat-wireless-2012-02-28/config.mk:242: "WARNING:
>>>>> CONFIG_CFG80211_WEXT will be deactivated or not working because kernel
>>>>> was
>>>>> compiled with CONFIG_WIRELESS_EXT=n. Tools
>>>>> using wext interface like iwconfig will not work. To activate it build
>>>>> your kernel e.g. with CONFIG_LIBIPW=m."
>>>>>
>>>>> Does this process work in my workflow? What do I need to do to
>>>>> get it going?
>>>>
>>>>
>>>>
>>>> I managed to get past this, using this
>>>> % make KLIB=/tmp/kernel_build KLIB_BUILD=/tmp/kernel_build
>>>> but to get it to actually build anything, I had to append the
>>>> 'modules' target, e.g.
>>>> % make KLIB=/tmp/kernel_build KLIB_BUILD=/tmp/kernel_build modules
>>>>
>>>> Next problems:
>>>> * How do I select sub-options? I only want WL12xx support with SDIO, but
>>>> that requires some sub-options to be set that don't appear to happen.
>>>> I get the main wl12xx module, but not wl12xx_sdio or
>>>> wl12xx_platform_data
>>>> * There are a number of files which don't build against my 2.6.37
>>>> kernel,
>>>> but none of these are important to me (they are in the bluetooth driver
>>>> which I don't need, but nonetheless it gets built)
>>>> * The make/install is terribly broken for cross-builds.
>>>>
>>>> I hacked my way past these problems and finally got some modules which
>>>> I can try. Sadly, they don't work at all:
>>>> # modprobe wl12xx_sdio
>>>> wl12xx: loaded
>>>> # ifconfig wlan0 up
>>>> wl1271_sdio mmc1:0001:2: sdio write failed (-110)
>>>> wl1271_sdio mmc1:0001:2: sdio write failed (-110)
>>>> ...
>>>
>>>
>>>
>>> Sadly, this one was my fault - one of my build hacks got in the way :-(
>>>
>>> Now, I'm getting this error:
>>> ?wl12xx: ERROR could not get firmware ti-connectivity/wl127x-fw-4-sr.bin:
>>> -2
>>> But this file is not available at the Linux firmware tree
>>>
>>> (git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git)
>>>
>>> Where can I find it?
>>>
>>
>> Try here: ?git://github.com/TI-OpenLink/firmwares.git
>
>
> Thanks. ?Do you know if these will be moving to kernel.org anytime soon?
> My build recipes expect that to be the official home for firmware.
>
I believe Luciano submitted these a few weeks back, so all in good time :)
> --
> ------------------------------------------------------------
> Gary Thomas ? ? ? ? ? ? ? ? | ?Consulting for the
> MLB Associates ? ? ? ? ? ? ?| ? ?Embedded world
> ------------------------------------------------------------