public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Roman K <papa@rbcmail.ru>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] TECOM BT3035
Date: Mon, 26 Jul 2004 09:12:31 +0200	[thread overview]
Message-ID: <1090825950.31693.55.camel@pegasus> (raw)
In-Reply-To: <200407260936.55023.papa@rbcmail.ru>

Hi Roman,

> I have only one last question. Have you tested your patch with THIS device (I 
> mean 3035 not it's family).

I don't know if it was from Tecom, but it was the Broadcom version of
HID proxy. The hci_usb drivers states it as BCM2035 with the USB vendor
and product id of 0a5c:200a. Check for yourself.

> It looks like SuSE kernel uses you patches (when your patch trying to create a 
> file it reports that file already exists and most hunk are rejected because 
> of they are previously applied).

Of course they do. Everyone uses my patches, because I send them back to
mainline if I know that they are working. The -mh patches are against a
vanilla kernel and you couldn't expect that they apply cleanly to any of
the vendor kernel out there. No matter if it is SuSE or RedHat.

> SuSE usually uses a lot of patches (MUCH more then vanilla) and It usually  
> supports MUCH more hardware then RedHat..
> But  in this case something wrong...

Maybe they haven't picked up that patch. So what? Use the latest vanilla
2.4 kernel or extract that hunk that I told you from the kernel tree and
apply it by hand. Or simply update to SuSE 9.1 with a 2.6 kernel.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  parent reply	other threads:[~2004-07-26  7:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200407231440.i6NEeI5l048844@www1.pochta.ru>
2004-07-23 14:49 ` [Bluez-users] TECOM BT3035 Marcel Holtmann
     [not found]   ` <200407232245.46776.papa@rbcmail.ru>
2004-07-24  9:04     ` Marcel Holtmann
     [not found]       ` <200407260936.55023.papa@rbcmail.ru>
2004-07-26  7:12         ` Marcel Holtmann [this message]
2004-07-23 12:16 òÏÍÁÎ
2004-07-23 12:40 ` 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=1090825950.31693.55.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-users@lists.sourceforge.net \
    --cc=papa@rbcmail.ru \
    /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