Message ID | CAEUhbmXK8RjWpn+JkJnhOYrYzvGm_7Cqz_gaZ65nX8sw9UjYZg@mail.gmail.com |
---|---|
State | Superseded |
Delegated to: | Simon Glass |
Headers | show |
Hi Bin, On 15 September 2015 at 00:12, Bin Meng <bmeng.cn@gmail.com> wrote: > Hi Simon, > > On Wed, Sep 9, 2015 at 12:32 PM, Simon Glass <sjg@chromium.org> wrote: >> Adjust this driver to support driver model. The only users are x86 boards >> so this should be safe. >> >> Signed-off-by: Simon Glass <sjg@chromium.org> >> --- > > After updating QEMU to use the DM i8042 driver below: > > diff --git a/arch/x86/dts/qemu-x86_i440fx.dts b/arch/x86/dts/qemu-x86_i440fx.dts > index fc74cd0..14782b3 100644 > --- a/arch/x86/dts/qemu-x86_i440fx.dts > +++ b/arch/x86/dts/qemu-x86_i440fx.dts > @@ -11,6 +11,7 @@ > /include/ "skeleton.dtsi" > /include/ "serial.dtsi" > /include/ "rtc.dtsi" > +/include/ "keyboard.dtsi" > > / { > model = "QEMU x86 (I440FX)"; > diff --git a/include/configs/qemu-x86.h b/include/configs/qemu-x86.h > index 1b544c1..9daf943 100644 > --- a/include/configs/qemu-x86.h > +++ b/include/configs/qemu-x86.h > @@ -30,7 +30,7 @@ > > #define CONFIG_PCI_PNP > > -#define CONFIG_STD_DEVICES_SETTINGS "stdin=serial,vga\0" \ > +#define CONFIG_STD_DEVICES_SETTINGS "stdin=serial,i8042-kbd\0" \ > "stdout=serial,vga\0" \ > "stderr=serial,vga\0" > > > The i8042 still does not work. I've applied the same changes to Crown > Bay. i8042 does not work either. Could you please have a look? > It's hard for me to debug this on hardware. I should be able to use qemu though. Is there anything special needed to make it use that keyboard? Regards, Simon
Hi Bin, On 18 October 2015 at 17:17, Simon Glass <sjg@chromium.org> wrote: > Hi Bin, > > On 15 September 2015 at 00:12, Bin Meng <bmeng.cn@gmail.com> wrote: >> Hi Simon, >> >> On Wed, Sep 9, 2015 at 12:32 PM, Simon Glass <sjg@chromium.org> wrote: >>> Adjust this driver to support driver model. The only users are x86 boards >>> so this should be safe. >>> >>> Signed-off-by: Simon Glass <sjg@chromium.org> >>> --- >> >> After updating QEMU to use the DM i8042 driver below: >> >> diff --git a/arch/x86/dts/qemu-x86_i440fx.dts b/arch/x86/dts/qemu-x86_i440fx.dts >> index fc74cd0..14782b3 100644 >> --- a/arch/x86/dts/qemu-x86_i440fx.dts >> +++ b/arch/x86/dts/qemu-x86_i440fx.dts >> @@ -11,6 +11,7 @@ >> /include/ "skeleton.dtsi" >> /include/ "serial.dtsi" >> /include/ "rtc.dtsi" >> +/include/ "keyboard.dtsi" >> >> / { >> model = "QEMU x86 (I440FX)"; >> diff --git a/include/configs/qemu-x86.h b/include/configs/qemu-x86.h >> index 1b544c1..9daf943 100644 >> --- a/include/configs/qemu-x86.h >> +++ b/include/configs/qemu-x86.h >> @@ -30,7 +30,7 @@ >> >> #define CONFIG_PCI_PNP >> >> -#define CONFIG_STD_DEVICES_SETTINGS "stdin=serial,vga\0" \ >> +#define CONFIG_STD_DEVICES_SETTINGS "stdin=serial,i8042-kbd\0" \ >> "stdout=serial,vga\0" \ >> "stderr=serial,vga\0" >> >> >> The i8042 still does not work. I've applied the same changes to Crown >> Bay. i8042 does not work either. Could you please have a look? >> > > It's hard for me to debug this on hardware. I should be able to use > qemu though. Is there anything special needed to make it use that > keyboard? Actually it works for me with qemu. However it is intermittent, as it was before my series. So there is something else going on. Regards, Simon
Hi Simon, On Mon, Oct 19, 2015 at 7:17 AM, Simon Glass <sjg@chromium.org> wrote: > Hi Bin, > > On 15 September 2015 at 00:12, Bin Meng <bmeng.cn@gmail.com> wrote: >> Hi Simon, >> >> On Wed, Sep 9, 2015 at 12:32 PM, Simon Glass <sjg@chromium.org> wrote: >>> Adjust this driver to support driver model. The only users are x86 boards >>> so this should be safe. >>> >>> Signed-off-by: Simon Glass <sjg@chromium.org> >>> --- >> >> After updating QEMU to use the DM i8042 driver below: >> >> diff --git a/arch/x86/dts/qemu-x86_i440fx.dts b/arch/x86/dts/qemu-x86_i440fx.dts >> index fc74cd0..14782b3 100644 >> --- a/arch/x86/dts/qemu-x86_i440fx.dts >> +++ b/arch/x86/dts/qemu-x86_i440fx.dts >> @@ -11,6 +11,7 @@ >> /include/ "skeleton.dtsi" >> /include/ "serial.dtsi" >> /include/ "rtc.dtsi" >> +/include/ "keyboard.dtsi" >> >> / { >> model = "QEMU x86 (I440FX)"; >> diff --git a/include/configs/qemu-x86.h b/include/configs/qemu-x86.h >> index 1b544c1..9daf943 100644 >> --- a/include/configs/qemu-x86.h >> +++ b/include/configs/qemu-x86.h >> @@ -30,7 +30,7 @@ >> >> #define CONFIG_PCI_PNP >> >> -#define CONFIG_STD_DEVICES_SETTINGS "stdin=serial,vga\0" \ >> +#define CONFIG_STD_DEVICES_SETTINGS "stdin=serial,i8042-kbd\0" \ >> "stdout=serial,vga\0" \ >> "stderr=serial,vga\0" >> >> >> The i8042 still does not work. I've applied the same changes to Crown >> Bay. i8042 does not work either. Could you please have a look? >> > > It's hard for me to debug this on hardware. I should be able to use > qemu though. Is there anything special needed to make it use that > keyboard? > I will have another try (and debug if it is needed) on Crown Bay when you send the v2 series. Regards, Bin
Hi Bin, On 18 October 2015 at 21:01, Bin Meng <bmeng.cn@gmail.com> wrote: > Hi Simon, > > On Mon, Oct 19, 2015 at 7:17 AM, Simon Glass <sjg@chromium.org> wrote: >> Hi Bin, >> >> On 15 September 2015 at 00:12, Bin Meng <bmeng.cn@gmail.com> wrote: >>> Hi Simon, >>> >>> On Wed, Sep 9, 2015 at 12:32 PM, Simon Glass <sjg@chromium.org> wrote: >>>> Adjust this driver to support driver model. The only users are x86 boards >>>> so this should be safe. >>>> >>>> Signed-off-by: Simon Glass <sjg@chromium.org> >>>> --- >>> >>> After updating QEMU to use the DM i8042 driver below: >>> >>> diff --git a/arch/x86/dts/qemu-x86_i440fx.dts b/arch/x86/dts/qemu-x86_i440fx.dts >>> index fc74cd0..14782b3 100644 >>> --- a/arch/x86/dts/qemu-x86_i440fx.dts >>> +++ b/arch/x86/dts/qemu-x86_i440fx.dts >>> @@ -11,6 +11,7 @@ >>> /include/ "skeleton.dtsi" >>> /include/ "serial.dtsi" >>> /include/ "rtc.dtsi" >>> +/include/ "keyboard.dtsi" >>> >>> / { >>> model = "QEMU x86 (I440FX)"; >>> diff --git a/include/configs/qemu-x86.h b/include/configs/qemu-x86.h >>> index 1b544c1..9daf943 100644 >>> --- a/include/configs/qemu-x86.h >>> +++ b/include/configs/qemu-x86.h >>> @@ -30,7 +30,7 @@ >>> >>> #define CONFIG_PCI_PNP >>> >>> -#define CONFIG_STD_DEVICES_SETTINGS "stdin=serial,vga\0" \ >>> +#define CONFIG_STD_DEVICES_SETTINGS "stdin=serial,i8042-kbd\0" \ >>> "stdout=serial,vga\0" \ >>> "stderr=serial,vga\0" >>> >>> >>> The i8042 still does not work. I've applied the same changes to Crown >>> Bay. i8042 does not work either. Could you please have a look? >>> >> >> It's hard for me to debug this on hardware. I should be able to use >> qemu though. Is there anything special needed to make it use that >> keyboard? >> > > I will have another try (and debug if it is needed) on Crown Bay when > you send the v2 series. Thanks - also note that I have not fixed the hang on caps lock that you reported. Regards, Simon
diff --git a/arch/x86/dts/qemu-x86_i440fx.dts b/arch/x86/dts/qemu-x86_i440fx.dts index fc74cd0..14782b3 100644 --- a/arch/x86/dts/qemu-x86_i440fx.dts +++ b/arch/x86/dts/qemu-x86_i440fx.dts @@ -11,6 +11,7 @@ /include/ "skeleton.dtsi" /include/ "serial.dtsi" /include/ "rtc.dtsi" +/include/ "keyboard.dtsi" / { model = "QEMU x86 (I440FX)"; diff --git a/include/configs/qemu-x86.h b/include/configs/qemu-x86.h index 1b544c1..9daf943 100644 --- a/include/configs/qemu-x86.h +++ b/include/configs/qemu-x86.h @@ -30,7 +30,7 @@ #define CONFIG_PCI_PNP -#define CONFIG_STD_DEVICES_SETTINGS "stdin=serial,vga\0" \ +#define CONFIG_STD_DEVICES_SETTINGS "stdin=serial,i8042-kbd\0" \ "stdout=serial,vga\0" \ "stderr=serial,vga\0"