On Wed, Apr 21, 2004 at 04:11:29PM +0200, Maciej W. Rozycki wrote: > On Tue, 20 Apr 2004, Jun Sun wrote: > > > > drivers/pci can do that, you just need to supply a few board specific > > > functions, see for example arch/alpha/kernel/pci.c. So pci_auto.c isn't > > > only b0rked, it also duplicates code. > > > > Has anybody succssfully used pci_assign_unassigned_resources() in latest 2.4? > > It was badly broken in early 2.4 kernels while pci_auto was the only > > option. > > In that case, fixing pci_assign_unassigned_resources() was the right way > to go, instead of implementing a system-specific workaround. Using pci_auto() represented a different approach, which to many seems more correct. It does assignment first and then scanning. It is supplied as a replacement for broken firmware. At one time a couple of pci_auto()'s existed in more than one arch. And there was a chance to make this approach the official one and completely eliminate pci_assign_unassigned_resources(). Having competing approaches co-existing in Linux is a norm. > There are no > excuses -- the source is available. > Please don't always assume other people are more ignorant .... Jun
