Linux bluetooth development
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Max Krasnyansky <maxk@qualcomm.com>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] Re: BCM2033 firmware loader
Date: Sat, 17 Jan 2004 02:19:59 +0100	[thread overview]
Message-ID: <1074302399.2629.137.camel@pegasus> (raw)
In-Reply-To: <1074287664.2559.422.camel@localhost>

Hi Max,

> > 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.

of course. I mixed it, maybe because I talked about ISOC transfer and
the HCI USB driver problem on the Linux USB mailing list ;)

> > 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 ;-). 

I simply agree with you on all points. If I found enough time to look at
my usbfs problems I will try to fix them.

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?

Regards

Marcel




-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2004-01-17  1:19 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       ` Marcel Holtmann [this message]
2004-01-20 19:27         ` [Bluez-devel] " 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=1074302399.2629.137.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=maxk@qualcomm.com \
    /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