That is a very good question. The drivers, from what I can see, for this moment are mostly to allow SDR hardware to work as v4l devices (hence RX only). But eventually I'm sure that all SDR devices will be treated like network drivers are today. And hopefully gnuradio and these drivers will meet somewhere in a middle ground with a single very good API, that allows TX as well as RX. But for the moment, it is either have these drivers in place and not use gnuradio or disable them and use gnuradio.
Exactly like rtlsdr is today, by default it is a TV tuner, unless you blacklist the dvb_usb_rtl28xxu, e4000, rtl2832 modules. On 21/03/2015 03:06, Rick "Zero_Chaos" Farina wrote: > On 03/19/15 06:34, Paul Connolly wrote: >> The kernel modules (RX only) for new SDR devices was known to be >> arriving for the HackRF in 3.18 for a while. >> http://palosaari.fi/linux/ >> ... snip ... >> AirSpy SDR driver (airspy) >> * Kernel 3.17 >> >> HackRF SDR driver (hackrf) >> * Kernel 3.18 >> * only RX >> ... snip ... >> > Is this stuff known bad or what? Should everyone be avoiding the in > kernel drivers? > > -Zero_Chaos >> On 19/03/2015 06:15, Tom wrote: >>> I got this error when I updated from kali 3.14 to 3.18. >>> >>> Works fine on 3.14 >>> _______________________________________________ >>> HackRF-dev mailing list >>> [email protected] >>> https://pairlist9.pair.net/mailman/listinfo/hackrf-dev >> >> >> >> _______________________________________________ >> HackRF-dev mailing list >> [email protected] >> https://pairlist9.pair.net/mailman/listinfo/hackrf-dev >> > > > > _______________________________________________ > HackRF-dev mailing list > [email protected] > https://pairlist9.pair.net/mailman/listinfo/hackrf-dev
signature.asc
Description: OpenPGP digital signature
_______________________________________________ HackRF-dev mailing list [email protected] https://pairlist9.pair.net/mailman/listinfo/hackrf-dev
