R3000Z Compat Patch
astrodog at gmail.com
Thu Nov 11 19:39:38 GMT 2004
I was looking over the PR, there seemed to be an issue with other bits
of code calling it, I'm not sure if that is still a consideration.
Also, I've verified the behavior still occurs on an unpatched version,
with a Sempron processor (32-bit only). I'm guessing its specific to
the motherboard these use, and is not unique to AMD64 arch.
On Thu, 11 Nov 2004 13:24:13 -0600, Astrodog <astrodog at gmail.com> wrote:
> I'll take a look. In the end, I think an automated solution needs to
> be found... but how to detect these specific motherboards, with this
> issue escapes me at the moment, any thoughts there? Also you might
> want to take a look at the patch I've got going below.
> --- Harrison Grundy
> On Thu, 11 Nov 2004 14:17:55 -0500, John Baldwin <jhb at freebsd.org> wrote:
> > On Thursday 11 November 2004 07:36 am, Astrodog wrote:
> > > Should work either way... I'm having some problems writing it... the
> > > keyboard test seems to happen too early to use kenv() to pull device
> > > hints.
> > Did you see the patch I posted earlier to make a flag in atkbd0 turn this test
> > off? If so, can you test it? It's in the PR feedback. I posted it over a
> > week ago and no one has tested it yet.
> > > On Thu, 11 Nov 2004 00:13:55 -0800 (PST), Neil Short <neshort at yahoo.com>
> > wrote:
> > > > Mine's an HP.
> > > >
> > > > --- Astrodog <astrodog at gmail.com> wrote:
> > > > > I'm going to write something mergable, because this
> > > > > is just nuts. ISO
> > > > > URLs coming in the next few hours, along with a
> > > > > diff, assuming the
> > > > > testing is sucessful. I'm using a device hint,
> > > > > hw.compaqr3000z, if I
> > > > > should use another naming convention, lemme know.
> > > > >
> > > > > --- Harrison Grundy
More information about the freebsd-amd64