linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Roskin <proski@gnu.org>
To: seco.wu@gmail.com
Cc: "Gábor Stefanik" <netrolller.3d@gmail.com>,
	linux-wireless@vger.kernel.org
Subject: Re: update compat drivers,adpter can not be work,4 help.tks
Date: Tue, 27 Apr 2010 01:55:54 -0400	[thread overview]
Message-ID: <1272347754.22987.54.camel@mj> (raw)
In-Reply-To: <s2ne4fca08d1004250142ga518cbfdn1692b54c23191bef@mail.gmail.com>

On Sun, 2010-04-25 at 16:42 +0800, SECO wrote:
> tks Sir
> 
> what's matter with update compat-wireless under bt4?
...
> 00000-9FFFF write-back
>   A0000-BFFFF uncachable

Please don't waste bandwidth and space with irrelevant logs.

> b43: Unknown symbol ssb_pmu_set_ldo_paref

It looks like b43 was compiled, but ssb wasn't.  I can reproduce the
problem with Linux 2.6.26 without SSB enabled.

The logic for enabling ssb and SSB based devices in compat-wireless has
been broken for some time.  I reported it in the past.  But not enabling
the ssb module is a new problem.

> 2010/4/23, Gábor Stefanik <netrolller.3d@gmail.com>:
> > On Fri, Apr 23, 2010 at 2:20 AM, SECO <secowu@gmail.com> wrote:
> >> & this is the full log
> >>
> >>
> >> ./scripts/gen-compat-autoconf.sh config.mk >
> >> include/linux/compat_autoconf.h
> >> make -C /lib/modules/2.6.30.9/build M=/root/compat-wireless-2.6.34-rc4
> >> modules
> >> make[1]: Entering directory `/usr/src/linux-source-2.6.30.9'

Please don't quote text irrelevant to your message.

-- 
Regards,
Pavel Roskin

      reply	other threads:[~2010-04-27  5:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-22 23:25 update compat drivers,adpter can not be work,4 help.tks SECO
2010-04-23  0:20 ` SECO
2010-04-23  8:08   ` Gábor Stefanik
2010-04-25  8:42     ` SECO
2010-04-27  5:55       ` Pavel Roskin [this message]

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=1272347754.22987.54.camel@mj \
    --to=proski@gnu.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netrolller.3d@gmail.com \
    --cc=seco.wu@gmail.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).