From: Jorgen Lundman <lundman@lundman.net>
To: linux-bluetooth@vger.kernel.org
Subject: Re: Linux 2.6.28-10 Oops in hci_send_to_sock
Date: Thu, 03 Mar 2011 11:37:57 +0900 [thread overview]
Message-ID: <4D6EFF05.8080509@lundman.net> (raw)
In-Reply-To: <4D69EE46.9050401@lundman.net>
> register int evt = (*(__u8 *)skb->data & HCI_FLT_EVENT_BITS);
Ok, so skb->data has value 8, this is probably because the kernel sk_buff and
the one I use to compile are too different. Sure enough. Intel uses a vastly
different kernel not easily obtainable. But once I had it, this issue went away.
Sorry for the noise.
Lund
--
Jorgen Lundman | <lundman@lundman.net>
Unix Administrator | +81 (0)3 -5456-2687 ext 1017 (work)
Shibuya-ku, Tokyo | +81 (0)90-5578-8500 (cell)
Japan | +81 (0)3 -3375-1767 (home)
next prev parent reply other threads:[~2011-03-03 2:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-27 6:25 Linux 2.6.28-10 Oops in hci_send_to_sock lundman
2011-03-03 2:37 ` Jorgen Lundman [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-02-26 5:57 lundman
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=4D6EFF05.8080509@lundman.net \
--to=lundman@lundman.net \
--cc=linux-bluetooth@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).