> Hi, I have been mia for a few days, sorry about that.
No problem.
> > Coleman: Do you know, how you can get at "raw" input from the BSD
> > console ?
> Yeah, we have a device called /dev/kbd, that can handle input from an
> AT, PS/2, or USB keyboard (whatever is used by the console). You can
> use the ioctl K_RAW to get this information, untranslated keyboard scan
> codes.
Ah - good. Is it possible to get at the in-kernel translation tables to
take care for the internationalization (for generating symbol and label) ?
> This will also get you those extra MS keys they put on all the
> new keyboards to make the spacebar small.
hehe ... there are nice replacement caps out there with penguins on them.
Maybe there are as well versions with the little daemon ?
> > Sorry, I don't either, as it seems like I can't get it to work - I got
> > to run some diagnostics on my card to make sure it has the required
> > VESA version in BIOS ...
> We use VM86 for our VESA support. I believe there are a few PM VESA
> calls that we use as well. I think that you need VBE 1.2+ to have it
> recognized in freebsd.
I'll check that. IIRC my card is only VESA 1.0 until I load a driver under
Win, but that doesn't help of course.
> > If glide is available for BSD, yes, it should work with maybe some
> > tweaking.
> I have been trying to get glide for BSD. Do you have any info on where I
> may be able to get it? The mailing lists turned up broken links.
I'll ask on the GGI mailing list. Anyone knows where to find a working Glide
for FreeBSD ?
> > Coleman: What kind of graphics card do you have ? If it's supported by
> > KGI, that would help when trying to port that part over as well ...
> I have a Matrox G200 and a Matrox Mystique 220. Dual-Head X.
O.K. - AFAIK the Matrox cards are supported by the kgicon layer.
That will help porting the native drivers over.
CU, ANdy
--
= Andreas Beck | Email : <[EMAIL PROTECTED]> =
