On Tuesday 07 June 2011 03:08 pm, Andriy Gapon wrote: > on 07/06/2011 21:02 John Baldwin said the following: > > On Tuesday, June 07, 2011 11:39:26 am Jung-uk Kim wrote: > >> On Tuesday 07 June 2011 09:52 am, John Baldwin wrote: > >> The whole point of this commit is to blacklist *recent* BIOS (or > >> CSM) from probing keyboard typematic information, more > >> specifically, recent Intel chipset platforms. They don't > >> support many INT 15h/16h functions but only cause trouble at > >> best. OTOH, I haven't seen such problems with AMD chipset > >> systems and they all seem to have traditional entry points at > >> the interrupt vector table, for example. > > > > Err, but you didn't blacklist recent BIOS. You blacklist _all_ > > BIOS that use entry points other than the ones from the UEFI > > spec, including BIOSes that don't claim to support UEFI and the > > BIOS from the two systems I quoted. > > I'd like to simply add two datapoints: > 1) recent AMD system: > > $ dd if=/dev/mem bs=4 iseek=0x15 count=2 | hd > 00000000 59 f8 00 f0 2e e8 00 f0
Yes, that's exactly what I am seeing from all of my AMD systems and a 11-year old Pentium III system. > 2) very old PIIX/440BX system (manufactured ~1999): > $ dd if=/dev/mem bs=4 iseek=0x15 count=2 | hd > 00000000 9a 06 b8 9c 2e e8 00 f0 INT 15h is relocated under 0xa0000, i.e., "highmem". Are you using non-FreeBSD chain loader? Do you have "relocate to highmem" option in the BIOS configuration? Most importantly, does it support keyboard typematic feature? Jung-uk Kim _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/svn-src-head To unsubscribe, send any mail to "[email protected]"
