Re: [hpoj-devel] 2.4 kernel issues

[Burkhard K. <bu...@bu...>]

Tim Waugh
> On Sun, Dec 31, 2000 at 11:10:34AM -0800, David Paschal wrote:
> 
> > > It looks
> > > that access to some parport registers is now considered lowlevel 
> > > enough to justify hiding it from driver developers.
> > I can understand removing direct register access from individual drivers,
> > but I can't understand not providing an alternative interface.
> 
> It's because of other architectures that don't even have those
> registers.
> 

Thanks Tim for commenting on this. I certainly see your argument.

I hope you don't mind if I ask you some questions, maybe you 
can help:

What would be the proper replacement for a statement like
      outb(PAR_ECP_CONTROL_BIDIRECTIONAL, ECONTROL(l->port));
when switching from ecp forward to reverse? Or is that now obsolete
because it could handled by the parport_pc module? Unfortunately
we can't use the ieee1284 functions.

From the parport driver sources I see that there is no BECP support 
for now - do you expect to have it in the near future? In ieee12844pp.c
there is actually only one event (41) referring to becp when switching
from ecp reverse to forward when the peripheral is idle.

Regards,

Burkhard
-- 
Burkhard Kohl			bu...@bu...