On Wed, Dec 07, 2022 at 09:14:39AM -0500, James Bottomley wrote:
> On Wed, 2022-12-07 at 15:09 +0100, Ard Biesheuvel wrote:
> > So at some point, these drivers will be removed rather than kept
> > alive by the core team unless someone steps up.
>
> How important is keeping them alive?
Most common
Hi,
> A patch mentioned above set MPT_SCSI_ENABLE=FALSE, that removed
> support for LSI 53C1030 and SAS1068.
> These SCSI controllers were emulated by VMware, Parallels and I guess
> VitualBox.
> This is generic setup for VMware VMs, as far as I remember.
> So the booting of such VMs (probably
On Mon, Dec 05, 2022 at 04:36:15PM -0700, dann frazier wrote:
> On Tue, Jul 26, 2022 at 12:46:39PM -0700, Michael D Kinney wrote:
> > The email addresses for the reviewers of the MptScsi and
> > PvScsi are no longer valid. Disable the MptScsi and PvScsi
> > drivers in all DSC files until new maint
Hi,
> I have similar problems as the original reporter, specifically, after
> upgrading to qemu 3.1 from stretch [from qemu 2.8 -- mjt], mouse pointer
> is invisible in guest systems iff the pointer is grabbed,
> with -display gtk and qxl is used.
> When using -vga std, both linux and windows g
Hi,
> > That is, when I run either a standard ubuntu 17.10 or windows 10 (with
> > qxl-dod driver), then by default they switch off the screen after a while,
> > which results in black screen in qemu, as expected.
Just the screen saver I guess.
> > If I let the systems idle for longer (say, ha
Hi,
> With this patch, the gtk and sdl UIs are working fine.
Good.
> Under the vnc UI,
> a lot of keys don't work, unless the option -k is used. According to the
> manpage, this options is needed for the vnc UI:
>
> -k language
> Use keyboard layout language (for example "fr" fo
This patch adds the two extra brazilian keys to the evdev keymap for
X11. This patch gets the two keys going with the vnc, gtk and sdl1
UIs.
The SDL2 library complains it doesn't know these keys, so the SDL2
library must be fixed before we can update ui/sdl2-keymap.h
Signed-off-by:
ommand.
Signed-off-by: Gerd Hoffmann
---
qapi-schema.json | 4 +++-
ui/input-keymap.c | 4
2 files changed, 7 insertions(+), 1 deletion(-)
diff --git a/qapi-schema.json b/qapi-schema.json
index f97ffa1..25df463 100644
--- a/qapi-schema.json
+++ b/qapi-schema.json
@@ -2784,6 +2784,7 @@
#
Hi,
> For EVDEV_KPCOMMA it maps to XT KBD code 126 (0x7e in decimal) which
> does not match your patch. I'm not sure where I got that mapping
> from originally - probably from the Linux kernel's XT <-> evdev
> keymapping tables.
Did some more testing, 0x7e seems to be the correct one. Everyth
Hi,
> For EVDEV_KPCOMMA it maps to XT KBD code 126 (0x7e in decimal) which
> does not match your patch. I'm not sure where I got that mapping
> from originally - probably from the Linux kernel's XT <-> evdev
> keymapping tables.
>
> So presumably you were finding the KPCOMMA one was broken in
On Mi, 2015-05-27 at 13:19 +0200, Markus Armbruster wrote:
> Gerd Hoffmann writes:
>
> > This patch adds the two extra brazilian keys to the evdev keymap for
> > X11. This patch gets the two keys going with the gtk and sdl1 UIs.
> >
> > With vnc (remote-vie
On Mi, 2015-05-27 at 06:27 -0300, Joao Luis Meloni Assirati wrote:
> On 26-05-2015 10:58, Gerd Hoffmann wrote:
> > This patch adds the two extra brazilian keys to the evdev keymap for
> > X11. This patch gets the two keys going with the gtk and sdl1 UIs.
> >
> > With v
On Di, 2015-05-26 at 18:24 -0300, Joao Luis Meloni Assirati wrote:
> Hello,
>
> > I've tested an unpatched QEMU 2.3.0 (x86_64) with "-k pt_br" option and
> > the
> > "/?°" key works perfectly.
>
> From the manpage of qemu:
>
> -k language
>Use keyboard layout language (for example "fr" for
Hi,
> >> 12:44:04.253486: EV_MSC MSC_SCAN 458885 <== Here, . in the numpad was
> >> pressed
> >> 12:44:04.253486: EV_KEY KEY_KPCOMMA (0x79) pressed
> >
> > Ok. Is there a key with ',' too in your numpad?
>
> Yes, there is a separated ',' in the numpad, and when I press it I get
>
> 17:48:47.8
> static const uint8_t evdev_keycode_to_pc_keycode[61] = {
> -0, /* 97 EVDEV - RO ("Internet" Keyboards) */
> +0x73, /* 97 EVDEV - /? (ABNT2 Keyboards) */
That one looks good.
> -0, /* 129 EVDEV - I129 ("Internet" Keyboards) */
> +0x34, /* 129 abnt2
doesn't know these keys, so the SDL2
library must be fixed before we can update ui/sdl2-keymap.h
Signed-off-by: Gerd Hoffmann
---
ui/x_keymap.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/ui/x_keymap.c b/ui/x_keymap.c
index b9b0944..4e899b4 100644
--- a/ui/x_key
ommand.
Signed-off-by: Gerd Hoffmann
---
qapi-schema.json | 4 +++-
ui/input-keymap.c | 4
2 files changed, 7 insertions(+), 1 deletion(-)
diff --git a/qapi-schema.json b/qapi-schema.json
index f97ffa1..25df463 100644
--- a/qapi-schema.json
+++ b/qapi-schema.json
@@ -2784,6 +2784,7 @@
#
Hi,
> 12:44:02.389552: EV_MSC MSC_SCAN 458887 <== Here, / was pressed
> 12:44:02.389552: EV_KEY KEY_RO (0x59) pressed
'RO'. Hmm, not very descriptive. Any idea what this could stand for?
> 12:44:04.253486: EV_MSC MSC_SCAN 458885 <== Here, . in the numpad was pressed
> 12:44:04.253486: EV_KEY
Hi,
> > Anyone having such a keyboard and willing to run some tests?
>
> Adding Cc's. This has been reported to debian too,
> http://bugs.debian.org/772422 (also in Cc).
Ok, so just replying should stick this into the debian bug tracker,
right?
Ok, instructions are here:
(a) Go grab https:/
On Di, 2014-10-28 at 23:58 +0100, Stéphane Aulery wrote:
> In automatic mode, does not change the picture if it is already well oriented,
> unless other options are used together, especially -c and -g.
How about attached patch instead?
cheers,
Gerd
diff --git a/jpegtools.c b/jpegtools.c
index
On So, 2014-11-02 at 00:41 +0100, Stéphane Aulery wrote:
> Hello Gerd,
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=429141
>
> I asked the opinion of Moritz on this bug. I'm not convinced that this
> work worthwhile. What do you say please?
Checking each and every malloc is pretty poin
Hi,
> P4 is displayed with pgm parser and its colors are reversed.
fixed.
> P6 is displayed with libwebpm parser (OK) or ppm parser (KO).
Don't see this.
> I commented initialization parsers pbm / pgm / pnm in rd/read-ppm.c and then
> fbi systematically uses libjpeg without problem.
Sure?
On Do, 2014-10-23 at 16:19 +0200, Stéphane Aulery wrote:
> forwarded 645838 g...@kraxel.org
> stop
>
>
>
> Hello Gerd,
>
> Fabien C. proposed the previous patch I have sent to you with this comment :
>
> > Exiftran exi
On Di, 2014-08-26 at 09:55 +0400, Michael Tokarev wrote:
> 26.08.2014 09:40, Gerd Hoffmann wrote:
> > There should be a delay after every character. It can be pretty small.
> > 10ms should be enough (you should set TCP_NODELAY though to make sure
> > the key events are not bu
On Mo, 2014-08-25 at 21:11 -0700, Marc wrote:
> Hi,
>
>
> On August 25, 2014 at 3:40:01 AM, Gabriele Giacone
> (1o5g4...@gmail.com) wrote:
> >
> > > IMO vncdotool should be fixed to add small delays between
> > keyboard
> > > events, as if a real person is typing, instead of sending the key
> >
On Sa, 2014-08-23 at 12:56 +0400, Michael Tokarev wrote:
> There's a bug filed against debian qemu package, there:
>
> http://bugs.debian.org/758881
>
> which says about problems sending keypress events over VNC to
> a qemu guest, -- some keypresses gets lost, at least.
> So it looks like somet
http://www.kraxel.org/blog/2011/07/input-1-0-released/
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Hi,
If you don't want package celt 0.5.1 -- fine. You can patch your
spice server and client to just not signal the celt capability, and
they will interoperate just fine with everybody else using raw
uncompressed audio. But IMHO it would be stupid to not support
audio compression in your spi
On 11/17/10 13:04, Ron wrote:
Hi Hans,
Hans de Goede writes:
The if at all part depends on if it will be doable without too much
pain to support both celt-0.5.1 and celt "1.0" in the same binary.
Should work without major trouble, the symbols exported by the shared
library have a versioned
Moritz Muehlenhoff wrote:
> Since fbi is not suitable for non-interactive use and the filename would
> need to contain the commands to be executed I don't consider this a
> security problem. Still, it should be fixed.
>
It is at least quite hard to exploit remotely. Even when configuring
fbi as
30 matches
Mail list logo
