public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: "PAN Sunny S K" <sunnypan@ust.hk>
To: "G�bor Stefanik" <netrolller.3d@gmail.com>
Cc: "PAN Sunny S K" <sunnypan@ust.hk>,
	"Pavel Roskin" <proski@gnu.org>,
	"Luis R. Rodriguez" <mcgrof@gmail.com>,
	linux-wireless@vger.kernel.org
Subject: Re: Building of compat-wireless-old in 2.6.25 BSP kernel for PowerPC architecture
Date: Mon, 1 Feb 2010 12:29:31 +0800 (HKT)	[thread overview]
Message-ID: <55076.143.89.144.207.1264998571.squirrel@sqmail.ust.hk> (raw)
In-Reply-To: <69e28c911001312014r552f6947pccda2e6c8d2b5e5e@mail.gmail.com>

> On Mon, Feb 1, 2010 at 5:06 AM, PAN Sunny S K <sunnypan@ust.hk> wrote:
>> Hi Pavel,
>>
>> It is unfortunate that the ath_pci is dependent on ath.
>
> No, you shouldn't even try to load ath_pci - ath_pci is part of
> Madwifi, you need to load ath9k instead.
>
> BTW are you loading the modules using modprobe or insmod?
>

Thanks, both insmod and modprobe for ath produces the same result:

ath: Unknown symbol wiphy_apply_custom_regulatory
ath: Unknown symbol freq_reg_info

modprobe for rfkill_backport and cfg80211 even produce not found error and
only insmod will produce the provided snapshot.

