Date: Tue, 9 Jan 2001 11:00:02 -0800 (PST) From: Matthew Jacob <mjacob@feral.com> To: freebsd-alpha@freebsd.org Subject: Re: alpha/24177: Patch for fxp on Alpha Message-ID: <200101091900.f09J02q15286@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR alpha/24177; it has been noted by GNATS. From: Matthew Jacob <mjacob@feral.com> To: Kees Jan Koster <dutchman@tccn.cs.kun.nl> Cc: FreeBSD-gnats-submit@FreeBSD.ORG Subject: Re: alpha/24177: Patch for fxp on Alpha Date: Tue, 9 Jan 2001 10:51:36 -0800 (PST) On Tue, 9 Jan 2001, Kees Jan Koster wrote: > > > > You don't say which specific platform this is. It's unusual that I/O space > > works better than Memory space. It's also true that various flavors of EEPRO > > are known to work. > > > D'oh! I keep forgetting Alpha's aren't PC's. :) Here's the relevant > dmesg snippet. > > DEC AXPpci > Alpha PC AXPpci33, 166MHz > 8192 byte page size, 1 processor. > CPU: LCA Family major=4 minor=2 > OSF PAL rev: 0x100090002012d > > I apologize for not including this information immediately. No, that's fine... I just needed to know. You know, I'd forgotten about LCA- that probably is the only PCI chipset for alphas where I/O space is more functional than Memory space. > > > > > I sure wish I knew whether the maintainer for this card s active or not on > > this. I think your patches are in the right direction, but aren't really quite > > what we should be looking for- they could be a lot tighter and should be > > runtime as opposed to compile time settable- see isp_pci.c for an example (not > > the best, granted) of this. > > > These are not my own patches. I reported this problem earlier on > freebsd-alpha and in the resulting discussion these patches came up. I > tried them and they worked for me. The discussion was in the "fxp0 hangs > on a PC164 using STABLE" and the "fxp0 hangs my AXPpci33" threads, on > freebsd-alpha around July 2000. > > At the time they were not committed because of their hackish nature, as > you have noted yourself. Someone hinted that he was going to rework them > in a more socially acceptable manner, but his time seems to have been > claimed by more important matters. Since this was months ago I figured > that I should try to get the patch committed. Was the driver author gonna do this? Who? Yes, it should be done. I could probably even get to it myself- but not if somebody else is on it. -matt 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?200101091900.f09J02q15286>