From: bugs at busybox.net <bugs@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [buildroot 0005914]: add 915resolution and v86d
Date: Mon, 3 Nov 2008 02:55:00 -0800 [thread overview]
Message-ID: <11d345cd304249b93360011d9def0bc8@busybox.net> (raw)
A NOTE has been added to this issue.
======================================================================
http://busybox.net/bugs/view.php?id=5914
======================================================================
Reported By: robang74
Assigned To: buildroot
======================================================================
Project: buildroot
Issue ID: 5914
Category: New Features
Reproducibility: N/A
Severity: feature
Priority: normal
Status: assigned
======================================================================
Date Submitted: 11-01-2008 03:23 PDT
Last Modified: 11-03-2008 02:55 PST
======================================================================
Summary: add 915resolution and v86d
Description:
add 915resolution and v86d for supporting non standard video resolutions
======================================================================
----------------------------------------------------------------------
robang74 - 11-01-08 13:24
----------------------------------------------------------------------
In the resolutions.patch:
s,$(INSTALL),$(INSTALL) -D,
for both the package. Thanks.
----------------------------------------------------------------------
jacmet - 11-02-08 10:39
----------------------------------------------------------------------
Isn't 915resolution only for really old Intel drivers? Shouldn't we bump
the intel driver version instead?
----------------------------------------------------------------------
robang74 - 11-03-08 02:55
----------------------------------------------------------------------
AFAIK 915resolutions is a user space utility which overwrite BIOS
resolutions table in order to activate/use non standard resolutions like
800x480 in X (i.e.: in eeepc). Instead v86d is a user space helper for
uvesafb (a kernel patch) which is useful for use frame buffer at non
standard resolutions like 800x480 (i.e.: in eeepc).
Issue History
Date Modified Username Field Change
======================================================================
11-01-08 03:23 robang74 New Issue
11-01-08 03:23 robang74 Status new => assigned
11-01-08 03:23 robang74 Assigned To => buildroot
11-01-08 03:23 robang74 File Added: resolutions.patch
11-01-08 03:23 robang74 Issue Monitored: robang74
11-01-08 13:24 robang74 Note Added: 0014784
11-01-08 13:24 robang74 Note Edited: 0014784
11-02-08 10:39 jacmet Note Added: 0014884
11-03-08 02:51 robang74 File Added: resolutions.patch2
11-03-08 02:55 robang74 Note Added: 0014914
======================================================================
next reply other threads:[~2008-11-03 10:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-03 10:55 bugs at busybox.net [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-11-14 7:37 [Buildroot] [buildroot 0005914]: add 915resolution and v86d bugs at busybox.net
2008-11-03 11:22 bugs at busybox.net
2008-11-03 11:01 bugs at busybox.net
2008-11-02 18:39 bugs at busybox.net
2008-11-01 20:24 bugs at busybox.net
2008-11-01 10:23 bugs at busybox.net
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=11d345cd304249b93360011d9def0bc8@busybox.net \
--to=bugs@busybox.net \
--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