From: Michael Frey <mfrey@pepper.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Unable to get hciattach to work...
Date: Wed, 21 Apr 2004 11:44:28 -0400 [thread overview]
Message-ID: <C65C90C8-93AA-11D8-88A9-00039390D626@pepper.com> (raw)
In-Reply-To: <1082560168.23959.40.camel@pegasus>
Marcel,
Ok -- I was able to patch my kernel -- fixing up by hand any rejects
but I get the following when trying to build the bluez modules.
core.c: In function `bnep_session':
core.c:463: error: structure has no member named `nice'
core.c: In function `bnep_add_connection':
any idea on this one?
Michael
On Apr 21, 2004, at 11:09 AM, Marcel Holtmann wrote:
> Hi Michael,
>
>> Yes, I used the bluez-kernel-2.3.tgz release for my 2.4.18 kernel. I
>> tried downloading the latest 2.4.20 patch and I get many rejected
>> hunks. That's why I am just using the modules that come with the
>> kernel tree.
>> Is there a standalone kernel package like there was in the past and
>> just use them and not the ones in the kernel tree?
>
> there is no seperate package anymore. However the CVS contains a
> framework with that it might be possible to build the Bluetooth modules
> outside the kernel.
>
> Regards
>
> Marcel
>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: IBM Linux Tutorials
> Free Linux tutorial presented by Daniel Robbins, President and CEO of
> GenToo technologies. Learn everything from fundamentals to system
> administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
> _______________________________________________
> Bluez-devel mailing list
> Bluez-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2004-04-21 15:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-21 14:47 [Bluez-devel] Unable to get hciattach to work Michael Frey
2004-04-21 14:57 ` Marcel Holtmann
2004-04-21 15:06 ` Michael Frey
2004-04-21 15:09 ` Marcel Holtmann
2004-04-21 15:44 ` Michael Frey [this message]
2004-04-21 15:50 ` Marcel Holtmann
2004-04-21 16:47 ` Michael Frey
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=C65C90C8-93AA-11D8-88A9-00039390D626@pepper.com \
--to=mfrey@pepper.com \
--cc=bluez-devel@lists.sourceforge.net \
--cc=marcel@holtmann.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