Hi Daniel, >> Since this is not your fault, I am willing to merge this change (after minor cleanup) and then convert it over to move the vendor HCI commands into btrtl.ko separate module. >> >> I have already done this for btbcm.ko and btintel.ko and I will do this with other vendor details as well. So this is the strategy that we are heading towards. As I said, this is something that came along and is a new requirement and I am willing to do fix this up for you after merging the patch. So nothing to worry about. It is just a heads up. > > Nice. I would be happy to do this, but it might take me a week or so > to get to it. no worries. Just address my comments and I can deal with moving this into a separate module. I have no issue with doing that into a two step process. >> This needs to be a separate patch on top of adding basic support for Realtek devices. So please split this out. >> >> And while you do, please create a data->flags for it and not copy the driver_info into the btusb_data structure. Lets define a common flag indicating the need for reset_resume = 1. And then only if the Realtek hardware has been detected, this flag gets set. > > OK. I will submit this as a separate patch once the main part has gone in. Sounds good to me. Regards Marcel -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
