Re: Parallel Port access...
On Wed, Nov 25, 2009 at 01:14:27PM -0500, A. Maitland Bottoms wrote:
> Non-Linux types:
> The predict package FTBFS on hurd and kfreebsd ports because
> it has Linux-specific code for using a parallel port.
> Rather than disable the feature to control Easycom or
> fodtrack rotor interfaces with use the parallel port interface,
> I'd like some pointers on how one might write to a prallel
> port in hurd and freebsd. How hard can it be?
> Perhaps you've seen FTBFS for
> #include <linux/parport.h>
> #include <linux/ppdev.h>
> before. I'd appreciate any clues you could send my way
> for freebsd and hurd systems.
In theory you can use a parallel port portably, but some control features
might be unavailable. Inclussion of these files doesn't tell a lot (they
may be gratuitous); see what happens if you remove them (which declarations
are missing, what's their purpose, etc).
The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
how) you may access your data; but nobody's threatening your freedom: we
still allow you to remove your data and not access it at all."