From: Hauke Mehrtens <hauke@hauke-m.de>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: Elvis Dowson <elvis.dowson@mac.com>, "Kahn, Gery" <geryk@ti.com>,
Oz Krakowski <ozk@ti.com>,
Linux Wireless Mailing List <linux-wireless@vger.kernel.org>
Subject: Re: Backporting wl1271 driver to kernel-2.6.32 using compat-wireless
Date: Wed, 22 Dec 2010 19:13:15 +0100 [thread overview]
Message-ID: <4D123FBB.1050801@hauke-m.de> (raw)
In-Reply-To: <AANLkTimMWH63yG2tdu7OHemHs=6OOy_i5fpeEDhhh6O9@mail.gmail.com>
On 12/22/2010 06:39 PM, Luis R. Rodriguez wrote:
> On Wed, Dec 22, 2010 at 12:29 PM, Elvis Dowson <elvis.dowson@mac.com> wrote:
>> Hi,
>>
>> On Dec 22, 2010, at 8:47 PM, Hauke Mehrtens wrote:
>>
>>> On 12/22/2010 05:13 PM, Luis R. Rodriguez wrote:
>>>> On Wed, Dec 22, 2010 at 11:09 AM, Elvis Dowson <elvis.dowson@mac.com> wrote:
>>>>> netdev_alloc_skb_ip_align
>>>>
>>>> I notice you have an android kernel, is that kernel a vanilla kernel
>>>> or did it get netdev_alloc_skb_ip_align() cherry picked into it?
>>
>>
>> Yes, it is an android enabled 2.6.32 kernel. It also includes the TI
>> OMAP35xx/AM35xx platform support package SDK v03.00.01.06/
>>
>>
>>> netdev_alloc_skb_ip_align is not defined in the 2.6.32.27 vanilla
>>> kernel. Someone else (google or ti) must have backported it to this
>>> kernel and added it to your kernel.
>>>
>>> I do not want to add some special handling into compat-wireless just for
>>> some android kernel. Just remove netdev_alloc_skb_ip_align() and
>>> NETDEV_POST_INIT from include/linux/compat-2.6.33.h and the compile
>>> problems you posted should be fixed.
>>
>> I made the following modifications, but get another error:
>>
>> diff --git a/include/linux/compat-2.6.33.h b/include/linux/compat-2.6.33.h
>> index c2dbc1b..468a074 100644
>> --- a/include/linux/compat-2.6.33.h
>> +++ b/include/linux/compat-2.6.33.h
>> @@ -52,19 +52,6 @@ static inline void compat_release_firmware(const struct firmware *fw)
>> #define IFF_DONT_BRIDGE 0x800 /* disallow bridging this ether dev */
>> /* source: include/linux/if.h */
>>
>> -/* this will never happen on older kernels */
>> -#define NETDEV_POST_INIT 0xffff
>> -
>> -static inline struct sk_buff *netdev_alloc_skb_ip_align(struct net_device *dev,
>> - unsigned int length)
>> -{
>> - struct sk_buff *skb = netdev_alloc_skb(dev, length + NET_IP_ALIGN);
>> -
>> - if (NET_IP_ALIGN && skb)
>> - skb_reserve(skb, NET_IP_ALIGN);
>> - return skb;
>> -}
>> -
>> #if defined(CONFIG_PCCARD) || defined(CONFIG_PCCARD_MODULE)
>>
>> #if defined(CONFIG_PCMCIA) || defined(CONFIG_PCMCIA_MODULE)
>
> I'd rather you figure out a way to identify that android kernel
> somehow reliably and send a patch upstream to ifdef out
> netdev_alloc_skb_ip_align() for that kernel, that way other Android
> hackers can benefit.
>
>> CC [M] /tool/patches/compat-wireless-2.6.37-rc6-3-patchwork/net/mac80211/led.o
>> /tool/patches/compat-wireless-2.6.37-rc6-3-patchwork/net/mac80211/led.c: In function ‘ieee80211_led_init’:
>> /tool/patches/compat-wireless-2.6.37-rc6-3-patchwork/net/mac80211/led.c:59: error: invalid application of ‘sizeof’ to incomplete type ‘struct led_trigger’
>
>
> This is from:
>
> void ieee80211_led_init(struct ieee80211_local *local)
> {
> local->rx_led = kzalloc(sizeof(struct led_trigger), GFP_KERNEL);
> ...
> }
>
> Looks good to me.. Not sure what can cause this, hrm.
>
> Luis
In your kernel config CONFIG_LEDS_TRIGGERS is probably unset and then
net/mac80211/led.c should not be build at all. In the kernel
CONFIG_MAC80211_LEDS will select CONFIG_LEDS_TRIGGERS, but in
compat-wireless this should just be disabled.
I provided a patch for this problem, please apply it and try again.
Hauke
next prev parent reply other threads:[~2010-12-22 18:13 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1CA1EE34-CB3D-404D-ADEE-612C8783BFCF@mac.com>
[not found] ` <AANLkTin8RZwVrWAdNn_Q+_bX8BAHgKreyHiVjznZtMxU@mail.gmail.com>
[not found] ` <1A56906E-D786-45E6-9C77-C9D600B508B0@mac.com>
[not found] ` <AANLkTikhLKuw56BhDkBUMU-nf8ZYF1v5Berj-+qupAtO@mail.gmail.com>
[not found] ` <E90F18E9-6332-4A7C-97DA-01169E5BB5E1@mac.com>
[not found] ` <AANLkTik6m0rabY3ZCseoch7fwxhMksMD83A-ygtN4cVu@mail.gmail.com>
2010-12-22 11:30 ` Backporting wl1271 driver to kernel-2.6.32 using compat-wireless Elvis Dowson
2010-12-22 15:39 ` Kahn, Gery
[not found] ` <AANLkTi=owvDyO3qfahUwRv4MxJrvMK9hjh5NOwRHQuO+@mail.gmail.com>
2010-12-22 16:09 ` Elvis Dowson
2010-12-22 16:13 ` Luis R. Rodriguez
2010-12-22 16:47 ` Hauke Mehrtens
2010-12-22 17:21 ` Luis R. Rodriguez
2010-12-22 17:22 ` Luis R. Rodriguez
2010-12-22 17:32 ` John W. Linville
2010-12-22 17:29 ` Elvis Dowson
2010-12-22 17:39 ` Luis R. Rodriguez
2010-12-22 18:13 ` Hauke Mehrtens [this message]
2010-12-22 19:34 ` Elvis Dowson
2010-12-22 20:03 ` Elvis Dowson
2010-12-22 20:12 ` Hauke Mehrtens
2010-12-22 20:34 ` Elvis Dowson
2010-12-22 21:00 ` Hauke Mehrtens
2010-12-22 21:07 ` Elvis Dowson
2010-12-23 5:52 ` Ohad Ben-Cohen
2010-12-23 21:12 ` Elvis Dowson
2010-12-25 8:05 ` Ohad Ben-Cohen
2010-12-23 9:44 ` Elvis Dowson
2010-12-23 14:57 ` Elvis Dowson
2010-12-23 15:56 ` Elvis Dowson
2010-12-23 15:33 ` Elvis Dowson
2010-12-24 5:17 ` Elvis Dowson
2010-12-25 8:02 ` Ohad Ben-Cohen
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=4D123FBB.1050801@hauke-m.de \
--to=hauke@hauke-m.de \
--cc=elvis.dowson@mac.com \
--cc=geryk@ti.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@gmail.com \
--cc=ozk@ti.com \
/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).