Date: Thu, 22 Jun 2000 15:54:40 -0400 (EDT) From: Andrew Gallatin <gallatin@cs.duke.edu> To: =?ISO-8859-1?Q?G=E9rard_Roudier?= <groudier@club-internet.fr> Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: Problems installing FreeBSD 4.0-RELEASE on an Alpha system Message-ID: <14674.26845.214876.230507@grasshopper.cs.duke.edu> In-Reply-To: <Pine.LNX.4.10.10006222031520.1257-100000@linux.local> References: <14674.13167.247088.580096@grasshopper.cs.duke.edu> <Pine.LNX.4.10.10006222031520.1257-100000@linux.local>
next in thread | previous in thread | raw e-mail | index | archive | help
G=E9rard Roudier writes: > 3) The BUS physical addresses (as seen from PCI BUS), the SCRIPTS > processor is provided with, are wrong. >=20 > Given that the driver succeeded initialisations and seems to success= fully=20 > read chip IO registers using MMIO, the actual reason of the breakage= is=20 > probably not (1) and (2) does not seem to me a good culprit :). >=20 > Regarding possible reason (3), the SCRIPTS processor fetches instruc= tions > from on-chip RAM using internal path (not using PCI external cycles)= . > For this to work, the BAR that is supposed to contain the address of= =20 > the on-chip RAM must match the BUS physical address of the on-chip R= AM=20 > as seen from the BUS. >=20 > If for some reason BUS physical addresses ad seen from CPU differs f= rom > BUS physical address as seen from the PCI BUS, and the BAR contains = the > former address value, then the current driver code will not work. A > work-around could consist in using main memory for SCRIPTS instead o= f > on-chip RAM. #3 is most likely the culprit. Right now we steal the upper bit(s) of the port or address passed down to the chipset's inX/outX readX/writeX functions to allow drivers to use inX/outX and readX/writeX. This is done so as to give hints to the lowlevel chipset code as to which hose the address in question is on. This hackery will go away when the previously mentioned changes to the alpha pci code happen. (Those changes are why Doug wanted to get all important drivers using busspace). Thanks for explaining it! I've long suspected that something like this was going on but never had the time to really understand either ncr driver well enough to figure it out for myself. Cheers, Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?14674.26845.214876.230507>