Subject: Re: Anyone got a recent current snapshot?
To: Peter Joules <peter@joules0.demon.co.uk>
From: Jon W Grubbs <jgrubbs@megsinet.net>
List: port-vax
Date: 03/23/2000 08:42:36
OOPS!

The real location is:

ftp://ftp.jg3.com/pub/jg3/NetBSD/netbsd-ncr5380-tisyncfix

Sorry for the misdirection....

--Jon

At 08:35 AM 03/23/00 -0600, Jon W Grubbs wrote:
>Pete,
>
>I have posted the kernel I am currently using on a VS3100/M48 with the 
>NCR5380 TI Sync patch applied:
>
>ftp://ftp.jg3.com/pub/jg3/NetBSD/kernel-ncr5380-tisyncfix
>
>NOTE: WARNING! Remember that once you use this kernel to utilize an RZ56 
>(or any other drive that chokes because of the problem with the NCR5380 TI 
>Sync handling), you have to use a kernel with the TI Sync problem fixed in 
>order to access that drive.
>
>This is a 1.4T kernel built with a GENERIC config file.
>
>I will also post the patch details to that location as time permits.
>
>HTH,
>
>--
>Jon Grubbs
>jgrubbs@megsinet.net
>
>
>
>At 08:50 PM 03/22/00 +0000, Peter Joules wrote:
>>In article <4.3.1.2.20000322072946.00b89bb0@mail.corecomm.net>, Jon W
>>Grubbs <jgrubbs@megsinet.net> writes
>> >The RZ56 will probably not be seen even with the -current
>> >build kernel.  I submitted a patch for the MI NCR5380 driver a couple of
>> >weeks ago that has not yet been incorporated into current.  Without it, the
>> >RZ56 gets hung due to a bug in the TI sync processing in the driver.
>> >
>>
>>I had assumed that, when a patch was posted to the port specific list as
>>you did with yours, someone would pick it up and apply it.  Clearly this
>>was a simplistic view.  Can anyone on the list, either let me know when
>>I can reasonably expect to be able to download a kernel incorporating
>>the patch or tell me how to compile my own?
>>
>> From what I gather from an earlier reply there is no specific kernel
>>source tree as there is with Linux.  Do I need to download the entire
>>source tree and run a make on it?  Is there a configuration utility like
>>Linux's 'menuconfig'?  If not how does one specify which architecture
>>one is compiling for?
>>--
>>Regards
>>Pete