On Sun, Nov 26, 2000 at 02:30:14PM +0000, Dave Farrance wrote:
> So, where do I go from here? Suggestions as to which documents to read etc.
> will be gratefully received.
The output of 'lspci -nvv' would be handy, so that we can see which
I/O regions are in which base address registers (probably 0 and 1, but
you never know).
You could try this patch (against 2.2.18pre23, should apply to any
recent 2.2 kernel), which stands a reasonable chance of making it Just
Work:
--- linux/include/linux/pci.h.9940 Sun Nov 26 23:01:28 2000
+++ linux/include/linux/pci.h Sun Nov 26 23:02:02 2000
@@ -1101,6 +1101,7 @@
#define PCI_VENDOR_ID_AFAVLAB 0x14db
#define PCI_DEVICE_ID_AFAVLAB_TK9902 0x2120
+#define PCI_DEVICE_ID_AFAVLAB_9940 0x2121
#define PCI_VENDOR_ID_SYMPHONY 0x1c1c
#define PCI_DEVICE_ID_SYMPHONY_101 0x0001
--- linux/drivers/misc/parport_pc.c.9940 Sun Nov 26 23:02:17 2000
+++ linux/drivers/misc/parport_pc.c Sun Nov 26 23:03:45 2000
@@ -906,6 +906,8 @@
{ { 0, -1 }, } },
{ PCI_VENDOR_ID_AFAVLAB, PCI_DEVICE_ID_AFAVLAB_TK9902, 1,
{ { 0, 1 }, } },
+ { PCI_VENDOR_ID_AFAVLAB, PCI_DEVICE_ID_AFAVLAB_9940, 2,
+ { { 0, -1 }, { 1, -1 }, } },
{ PCI_VENDOR_ID_OXSEMI, PCI_DEVICE_ID_OXSEMI_16PCI954PP, 1,
{ { 0, -1 }, } },
{ PCI_VENDOR_ID_OXSEMI, PCI_DEVICE_ID_OXSEMI_12PCI840, 1,
..or you could just try:
# dmesg -c > /dev/null
# insmod parport
# insmod parport_pc io=0xa000
# rmmod parport_pc
# insmod parport_pc io=0xa400
# rmmod parport_pc
# dmesg > output
and show us the resulting 'output' file.
Tim.
*/
-- 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 : Sun Nov 26 2000 - 18:11:53 EST