From: Geert U. <ge...@li...> - 2001-02-09 11:01:37
|
On Fri, 9 Feb 2001, Sven LUTHER wrote: > On Fri, Feb 09, 2001 at 09:53:59AM +0100, Glenn Hisdal wrote: > > Sven LUTHER wrote: > > > > > > On Wed, Feb 07, 2001 at 06:57:51PM +0100, Glenn Hisdal wrote: > > > > Hi, > > > > > > > > I have just tried a 2.4.1 kernel with PCI support enabled. > > > > > > apus_pci: apus_setup_pci_ptrs: Phase5 B/CVisionPPC PCI bridge detected. > > > > > > > > APUS: BATs=1, BUS=67MHz, RAM=70ns, PCI bridge=1 > > > > > > > > PCI: Probing PCI hardware > > > > > > Erm, ... > > > > > > what is the content of /proc/pci, i think it is empty. > > > > /proc/pci doesn't exist at all. > > Ok ... > > > > Notice that pci code seems to be broken on 2.4 kernels right now (well for > > > apus-pci anyway, not the generic pci code naturally). > > > > > Help is wanted to fix this, you volunteer ? > > > > I'm not sure how much I can help with the coding. > > If someone can point me in the right direction, and give me some info on > > the implementation of the pci code, I could have a look, but I doubt > > I'll be able to fix anything. Think it may be a bit lowlevel for me... > > Did we not all begin like that, ... > > Just have a look, and read the docs. > > Not sure even if it all that low level, Michel, any hint on that ? As an example, you can take a look at all `gg2' stuff in arch/ppc/kernel/chrp_pci.c. It's known to work fine on my PPC box. Basically you need to know - how to access PCI config space (old code knew) - wehere PCI memory and I/O space are located, to set up the bus resources. And enable all DEBUG code in drivers/pci/*.c and arch/ppc/kernel/pci.c. Good luck! Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@li... In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds |