From mboxrd@z Thu Jan 1 00:00:00 1970 From: Uli Luckas Date: Thu, 17 Jun 2004 06:16:52 +0000 Subject: Re: sun4c driver/dma problems Message-Id: <200406170816.52980.luckas@musoft.de> List-Id: References: <200406020818.13705.luckas@musoft.de> In-Reply-To: <200406020818.13705.luckas@musoft.de> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: sparclinux@vger.kernel.org Am Dienstag, 8. Juni 2004 18:12 schrieb Uli Luckas: > Am Dienstag, 8. Juni 2004 17:53 schrieb Keith M Wesolowski: > > On Tue, Jun 08, 2004 at 09:22:44AM +0200, Uli Luckas wrote: > > > the above cited DMA message seems to be the root of the driver > > > problems. From the 2.2.26 kernel I know it should read: > > > dma0: Revision 1 > > > > > > So what can I do to help, getting this fixed? Who works on this code? > > > I already know, it's not only the version detection. Defining a new > > > version 70000000 "Revision 1 broken" and initialising it just as a > > > "Revision 1" works around the above message, but all the device drivers > > > report all kind of DMA related problems later on and of course don't > > > work. > > > > Reading your messages, I'm uncertain exactly how well 2.2.26 works. > > Can you please clarify? If it's perfect, then I may invest a few > > hours trying to fix this for you in 2.6. If there's no known-working > > kernel, it's unlikely that it ever will be fixed. > > Hi Keith, > thanks for your reply. > The machine works nicely and stable with 2.2 kernels, nfs root and nbd > swap. With 2.2 kernels I can also access the local SCSI cdrom and hard > drives which host an old SunOS 4.1.3 installation. > > Please let me know, if you need more information. Hi Keith, did you get any chance to look into the problem? Uli -- "[...]Yes, Mr. Gates, recently you have helped open source succeed -- in much the same way Osama bin Laden has helped beef up airport security lately." -- Eric S. Raymond, 9.11.2001