From: Marcel Holtmann <marcel@holtmann.org>
To: Michael Frey <mfrey@pepper.com>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Unable to get hciattach to work...
Date: Wed, 21 Apr 2004 17:09:28 +0200 [thread overview]
Message-ID: <1082560168.23959.40.camel@pegasus> (raw)
In-Reply-To: <80000A27-93A5-11D8-88A9-00039390D626@pepper.com>
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:09 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 [this message]
2004-04-21 15:44 ` Michael Frey
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=1082560168.23959.40.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=mfrey@pepper.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 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.