From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] frame buffer problems
Date: Fri, 6 Apr 2007 18:39:50 +0200 [thread overview]
Message-ID: <20070406163950.GA6131@aon.at> (raw)
In-Reply-To: <2034.63.193.249.101.1175876073.squirrel@webmail.aerende.com>
On Fri, Apr 06, 2007 at 09:14:33AM -0700, nina.holly at aerende.com wrote:
>Hi,
> I am using Linux 2.6.10 with devfs on ARM. I know that
>devfs is deprecated/obsolete. The framebuffer works fine
>with buildroot svn version 15763. But when I switched to
>buildroot version 17224 I get a return value < 0 when I try to execute
>
>ioctl(frame_buffer_ptr, FBIOGET_VSCREENINFO, &var_info);
>
>I.E. I can't read the basic frame buffer information.
>
>1. Is this a problem in the version of buildroot that I am using?
>
>2. Is this because buildroot version 17224 doesn't work
> with devfs and I need to switch to using udev?
>
>3. Do I need to use Linux version greater than 2.6.15 (which works
> with udev) to work with buildroot version 17224?
I'm using 2.6.20.4 with binutils-2.17.50.0.14 and gcc-4.2. I have
BR2_PACKAGE_BUSYBOX_CONFIG="busybox.config"
BR2_PACKAGE_BUSYBOX_HIDE_OTHERS=y
BR2_PACKAGE_BUSYBOX_SKELETON=y
and use mdev (from buysbox trunk) to create my device nodes, dunno
about udev and don't want to know about devfs anymore ;)
I do use sysfs and configfs, though, the former is required for mdev to
work.
Works fine for me, fwiw.
next prev parent reply other threads:[~2007-04-06 16:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-06 16:14 [Buildroot] frame buffer problems nina.holly at aerende.com
2007-04-06 16:39 ` Bernhard Fischer [this message]
2007-04-06 17:05 ` Luis R. Rodriguez
2007-04-07 13:31 ` nina.holly at aerende.com
2007-04-10 7:00 ` Peter Korsgaard
2007-04-12 15:00 ` nina.holly at aerende.com
2007-04-12 15:08 ` Peter Korsgaard
2007-04-13 14:45 ` nina.holly at aerende.com
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=20070406163950.GA6131@aon.at \
--to=rep.dot.nop@gmail.com \
--cc=buildroot@busybox.net \
/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