From: Marcel Holtmann <marcel@holtmann.org>
To: Bastian Ballmann <Crazydj@chaostal.de>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] PAN and kernel 2.4.26
Date: Mon, 28 Jun 2004 11:19:07 +0200 [thread overview]
Message-ID: <1088414347.3774.170.camel@pegasus> (raw)
In-Reply-To: <1088413956.2508.3.camel@espy.crazydj.de>
Hi Bastian,
> > so about what kernel version are we talking that fails? I am little bit
> > lost.
>
> PAN on 2.4.26 fails with "Failed to get L2CAP options. Invalid argument(22)",
> but it cannot be a problem with that kernel version, because I am
> now using the same kernel version on my laptop and PAN is working.
now I understand it. Is this a vanilla 2.4.26 from kernel.org?
Regards
Marcel
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2004-06-28 9:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-26 17:41 [Bluez-devel] PAN and kernel 2.4.26 Bastian Ballmann
2004-06-27 19:20 ` Marcel Holtmann
2004-06-27 21:41 ` Bastian Ballmann
2004-06-28 7:01 ` Marcel Holtmann
2004-06-28 9:12 ` Bastian Ballmann
2004-06-28 9:19 ` Marcel Holtmann [this message]
2004-06-28 10:27 ` Bastian Ballmann
2004-06-28 10:36 ` Marcel Holtmann
[not found] ` <1088423529.2513.15.camel@espy.crazydj.de>
2004-06-28 12:58 ` Marcel Holtmann
2004-06-28 13:23 ` Bastian Ballmann
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=1088414347.3774.170.camel@pegasus \
--to=marcel@holtmann.org \
--cc=Crazydj@chaostal.de \
--cc=bluez-devel@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.