The keyboard is PS/2, also, a little detail on the patch. Its not actually disabling the full driver. I "stole" the hint to use to just disable the testing code. I like the solution of replacing it with the flags, but then doing the edit in atkbdc.c. According to the PR Trail on this, atleast one other thing referenced the offending functions, if there's any uncertainty as to if that's still happening, I think that putting the edit in atkbdc.c is the only way to go... unless someone wants to rewrite it all, which I'm not even capible of. I can put that together pretty quickly if its needed. --- Harrison Grundy On Thu, 11 Nov 2004 12:31:41 -0800, Peter Wemm <peter_at_wemm.org> wrote: > On Thursday 11 November 2004 07:48 am, Astrodog wrote: > > Any hint will do, honestly. Just altering the patch to reflect the > > change will work. I'd like to automate it by detecting the mobile > > nforce3 chipsets, but I don't even know where to start with that yet. > > Any suggestions? > > How do these work anyway? USB keyboard? > > If so, I'm wondering if the problem is some problem with the legacy > keyboard emulation by the bios.. > -- > Peter Wemm - peter_at_wemm.org; peter_at_FreeBSD.org; peter_at_yahoo-inc.com > "All of this is for nothing if we don't go to the stars" - JMS/B5 >Received on Thu Nov 11 2004 - 19:48:48 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:22 UTC