Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
* [Buildroot]  read-edid package - clarifications
@ 2012-05-03 13:27 Dimitry Golubovsky
  2012-05-03 18:22 ` Baruch Siach
  0 siblings, 1 reply; 6+ messages in thread
From: Dimitry Golubovsky @ 2012-05-03 13:27 UTC (permalink / raw)
  To: buildroot

Hi,

Thomas Petazzoni wrote:

> On Ubuntu, parse-edid is in usr/bin, get-edid is in usr/sbin. See
> http://packages.ubuntu.com/quantal/i386/read-edid/filelist

There is another package in my queue for submission which is v86d, and
this program is about to be used at about the same stage of boot as
get-edid. Ubuntu has it in /sbin per
http://packages.ubuntu.com/quantal/i386/v86d/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.

OK, perhaps I'll place all three (get-edid, parse-edid, v86d) in /sbin.

Baruch Siach wrote:

> read-edid seems to work perfectly on my x86_64 laptop. So keeping BR2_x86_64
> should be safe.

OK, if you tried what I submitted then I'll add x86_64 (I just do not
have a hardware to test it such way).

> As for PowerPC, I guess the low level code is selected at build time according
> to the target platform. I haven't looked at the code, though.

Well, this one uses real-mode BIOS call to VBE ROM via lrmi
(http://lrmi.sf.net - not sure if it supports powerpc). There is
another version of monitor info dump program in existence which uses
i2c which may work on something other than PC. Not the one I am
submitting.

Thanks.

-- 
Dimitry Golubovsky

Anywhere on the Web

^ permalink raw reply	[flat|nested] 6+ messages in thread
* [Buildroot] read-edid package - clarifications
@ 2012-05-03 10:32 Dimitry Golubovsky
  2012-05-03 12:23 ` Thomas Petazzoni
  2012-05-03 12:49 ` Baruch Siach
  0 siblings, 2 replies; 6+ messages in thread
From: Dimitry Golubovsky @ 2012-05-03 10:32 UTC (permalink / raw)
  To: buildroot

Hi,

Thanks to Baruch and Thomas for the comments. I'll try to implement them.

Few thoughts though:

Thomas' comment:

> 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).

Baruch's comment:

> read-edid can only run on x86 PCs and PowerPC Macs, so it should depend on
> (BR2_i386 || BR2_x86_64 || BR2_powerpc).

I only tested it on i386, not sure about x86-64, and definitely not on
powerpc as it has x86 real-mode stuff in it. So perhaps I'll keep i386
only.

Thanks.

-- 
Dimitry Golubovsky

Anywhere on the Web

^ permalink raw reply	[flat|nested] 6+ messages in thread
end of thread, other threads:[~2012-05-03 18:43 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-05-03 13:27 [Buildroot] read-edid package - clarifications Dimitry Golubovsky
2012-05-03 18:22 ` Baruch Siach
2012-05-03 18:43   ` Dimitry Golubovsky
  -- strict thread matches above, loose matches on Subject: below --
2012-05-03 10:32 Dimitry Golubovsky
2012-05-03 12:23 ` Thomas Petazzoni
2012-05-03 12:49 ` Baruch Siach

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox