Re: [hpoj-devel] new "ptal-mlcd" I/O driver checked into CVS

[Joe P. <joe...@sn...>]

On Friday 09 March 2001 09:29 pm, PASCHAL,DAVID (HP-Roseville,ex1) wrote:
> Hi,
>
> I'm pleased to announce that the new "ptal-mlcd" I/O driver I've talked a
> lot about lately is now checked into CVS.  In addition to providing a more
> robust I/O infrastructure for the hpoj software, ptal-mlcd now supports USB
> for the OfficeJet G, K, and LaserJet 3200 series.  I would like to invite
> everyone to download the new code from CVS and try it out, particularly
> those who have requested USB support or who have reported problems with the
> old kernel-mode drivers related to SMP machines or particular kernel
> versions.
>
> In addition to the ptal-mlcd addition, I also changed ptal-printd to fork
> into the background by default (unless the "-nofork" switch is given), and
> reorganized the codebase and build process somewhat.
>
> Please let me know on the hpoj-devel mailing list of any problems that you
> find that I may have missed, but also be sure to look at the "Bugs and
> TODO" page (http://hpoj.sourceforge.net/todo.shtml) for information on
> known issues.  In particular, xojpanel is temporarily disabled while I
> finish the new PTAL PML support, and there are currently some performance
> and CPU utilization issues I need to resolve as well.


David:

The build fails with this output:
...
...
gcc -I/home/joe/hpoj_proj/CVS/hpoj_CVS_03-10-2001/mlcd 
-I/home/joe/hpoj_proj/CVS/hpoj_CVS_03-10-2001/mlcd/transport -O -g -Wall 
-DEX_TRANSPORT_UNIX_PORT -DPAR_PLATFORM_LINUX -DUSB_PLATFORM_NONE -DJD_DEBUG 
-c -o ExMgr.o ExMgr.cpp
In file included from 
/home/joe/hpoj_proj/CVS/hpoj_CVS_03-10-2001/mlcd/ParPort.h:396,
                 from ExMgr.cpp:1981:
/usr/include/sys/io.h: In function `void outb(unsigned char, short unsigned 
int)':
/usr/include/sys/io.h:98: parse error before `::'
/usr/include/sys/io.h: In function `void outb_p(unsigned char, short unsigned 
int)':
/usr/include/sys/io.h:104: parse error before `::'
/usr/include/sys/io.h: In function `void outw(short unsigned int, short 
unsigned int)':
/usr/include/sys/io.h:111: parse error before `::'
/usr/include/sys/io.h: In function `void outw_p(short unsigned int, short 
unsigned int)':
/usr/include/sys/io.h:118: parse error before `::'
/usr/include/sys/io.h: In function `void outl(unsigned int, short unsigned 
int)':
/usr/include/sys/io.h:125: parse error before `::'
/usr/include/sys/io.h: In function `void outl_p(unsigned int, short unsigned 
int)':
/usr/include/sys/io.h:131: parse error before `::'
make[1]: *** [ExMgr.o] Error 1
make[1]: Leaving directory `/home/joe/hpoj_proj/CVS/hpoj_CVS_03-10-2001/mlcd'
make: *** [all] Error 2

My system is running linux kernel 2.2.16 . The compiler is gcc-2.95.2 . The 
box has one MB-based parport, with a second parport on a separate I/O card.

I tried configuring with and without USB support. USB is disabled in the bios 
at present. I also rmmoded the ieee* modules, removed libptal*, and killed 
ptal-printd before building.

The io.h referred to is from the redhat glibc-devel-2.1.3-22.i386.rpm. Below 
is the section of io.h containing line 98.

extern inline void
outb (unsigned char value, unsigned short port)
{
  __asm__ __volatile__ ("outb %b0,%w1"::"a" (value), "Nd" (port));
}



> (Joe, since you still depend on the old functionality of ojlib to do your
> xojpanel development, you might want to save your old sandbox and create a
> separate one if you want to try out the new code.  Also, I haven't checked
> in your latest xojpanel changes since it currently isn't being built, but I
> can if you're at a stopping place for the time being and would like me to
> check in what you have so far.)

Can you hold off on checking in the patch I posted recently? I only sent it 
so you could look at the changes if you wanted to, and see if they work 
correctly.

I'd like to modify some of the comments a little more to enable (but not 
necessarily include) document generation by Doxygen or a similar utility, so 
there will be at least one more patch, probably applied against the last 
official release (0.7).

Generated documentation can be a benefit. Would it be a good idea for the 
entire project?

-- 
Joe