[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Discuss-gnuradio] What is a ppio_ppdev?

From: Berndt Josef Wulf
Subject: Re: [Discuss-gnuradio] What is a ppio_ppdev?
Date: Sun, 20 Feb 2005 11:54:44 +1030
User-agent: KMail/1.7.2

On Sun, 20 Feb 2005 12:46 am, Stephane Fillod wrote:
> On Sat, Feb 12, 2005 at 09:30:33AM -0800, Eric Blossom wrote:
> > On Sun, Feb 13, 2005 at 01:46:22AM +1030, Berndt Josef Wulf wrote:
> > > ppio_ppdev: Not implemented on this platform
> > >
> > > Running NetBSD, I suspect this to be a Linux specific device.
> Is there some arch portable way of controlling the parallel port (like
> Linux ppdev) under NetBSD?

According to the ppbus(4) documentation,there appears to be support for such 
device - ppi(4) - see below:

           o  a user interface named ppi(4) that allows parallel port access
               from outside the kernel without conflicting with kernel-in

However, I failed to source the man page for ppi(4). I've posted an email to 
the relevant NetBSD mailing list for more info about this interface.

> > In general we should abstract the interface to the RF front end.
> > The the user would specify -- perhaps through some kind of preference
> > file -- which specific RF front end to use.
> Ah, you mean some kind of abstraction library, that is consistent and
> portable, has python binding, yet with a *GPL license? We have it,
> it's called Hamlib[1] :-) There's already support for microtune 4937 and
> 4702 (I haven't tested though), a bunch a various transceivers (incl.
> SDR1000), receivers, kits, etc.
> Would that make it?
> [1] http://hamlib.org

I have a Microtune 4707 tuner and would be interested in supporting this in 
hamlib if it is of any interest. I haven't compared the docs for 4702 and 
4707 but suspect that it should be relatively easy to support both. I was 
planing to build a daughter board connecting the tuner to the USRP.

cheerio Berndt
Every man who says frankly and fully what he thinks is doing a public service.
[Leslie Stephen]

reply via email to

[Prev in Thread] Current Thread [Next in Thread]