All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lawrence <lawrencio@hotpop.com>
To: linux-assembly@vger.kernel.org
Subject: Re: Using framebuffer device under Linux
Date: Thu, 20 Nov 2003 09:34:40 +0800	[thread overview]
Message-ID: <3FBC1A30.1050409@hotpop.com> (raw)
In-Reply-To: <20031119220516.DCC11D72E@mluwis17.wiwi.uni-halle.de>

Hi Karsten,

Thank you very much for your invaluable adivce. Your assumption is 
right. I've set the color bit to 24bit so that the program fail. After 
setting it back to 8 bit, the program works elegantly.

Next I'll examine the code carefully in order to grasp the assets in it.

Thanks again for all your help.

Best Regards,
Lawrence

Karsten Scheibler ??:

>Hello Lawrence,
>
>  
>
>>Thanks for your suggestion. here is what I got from strace:
>>
>>execve("./fb", ["./fb"], [/* 18 vars */]) = 0
>>ioctl(0, 0x4b3b, 0x80492e8)             = 0
>>ioctl(0, 0x4b3a, 0x1)                   = 0
>>open("/dev/fb0", O_RDWR)                = 3
>>ioctl(3, 0x4600, 0x804931c)             = 0
>>ioctl(3, 0x4604, 0x80492ec)             = 0
>>ioctl(3, 0x4601, 0x80493bc)             = -1 EINVAL (Invalid argument)
>>ioctl(3, 0x4601, 0x804931c)             = 0
>>ioctl(3, 0x4605, 0x80492ec)             = 0
>>ioctl(0, 0x4b3a, 0)                     = 0
>>_exit(1)                                = ?
>>
>>
>>The system call in question seems on setting screen parameters.  But I 
>>don't know how to deal with this.  Could you please give me some hints?
>>    
>>
>
>The fb example code tries to change the colordepth to 8bpp. That brings me to
>the assumption that you use vesafb with another colordepth. vesafb is unable
>to change colordepth after boot. All "real" fb drivers allow that, vesafb
>not, due to BIOS calling limitations after boot. You should
>change your vga= line which is passed to the kernel, to a mode with 8bpp.
>
>If 
>
>cat /proc/fb
>
>outputs something like
>
>0 VESA
>
>then my assumption is right. Otherwise i would be interested in additional
>information about your system (kernelversion etc.).
>
>You may try to execute
>
>fbset
>
>to see your current fb parameters
>
>
>
>karsten
>-
>To unsubscribe from this list: send the line "unsubscribe linux-assembly" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
>  
>



  reply	other threads:[~2003-11-20  1:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-19  1:28 Using framebuffer device under Linux Lawrence
2003-11-19 22:03 ` Karsten Scheibler
2003-11-20  1:34   ` Lawrence [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-11-18 12:41 Lawrence
2003-11-18 13:11 ` Frederic Marmond
2003-11-18 14:00   ` Lawrence
2003-11-18 21:01     ` Karsten Scheibler

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=3FBC1A30.1050409@hotpop.com \
    --to=lawrencio@hotpop.com \
    --cc=linux-assembly@vger.kernel.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.