On Thu, Nov 14, 2024 at 07:16:40PM -0800, Bryan Vyhmeister wrote:
> On Thu, Nov 14, 2024 at 06:56:07PM -0800, Mike Larkin wrote:
> > On Sun, Nov 10, 2024 at 01:20:27PM -0800, Bryan Vyhmeister wrote:
> > > I'm following up to see if any testing has been able to happen for
> > > comms/hackrf 2024.02.
On Thu, Nov 14, 2024 at 06:56:07PM -0800, Mike Larkin wrote:
> On Sun, Nov 10, 2024 at 01:20:27PM -0800, Bryan Vyhmeister wrote:
> > I'm following up to see if any testing has been able to happen for
> > comms/hackrf 2024.02.1. Here is the diff again. Thanks so much.
> >
> > Bryan
>
> installs and
On Sun, Nov 10, 2024 at 01:20:27PM -0800, Bryan Vyhmeister wrote:
> I'm following up to see if any testing has been able to happen for
> comms/hackrf 2024.02.1. Here is the diff again. Thanks so much.
>
> Bryan
installs and works. I need to update the firmware before I can run a sweep
but this see
On Sun, Nov 10, 2024 at 10:12:03PM +, Stuart Henderson wrote:
> I don't think many people have the hardware to test this
>
I do, but have been busy. Now that I'm home I can give it a try.
> --
> Sent from a phone, apologies for poor formatting.
>
> On 10 November 2024 21:20:49 Bryan Vyhmeist
I don't think many people have the hardware to test this
--
Sent from a phone, apologies for poor formatting.
On 10 November 2024 21:20:49 Bryan Vyhmeister wrote:
I'm following up to see if any testing has been able to happen for
comms/hackrf 2024.02.1. Here is the diff again. Thanks so much
I'm following up to see if any testing has been able to happen for
comms/hackrf 2024.02.1. Here is the diff again. Thanks so much.
Bryan
Index: comms/hackrf/Makefile
===
RCS file: /cvs/ports/comms/hackrf/Makefile,v
diff -u -p -r1.10
On Sun, Oct 13, 2024 at 07:14:21PM -0700, Mike Larkin wrote:
> 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 comm
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
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
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. Than
On Fri, Oct 11, 2024 at 10:29:40AM +0100, Stuart Henderson wrote:
> On 2024/10/10 20:49, Bryan Vyhmeister wrote:
> > 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.
>
> Minor bump seems correct here (added function). REVISION s
On 2024/10/10 20:49, Bryan Vyhmeister wrote:
> 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.
Minor bump seems correct here (added function). REVISION should go.
> Bryan
>
>
> Index: comms/hackrf/Makefile
> =
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 A
13 matches
Mail list logo
