Hi Adam,
On Wed, Oct 02, 2019 at 02:03:52PM -0500, Adam Ford wrote:
> On Tue, Mar 19, 2019 at 8:33 AM Sebastian Reichel wrote:
> After a bunch of testing, I think the issue I was having was the BTS
> file being pulled in from linux-firmware. I was able to successfully
> load a BTS file that I
On Tue, Mar 19, 2019 at 8:33 AM Sebastian Reichel wrote:
>
> Hi Hans,
>
> On Thu, Mar 14, 2019 at 09:20:10AM +0100, Hans Verkuil wrote:
> > On 12/21/18 2:17 AM, Sebastian Reichel wrote:
> > > This moves all remaining users of the legacy TI_ST driver to hcill
> > > (patches
> > > 1-3). Then
On Fri, May 10, 2019 at 10:38 AM Marcel Holtmann wrote:
>
> Hi Adam,
>
> >>> This moves all remaining users of the legacy TI_ST driver to hcill
> >>> (patches
> >>> 1-3). Then patches 4-7 convert wl128x-radio driver to a standard
> >>> platform
> >>> device driver with
Hi Adam,
>>> This moves all remaining users of the legacy TI_ST driver to hcill
>>> (patches
>>> 1-3). Then patches 4-7 convert wl128x-radio driver to a standard
>>> platform
>>> device driver with support for multiple instances. Patch 7 will result
>>> in
>>>
On Thu, Mar 14, 2019 at 3:21 AM Hans Verkuil wrote:
>
> Hi Sebastian,
>
> On 12/21/18 2:17 AM, Sebastian Reichel wrote:
> > Hi,
> >
> > This moves all remaining users of the legacy TI_ST driver to hcill (patches
> > 1-3). Then patches 4-7 convert wl128x-radio driver to a standard platform
> >
Hi,
On Sat, Dec 22, 2018 at 09:08:28PM +0100, Pavel Machek wrote:
> Merry Christmas!
>
> > This moves all remaining users of the legacy TI_ST driver to hcill (patches
> > 1-3). Then patches 4-7 convert wl128x-radio driver to a standard platform
> > device driver with support for multiple
* Adam Ford [181222 20:36]:
> As much as I'd like to see the ti-st kim stuff go, I am not able to
> load the Bluetooth on the Torpedo board (wl1283). The hooks on a
> different, wl18xx and 127x board work fine. I am not sure if there is
> anything different about the wl1283, but I don't have
* Sebastian Reichel [181222 02:48]:
> On Fri, Dec 21, 2018 at 10:02:05AM -0800, Tony Lindgren wrote:
> > Hmm so looks like nothing to configure for the clocks or
> > CPCAP_BIT_ST_L_TIMESLOT bits for cap for the EXT? So the
> > wl12xx audio is wired directly to cpcap EXT then and not a
> > TDM
Hi!
> > This moves all remaining users of the legacy TI_ST driver to hcill (patches
> > 1-3). Then patches 4-7 convert wl128x-radio driver to a standard platform
> > device driver with support for multiple instances. Patch 7 will result in
> > (userless) TI_ST driver no longer supporting radio at
On Sat, Dec 22, 2018 at 11:09 AM Tony Lindgren wrote:
>
> * Sebastian Reichel [181221 01:18]:
> > The new code has been tested on the Motorola Droid 4. For testing the audio
> > should be configured to route Ext to Speaker or Headphone. Then you need to
> > plug headphone, since its cable is
Merry Christmas!
> This moves all remaining users of the legacy TI_ST driver to hcill (patches
> 1-3). Then patches 4-7 convert wl128x-radio driver to a standard platform
> device driver with support for multiple instances. Patch 7 will result in
> (userless) TI_ST driver no longer supporting
Hi,
On Fri, Dec 21, 2018 at 10:02:05AM -0800, Tony Lindgren wrote:
> * Sebastian Reichel [181221 01:18]:
> > The new code has been tested on the Motorola Droid 4. For testing the audio
> > should be configured to route Ext to Speaker or Headphone. Then you need to
> > plug headphone, since its
* Sebastian Reichel [181221 01:18]:
> The new code has been tested on the Motorola Droid 4. For testing the audio
> should be configured to route Ext to Speaker or Headphone. Then you need to
> plug headphone, since its cable is used as antenna. For testing there is a
> 'radio' utility packages
Hi,
This moves all remaining users of the legacy TI_ST driver to hcill (patches
1-3). Then patches 4-7 convert wl128x-radio driver to a standard platform
device driver with support for multiple instances. Patch 7 will result in
(userless) TI_ST driver no longer supporting radio at runtime. Patch
14 matches
Mail list logo
