From: Pavel Roskin <proski@gnu.org>
To: Mijzelf <Mijzelf@live.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Uknown symbols in rfkill_backport.ko on 2.6.25.17 on mips
Date: Wed, 1 Aug 2012 18:09:34 -0400 [thread overview]
Message-ID: <20120801180934.4dc2c9e3@mj> (raw)
In-Reply-To: <loom.20120729T135851-141@post.gmane.org>
On Sun, 29 Jul 2012 12:31:16 +0000 (UTC)
Mijzelf <Mijzelf@live.com> wrote:
> Looking at this it seems to me it must be some compiler-inserted
> memory barrier, or something like that. But that memcpy baffles me.
You did a great job tracking down the problem. I think the next step
would be to ask in the mips mailing list. The wireless subsystem has
nothing to do with that problem.
> I think I'll just add a dummy _flush_cache. My target system is
> single core, I suppose it would be safe.
I think it's worth trying.
--
Regards,
Pavel Roskin
prev parent reply other threads:[~2012-08-01 22:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-22 19:11 Uknown symbols in rfkill_backport.ko on 2.6.25.17 on mips Mijzelf
2012-07-24 21:56 ` Pavel Roskin
2012-07-25 18:10 ` Mijzelf
2012-07-26 21:25 ` Pavel Roskin
2012-07-29 12:31 ` Mijzelf
2012-08-01 22:09 ` 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=20120801180934.4dc2c9e3@mj \
--to=proski@gnu.org \
--cc=Mijzelf@live.com \
--cc=linux-wireless@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).