QEMU Keyboard problems in v2

[Myles Watson]

Does anyone know why the keyboard isn't working in v2 for qemu?

I'll try to track it down, but I was hoping someone knew already.

If you use tint, filo, or adlo as a payload (probably others as well), the
key mappings are wrong.

Thanks,
Myles

[Jordan Crouse]

On 29/04/08 13:05 -0600, Myles Watson wrote:
> Does anyone know why the keyboard isn't working in v2 for qemu?
>
> I'll try to track it down, but I was hoping someone knew already.

Yeah, it has to do with the scancode set - we're all assuming set 1,
but FILO uses set 2 by default.

r2370 of libpayload should have fixed that - at least it works with 0.91 
here.

Jordan

[Myles Watson]

> -----Original Message-----
> From: Jordan Crouse [mailto:[e-mail]]
> Sent: Tuesday, April 29, 2008 2:01 PM
> To: Myles Watson
> Cc: [e-mail]
> Subject: Re: QEMU Keyboard problems in v2
>
> On 29/04/08 13:05 -0600, Myles Watson wrote:
> > Does anyone know why the keyboard isn't working in v2 for qemu?
> >
> > I'll try to track it down, but I was hoping someone knew already.
>
> Yeah, it has to do with the scancode set - we're all assuming set 1,
> but FILO uses set 2 by default.
>
> r2370 of libpayload should have fixed that - at least it works with 0.91
> here.

With v2?  I can't get it to work with 0.90 or 0.91 with etherboot, coreinfo,
tint, filo, or adlo, even though the same payloads work fine with v3.

Thanks,
Myles

[Jordan Crouse]

On 29/04/08 14:36 -0600, Myles Watson wrote:
> > -----Original Message-----
> > From: Jordan Crouse [mailto:[e-mail]]
> > Sent: Tuesday, April 29, 2008 2:01 PM
> > To: Myles Watson
> > Cc: [e-mail]
> > Subject: Re: QEMU Keyboard problems in v2
> >
> > On 29/04/08 13:05 -0600, Myles Watson wrote:
> > > Does anyone know why the keyboard isn't working in v2 for qemu?
> > >
> > > I'll try to track it down, but I was hoping someone knew already.
> >
> > Yeah, it has to do with the scancode set - we're all assuming set 1,
> > but FILO uses set 2 by default.
> >
> > r2370 of libpayload should have fixed that - at least it works with 0.91
> > here.
>
> With v2?  I can't get it to work with 0.90 or 0.91 with etherboot, coreinfo,
> tint, filo, or adlo, even though the same payloads work fine with v3.

Oops - I mean r3270 above.  Thats newer then the revision in buildrom.
I just tried r3270, and its working for coreinfo at least.

Jordan

[Myles Watson]

> > > Yeah, it has to do with the scancode set - we're all assuming set 1,
> > > but FILO uses set 2 by default.
> > >
> > > r2370 of libpayload should have fixed that - at least it works with
>
> 0.91
> > > here.
> >
> > With v2?  I can't get it to work with 0.90 or 0.91 with etherboot,
>
> coreinfo,
> > tint, filo, or adlo, even though the same payloads work fine with v3.
>
> Oops - I mean r3270 above.  Thats newer then the revision in buildrom.
> I just tried r3270, and its working for coreinfo at least.

Could you send me the working image?  I'd like to see what's different in
the serial output.  I've been using 3276, but I tried 3270 to see if that
was my problem.  All the payloads boot, but the keyboard doesn't function
correctly.

Thanks,
Myles