Multiple AD9361 Devices Cause Multiple Connections Error

JK
James Kulp
Thu, Jun 11, 2020 9:37 PM

This is issue #894 on gitlab.

Its unlikely for 1.7.0, but perhaps 1.7.1.  Sorry for the delay -
there's just lots going on...

On 6/10/20 10:57 AM, Brian Padalino wrote:

Wondering is this should be fixed for the v1.7.0 release.

If not, is there an issue I can track?

Thanks,
Brian

On Wed, Feb 19, 2020 at 12:45 PM Brian Padalino bpadalino@gmail.com wrote:

On Wed, Feb 19, 2020 at 11:33 AM Davis Hoover dhoover@geontech.com
wrote:

Glad you got the config build working. Let us know if you have any
bitstream build issues.

Please keep in mind this fix is intended as a temporary "hack". We will
continue to investigate proper resolution of the issue, likely via new XML
attributes for providing device/subdevice connection disambiguation, and
let you know of any further updates.

Roger that.  I will keep it as a set of my patches to apply to v1.5.1.

Again, thanks for the quick diagnosis and help.

Brian

This is issue #894 on gitlab. Its unlikely for 1.7.0, but perhaps 1.7.1.  Sorry for the delay - there's just lots going on... On 6/10/20 10:57 AM, Brian Padalino wrote: > Wondering is this should be fixed for the v1.7.0 release. > > If not, is there an issue I can track? > > Thanks, > Brian > > On Wed, Feb 19, 2020 at 12:45 PM Brian Padalino <bpadalino@gmail.com> wrote: > >> On Wed, Feb 19, 2020 at 11:33 AM Davis Hoover <dhoover@geontech.com> >> wrote: >> >>> Glad you got the config build working. Let us know if you have any >>> bitstream build issues. >>> >>> Please keep in mind this fix is intended as a temporary "hack". We will >>> continue to investigate proper resolution of the issue, likely via new XML >>> attributes for providing device/subdevice connection disambiguation, and >>> let you know of any further updates. >>> >> Roger that. I will keep it as a set of my patches to apply to v1.5.1. >> >> Again, thanks for the quick diagnosis and help. >> >> Brian >> >
BP
Brian Padalino
Thu, Jun 11, 2020 9:48 PM

On Thu, Jun 11, 2020 at 5:37 PM James Kulp jek@parera.com wrote:

This is issue #894 on gitlab.

Its unlikely for 1.7.0, but perhaps 1.7.1.  Sorry for the delay -
there's just lots going on...

Understandable, and no problem.  It's good to be able to track it.

Thanks,
Brian

On 6/10/20 10:57 AM, Brian Padalino wrote:

Wondering is this should be fixed for the v1.7.0 release.

If not, is there an issue I can track?

Thanks,
Brian

On Wed, Feb 19, 2020 at 12:45 PM Brian Padalino bpadalino@gmail.com
wrote:

On Wed, Feb 19, 2020 at 11:33 AM Davis Hoover dhoover@geontech.com
wrote:

Glad you got the config build working. Let us know if you have any
bitstream build issues.

Please keep in mind this fix is intended as a temporary "hack". We will
continue to investigate proper resolution of the issue, likely via new
XML
attributes for providing device/subdevice connection disambiguation,
and
let you know of any further updates.

Roger that.  I will keep it as a set of my patches to apply to v1.5.1.

Again, thanks for the quick diagnosis and help.

Brian

On Thu, Jun 11, 2020 at 5:37 PM James Kulp <jek@parera.com> wrote: > This is issue #894 on gitlab. > > Its unlikely for 1.7.0, but perhaps 1.7.1. Sorry for the delay - > there's just lots going on... > Understandable, and no problem. It's good to be able to track it. Thanks, Brian > > > > On 6/10/20 10:57 AM, Brian Padalino wrote: > > Wondering is this should be fixed for the v1.7.0 release. > > > > If not, is there an issue I can track? > > > > Thanks, > > Brian > > > > On Wed, Feb 19, 2020 at 12:45 PM Brian Padalino <bpadalino@gmail.com> > wrote: > > > >> On Wed, Feb 19, 2020 at 11:33 AM Davis Hoover <dhoover@geontech.com> > >> wrote: > >> > >>> Glad you got the config build working. Let us know if you have any > >>> bitstream build issues. > >>> > >>> Please keep in mind this fix is intended as a temporary "hack". We will > >>> continue to investigate proper resolution of the issue, likely via new > XML > >>> attributes for providing device/subdevice connection disambiguation, > and > >>> let you know of any further updates. > >>> > >> Roger that. I will keep it as a set of my patches to apply to v1.5.1. > >> > >> Again, thanks for the quick diagnosis and help. > >> > >> Brian > >> > >