Date: Tue, 2 Aug 2005 10:51:31 -0700 From: "David O'Brien" <obrien@freebsd.org> To: ticso@cicely.de Cc: freebsd-alpha@freebsd.org Subject: Re: KZPCC-CE SCSI controller Message-ID: <20050802175130.GK71672@dragon.NUXI.org> In-Reply-To: <20050802174144.GA71814@cicely12.cicely.de> References: <42EE1A34.6510B1CE@fadesa.es> <20050801151501.GA53593@freebie.xs4all.nl> <20050802172322.GC71672@dragon.NUXI.org> <20050802174144.GA71814@cicely12.cicely.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Aug 02, 2005 at 07:41:44PM +0200, Bernd Walter wrote: > On Tue, Aug 02, 2005 at 10:23:22AM -0700, David O'Brien wrote: > > It will not work as-is. I suspect it could be made to work using the > > ugly hack we have elsewhere in src/sys: > > > > #ifdef __alpha__ > > #undef vtophys > > #define vtophys(va) alpha_XXX_dmamap((vm_offset_t)va) > > So this driver is not busdma'ed yet? Correct. > Igh - this will invalidate it for lots of machines, not just alpha. Very well known. > Since I'm working on > 2G support and AFAIK the asked machine can > have more than that this may be a problem. > I intent to panic if a driver calls vtophys on a large mem alpha. You might want to see how many drivers still do this ugly vtophys hack. I recall are(were) several. -- -- David (obrien@FreeBSD.org)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050802175130.GK71672>