From: Frederic Marmond <fmarmond@eprocess.fr>
To: Lawrence <lawrencio@hotpop.com>
Cc: linux-assembly@vger.kernel.org
Subject: Re: Using framebuffer device under Linux
Date: Tue, 18 Nov 2003 14:11:26 +0100 [thread overview]
Message-ID: <3FBA1A7E.6010405@eprocess.fr> (raw)
In-Reply-To: <3FBA137E.7000108@hotpop.com>
(re)Hi Lawrence! ;)
I don't know about the FB managment in linuxassembly, but here is some
points you can have a look regarding FB:
- kernel may have support for FB already compiled in (see the kernel
.config, and check that FB_ options are correctly setted)
- if kernel has the FB support, have a look at the kernel parameters
(append="video=something" in your lilo.conf)
- you can also have a look at /var/log/messages
- to see if FB is already working, have a look at the '/proc' (mount
/proc;cat /proc/fb)
- to access FB, open/write to /dev/fb0
- to use kernel driver fb routines, use ioctl to /dev/fb0
- read documentation about the driver in /usr/src/linux/Documentation
(if the kernel sources are installed, and if the kernel you run was
compiled there)
- you can use the VESA driver (less optimised than a specific FB driver,
but often work). Use the "vga=mode" parameter in your lilo to activate it.
To access the frame buffer as a large memory, you must use *mmap* in C.
I don't know how it may be called in assembly under Linux, but this may
be a start for you.
mmap will be used to map the device /dev/fb0 into memory. So, you may
access the FB with assembly mov, very easily, as a 'standard' memory region.
Regards,
Fred
Lawrence wrote:
>Hi All,
>
>I am planning to do graphic with asm under Linux without X11. I am try
>to use framebuffer as the "drawing plane".
>
>I've reached the article entitled "Using the framebuffer device under
>Linux" within http://linuxassembly.org and I've extracted and compiled
>fb.n according to the instruction. However, when I run "fb" under the
>console in RH9, I only got a refresh and then back to the text console.
>
>I've tried fb under the installation environment of Debian 3.0, with I
>thought it is already in framebuffer mode, but still got a failure.
>
>
>I've tried ald fb, but when it is going to switch to framebuffer mode,
>Linux squeeze and I have to telnet into my linux box using another
>machine and issue a reboot...
>
>I can successfully run "leaves" under a-linux however, but I don't know
>how to put fb under a-linux so as to see if it works, as there seems no
>way to mount a floppy or access ethernet under a-linux.
>
>Would anyone be so kind as to tell me how could I access linux
>framebuffer correcely using assembly, or point me out the forgettable
>steps in order to run 'fb' successfully?
>
>my 'nasm -r' command spit out:
>
>NASM version 0.98.22 compiled on Sep 19 2003
>
>Thanks
>Lawrence
>
>
>-
>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
>
>
>
next prev parent reply other threads:[~2003-11-18 13:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-18 12:41 Using framebuffer device under Linux Lawrence
2003-11-18 13:11 ` Frederic Marmond [this message]
2003-11-18 14:00 ` Lawrence
2003-11-18 21:01 ` Karsten Scheibler
-- strict thread matches above, loose matches on Subject: below --
2003-11-19 1:28 Lawrence
2003-11-19 22:03 ` Karsten Scheibler
2003-11-20 1:34 ` Lawrence
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=3FBA1A7E.6010405@eprocess.fr \
--to=fmarmond@eprocess.fr \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).