Hello!
> I tried linux-2.3.99-pre3 and your patch. Now happily the scsi
> controller on the pci bus 1 was detected, but sadly it didn't work.
>
> Under the kernel 2.2.X or 2.3.99pre2 with my dirty patch, the driver
> would go its initialization or something after the detection, and the
> connected scsi devices were listed such like this.
This is strange, I've expected my patch will do exactly the same
thing as your dirty hack, but let's investigate further.
> sym53c8xx: at PCI bus 1, device 4, function 0
> sym53c8xx: setting PCI_COMMAND_PARITY...(fix-up)
> :::
> scsi0 : sym53c8xx - version 1.5k
> scsi1 : sym53c8xx - version 1.5k
> scsi : 2 hosts.
> sym53c896-0: command processing resumed
> sym53c896-1: command processing resumed
> Vendor: QUANTUM Model: ATLAS IV 9 SCA Rev: 0898
> Type: Direct-Access ANSI SCSI revision: 03
> :::
>
> Under the kernel 2.3.99pre3 with your patch, a part of your patch was
> rejected and I applied manually, the devices are not listed. And it
> seems retrying forever.
Can you attach PCI related bootup messages printed if you change #undef DEBUG
to #define DEBUG in arch/i386/kernel/pci-i386.h, please?
Have a nice fortnight
-- Martin `MJ' Mares <mj@ucw.cz> <mj@suse.cz> http://atrey.karlin.mff.cuni.cz/~mj/ "In accord to UNIX philosophy, PERL gives you enough rope to hang yourself." -- Larry Wall- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Apr 15 2000 - 21:00:12 EST