Hello Tim,
I don't know exactly what to test, but I assume that the parport
with this patch should detect the port without a special
entry in modules.conf ?
I tried this and it doesn't work.
>
>--- linux-2.2.14/drivers/misc/parport_pc.c Tue Jan 4 18:12:17 2000
>+++ linux/drivers/misc/parport_pc.c Tue Mar 28 13:33:12 2000
>@@ -907,6 +907,8 @@
> { { 0, -1 }, } },
> { PCI_VENDOR_ID_LAVA, PCI_DEVICE_ID_LAVA_DUAL_PAR_B, 1,
> { { 0, -1 }, } },
>+ { 0x1409, 0x7168, 1,
>+ { { 1, -1 }, } },
> { 0, }
> };
I checked where it fails, and the probe_one_port() function
gets called with port address 0 !?
So I added this print statements to see whats in the configuration space.
{
int j;
for (j=0; j<5; j++)
printk(KERN_NOTICE "parport_pc: base_address[%d] =
0x%08lx\n",j,pcidev->base_address[j]);
}
It prints the following:
Mar 29 11:44:44 panther kernel: parport_pc: base_address[0] = 0x0000d001
Mar 29 11:44:44 panther kernel: parport_pc: base_address[1] = 0x00000000
Mar 29 11:44:44 panther kernel: parport_pc: base_address[2] = 0x0000b801
Mar 29 11:44:44 panther kernel: parport_pc: base_address[3] = 0x0000b401
Mar 29 11:44:44 panther kernel: parport_pc: base_address[4] = 0x00000000
So there is in-between a zero address?!
I modified your patch to this
{ { 0, -1 }, } },
{ 0x1409, 0x7168, 1,
{ { 2, -1 }, } },
{ 0, }
and then the port gets detected w/o modules.conf entry.
regards,
chris
-- To unsubscribe, send mail to: linux-parport-request@torque.net --
-- with the single word "unsubscribe" in the body of the message. --
This archive was generated by hypermail 2b29 : Wed Mar 29 2000 - 05:35:06 EST