Compaq R3000 Series

[Astrodog]

On Fri, 3 Dec 2004 21:23:30 -0800, David O'Brien <obrien at freebsd.org> wrote:
> On Fri, Dec 03, 2004 at 06:54:12PM -0500, Nicolas Blais wrote:
> > I would like to know what the situation is with the Compaq/HP R3000 Series
> > problem at boot with 5-STABLE.  Was the patch to at least get it booted
> > commited to -STABLE and/or CURRENT?
> 
> If the patch you're refering to the keyboard related patch, no it hasn't.
> 
> Someone that experiences the problem needs to take the patch that is
> floating around and make it commitable.  This means rather than cutting
> out the code that the patch does, it is wrapped around a loader tunable
> so it only gets turned off on these laptops.
> 
> Or someone needs to go read the code and explain why removing that
> section makes a difference (ie, understand what is really going on), and
> make an argument that removing that code is OK for the rest of the world
> that isn't experiencing the problem.
> 
> --
> -- David  (obrien at FreeBSD.org)
> 
> 
> _______________________________________________
> freebsd-amd64 at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-amd64
> To unsubscribe, send any mail to "freebsd-amd64-unsubscribe at freebsd.org"
> 

There are 3 working patches out now, the first being the #if 1 one I
used to build that ISO. There's also aparently the flags one, listed
on the PR, and the hints one I made awhile back.

The code in question, that causes the bug sends a command to the
keyboard controller to test the status of the port. The potential bug
I can see cropping up with just removing the code is the failure of
anything that relies on actually testing the keyboard port. That might
extend to some com port console things.

To avoid that protential problem for everyone else, and still let
R3000Z users actually use their laptops with FreeBSD, without a 2 line
fork, I think the flags fix, listed in the PR might be the best
solution, atleast for the time being.

--- Harrison Grundy