On Sunday 18 February 2007 9:28 pm, Randy Dunlap wrote: > On Sun, 18 Feb 2007 21:08:07 -0800 David Brownell wrote: > > > Currently a parport_driver can't get a handle on the device node for the > > underlying parport (PNPACPI, PCI, etc). That prevents correct placement > > of sysfs child nodes, which can affect things like power management. > > > > This patch resolves that issue for non-legacy configurations: > > ... > > Does this patch address http://bugzilla.kernel.org/show_bug.cgi?id=5496 ?
I don't think it would affect that behavior, but surprises can happen; like the root cause of 5496 being the lack of hookup to the real device. > What are you wondering about parport DMA? First, whether it ever worked on ports enumerated through PNP. After all, I saw it oops there, ergo the surprisingly-far-afield parts of this patch to update PNP so it now sets up DMA masks. (Which, I was thinking, probably matters mostly for parport; but I'm just assuming 24-bit masks are correct there.) > Please see http://bugzilla.kernel.org/show_bug.cgi?id=7491 > and http://bugzilla.kernel.org/show_bug.cgi?id=7492 Suggesting that no, it's never worked on ports enumerated through PNP. There's a possibility that if it previously worked through PCI, it now works ... someone with a parport printer could check it out. - Dave - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
