Re: parport1 gone in 2.2.18

[Tim Waugh <twaugh@redhat.com>]

[-- Attachment #1: Type: text/plain, Size: 1343 bytes --]

On Wed, Dec 13, 2000 at 09:01:56PM +0100, Peter Bornemann wrote:

> I have a second parport installed as a PCI-card. In earlier Linux-versions
> this would lock the machine completely if parport & Co where compiled as
> modules (2.2.16 and 2.2.17). Compiled into the kernel however, everything
> worked fine. I wrote about that to LK, but no solution was found. Now in
> 2.2.18 it is the other way round, modules work with the proper
> initialization in modules.conf, but if compiled into the kernel, the
> second parport vanishes completely.

The problem was that there are many more Timedia cards than I
realised, and they are only distinguishable from each other by their
subdevice ID (vendor and device isn't enough).  So we were probably
using the wrong BARs, which probably caused the freezes you saw.

The 2.4.x parport_pc card table can deal with this; the 2.2.x
parport_pc card table can't.  So rather than leave a potential freeze
in I pulled those cards from the table altogether.  Sorry if I didn't
tell you this.

For 2.2.19 I'm hoping to backport the 2.4.x parport_pc card table
structure if Alan doesn't think that's too big a change.

The reason it works for you with modules is probably because you have
an options line in /etc/modules.conf that tells parport_pc which
addresses your PCI card is using at the moment.

Tim.
*/

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]