Re: Conflict when loading initio driver

2007-10-10 Thread Scott Simpson
OK. I did some debugging in this initio.c driver. I put printk statements at the beginning of each routine and I got the following output: initio_se2_rd initio_se2_instr (The previous two routines repeat a bunch of times then I get:) initio_stop_bm i91u: PCI Base=0xEC00, IRQ=0, BIOS=0x, SCSI I

Re: Conflict when loading initio driver

2007-10-06 Thread Alan Cox
> > + host->addr = pci_resource_start(pdev, 0); > > > > if (!request_region(host->addr, 256, "i91u")) { > > printk(KERN_WARNING "initio: I/O port range 0x%x is busy.\n", > > host->addr); > > I tried this fix on my SuSE 10.3 system (2.6.22.5-29 kernel) and it > didn't work. The s

Re: Conflict when loading initio driver

2007-10-05 Thread Scott Simpson
Alan Cox wrote: > Humm not a collision - thats a bug in the driver updating. Looks like the > changes I made and combined with Christoph's lost a line somewhere when I > was merging it all. Try the following > > Signed-off-by: Alan Cox <[EMAIL PROTECTED]> > > diff -u --new-file --exclude-from /usr/

Re: Conflict when loading initio driver

2007-09-30 Thread Alan Cox
>I have a scanner connected to a Initio INI-950 SCSI card and I recently > upgraded from SuSE 10.2 to 10.3. The new kernel doesn't see any of my > devices. I get the following in /var/log/messages: > > > > > >Sep 30 09:05:13 r2d2 kernel: ACPI: PCI Interrupt :00:0a.0[A] -> GSI

Conflict when loading initio driver

2007-09-30 Thread Scott Simpson
SuSE 10.3 (new release candidate), 2.6.22.5-29 kernel, SCSI initio driver I have a scanner connected to a Initio INI-950 SCSI card and I recently upgraded from SuSE 10.2 to 10.3. The new kernel doesn't see any of my devices. I get the following i