Share

libieee1284

Code

Programming Languages: C

License: GNU General Public License (GPL)

Repositories

browse code, statistics, last commit on 2007-09-18 cvs -d:pserver:anonymous@libieee1284.cvs.sourceforge.net:/cvsroot/libieee1284 login

cvs -z3 -d:pserver:anonymous@libieee1284.cvs.sourceforge.net:/cvsroot/libieee1284 co -P modulename

Show:

What's happening?

  • Support for NetBSD

    This patch adds support for NetBSD. It's applied to release 0.2.11 of libieee1284.

    2009-07-30 10:13:26 UTC by jpelletier

  • data count and bandwidth during ecp_read_data

    Hello, It's been a couple of years since anyone has posted here, and it's probably because libieee1284 is working great for everyone! The library seems as relevant as ever. Here we're interfacing the PC to embedded logic and memory via ieee1284_ecp_read_data. We use no ieee1284 negotiate, read device id, or negotiate channel forward to reverse. We just open the port, claim it and cal.

    2009-03-06 03:17:19 UTC by johnea

  • Comment: Direction not assured in write_compat

    Hi Lars, I had similar problems, and I figured out that I needed to issue a ieee1284_negotiate() before reading data, and a ieee1284_terminate() just after reading, so that I could write data again. The API documentation does not say about this where it describes the data transfer functions, but it makes this clear when describing the negotiate/terminate functions. I hope this helps you.

    2008-06-11 22:56:30 UTC by nobody

  • Direction not assured in write_compat

    I'm using libieee1284 as packaged in Debian Etch, i.e. 0.2.10.4. But since the Bug-Tracker does not mention this issue it's probably still there. I perform bi-directional communication in byte mode to an external µC. Writing using write_compat() and reading using byte_read(). Whence the first cycle works fine, subsequent writes after the first read fail, because the PC does not issue any...

    2008-02-26 17:41:35 UTC by nobody

  • Comment: configure: C++ preprocessor "/lib/cpp" fails sanity check

    Hi, I have found that the correct libieee1284 has already been installed in Ubuntu.... The original source of the problem has not been found, but it doesn't matter so much anymore. Thanks, Alf Lacis For email contact see Alf Lacis -- Minimalist Web Site http://au.geocities.com/lacis_alfredo/.

    2007-09-18 11:14:33 UTC by lacis_alfredo

  • libieee1284

    twaugh committed patchset 283 of module libieee1284 to the libieee1284 CVS repository, changing 3 files.

    2007-09-18 09:58:42 UTC by twaugh

  • Comment: libieee1284 fails to work with linux-2.6.22-rc{1..5}

    As the ChangeLog shows [1], Tim Waugh took the patch into CVS. Great. Now we only need a release to get it into distributions. [1] http://libieee1284.cvs.sourceforge.net/libieee1284/libieee1284/ChangeLog?revision=1.155&view=markup.

    2007-09-11 10:04:56 UTC by nobody

  • libieee1284

    twaugh committed patchset 282 of module libieee1284 to the libieee1284 CVS repository, changing 2 files.

    2007-08-31 16:09:17 UTC by twaugh

  • Comment: libieee1284 fails to work with linux-2.6.22-rc{1..5}

    The mentioned patch went into Debian unstable in libieee1284 (0.2.10-8) [1]. Best regards, Philipp [1] http://packages.debian.org/changelogs/pool/main/libi/libieee1284/libieee1284_0.2.10-8/changelog#versionversion0.2.10-8.

    2007-08-23 09:18:40 UTC by nobody

  • Comment: libieee1284 fails to work with linux-2.6.22-rc{1..5}

    I'm unsure, but think that the change to forceing nlink to 0 on dirs and 1 on files at /proc was due to several link count problems in incorrectly (un)registering several devices. I'm trying to find the lkml thread discussion on it. In the meantime, I've sent your patch and disscusion to lkml and redhat bugzilla.

    2007-08-14 11:43:46 UTC by nobody

Our Numbers