On Fri, Oct 1, 2010 at 4:12 AM, Bala Shanmugam <sbalashanmugam@xxxxxxxxxxx> wrote: > Disabled staging directory compilation for bt target. Huh? This commit log message also is unrelated to the patch below, please separate and submit two separate patches. > Signed-off-by: Bala Shanmugam <sbalashanmugam@xxxxxxxxxxx> > --- > ÂMakefile                 Â|  Â9 +- > Âcrap/0003-btusb-Add-fw-load-support.patch | Â424 +++++++++++++++++++++++++++++ > Â2 files changed, 428 insertions(+), 5 deletions(-) > Âcreate mode 100644 crap/0003-btusb-Add-fw-load-support.patch > > diff --git a/Makefile b/Makefile > index e2c594a..4505080 100644 > --- a/Makefile > +++ b/Makefile > @@ -31,17 +31,16 @@ obj-$(CONFIG_COMPAT_NET_USB_MODULES) += drivers/net/usb/ > > Âobj-$(CONFIG_COMPAT_NETWORK_MODULES) += drivers/net/ > Âobj-$(CONFIG_COMPAT_VAR_MODULES) += Âdrivers/ssb/ drivers/misc/eeprom/ > -endif > - > -obj-$(CONFIG_COMPAT_BLUETOOTH) += net/bluetooth/ > -obj-$(CONFIG_COMPAT_BLUETOOTH_MODULES) += drivers/bluetooth/ > - > > Âifeq ($(CONFIG_STAGING_EXCLUDE_BUILD),) > Âobj-$(CONFIG_COMPAT_STAGING) += drivers/staging/ath6kl/ > Âobj-$(CONFIG_COMPAT_STAGING) += drivers/staging/brcm80211/ > Âendif > > +endif > + > +obj-$(CONFIG_COMPAT_BLUETOOTH) += net/bluetooth/ > +obj-$(CONFIG_COMPAT_BLUETOOTH_MODULES) += drivers/bluetooth/ > > Âelse > > diff --git a/crap/0003-btusb-Add-fw-load-support.patch b/crap/0003-btusb-Add-fw-load-support.patch > new file mode 100644 > index 0000000..2fc1abe > --- /dev/null > +++ b/crap/0003-btusb-Add-fw-load-support.patch Actually I'd like to apply this patch to linux-next-pending/ not to crap/ as you *did* post the patch upstream right? It just is not getting applied yet for the reasons you stated. > @@ -0,0 +1,424 @@ > +Reason for not yet publishing: This not accurate, you did publish the patch, this goes into linux-next-pending and you instead need a "Reason for not being merged yet" or for adding it to the linux-next-pending/ directory. > Marcel feels that Atheros sflash based BT device > +doesn't follow bluetooth H:2 specification and HCI commands should be supported > +in firmware if it is detected as bluetooth device. Using HCI command, firmware > +should be loaded. > + > +In sfash based device we don't have enough memory to support HCI commands in firmware. > +So load firmware from btusb when the device comes up. > + You should still ask the maintainer for an alternative, otherwise the device unusable. Did you submit the patch first in [PATCH] form? If not please submit the patch, all I saw as an RFC and no followup at all. -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
