From: Brad Midgley <bmidgley@xmission.com>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Problems with Ambicom BT-2000E
Date: Thu, 20 Jul 2006 09:19:30 -0600 [thread overview]
Message-ID: <44BF9F02.2040103@xmission.com> (raw)
In-Reply-To: <20060720145130.GA19833@adamis.de>
Mathias
> However it wouldn't be that bad not having to patch each new kernel
> again and again... maybe you know some contact to get this thing solved?
I don't know anyone like that--sorry.
One reason I think it got overlooked is you claimed to support hardware
that you didn't have around to test. Keep the scope and impact limited
and if it supports something new as a side effect, you may want to keep
that under your hat if you don't have someone to test it.
The other route you can go is ask a vendor to support it. I think ubuntu
is in a good position for that. If people start to benefit from a vendor
patch, the kernel guys may see it differently.
Brad
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2006-07-20 15:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-19 21:02 [Bluez-users] Problems with Ambicom BT-2000E Eran
2006-07-19 21:42 ` Mathias Adam
2006-07-20 0:28 ` Brad Midgley
2006-07-20 14:51 ` Mathias Adam
2006-07-20 15:19 ` Brad Midgley [this message]
2006-07-26 7:29 ` Marcel Holtmann
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=44BF9F02.2040103@xmission.com \
--to=bmidgley@xmission.com \
--cc=bluez-users@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 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).