On Thu, Mar 09, 2006 at 09:44:51AM -0800, Jurij Smakov wrote: > >What version of the kernel was this analysis done with? The workaround in > >yaird is explicitly commented as existing for the benefit of older kernel > >versions; can you assure us that this aspect of the driver design is > >unchanged from 2.6.8 through 2.6.15? > That's a good point. I was looking at the latest kernel (2.6.15), and > Frans and Anthony mentioned that ide-generic was neccessary in the past. > I'll try to figure it out. Ok, thanks for your work on this, Jurij. And to answer Sven's question, On Thu, Mar 09, 2006 at 11:08:33AM +0100, Sven Luther wrote: > > What version of the kernel was this analysis done with? The workaround in > > yaird is explicitly commented as existing for the benefit of older kernel > > versions; can you assure us that this aspect of the driver design is > > unchanged from 2.6.8 through 2.6.15? > Steve, what is the interest of doing this ? We only have 2.6.15 currently in > sid/etch, and sarge uses 2.6.8 together with initrd-tool, so it is a > non-issue. Whether this workaround is needed for older kernels is a technical factor. You may not consider supporting older kernels worthwhile (and neither do I in this case, really), but it's clear that Jonas *does* consider it important; if he didn't, there would obviously be no need to overrule Jonas at this point. Since he does, it's important that we have as much information as possible about this case in order to make an informed decision. Reaching a technical solution that satisfies both parties should *always* be preferred over forcing a maintainer to do something he disagrees with. But even if that's not possible, we still have a responsibility to base our decision on as clear a picture of the evidence as possible. I've done a little poking of my own at sysfs based on the comments in the yaird code. I can confirm that it is possible for a PCI IDE driver to be listed as associated with a PCI device without actually being the driver used to access the device. This happens on my alpha, where ide-generic must be used due to bugs in the cmd64x driver, yet running modprobe cmd64x does show this driver associated with the PCI device: $ ls -l /sys/devices/pci0000\:00/0000\:00\:0b.0/driver lrwxrwxrwx 1 root root 0 2006-03-09 19:46 /sys/devices/pci0000:00/0000:00:0b.0/driver -> ../../../bus/pci/drivers/CMD64x_IDE $ However, /sys/block/hda/device still points to the right place, and it's my understanding that /sys/block is what yaird walks, so this still is no explanation for how someone could have mis-identified a bug in this area. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. vorlon@debian.org http://www.debian.org/
Attachment:
signature.asc
Description: Digital signature