>> Moreover, after
>> some trial, found that the rfkill_backport and cfg80211 also have
>> problem
>> in loading which is possibly due to the lacking of other symbolic link
>> in
>> the current kernel or other modules.
>> Since other issues (iw, libnl... etc) makes the difficulties in
>> integrating ath9k into the current LTIB harder than using of OpenWrt
>> with
>> the latest kernel  (although still have some problem in building of
>> OpenWrt for the platform). I've since moved the effort to building of
>> OpenWrt.
>> Anyhow, many thanks for the advice and below please find a snapshot of
>> the
>> error output from the ath9k with kernel 2.6.25 from LTIB for your future
>> reference.
>>
>> ath: Unknown symbol wiphy_apply_custom_regulatory
>>
>> ath: Unknown symbol freq_reg_info
>>
>> ath_pci: Unknown symbol ath_config_crypto_get
>>
>> ath_pci: Unknown symbol ath_config_ioctl_getwscie
>>
>> ath_pci: Unknown symbol ath_config_ioctl_addmac
>>
>> ath_pci: Unknown symbol ath_config_ioctl_delkey
>>
>> ath_pci: Unknown symbol ath_config_set_txmode
>>
>> ath_pci: Unknown symbol ath_config_ioctl_getkey
>>
>> ath_pci: Unknown symbol ath_config_set_rate
>>
>> ath_pci: Unknown symbol ath_config_getstastats
>>
>> ath_pci: Unknown symbol ath_config_ioctl_getchaninfo
>>
>> ath_pci: Unknown symbol ath_config_set_phy_mode
>>
>> ath_pci: Unknown symbol ath_config_setparam
>>
>> ath_pci: Unknown symbol ath_config_set_ap
>>
>> ath_pci: Unknown symbol ath_config_set_essid
>>
>> ath_pci: Unknown symbol ath_config_crypto_set
>>
>> ath_pci: Unknown symbol ath_config_set_nickn
>>
>> ath_pci: Unknown symbol ath_config_getwmmparams
>>
>> ath_pci: Unknown symbol ath_config_ioctl_sendaddba
>>
>> ath_pci: Unknown symbol ath_config_get_chanlist
>>
>> ath_pci: Unknown symbol ath_config_get_frag
>>
>> ath_pci: Unknown symbol ath_config_vdev_getstats
>>
>> ath_pci: Unknown symbol ath_config_getcounter
>>
>> ath_pci: Unknown symbol ath_config_get_nickn
>>
>> ath_pci: Unknown symbol ath_config_ioctl_setaddbaresponse
>>
>> ath_pci: Unknown symbol ath_config_set_power
>>
>> ath_pci: Unknown symbol ath_handler_register
>>
>> ath_pci: Unknown symbol ath_config_set_remote_acl_status
>>
>> ath_pci: Unknown symbol ath_config_set_chanlist
>>
>> ath_pci: Unknown symbol ath_config_ioctl_setkey
>>
>> ath_pci: Unknown symbol set_quality
>>
>> ath_pci: Unknown symbol ath_config_get_txpow
>>
>> ath_pci: Unknown symbol ath_config_getstainfo
>>
>> ath_pci: Unknown symbol ath_config_get_scan
>>
>> ath_pci: Unknown symbol ath_config_getstats
>>
>> ath_pci: Unknown symbol ath_config_ioctl_gethwdata
>>
>> ath_pci: Unknown symbol ath_config_ioctl_getaddbastatus
>>
>> ath_pci: Unknown symbol ath_config_ioctl_setoptie
>>
>> ath_pci: Unknown symbol ath_config_ismodesupported
>>
>> ath_pci: Unknown symbol ath_config_get_rate
>>
>> ath_pci: Unknown symbol ath_config_get_ap
>>
>> ath_pci: Unknown symbol ath_config_set_frag
>>
>> ath_pci: Unknown symbol ath_config_set_channel
>>
>> ath_pci: Unknown symbol ath_config_set_cwsize
>>
>> ath_pci: Unknown symbol ath_config_get_phy_mode
>>
>> ath_pci: Unknown symbol ath_newstate
>>
>> ath_pci: Unknown symbol ath_config_get_channel_list
>>
>> ath_pci: Unknown symbol ath_config_get_essid
>>
>> ath_pci: Unknown symbol ath_config_ioctl_chanswitch
>>
>> ath_pci: Unknown symbol ath_config_vdev_iw_getstats
>>
>> ath_pci: Unknown symbol ath_config_set_txpow
>>
>> ath_pci: Unknown symbol ath_config_ioctl_senddelba
>>
>> ath_pci: Unknown symbol ath_set_mac_address
>>
>> ath_pci: Unknown symbol ath_config_get_opmode
>>
>> ath_pci: Unknown symbol ath_config_get_rate_list
>>
>> ath_pci: Unknown symbol ath_config_set_scan
>>
>> ath_pci: Unknown symbol ath_config_get_rts
>>
>> ath_pci: Unknown symbol ath_config_ioctl_getwpaie
>>
>> ath_pci: Unknown symbol ath_config_set_rts
>>
>> ath_pci: Unknown symbol ath_handler_unregister
>>
>> ath_pci: Unknown symbol ath_config_get_power
>>
>> ath_pci: Unknown symbol ath_config_get_txmode
>>
>> ath_pci: Unknown symbol ath_config_ioctl_delmac
>>
>> ath_pci: Unknown symbol ath_config_getstrparam
>>
>> ath_pci: Unknown symbol ath_config_ioctl_setmlme
>>
>> ath_pci: Unknown symbol ath_config_getaddrparam
>>
>> ath_pci: Unknown symbol ath_config_setwmmparams
>>
>> ath_pci: Unknown symbol ath_config_get_wbuf
>>
>> ath_pci: Unknown symbol ath_config_get_channel
>>
>> ath_pci: Unknown symbol ath_iterate_vaps
>>
>> ath_pci: Unknown symbol ath_config_getparam
>>
>> rfkill_backport: Unknown symbol dev_set_name
>>
>> rfkill_backport: Unknown symbol input_register_handle
>>
>> rfkill_backport: Unknown symbol input_open_device
>>
>> rfkill_backport: Unknown symbol led_trigger_unregister
>>
>> rfkill_backport: Unknown symbol input_close_device
>>
>> rfkill_backport: Unknown symbol input_unregister_handler
>>
>> rfkill_backport: Unknown symbol input_register_handler
>>
>> rfkill_backport: Unknown symbol led_trigger_register
>>
>> rfkill_backport: Unknown symbol input_unregister_handle
>>
>> rfkill_backport: Unknown symbol led_trigger_event
>>
>> cfg80211: Unknown symbol backport_rfkill_blocked
>>
>> cfg80211: Unknown symbol backport_rfkill_register
>>
>> cfg80211: Unknown symbol backport_rfkill_destroy
>>
>> cfg80211: Unknown symbol backport_rfkill_unregister
>>
>> cfg80211: Unknown symbol backport_rfkill_resume_polling
>>
>> cfg80211: Unknown symbol backport_rfkill_set_sw_state
>>
>> cfg80211: Unknown symbol backport_rfkill_pause_polling
>>
>> cfg80211: Unknown symbol backport_rfkill_set_hw_state
>>
>> cfg80211: Unknown symbol backport_rfkill_alloc
>>
>> Best regards,
>> Sunny
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe
>> linux-wireless" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>
>
>
>
> --
> Vista: [V]iruses, [I]ntruders, [S]pyware, [T]rojans and [A]dware. :-)
>



  reply	other threads:[~2010-02-01  4:29 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-26  6:44 Building of compat-wireless-old in 2.6.25 BSP kernel for PowerPC architecture PAN Sunny S K
2010-01-26  7:28 ` Pavel Roskin
2010-01-26 16:31 ` X Xiao
2010-01-26 16:53 ` Luis R. Rodriguez
2010-01-27 10:48   ` PAN Sunny S K
2010-01-27 18:06     ` Luis R. Rodriguez
2010-01-29  6:41       ` PAN Sunny S K
2010-01-29 17:35         ` Pavel Roskin
2010-02-01  4:06           ` PAN Sunny S K
2010-02-01  4:14             ` Gábor Stefanik
2010-02-01  4:29               ` PAN Sunny S K [this message]
2010-02-01 18:03                 ` Gábor Stefanik
2010-02-02 12:15                   ` Sunny Pan
2010-01-27 22:02     ` Pavel Roskin

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=55076.143.89.144.207.1264998571.squirrel@sqmail.ust.hk \
    --to=sunnypan@ust.hk \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mcgrof@gmail.com \
    --cc=netrolller.3d@gmail.com \
    --cc=proski@gnu.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