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: BCM2033 firmware loader
Date: Fri, 16 Jan 2004 13:14:24 -0800	[thread overview]
Message-ID: <1074287664.2559.422.camel@localhost> (raw)
In-Reply-To: <1074197813.2629.52.camel@pegasus>

On Thu, 2004-01-15 at 12:16, Marcel Holtmann wrote:
> Hi Max,
> 
> > What's wrong with BlueFW ? Why did you implement BCM FW loader in the
> > kernel ?
> > I looked in the archive and the only thing I could find was that you
> > don't want to keep it without an explanation why.
> 
> actually I never got bluefw working stable with 2.6. The usbfs interface
> causes troubles which I can't explain. Maybe the problems are caused by
> my hardware, but I don't know. I also want to avoid using bulk transfer
> over ISOC endpoint to make OHCI happy and it seems that inside the
> kernel there exists no more problems for the OHCI chips. 
You mean Bulk over Interrupt. BlueFW doesn't send Bulk over Isoc.

> So after I made
> my experiences with the request_firmware() interface and the bfusb
> driver I decided to give it a try and the bcm203x driver was born.

I see. I have no problem with implementation in fact it's very clean and
nice. My only concern is that if it can be done from user space it
should be done in user-space thing :). I mean nobody is going to unload
this bcm203x module after fw download is complete. Yeah it's small but
it's still a waste. I'd rather fix usbfs if it's broken. Greg and
Johannes will happily accept patches ;-). 

Max

  reply	other threads:[~2004-01-16 21:14 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 [this message]
2004-01-17  1:19       ` Marcel Holtmann
2004-01-20 19:27         ` Max Krasnyansky
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=1074287664.2559.422.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.