From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] read-edid package - clarifications
Date: Thu, 3 May 2012 14:23:35 +0200 [thread overview]
Message-ID: <20120503142335.461f63c1@skate> (raw)
In-Reply-To: <CADiAo4K90x6ZANyvQk7SYP=o=YmimOHDn+wfHLSrwE7bumcLKA@mail.gmail.com>
Le Thu, 3 May 2012 06:32:35 -0400,
Dimitry Golubovsky <golubovsky@gmail.com> a ?crit :
> > non-essential binaries should probably live in usr/bin/ rather than
> > bin/.
>
> I think such program may be needed rather early in the boot process.
> Basically it is needed when setting up the framebuffer console
> resolution. I have a real case of Via Unichrome and a Dell widescreen
> monitor where the framebuffer driver is unable to sense the monitor
> (X.org driver does fine though), so the only way for me to initialize
> the console was to run read-edid even before I am attempting to load
> the framebuffer drivers and fbcon. That's why I placed it into /bin
> (or maybe it is even better in /sbin).
On Ubuntu, parse-edid is in usr/bin, get-edid is in usr/sbin. See
http://packages.ubuntu.com/quantal/i386/read-edid/filelist. I don't
feel strongly about this, if you prefer to keep them in bin/, it's
fine. On embedded systems, /usr is most likely on the same partition
as /, so it doesn't make much difference.
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-05-03 12:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-03 10:32 [Buildroot] read-edid package - clarifications Dimitry Golubovsky
2012-05-03 12:23 ` Thomas Petazzoni [this message]
2012-05-03 12:49 ` Baruch Siach
-- strict thread matches above, loose matches on Subject: below --
2012-05-03 13:27 Dimitry Golubovsky
2012-05-03 18:22 ` Baruch Siach
2012-05-03 18:43 ` Dimitry Golubovsky
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=20120503142335.461f63c1@skate \
--to=thomas.petazzoni@free-electrons.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