On Sun, Oct 13, 2024 at 07:09:10PM -0700, Bryan Vyhmeister wrote:
> On Sun, Oct 13, 2024 at 06:59:45PM -0700, Mike Larkin wrote:
> > On Thu, Oct 10, 2024 at 08:49:35PM -0700, Bryan Vyhmeister wrote:
> > > This is an update to comms/hackrf from the previous 2023.01.1 release to
> > > 2024.02.1. The major changes are:
> > >
> > > "A new utility, hackrf_biast, provides a way to control the "bias
> > > tee" antenna port power output on HackRF One. Thank you, Jonathan Suite
> > > (AI6AJ)!
> > > Completely new and comprehensive libhackrf API documentation generated
> > > from source is now available in the release package. Thank you, L?szl?
> > > Bar?th!
> > > hackrf_sweep now supports more FFTW features including the ability to
> > > use a wisdom file. Thank you, Jonathan Suite (AI6AJ)!
> > > HackRF One r10, the latest hardware revision, is based on r8, reverting
> > > most of the changes made in r9."
> > >
> > > https://github.com/greatscottgadgets/hackrf/releases/tag/v2024.02.1
> > >
> > > I don't yet have a HackRF One to use this with. If someone could test
> > > with a HackRF One, that would be great. The link above does note, "To
> > > upgrade to this release, you must update libhackrf and hackrf-tools on
> > > your host computer. You must also update firmware on your HackRF."
> > >
> > > I bumped SHARED_LIBS from 0.0 to 0.1. From the ports FAQ, I might need
> > > to bump it to 1.0 but not sure on that one.
> > >
> > > Bryan
> > >
> >
> > I do have one, how/what do you want me to test?
>
> If you could just test that the software seems to work with your device
> in whatever way you normally use it, that would be great. There is also
> the new hackrf_biast binary. If you could just make sure it connects to
> the HackRF One and seems to work normally, I would greatly appreciate
> it. I don't want to update the port and break its use with the HackRF
> One. I think everything will be fine but would appreciate confirmation.
> Thank you!
>
> Bryan
>
TBH I could never really get it working with openbsd in the first place, but
I will make sure it can at least connect. I never found a way to actually
tune anything with the port.
>
> Index: comms/hackrf/Makefile
> ===================================================================
> RCS file: /cvs/ports/comms/hackrf/Makefile,v
> diff -u -p -r1.10 Makefile
> --- comms/hackrf/Makefile 19 May 2024 11:13:01 -0000 1.10
> +++ comms/hackrf/Makefile 11 Oct 2024 11:25:41 -0000
> @@ -1,10 +1,9 @@
> COMMENT = host software for the HackRF One SDR
>
> -V = 2023.01.1
> +V = 2024.02.1
> DISTNAME = hackrf-$V
> -REVISION = 1
>
> -SHARED_LIBS += hackrf 0.0 # 0.8
> +SHARED_LIBS += hackrf 0.1 # 0.8
>
> CATEGORIES = comms
>
> Index: comms/hackrf/distinfo
> ===================================================================
> RCS file: /cvs/ports/comms/hackrf/distinfo,v
> diff -u -p -r1.2 distinfo
> --- comms/hackrf/distinfo 15 May 2023 09:23:36 -0000 1.2
> +++ comms/hackrf/distinfo 11 Oct 2024 11:25:26 -0000
> @@ -1,2 +1,2 @@
> -SHA256 (hackrf-2023.01.1.tar.xz) = MqA/lDowvkukeOlL9p8UpbfVW+Z2EAf0pPVFNBggahE=
> -SIZE (hackrf-2023.01.1.tar.xz) = 23030956
> +SHA256 (hackrf-2024.02.1.tar.xz) = 2c7WfmuAHNAsGNDEZU7RikvLNsJKZDMMNH38y9hZrRY=
> +SIZE (hackrf-2024.02.1.tar.xz) = 21734672
> Index: comms/hackrf/pkg/PLIST
> ===================================================================
> RCS file: /cvs/ports/comms/hackrf/pkg/PLIST,v
> diff -u -p -r1.3 PLIST
> --- comms/hackrf/pkg/PLIST 15 May 2023 09:23:36 -0000 1.3
> +++ comms/hackrf/pkg/PLIST 11 Oct 2024 11:25:26 -0000
> @@ -1,3 +1,4 @@
> +@bin bin/hackrf_biast
> @bin bin/hackrf_clock
> @bin bin/hackrf_cpldjtag
> @bin bin/hackrf_debug
>
No comments:
Post a Comment