It wasn't really the intent that CONFIG_PARPORT_OTHER would get used for this,
and I'm not sure I like it. It makes the semantics unnecessarily murky -
support for other hardware ought to be completely orthogonal to how the
sharing works.
>I think that there's a reason for not looking for "gaps" when registering
>a port, too (register parport0, register parport1, unregister parport0,
>then re-register at parport*0* rather than parport2). I can't think what
>it is at the moment.
It's more predictable the way it works now. As I've mentioned before, the
SCSI code does the same thing - though you don't refer to a SCSI host adapter
by name very often so it's not so significant.
If there's a weight of opinion in favour of changing it to `look for gaps'
then go ahead. There's no major technical obstacle.
p.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu