All of lore.kernel.org
 help / color / mirror / Atom feed
From: Max Krasnyansky <maxk@qualcomm.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Re: BCM2033 firmware loader
Date: Tue, 20 Jan 2004 11:27:36 -0800	[thread overview]
Message-ID: <1074626856.1707.108.camel@localhost> (raw)
In-Reply-To: <1074302399.2629.137.camel@pegasus>

On Fri, 2004-01-16 at 17:19, Marcel Holtmann wrote:
> On the other hand it is also possible to make the firmware loading
> routine of the bcm203x driver a compile time option of the hci_usb
> driver. Of course this is also a waste inside the kernel, but you don't
> have an extra module to load. Do you think this is a better approach?
No no. I actually quite liked the idea of making it a separate driver.
Because it makes an unloading possible. I mean it won't be unloaded
automatically but at least you can do it manually.

I'll play with latest 2.6 and bluefw to see what's wrong with usbfs.

Thanks
Max

  reply	other threads:[~2004-01-20 19:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-15 19:07 [Bluez-devel] Bluetooth kernel patch for 2.6.1 Marcel Holtmann
2004-01-15 19:50 ` BCM2033 firmware loader [was Re: [Bluez-devel] Bluetooth kernel patch for 2.6.1] Max Krasnyansky
2004-01-15 20:16   ` [Bluez-devel] Re: BCM2033 firmware loader Marcel Holtmann
2004-01-16 21:14     ` Max Krasnyansky
2004-01-17  1:19       ` [Bluez-devel] " Marcel Holtmann
2004-01-20 19:27         ` Max Krasnyansky [this message]
2004-01-15 20:03 ` [Bluez-devel] Bluetooth kernel patch for 2.6.1 Max Krasnyansky
2004-01-15 20:30   ` Marcel Holtmann
2004-01-16 21:25     ` Max Krasnyansky
2004-01-17  1:08       ` Marcel Holtmann
2004-01-20 19:23         ` Max Krasnyansky
2004-01-21  1:36           ` 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=1074626856.1707.108.camel@localhost \
    --to=maxk@qualcomm.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 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.