From: Marcel Holtmann <marcel@holtmann.org>
To: cijoml@volny.cz
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] bluetooth.init enhance
Date: Sat, 10 Jul 2004 13:01:58 +0200 [thread overview]
Message-ID: <1089457318.13519.56.camel@pegasus> (raw)
In-Reply-To: <200407101251.18796.cijoml@volny.cz>
Hi Michal,
> > this is nice, but there exists already a backport of HIDP for 2.4 and I
> > submitted the HIDP support with boot protocol only for inclusion into
> > 2.6 and my plan is to include the same into 2.4.28 and my patches if I
> > found time to do this.
>
> Hmmm :) Few mounths ago you posted into mailing list that you don't plan to
> port hidp into 2.4. It's nice to hear that you changed your opinion :)
I don't really planned it, but at that point I also had no plans for the
boot protocol mode. The broken EPoX devices convinced me otherwise and
so a least the boot protocol mode should be possible for 2.4, but don't
ask me how soon I will do that. Is there anyone else who will fill this
gap right now?
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-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2004-07-10 11:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-10 10:16 [Bluez-users] bluetooth.init enhance Bc. Michal Semler
2004-07-10 10:45 ` Marcel Holtmann
2004-07-10 10:51 ` Bc. Michal Semler
2004-07-10 11:01 ` Marcel Holtmann [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=1089457318.13519.56.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-users@lists.sourceforge.net \
--cc=cijoml@volny.cz \
/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.