All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Luiz Capitulino <lcapitulino@redhat.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1/2] fbdev: add linux framebuffer display driver.
Date: Thu, 27 Jun 2013 11:58:57 +0200	[thread overview]
Message-ID: <51CC0CE1.9030008@redhat.com> (raw)
In-Reply-To: <20130626114834.08d81459@redhat.com>

  Hi,

>> +    /* open framebuffer */
>> +    if (device == NULL) {
>> +        device = getenv("FRAMEBUFFER");
>> +    }
>> +    if (device == NULL) {
>> +        device = "/dev/fb0";
>> +    }
> 
> Maybe this is a matter of taste, but I think that having this logic at
> this layer makes the API harder to use. What about moving this to the
> call in vl.c and making the device name required in QMP?

I'll just drop the getenv.  That will make "/dev/fb0" the default value
no matter what.  Ok?

>> +    s->fb = open(device, O_RDWR);
>> +    if (s->fb == -1) {
>> +        error_setg(err, "open %s: %s\n", device, strerror(errno));
> 
> We have error_setg_errno() :)

Also error_setg_file_open() ;)

cheers,
  Gerd

  reply	other threads:[~2013-06-27  9:59 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-26 11:38 [Qemu-devel] [PATCH 1/2] fbdev: add linux framebuffer display driver Gerd Hoffmann
2013-06-26 11:38 ` [Qemu-devel] [PATCH 2/2] fbdev: add monitor commands to enable/disable/query Gerd Hoffmann
2013-06-26 15:56   ` Luiz Capitulino
2013-06-27 10:05     ` Gerd Hoffmann
2013-06-27 13:29       ` Luiz Capitulino
2013-06-27 22:03         ` Eric Blake
2013-06-28 14:26           ` Luiz Capitulino
2013-06-27 21:55     ` Eric Blake
2013-06-26 15:48 ` [Qemu-devel] [PATCH 1/2] fbdev: add linux framebuffer display driver Luiz Capitulino
2013-06-27  9:58   ` Gerd Hoffmann [this message]
2013-06-27 13:23     ` Luiz Capitulino
  -- strict thread matches above, loose matches on Subject: below --
2013-06-06 15:37 Gerd Hoffmann
2013-06-06 19:33 ` Anthony Liguori
2013-06-11  6:12   ` Gerd Hoffmann
2013-06-12  8:34     ` Gerd Hoffmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=51CC0CE1.9030008@redhat.com \
    --to=kraxel@redhat.com \
    --cc=aliguori@us.ibm.com \
    --cc=lcapitulino@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.