Re: Booting on RiscPC

Stephen Borrill <[email protected]> Tue, 2 Apr 2019 15:04:36 +0100 (BST)
Newsgroups gmane.os.netbsd.ports.acorn32
Message-ID <Pine.NEB.4.64.1904021452480.3448@ugly>
On Mon, 1 Apr 2019, Mike Pumford wrote:
> On 28/03/2019 09:43, Stephen Borrill wrote:
>> On Wed, 27 Mar 2019, Mike Pumford wrote:
>
>>> It may take a few days as I'm going to be away from the hardware but I'll 
>>> have a look into the driver and see if I can see any way for that keyboard 
>>> failure to happen. Is the behaviour consistent? does the same key always 
>>> give the same pair of characters?
>> 
>> Yes, always consistent.
>
> I did find a couple of possible start of day quirks where we could 
> potentially take an interrupt before the code was really ready. I've also 
> added code that drains the keyboard input before we attach (the pckbc code 
> does this and it seems reasonable given that the code is taking over control 
> from another OS). Not sure if this will help you out or if we need to do more 
> things to ensure the keyboard controller is in a sane state when we take over 
> from RISC OS.

The patch doesn't seem to help. I did try bypassing the RISC OS boot 
sequence just in case I had some odd module loaded that did something 
strange.

-- 
Stephen